All 94 skillsPlan and decide6 of 15
stryx:bakeoff
When two or more very different approaches must each be drafted before you can choose.
/stryx:bakeoffInside its piece: 9 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- 6reference files
- 1helper scripts
- 9files in the skill
- 70KB on disk
- 4chapters
Use it when
in the skill’s own wordsWhen a defined goal has two or more structurally different ways to meet it and choosing well needs each one developed first
- The user says
- "bake-off"
- "bakeoff"
- "have several agents each draft an approach"
- "competing proposals"
- "let independent agents design it and pick the best"
- "develop the options before we choose"
- hands over rough options too thin to judge
- When stryx:taskmaster, stryx:architect or stryx:brainstorm hands over a consequential open HOW (a data shape, storage format, interface or ownership boundary that is expensive to reverse)
Not for
another skill does it- Judging options that are already developed or whether to adopt a technology→ stryx:pov
- Finding ideas→ stryx:ideate
- Deciding what to build→ stryx:brainstorm
- Racing runnable code or fixes→ stryx:orchestrate Race
- Measured experiments→ stryx:optimize
- Hands-on feel questions→ stryx:prototype
- Routine choices
What it covers
4 parts- non-executable designs - approach briefs
- architecture sketches
- product mechanisms
- directional pseudocode
Inside the book
4 chapters, by title only- Authority
- Hard rules
- Core procedure
- Failure modes: the sign, and what to do
Works with
the skills it names most- stryx:pov→You want one firm verdict for this project: adopt it or not, switch or stay.
- stryx:brainstorm→You want something new built: it agrees what to build before any code is written.
- stryx:optimize→When a number should move and nobody knows which change wins: try, measure, keep the winners.
- stryx:prototype→You need to click through a throwaway version before deciding how something should work or feel.
- stryx:architect→When the hard part is structure: how the parts of a system fit, and the trade-offs between designs.
- stryx:orchestrate→When a job could use more than one agent: how to split it, staff it and merge the results.
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.