rizanw/steno-spec / packages/skills/skills/steno-brainstorm
steno-brainstorm
VerifiedStress-test a rough idea before writing requirements and save the agreed direction as brief.md.
steno-brainstorm — concept brief
Goal: brief.md in the spec folder with the problem, the chosen direction, rejected alternatives, open questions and a decision. Short: under 80 lines.
Steps
- If the spec does not exist:
steno new <slug> --brief(writes onlybrief.md). Note the folder it prints. - EGM, only on request. If the user asked for EGM in this request and it is installed (an
egm-brainstormskill or/egm:egm-brainstormcommand is available): invoke it with the user's idea and this instruction: "Save the concept brief to<spec folder>/brief.mdusing headings Problem, Proposed direction, Alternatives considered, Open questions, Decision." EGM runs fresh-context reviewers against the idea; let it finish, then go to step 5. - Otherwise (the default), run a lightweight version yourself:
- Ask the user at most three questions, one at a time: who has the problem, what happens today, what would make them say it is solved.
- Propose two or three directions in one paragraph each, with the main risk of each.
- If this session can start a sub-agent with no shared history, give it only the idea and the directions and ask it for the strongest objection to each. Fold the objections in. If it cannot, say so and skip; do not pretend to review.
- Write
brief.md. Record the user's choice under## Decision, with what is explicitly out of scope. steno approve brief, then continue with thesteno-specskill, which scaffolds and writesrequirements.md. The brief is input to requirements, not a substitute.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |