All 94 skillsPlan and decide11 of 15
stryx:estimation
Someone asks how long, how big or when it will be done.
/stryx:estimationInside its piece: 8 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- 5reference files
- 1helper scripts
- 8files in the skill
- 106KB on disk
- 15chapters
- 2agents work by this book
Use it when
in the skill’s own wordsWhen someone asks how long or how big something is, or when it will be done
- an estimate
- an effort or time guess
- a deadline or release-date forecast
- story points
- sizing a story or epic
- T-shirt sizes
- planning poker
- PERT or a three-point estimate
- risk or integration buffers
- a complexity score
- sprint velocity
- team capacity
- how many points to commit to a sprint
- a team sprint's burndown
- scope-creep or carry-over numbers in story points
- estimation accuracy and calibration
- the confidence behind an estimate
- re-estimating after a scope change or an overrun
Not for
another skill does it- Breaking work into tracked tasks or a working-session sprint's status or burndown→ stryx:taskmaster
- The process level or a sprint plan document→ stryx:workflow
- Plan-vs-code status→ stryx:project-status-analyst
- Writing the plan→ stryx:planner
- Deciding what to build→ stryx:brainstorm
What it covers
5 parts- the PERT protocol
- Fibonacci sizing
- the complexity matrix
- risk registers
- velocity and capacity maths and the [ESTIMATE] format
Inside the book
15 chapters, by title only- Which method answers which question
- Invariants - no context, urgency or authority overrides these
- Quick reference card
- Scope boundaries
- Words this skill uses (read first)
- Estimation protocol - six steps, every estimate
- The buffer ledger - one job per buffer, each applied once
- Story sizing (Fibonacci points)
- Sprint planning numbers
- Complexity assessment matrix
- Risk categories and compound risk
- Communicating an estimate
- Burndown and delivery tracking
- Verification gates - before finalizing ANY estimate
- Fresh eyes for L3/L4 estimates
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:workflow→When starting or resuming a big piece of work and deciding how much process it needs.
- stryx:taskmaster→When an agreed spec must become a step-by-step plan, a roadmap or a sprint.
- stryx:brainstorm→You want something new built: it agrees what to build before any code is written.
- stryx:architect→When the hard part is structure: how the parts of a system fit, and the trade-offs between designs.
- stryx:patterns→When reading unfamiliar code, choosing a design pattern or sizing up technical debt.
- stryx:ai-power→When you are not sure which skill fits, or you say "load aipower": it is the map of all skills.
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.