brainstorming

To convert raw ideas into structured design specs, engage in a collaborative brainstorming process that asks clarifying questions one at a time, proposes 2-3 design approaches, and secures approval before finalizing a formal design document.

The best way to gather requirements for implementation planning is through structured dialogue where constraints and goals are explored iteratively, resulting in validated design approaches and a formal handoff document.

Collaborative brainstorming surfaces design trade-offs by generating 2-3 distinct design approaches for review, allowing you to evaluate options and secure client approval before proceeding to implementation.

Yes, you can use it for software design specification. It produces a formal design document saved to the specs directory and explicitly hands off to the implementation planning stage via the writing-plans skill.

No, the brainstorming process requires no external dependencies to work. It operates independently using internal scripts to guide the structured dialogue and generate the final design specifications.

You should not use a one-question-at-a-time design approach if your project context is already fully defined, your requirements are rigidly specified, or immediate implementation is required without formal design validation.