brainstorming

To create a software design specification, this skill explores project context, asks clarifying questions, and proposes viable approaches with trade-offs. It outputs a structured design doc stored in the specs directory and requires explicit user approval before any implementation begins.

Brainstorming software architecture involves reviewing project files and commits, then asking targeted questions to define constraints and success criteria. This skill generates two to three solution proposals with a recommendation, producing a detailed design blueprint prior to coding.

Yes, visual mockups and diagrams can be generated during planning. This skill integrates an optional visual companion that presents diagrams when visual clarification is beneficial for aligning on the architectural design and feature requirements.

Yes, the design specification process enforces hard gates to prevent code generation. It requires explicit user sign-off on the proposed design doc before allowing any transition to implementation planning and writing code.

To transition from a design spec to an implementation plan, this skill hands off to the writing-plans skill after user approval. It completes the architectural brainstorming phase and passes the structured specification directly to the planning workflow.