You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
SkillScore41Maintained
Automatic
◆Product Management pack
Last verified 8/8/2026
What it changes
Passed 9 of 21 test cases with the skill, and 7 of 21 without it.
Without skill32%
With skill41%
Checks it passed that the model alone missed
The response contains strictly one question.
The response leads with a recommended option.
The response provides multiple-choice options for the question.
and 7 more in the full report
7 fixed2 passed either way8 still failing5 broke
Pass-rate lift
+9 pp
Tokens
-50%
Agent turns
0%
Response time
-63%
Model gemini-3.6-flashMeasured 8/8/2026v19 of 22 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
We have completed and committed the design document for our webhook dispatcher system. How do we transition from the design phase into implementation?
What was checked, without and with the skill
Checked
Without skill
With skill
The response explicitly asks if the user is ready to set up for implementation.
Missed
Passed
case-12 · gemini-3.6-flash · 8/8/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md49 linessingle file
Brainstorming Ideas Into Designs
Overview
Help turn ideas into fully formed designs and specs through natural collaborative dialogue.
Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design in small sections (200-300 words), checking after each section whether it looks right so far.
The Process
Understanding the idea:
Check out the current project state first (files, docs, recent commits)
Ask questions one at a time to refine the idea
Prefer multiple choice questions when possible, but open-ended is fine too
Only one question per message - if a topic needs more exploration, break it into multiple questions
Focus on understanding: purpose, constraints, success criteria
Exploring approaches:
Propose 2-3 different approaches with trade-offs
Present options conversationally with your recommendation and reasoning
Lead with your recommended option and explain why
Presenting the design:
Once you believe you understand what you're building, present the design
Break it into sections of 200-300 words
Ask after each section whether it looks right so far
Cover: architecture, components, data flow, error handling, testing
Be ready to go back and clarify if something doesn't make sense
After the Design
Documentation:
Write the validated design to docs/plans/YYYY-MM-DD-<topic>-design.md
Use elements-of-style:writing-clearly-and-concisely skill if available
Commit the design document to git
Implementation (if continuing):
Ask: "Ready to set up for implementation?"
Use superpowers:using-git-worktrees to create isolated workspace
Use superpowers:writing-plans to create detailed implementation plan