Settle the scope before you start building.
Classifies requested changes into direct implementation, a light specification, or a full design so work starts with an appropriate contract.
When to use it
Use when a request needs design decisions, such as new features, UX behavior, architecture changes, unclear success criteria, or materially different approaches.
It changes how the agent scopes project changes, routing straightforward work to implementation and requiring an approved, saved specification for full design.
What you provide
Route A requires handing behavior changes to tdd as the matching implementation skill.
Route A requires handing bugs with known expected behavior to debugging as the matching implementation skill.
Route C must finish by invoking plan-crafting after the user reviews the written specification.
No additional actions listed.