Brainstorm product requirements and scope for a feature before technical design begins.
npx skills add https://github.com/cagriy/dev-skills --skill feature-storm-cagriy
Please help me install this Agent Skill. Skill: feature-storm Source: https://github.com/cagriy/dev-skills/tree/main/skills/feature-storm Command: npx skills add https://github.com/cagriy/dev-skills --skill feature-storm-cagriy
High-intent search queries and answers about installing and using this skill.
Run /feature-storm with a free-form description of the feature. It grounds the request against existing code and docs, generates ideas you did not bring, asks clarifying questions in rounds, and writes an approved brainstorm document once scope is fully settled.
feature-storm works at the product layer: goals, users, scope, and rough technical direction. feature-design handles the technical design afterward. Deep decisions like schemas, algorithms, and library choices are deferred to design as open questions.
No. The clarification and convergence loop is mandatory even in auto or non-interactive mode, because settling product intent before writing the brainstorm document is the skill's core purpose. It will not proceed until every capability is explicitly in scope or deferred.
Yes. When requirements reference prior feature versions, existing code, or external services, the skill performs a grounding read of the relevant docs and code paths first, so its questions and options are fact-based from the first round.
It resolves a feature folder via the feature-resolve skill, writes a versioned brainstorm document named feature-storm-v<N>-<desc>.md, and updates the per-feature tracker with the storming section and progress state.
Antony-FigueroaTurns raw ideas into structured design briefs and specifications.
rombel00Designs technical architecture documents from task_spec inputs covering components, data models, and interfaces.
cuiossApply accumulated lessons to component documentation with dry-run and list options.
GenproMMExecute small ad-hoc tasks with atomic commits and state tracking.
