Use when a user needs architecture or product-design sparring on system design, runtime boundaries, config, deployment, operations, or implementation plans; ask one focused question at a time.
Use when ready to ship confirmed local changes through a draft PR: check dirty-worktree scope, create a branch, stage only intended paths, commit, push, open a PR, wait for CI, and fix red checks.
Use when creating or updating current-state project context documentation under docs/context/.
Use when reviewing local code changes before a PR: review my changes/code, check my work, security review, review before push; rank bugs, security, perf, and production risks.
Triage CodeRabbitAI review comments on current PR, fix legitimate issues, push, resolve threads
Create a committed Markdown todo in ~/.create-todo from a todo, task, follow-up, $create-todo request, or current conversation context.
Use when creating concise Markdown docs-as-code for critical user journeys, flows, acceptance scenarios, service blueprints, telemetry, portfolios, story maps, and coverage matrices.
Commit all changes, push, wait for CI, fix if red, iterate until green