brainstorming

To turn vague ideas into an approved design specification, the skill explores project context, asks one clarifying question at a time, proposes approaches with trade-offs, and presents the design in sections requiring user approval before writing a spec file.

Documenting requirements for cross-module changes involves stepwise clarification of constraints, proposing 2-3 alternative approaches, and saving the approved sectioned design document directly to the project's specs directory.

The incremental design approval process presents the specification in manageable sections and requires explicit user approval after each section, ensuring the validated design is reviewed before committing the final markdown file.

Yes, you can optionally launch a browser-based visual companion helper to generate mockups and diagrams, which assists in clarifying visual product requirements during the brainstorming session.

Yes, the skill checks existing project files, documentation, and recent git commits to ground its clarifying questions and proposed design approaches in the current codebase context.

You should avoid using an automated design spec generator for project planning when a request has completely clear scope and immediate implementation is required, as this tool enforces a stepwise clarification and approval gate to prevent premature coding.