brainstorming

To turn ambiguous requirements into a design spec, the skill explores project context, asks clarifying questions one at a time, and compares approaches. It requires explicit user approval before writing a dated design document and proceeding to implementation planning.

Evaluating architecture trade-offs involves comparing 2–3 proposed design approaches for your feature. This skill presents these options incrementally to validate system decisions and align on scope before any implementation actions begin.

Preventing wasted implementation requires enforcing an approval gate on the proposed design. The skill explicitly disallows code changes until the user reviews and approves the documented design spec, ensuring early alignment on intent.

Yes, you can use visual mockups during design validation. The skill offers optional Visual Companion support, providing a browser tool to generate diagrams or mockups when they would improve understanding of the proposed architecture.

No, it does not generate the plan immediately after the design is documented. The skill enforces a hard gate, transitioning to the implementation-planning phase only after the user explicitly approves the presented design proposal and written spec.

You should not use this structured brainstorming approach for changes that require immediate, undocumented code execution. It is designed for product or component changes needing scope clarification and architecture decisions, explicitly blocking implementation actions until design approval.