brainstorming

To translate ideas into design specifications before coding, this skill generates structured design documents by exploring repository context, asking clarifying questions, and proposing multiple approaches with trade-offs before any implementation begins.

Planning a new feature across existing repository files requires context exploration. This skill reviews your repository files, documentation, and recent git commits to clarify requirements and constraints before generating a recommended design proposal.

Yes, you can commit design documentation to your git workflow. This skill automatically creates a design markdown file and commits it directly to your repository to ensure specifications are version-controlled alongside your code.

Creating multiple design proposals for component redesign involves interactive clarification. This skill generates 2-3 approaches with detailed trade-offs and a recommended solution based on your refined requirements and project constraints.

Yes, the design specification process requires interactive clarification. It uses interactive Q&A to refine your requirements and constraints, ensuring the generated design proposals accurately address your specific feature planning or configuration adjustment needs.

To transition from design specs to implementation planning, this skill hands off the generated design documentation to the writing-plans skill, enabling detailed planning and execution of your approved software feature or component changes.