Test Driven Development
Use when implementing any feature or bugfix, before writing implementation code
Verification Before Completion
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
Ml Feedback Ladder
Use when planning how to verify an ML experiment cheaply before expensive runs - design the R0-R7 ladder from local sanity checks to full study, with promotion/stop criteria.
Brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Ml Experiment Design
Use when turning a rough ML idea into a runnable experiment - define the experiment card (question, hypothesis, baseline, primary metric, budget, cheapest verification rung) before writing training code.
Systematic Debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Ml Result Review
Use when concluding an ML experiment - produce a sober conclusion that separates confirmed results from exploratory observations and states the highest verified rung.
Writing Skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Subagent Driven Development
Use when executing implementation plans with independent tasks in the current session
Writing Plans
Use when you have a spec or requirements for a multi-step task, before touching code
Executing Plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints