brainstorming

To create an implementation plan before writing code, use a design-before-code workflow that enforces explicit user approval on a proposed specification. This ensures a reviewable design doc is finalized before any execution begins.

The best way to gather requirements for vague software features is by asking one focused clarifying question at a time. This breaks down uncertainty to explicitly confirm scope, constraints, and success criteria before proposing solutions.

Evaluating architectural trade-offs involves proposing two to three distinct approaches and aligning on a final direction. This process highlights the specific benefits and compromises of each design option before implementation.

Yes, you can force a design review before an agent starts coding by applying a hard gate that requires explicit user approval. This prevents premature implementation by routing execution only after the spec is reviewed.

You need to write a design specification for project scaffolding when a behavior-changing request would otherwise lead directly to coding. Producing a reviewable spec prevents wasted engineering effort on unapproved architectures.