Lightweight pipeline for single, bounded implementation tasks — use this for any small change that doesn't need a full feature or bug workflow. Trigger whenever a user asks to: add a flag or option to an existing function or script, extract duplicated code into a constant or helper, rename a method or variable, make a hardcoded value configurable via an env var or parameter, add input validation to a specific function, or implement any other isolated change touching 1-3 files. Also trigger for phrases like 'small change', 'quick task', 'single task', 'one-off', or 'quick fix'followed by an implementation request. Do NOT trigger for bugs with unclear root cause (use diagnose), multi-file features (use grill-me → to-prd → to-tickets), architecture questions, PR reviews, or diagnostics.
Use to drain a local .workflow/kanban/ board of vertical-slice tickets. Picks eligible tickets (deps satisfied), dispatches a fresh specialist subagent per ticket running TDD, moves files between columns. Triggers: "drain the board", "run kanban", "/kanban-loop", or after to-tickets fills backlog/.
Break a plan, spec, or PRD into local kanban tickets written to .workflow/kanban/backlog/NN-slug.md using tracer-bullet vertical slices. No issue-tracker API required. Use when user wants to convert a PRD or spec into kanban tickets.
Rewrite AI-generated text so it reads human. Triggers: "humanize", "de-AI", "sounds like ChatGPT/Claude", "too many em dashes", "make this sound natural/less robotic", or user pastes AI-flavored prose to clean up.
Structured end-of-session summary for context handoff. Triggers: "session handoff", "wrap up session", "hand off", "handoff summary", or user about to /clear.
Write a single structured bug ticket to .workflow/kanban/backlog/ after running /diagnose. Use when diagnose has completed and you have a root cause, repro, and fix approach. Triggers: "to-bug-ticket", "/to-bug-ticket", "write bug ticket", "create bug ticket".
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.