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-refinement/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-refinement)<a href="https://agentmods.dev/skills/nerds-odd-e/doughnut/dough-story-refinement"><img src="https://agentmods.dev/badge/skills/nerds-odd-e/doughnut/dough-story-refinement/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-refinement"><img src="https://agentmods.dev/badge/skills/nerds-odd-e/doughnut/dough-story-refinement.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.00116 | $0.01592 |
| Opus 5.5 | $0.00046 | $0.00637 |
| Sonnet 5.5 | $0.00023 | $0.00318 |
| Haiku 4.5 | $0.00012 | $0.00159 |
Grade A, and why
dough-story-refinement 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 9d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Story refinement
Build shared understanding of one selected story, or several related stories whose boundaries need discussion. Record Goal, Scope, and Key examples in each story's seed.
Choose the workflow
If the parent problem, candidate selection, or story ordering needs reconsideration, use dough-story-decomposition. For smaller or clearer slices, use the project's execution-plan refinement workflow on the existing plan.
A refinement invocation authorizes slice planning of its story and landing the completed preparation under preparation journey; it authorizes no execution. Continue into planning without repeating answered questions.
Resolve required context
Identify this project's root, selected story links and seeds, and relevant prior decisions. When a seed is missing, resolve the canonical seed directory, ID and filename conventions, required metadata, and stable story-anchor convention. Resolve project paths from that repository, not this skill's location.
Resolve the project's slice-planning workflow for the continuation, and ADR context only when the architectural concern requires it under the reference below. If required context or a linked dependency is unavailable, name what is missing and stop the affected activity. Do not invent project paths or decisions.
Refine and continue
Read and follow planning scope and lifecycle for the
conversation, scope decisions, optional UI and architecture detail, seed updates,
and cleanup after implementation. When your instruction
carries an established preparation, follow
established preparation instead of the
workspace and announcement steps below. When the request explicitly selects
one-shot (--one-shot) for a queued story, follow
one-shot refinement instead of the
announcement step and the default disposition. Before writing to a story's seed,
establish or reuse the required workspace under
preparation workspace, then, for a
queued story, announce the preparation assignment;
refinement discussion and clarifying questions need neither on their own. After the
seed or correction-home write records goal, scope, and key examples for a work
item with a known identity, apply
record preparation facts.
What ships with it
23 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.
- references/established-preparation.md 2.8 KB
- references/executable-proof.md 12 KB
- references/one-shot-refinement.md 9.7 KB
- references/planning.md 15 KB
- references/preparation-assignment.md 13 KB
- references/preparation-disposition.md 13 KB
- references/preparation-journey.md 13 KB
- references/preparation-lost-workspace.md 3.3 KB
- references/preparation-workspace.md 13 KB
- references/refinement-options.json 11 KB
- scripts/established-preparation.mjs 1.5 KB runs code
- scripts/preparation-announcement.mjs 2.7 KB runs code
- scripts/preparation-assignment-abandon.mjs 5.7 KB runs code
- scripts/preparation-assignment-lost-workspace.mjs 3.6 KB runs code
- scripts/preparation-assignment-ownership.mjs 6.8 KB runs code
- scripts/preparation-assignment-release.mjs 5.2 KB runs code
- scripts/preparation-assignment-request.mjs 4.9 KB runs code
- scripts/preparation-assignment-start.mjs 7.3 KB runs code
- scripts/preparation-assignment-trunk.mjs 4.7 KB runs code
- scripts/preparation-assignment-unannounced.mjs 2.9 KB runs code
- scripts/preparation-assignment.mjs 4.5 KB runs code
- scripts/preparation-one-shot-recheck.mjs 1.6 KB runs code
- scripts/preparation-one-shot-start.mjs 4.3 KB runs code
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.
- 9d ago Changed · +1 lines a4aa8fea7def
- 18d ago Changed · +15 lines · +25 tokens per session 617d224f8266
- 26d ago Changed · +46 lines 292914f56b5d
- 28d ago Changed · +6 lines · +30 tokens per session a75bfdea6b64
- 29d ago Changed · +10 lines 502bb354baa5
- 1mo ago Changed · +1 lines 1759964980ee
- 1mo ago Changed · +3 lines 2bfc732eaab1
- 1mo ago Changed · +4 lines 4948c9d6405c
- 1mo ago Changed · +2 lines · +6 tokens per session cb90572f878c
- 1mo ago First seen · 48 lines · 55 tokens per session scan A fc700c10fe5e
dough-story-refinement is a skill published in the GitHub repository nerds-odd-e/doughnut (50 stars, last pushed today), licensed MIT. It adds 116 tokens to every session and 1,592 once invoked, about $0.0005 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.