bugmagnet
Lightweight bug discovery and test coverage analysis for a code module. Use when the user asks to find bugs, analyze test coverage, write edge case tests, or do exploratory testing on a file. Triggers on "bugmagnet", "find bugs in", "test coverage gaps", "edge cases for", or "exploratory testing on <file>".
create-plan
Create detailed implementation plans through interactive research and iteration
grill-me
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".
hamburger-method
Slices features into vertical deliverable pieces using the Hamburger Method. Generates 4-5 implementation options per layer and composes minimal end-to-end slices. Use when slicing work, breaking down features into layers, or delivering incrementally.
implement-plan
Implement technical plans from thoughts/shared/plans with verification
iterate-plan
Iterate on existing implementation plans with thorough research and updates
research-codebase
Document codebase as-is with thoughts directory for historical context
small-safe-steps
Small Safe Steps (S3): breaks work into 1-3h increments with zero downtime. Use when asking "how do I implement/migrate/refactor", "what steps to do X", "plan safe migration", or handling risky DB/API changes. Applies expand-contract pattern for migrations, refactorings, schema changes.
story-splitting
Detects stories that are too big and applies splitting heuristics. Identifies linguistic red flags (and, or, manage, handle, including) and suggests concrete splitting strategies. Use when breaking down requirements or splitting large work.
tdd
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.
test-desiderata
Analyze and improve test code quality using Kent Beck's Test Desiderata framework. Use when analyzing test files, reviewing test code, identifying test quality issues, suggesting test improvements, or when asked to evaluate tests against best practices. Applies to unit tests, integration tests, and any automated test code.
thoughts-management
Manage thoughts directory operations including initialization and metadata generation. Use when initializing a new project's thoughts/ structure or when gathering git metadata for document frontmatter.
validate-plan
Validate that plan was correctly implemented, verify all success criteria
commit
Create git commits with user approval and no Claude attribution
deep-research
Conduct multi-agent deep research on a topic with parallel web searches and synthesis