All 94 skillsPlan and decide13 of 15
stryx:workflow
When starting or resuming a big piece of work and deciding how much process it needs.
/stryx:workflowInside its piece: 13 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- 11reference files
- 13files in the skill
- 182KB on disk
- 14chapters
- 1agent works by this book
Use it when
in the skill’s own wordsWhen starting, planning or resuming a feature, project or multi-session piece of work and deciding how much process it needs
- When the user says
- workflow
- lifecycle
- phase gate
- PRD
- tech spec
- product brief
- architecture doc for a PRD's Solutioning gate
- user story
- sprint plan
- project status
- what's next
- which methodology
- TDD vs SDD vs BDD vs GSD
- role pipeline
- PM pipeline
- pm mode
- team mode
- full workflow
- conductor
- new track
- "plan this properly"
- When docs/workflow-status.yaml or a .conductor/ folder exists in the project
Not for
another skill does it- Carrying out an already written plan or a hands-off request-to-PR run→ stryx:execute
- Tracking tasks inside one session→ stryx:taskmaster
- Reviewing a PRD or plan before its gate→ stryx:plan-review
What it covers
8 parts- L0-L4 rigor levels
- methodology choice
- four gated phases with evidence
- the PM-Lead-Dev-QA role pipeline
- context-driven feature tracks
- requirement-to-test traceability
- status that survives sessions
- the proof needed before calling work done
On its shelf
13 files, 182 KB- references/11
- SKILL.md1
- evals/1
Inside the book
14 chapters, by title only- The 10 workflow rules (never broken)
- Stryx-HQ projects - check this first
- Terms used here
- Start or resume - every session
- Step 1 - Assess the level
- Step 2 - Pick the methodology
- Step 3 - Pick how the work is dispatched
- Step 4 - Run the phases and pass each gate
- Step 5 - Build: resolve unknowns, then write
- Step 6 - Prove it is done
- State that survives sessions
- Actions - /stryx:workflow <action> or plain words
- Role pipeline - pipeline
- Context-driven tracks - setup, track, revert
Its helper
1 agent works by this book- 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: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:execute→When a written plan must be carried out to the end, or you say "keep going until it passes".
- stryx:orchestrate→When a job could use more than one agent: how to split it, staff it and merge the results.
- stryx:test→When tests must be written or fixed, or you want the test written first (TDD).
- stryx:verify→When Claude is about to say done, fixed or ready to commit: fresh proof comes first.
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.