WorkJournal

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

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when implementing any feature or bugfix, before writing implementation code

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Use when the weekly scheduled run asks for this repository's weekly plan. Reads the past week's merged pull requests and the open issues, then posts one short plan comment on the pinned "Weekly plan" issue.

Use when the work-journal app asks to roll up a week of daily journal entries into themes, time trends, outcomes, and a draft status update.

Use when the work-journal app asks to roll up a week of daily journal entries into themes, time trends, outcomes, and a draft status update.