brainstorming

To turn a vague feature idea into an approved design spec, the brainstorming process reviews repository context, asks clarifying questions one at a time, and compares approaches before writing the spec. It waits for explicit user approval before proceeding.

The best way to analyze tradeoffs during feature planning is to compare two to three distinct approaches. This process presents the pros and cons of each direction alongside a recommendation, ensuring you choose the most suitable path before implementation.

You need requirements discovery when working on new features, behavior changes, or creative work that involves hidden assumptions. It refines goals, constraints, and success criteria through focused dialogue to prevent wasted development effort.

To prevent rushed implementation, use a design gate that produces a validated design spec and requires approval. This blocks coding until tradeoff analysis is complete and the project direction is confirmed.

Yes, this feature planning process reviews the current repository state first. Inspecting the project context happens before suggesting any change, ensuring the proposed design aligns with the existing codebase.

Yes, you can use this design spec process for creative work and behavior changes. It applies to any request requiring requirements discovery and tradeoff analysis, resolving hidden assumptions before coding begins.