Use when you need to turn a vague idea into a confirmed design spec before implementation (new feature/component/behavior change). First check project context, then ask one question at a time, provide 2-3 options with trade-offs, finally output design in segments (~200-300 words each) with confirmation after each. Triggers: brainstorm, clarify idea, design spec, refine concept, requirement clarification.
Transform "vague ideas/requirements" into actionable designs and specifications, producing reusable file artifacts (rather than just staying in chat).
Key requirement: Ask only one question at a time. If a topic is complex, break it into multiple rounds of Q&A—don't throw out a checklist all at once.
Before asking questions, quickly check:
README.md, docs/, design-system.md (if exists)package.json / / etc.Cargo.tomlpyproject.tomlgit log -n 10 --oneline (if it's a git repo)Output a very brief context summary: what you observed + possible constraint points (don't start designing yet).
Goal is to gather the minimum information set (purpose / constraints / success criteria).
Rules:
After you understand the requirements:
When you're confident you understand what needs to be done, start outputting the design spec.
Requirements:
If user disagrees with a segment: go back to questioning/option phase to clarify—don't push forward.
Prefer writing to run directory (artifact-first):
run_dir/evidence/YYYY-MM-DD-<topic>-design.mdIf there's no run_dir but there is a repo_root:
runs/brainstorm/active/<run_id>/, and write design to evidence/Note: Writing files is a write operation; if this is the user's project repo, confirm "should I persist to the project?" before writing.
After design is confirmed, ask one question to let user choose next step:
workflow-ship-faster or workflow-feature-shipper)run_dir/tasks.md, then wait for confirmation)run_dir/evidence/parallel/<task-name>/ and do in parallel)