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/product-backlog/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/product-backlog)<a href="https://agentmods.dev/skills/nerds-odd-e/doughnut/product-backlog"><img src="https://agentmods.dev/badge/skills/nerds-odd-e/doughnut/product-backlog.svg" alt="Measured on agentmods" 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.00060 | $0.00741 |
| Opus 5 | $0.00030 | $0.00370 |
| Sonnet 5 | $0.00012 | $0.00148 |
| Haiku 4.5 | $0.00006 | $0.00074 |
Grade A, and why
product-backlog 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 yesterday.
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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product backlog
Product settings
- Repository: the Donut checkout containing this skill (three directories above this skill directory). Resolve the following paths from that root.
- Canonical backlog:
.planning/PRODUCT-BACKLOG.mdin that repository. - Story homes:
.planning/seeds/SEED-NNN-*.md. - Required file layout: a short Near-future direction section immediately after the title, followed by the unfinished story queue, and a Recently done section at the bottom.
- The direction section states the general product goal for the near future. Most backlog items should align with that direction and goal; urgent fixes and urgent architecture changes are exceptions and may take priority.
- Queue format: one numbered list, highest priority first. Each entry contains only the exact story title linked to its heading or stable anchor, and its home seed ID. Keep requirements, estimates, dependencies, and status in the seed.
- The queue is a selection of unfinished stories, not an exhaustive inventory of seeds, a milestone roadmap, or an execution plan.
- Recently done lists the ten most recently completed items, newest first (or all completed items if fewer than ten). Use the same linked title and seed ID format as the queue; completion details stay in the home seed.
- Do not confuse this queue with the LeSS in Action class backlog produced by
prepare-product-backlog-for-lia.
Maintain the queue
Read the backlog, including its near-future direction, and the referenced story sections before changing order. Follow the owner's priority instructions; otherwise order by alignment with the direction, user value, learning value, and genuine product prerequisites, allowing the urgent exceptions above. Preserve unrelated order. Do not infer that seed number or order within a seed determines global priority.
One story has one canonical home even when its journey crosses several features. Related seeds may link to it; do not duplicate its requirements or enqueue the same outcome twice. Preserve stable story anchors when renaming or moving a story, and update incoming links when needed.
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.
- yesterday Changed · +16 lines 928e4579d3be
- 2d ago First seen · 47 lines · 60 tokens per session scan A 282a3f7aa394
product-backlog is a skill published in the GitHub repository nerds-odd-e/doughnut (49 stars, last pushed yesterday), licensed MIT. It adds 60 tokens to every session and 741 once invoked, about $0.0003 per session on Opus 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-05.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.