brainstorming

To turn informal project ideas into approved design specifications, use a discovery-first workflow that explores repository context, asks clarifying questions iteratively, proposes 2-3 approaches with trade-offs, and validates the final design before implementation begins.

The best way to clarify vague feature requirements is through a guided, question-driven dialogue that inspects repository files and recent commits to ground clarifying questions in the current project state, ensuring intent and constraints are fully uncovered.

You generate and compare design approaches by proposing 2-3 distinct solutions with clear trade-offs and a recommendation, allowing stakeholders to evaluate options against acceptance criteria before approving a design specification.

Yes, you can use a browser-based visual companion mockup and diagram tool during brainstorming sessions when visual exploration will help clarify decision-making and validate proposed design approaches.

You save validated design specs by writing the approved document to docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md, running a self-review loop, and committing the file before transitioning to implementation planning.

Your feature design process leads to wasted engineering effort when it skips disciplined discovery and starts with vague assumptions, causing rework and missed requirements that a structured, intent-uncovering brainstorming workflow prevents.