All 94 skillsPlan and decide12 of 15
stryx:plan-review
When a spec, plan or roadmap should be tested for holes before work starts.
/stryx:plan-reviewInside its piece: 22 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- 18reference files
- 1helper scripts
- 22files in the skill
- 230KB on disk
- 9chapters
- 1agent works by this book
Use it when
in the skill’s own wordsWhen a planning document should be reviewed or pressure-tested before work starts
- a spec
- requirements document
- PRD
- implementation plan
- roadmap
- STRATEGY.md or Stryx-HQ plan
- The user says
- "review this plan"
- "review the spec"
- "pressure-test this"
- "poke holes in this plan"
- "is this plan ready"
- "critique my PRD"
- "check this plan for gaps"
- "doc review"
- When stryx:brainstorm offers to pressure-test a finished spec, a plan from stryx:taskmaster is ready for review, or stryx:workflow wants a review before a gate
- When a calling skill or script needs a non-interactive review result (mode:non-interactive)
- For another pass after the document was revised
Not for
another skill does it- Reviewing code, a diff or a PR→ stryx:review
- Acting on review feedback you received→ stryx:review-feedback
- Writing or changing the spec or plan itself→ stryx:brainstorm, stryx:taskmaster, stryx:strategy
- A single adopt-or-not verdict→ stryx:pov
- Checking a finished visual design→ stryx:design-audit
On its shelf
22 files, 230 KB- references/18
- top level10
- personas/8
- top level2
- evals/1
- scripts/1
Inside the book
9 chapters, by title only- The review at a glance
- Phases 0-1: mode and document
- Phase 2: the team
- Phase 3: synthesis
- Phase 4: apply and present
- Phase 5: decisions (interactive only)
- Phase 6: return
- Never
- Files
Its helper
1 agent works by this book- stryx:plan-reviewerWhen a plan or spec needs a fresh pair of eyes that did not write it.
Works with
the skills it names most- stryx:brainstorm→You want something new built: it agrees what to build before any code is written.
- stryx:taskmaster→When an agreed spec must become a step-by-step plan, a roadmap or a sprint.
- stryx:architect→When the hard part is structure: how the parts of a system fit, and the trade-offs between designs.
- stryx:design-audit→When checking a design that exists: a UX walk-through, accessibility, polish or screen sizes.
- stryx:orchestrate→When a job could use more than one agent: how to split it, staff it and merge the results.
- stryx:pov→You want one firm verdict for this project: adopt it or not, switch or stay.
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.