Borrowing it
Nothing to install: this file belongs to nerds-odd-e/doughnut. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nerds-odd-e/doughnut/main/.agents/skills/dough-story-decomposition/SKILL.mdgit clone --depth 1 https://github.com/nerds-odd-e/doughnutWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/nerds-odd-e/doughnut/dough-story-decomposition)<a href="https://agentmods.dev/skills/nerds-odd-e/doughnut/dough-story-decomposition"><img src="https://agentmods.dev/badge/skills/nerds-odd-e/doughnut/dough-story-decomposition/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/nerds-odd-e/doughnut/dough-story-decomposition"><img src="https://agentmods.dev/badge/skills/nerds-odd-e/doughnut/dough-story-decomposition.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00049 | $0.00592 |
| Opus 5.5 | $0.00020 | $0.00237 |
| Sonnet 5.5 | $0.00010 | $0.00118 |
| Haiku 4.5 | $0.00005 | $0.00059 |
Grade A, and why
dough-story-decomposition scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Story decomposition
Produce one human-reviewed seed containing a clear parent problem and ordered candidate stories. Do not perform technical design or write an executable plan.
Choose the workflow
Use this skill when the beneficiary, problem, desired effect, or value is unclear; a request prescribes a solution without establishing why; several outcomes or story boundaries must be chosen; or the first increment's value or learning priority is disputed.
For selected-story goal, scope, and examples, use dough-story-refinement. Hand off one understood story to the project's execution-planning workflow only when the user explicitly requests planning. A seed or backlog selection does not authorize execution.
Resolve required context
Read the user's instructions and repository guidance to identify:
- The repository root, supplied seed or canonical seed directory, seed ID allocation and filename conventions, and stable story-anchor convention.
- Required seed metadata and lifecycle vocabulary.
- The project's definitions of S, M, and L effort bands.
- The canonical backlog path, only when queueing or reprioritizing is requested.
- The execution-planning workflow, only when that handoff is requested.
Resolve project paths from this project, not this skill's location. If context or a linked dependency needed for the current action is unavailable, name it, ask only for the missing information, and stop the affected activity before writing.
Decompose and record
Read and follow problem decomposition to establish human-owned framing decisions, challenge alternatives, and select, size, and order stories. Before writing to the seed, establish or reuse the required workspace under preparation workspace; this discussion and decomposition work needs no workspace on its own. Then use seed format to update the supplied seed or create a new seed in that workspace. After a write that leaves a candidate with a recorded identity in its canonical home, apply record preparation facts. Leave the seed there for review by default; this skill commits or publishes it only through that reference's disposition.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago Changed · +2 lines 47980b5684dd
- 1mo ago Changed · +7 lines b0d99a649fa1
- 1mo ago Changed · -1 lines 18138777e507
- 1mo ago Changed 99d6aa470565
- 1mo ago First seen · 57 lines · 49 tokens per session scan A f128d919b83c
dough-story-decomposition is a skill published in the GitHub repository nerds-odd-e/doughnut (50 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 592 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-08.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.