All 94 skillsPlan and decide2 of 15
stryx:brainstorm
You want something new built: it agrees what to build before any code is written.
/stryx:brainstormInside its piece: 19 specks, one for each file on its shelf. Its fourteen group-mates glow on the open book behind it. The light splits toward red, the band of Plan and decide.
In numbers
counted 2026-10-12 in the installed set- 16reference files
- 1helper scripts
- 19files in the skill
- 168KB on disk
- 7chapters
- 3agents work by this book
Use it when
in the skill’s own wordsWhen deciding or specifying what to build before code
- The user wants to plan, scope or spec a feature, product or app ("let's plan this", "spec this out", "design this feature", "write a spec", "what should this look like"), is planning a new Electron desktop app from zero, or wants a rough sketch of a UI or behavior choice while scoping it
- Also use before any new feature or behavior change whose requirements are not yet agreed, and whenever a request is vague, ambiguous or bigger than a quick fix, including non-software decisions
Not for
another skill does it- Generating or ranking ideas→ stryx:ideate
- Writing STRATEGY.md→ stryx:strategy
- A throwaway prototype to drive or see at real finish→ stryx:prototype
- Writing the implementation plan→ stryx:taskmaster
- Reviewing an existing spec→ stryx:plan-review
- Choosing process level or methodology→ stryx:workflow
- Building an already specified change→ stryx:execute
What it covers
Covers requirement specs, new-app product plans, non-software decisions and rough visual sketches.
On its shelf
19 files, 168 KB- references/16
- SKILL.md1
- evals/1
- scripts/1
Inside the book
7 chapters, by title only- Route the request
- Classify the path, out loud
- Rules that hold everywhere
- The architectural flow
- Bounded and spike flows
- Verification: is the brainstorm finished?
- Success criteria
Its helpers
3 agents work by this book- stryx:architect-agentWhen a design question needs its own room: options with trade-offs, or a review of a whole system.
- stryx:plan-reviewerWhen a plan or spec needs a fresh pair of eyes that did not write it.
- stryx:plannerWhen an approved spec should become a full plan with tasks, sizes and risks.
Works with
the skills it names most- stryx:prototype→You need to click through a throwaway version before deciding how something should work or feel.
- stryx:taskmaster→When an agreed spec must become a step-by-step plan, a roadmap or a sprint.
- stryx:ideate→You want many ideas, quick wins or a surprise before choosing one.
- stryx:strategy→When the product needs its STRATEGY.md: what it is, who it is for, what it will not do.
- stryx:execute→When a written plan must be carried out to the end, or you say "keep going until it passes".
- stryx:plan-review→When a spec, plan or roadmap should be tested for holes before work starts.
Claude loads it by itself when the moment comes; by hand, type the line at the top. It comes with the whole set: Installs all 94 skills, 32 agents and the brain program as one set. The skill’s own text is private source and is not shown here.