All 94 skillsPlan and decide10 of 15
stryx:taskmaster
When an agreed spec must become a step-by-step plan, a roadmap or a sprint.
/stryx:taskmasterInside its piece: 15 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- 12reference files
- 1helper scripts
- 15files in the skill
- 183KB on disk
- 8chapters
- 2agents work by this book
Use it when
in the skill’s own wordsWhen an approved spec, requirements doc or clear request needs an implementation plan before code
- "write the plan"
- "plan the implementation"
- "turn this spec into tasks"
- "deepen the plan"
- "plan for a plan"
- stryx:brainstorm hands over a spec
- When work must be broken into tasks
- "break this down"
- "decompose"
- "what are the tasks"
- When a whole app needs a phased roadmap
- "roadmap"
- "plan the whole build"
- "what phase are we on"
- When running a working-session sprint
- "start sprint"
- "sprint status"
- "end sprint"
- "session burndown"
- "what should I work on"
- "I'm blocked"
- "done with this"
- "resume the sprint"
- When a backlog needs ordering (MoSCoW, RICE, Eisenhower)
- When a non-software goal (trip, study plan, event, research plan) needs a plan
Not for
another skill does it- Deciding what to build→ stryx:brainstorm
- Carrying out a plan→ stryx:execute
- PERT, story points or a team sprint's velocity and burndown→ stryx:estimation
- Phase gates and PRDs→ stryx:workflow
On its shelf
15 files, 183 KB- references/12
- SKILL.md1
- evals/1
- scripts/1
Inside the book
8 chapters, by title only- Modes
- Plan mode: writing an implementation plan
- Break down: from feature to tasks
- Sprint: plan a working session
- Track: status, blockers, done
- Prioritize
- Check the output
- Templates and formats
Its helpers
2 agents work by this book- stryx:plannerWhen an approved spec should become a full plan with tasks, sizes and risks.
- stryx:project-status-analystYou ask "where are we really": it compares the plans with the code and the git history.
Works with
the skills it names most- stryx:execute→When a written plan must be carried out to the end, or you say "keep going until it passes".
- stryx:brainstorm→You want something new built: it agrees what to build before any code is written.
- stryx:estimation→Someone asks how long, how big or when it will be done.
- stryx:plan-review→When a spec, plan or roadmap should be tested for holes before work starts.
- stryx:verify→When Claude is about to say done, fixed or ready to commit: fresh proof comes first.
- stryx:workflow→When starting or resuming a big piece of work and deciding how much process it needs.
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.