Topics
- Design
- brainstorming
- requirements
- planning
- specification
- collaboration
- workflow
What it does
Enforces a structured brainstorming process before any implementation work: explores project context, asks clarifying questions one at a time, proposes 2-3 design approaches, presents a design for user approval, and writes a spec document to `docs/superpowers/specs/`. Prevents coding, scaffolding, or any implementation action until design approval is complete.
Generated from the current SKILL.md.
Frequently asked
Does this skill write code or just plan design?
This skill only plans and designs. It has a hard gate that prevents any code writing, scaffolding, or implementation until the user approves a written design spec. After approval, it invokes the writing-plans skill to create an implementation plan.
When should I use this skill?
Use this before any creative work — creating features, building components, adding functionality, or modifying behavior. It applies to every project regardless of perceived simplicity, including todo lists and single-function utilities.
What output does this skill produce?
A written design spec saved to `docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md`, covering architecture, components, data flow, error handling, and testing. The spec is committed to git and reviewed by the user before implementation planning begins.
Does this skill handle large projects with multiple subsystems?
If a project describes multiple independent subsystems, the skill flags this immediately and helps decompose it into sub-projects. Each sub-project gets its own design spec, implementation plan, and build cycle.
Can this skill create visual mockups?
Yes, via an optional Visual Companion tool that renders mockups, diagrams, and layout comparisons in a browser. The skill offers it only when visual content would help clarify upcoming questions.
Generated from the current SKILL.md. These answers refresh after source changes.