brainstorming

Start with a vagueness check stating the goal, constraints, and success criterion, then sketch 2-3 candidate approaches with a recommendation. Interview the user one question at a time, writing settled answers into a design doc, and get explicit approval before implementation.

Tiers scale ceremony to task risk: small covers localized reversible changes needing 1-2 questions, standard covers feature-sized work producing a committed design doc, and deep covers multi-subsystem or architectural changes where the user also reviews the written file.

When triage classifies the task as small tier, recording it with the req tier command lets the framework skip plan and validate nudges after design approval. The workflow then advances directly to the build phase for trivial localized fixes.

Yes, the flow includes an anchor peek step that reads just enough existing code to sketch credible approaches. It follows the repository's existing patterns and surfaces trade-offs when a better pattern conflicts with established conventions.

Only the rejected section is revised; the flow does not restart. Settled answers remain in the artifact, and the interview continues from the point of disagreement until that section earns approval.