Use when implementing any task end-to-end without user intervention - ensures continuous forward progress by always having a next tool call until the task is fully complete
Use when a task should be parallelized across multiple agents — decomposes work into Linear issues, then drains the queue by spawning worktree agents for unblocked tickets using drive-to-completion
Use when creating git commits - ensures messages follow Conventional Commits, explain motivation over implementation, and help future maintainers
Use when creating a Linear issue from a feature, bug, or task description — gathers required fields then calls the Linear MCP tool directly
Use to critically review a plan before approval - invokes a senior engineering review for readability, maintainability, operability, and testability
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
Use when creating or improving agent skills - ensures efficient context usage, clear activation conditions, and proper structure for different skill types