WorkJournal

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Use when the work-journal app asks to assign a category and confidence to each activity segment of an hour.

Use when the work-journal app asks to assign a category and confidence to each activity segment of an hour.

Use when the work-journal app asks to write the end-of-day journal entry from the day's hour summaries, meetings, and category totals.

Use when the work-journal app asks to write the end-of-day journal entry from the day's hour summaries, meetings, and category totals.

Use when the user asks for a commit message or wants help summarizing staged changes, e.g. "write a commit" or "git commit message". Reads the staged diff, picks the Conventional Commits type (feat, fix, refactor, docs, test, perf, chore), and writes an imperative subject of at most 72 characters, adding a body only for breaking changes, migrations or security fixes.

Use when the user asks for a commit message or wants help summarizing staged changes. Generates a Conventional Commits–formatted message from a diff.

Use when the user asks for a commit message or wants help summarizing staged changes, e.g. "write a commit" or "git commit message". Reads the staged diff, picks the Conventional Commits type (feat, fix, refactor, docs, test, perf, chore), and writes an imperative subject of at most 72 characters, adding a body only for breaking changes, migrations or security fixes.

Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

Use when the work-journal app asks which transcript utterances of an hour are bystander or personal non-work conversations to remove, and which spoken identifiers to redact.

Use when the work-journal app asks which transcript utterances of an hour are bystander or personal non-work conversations to remove, and which spoken identifiers to redact.

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when executing implementation plans with independent tasks in the current session

Use when the work-journal app asks to summarize one hour of recorded activity into a narrative, a timeline, detailed notes, a main focus, and action items.

Use when the work-journal app asks to summarize one hour of recorded activity into a narrative, a timeline, detailed notes, a main focus, and action items.

Use when the work-journal app asks to summarize a recorded meeting transcript into participants, summary, decisions, and action items.