All 94 skillsPlan and decide14 of 15
stryx:execute
When a written plan must be carried out to the end, or you say "keep going until it passes".
/stryx:executeInside 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- 9reference files
- 2helper scripts
- 13files in the skill
- 179KB on disk
- 12chapters
- 4agents work by this book
Use it when
in the skill’s own wordsWhen a written implementation plan, spec, Stryx-HQ Tasks list or concrete build request must be carried to verified completion in this session
- "execute the plan"
- "implement this plan"
- "run the tasks"
- "subagent-driven"
- "inline"
- "resume the plan"
- "pick up where we left off"
- When the user says
- "make it work"
- "fix all errors"
- "keep going until it passes"
- "iterate until done"
- "build and test loop"
- "ralph loop"
- "autonomous"
- "autopilot"
- "hands-off to a PR"
- "lfg"
- Also when an outer orchestrator needs implementation plus local verification returned as a structured result
Not for
another skill does it- Writing the plan→ stryx:taskmaster
- Open-ended bug diagnosis→ stryx:debug
- Deciding what to build→ stryx:brainstorm
What it covers
6 parts- inline
- subagent
- loop and pipeline modes
- the execution ledger and rulings
- return-to-caller results
- the plan_ws.py and loop.py helpers
On its shelf
13 files, 179 KB- references/9
- scripts/2
- SKILL.md1
- evals/1
Inside the book
12 chapters, by title only- The contract (every mode)
- Step 0: Intake
- Step 1: Pick the mode
- Step 2: Setup (inline and subagent)
- The ledger
- Step 3: Run the tasks
- Step 4: Final review
- Step 5: Finish
- Stryx-HQ projects
- Loop mode in brief
- Pipeline and return-to-caller in brief
- Verification and failure modes
Its helpers
4 agents work by this book- stryx:debuggerSomething is broken and the hunt would fill the chat: it finds the root cause and fixes it.
- stryx:orchestratorWhen a large job has many parts: it splits the work, sends specialists and checks their results.
- stryx:plannerWhen an approved spec should become a full plan with tasks, sizes and risks.
- stryx:reviewerWhen changes need a code review with a verdict before commit or merge.
Works with
the skills it names most- stryx:debug→Something is broken: a bug, an error, a crash, a failing test or wrong data.
- stryx:devops→When work must be committed, pushed, made a pull request, released or packaged.
- stryx:review→When code or a pull request should be checked before commit or merge.
- stryx:taskmaster→When an agreed spec must become a step-by-step plan, a roadmap or a sprint.
- stryx:ai-power→When you are not sure which skill fits, or you say "load aipower": it is the map of all skills.
- stryx:brainstorm→You want something new built: it agrees what to build before any code is written.
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.