Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/brainstorm
Use when you have a feature idea but the scope or UX is still ambiguous — runs a lightweight Socratic design dialogue (3-5 AUQ rounds) and writes a spec markdown file. Use BEFORE /plan feature when product intent needs validation; skip to /plan feature when scope is already clear. HARD-GATE prevents any code work until the design is user-approved.
Passed 2 of 8 test cases with the skill, and 2 of 8 without it.
and 1 more in the full report
3 fixed2 passed either way13 still failing4 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
We already have an approved design spec document at docs/specs/2025-01-10-sso-auth-design.md detailing SAML2 integration. Please help us convert this design spec into formal engineering tasks and acceptance criteria.
| Checked | Without skill | With skill |
|---|---|---|
| Recommends using feature planning tools to formalize existing design specs into implementation plans. | Missed | Passed |
| Avoids re-running the design brainstorming workflow. | Passed | Passed |
The instructions your model reads when the skill loads.
Lightweight Socratic design dialogue for per-feature exploration. Sibling to
/plan feature, not a replacement. Producesdocs/specs/YYYY-MM-DD-<slug>-design.mdafter the user approves an approach.
Read soul.md in this skill directory before anything else. It defines WHO you are — a Design Facilitator who shapes vague ideas into approved designs through Socratic questioning. Every interaction in this skill should reflect that identity.
/plan feature directly/plan new/plan feature to formalize it/debug (issue #37) once shippedRead skills/_shared/bootstrap-gate.md and execute the gate check. If GATE_CLOSED, invoke skills/bootstrap/SKILL.md and wait for completion before returning here. If GATE_OPEN, continue.
There is no bypass. There is no exception for urgent requests, demo features, or spike work. The ONLY valid next action when the design is unapproved is presenting a design and waiting for user approval.
Parse $ARGUMENTS for an optional topic or feature slug. The slug will be used in the spec filename. If absent, derive it from the user's Phase 1 answer.
Run a single AUQ to let the user characterize the problem in their own words:
test cases passed, vs 2 / 8 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.