dough-product-backlog git:20261021.51789e1A

Immutable. This exact content never changes and is served at /api/v1/blob/cea0a70ba5b89449.

---
name: dough-product-backlog
description: Maintains and reprioritizes a product backlog list of canonical story or bounded-correction references, and records necessary blocking story dependencies in canonical homes. Use to add, take, reorder, or complete backlog items, adopt or repair the done catalog beside them, record or inspect a justified prerequisite, correct an evidenced supplier agreement after cleanup, or resolve product backlog merge conflicts. Excludes classroom and workshop exercise backlogs.
---

# Product backlog

## Required context

Before editing, identify from human instructions or repository guidance:

- Repository root and canonical backlog path.
- Canonical seed locations, seed IDs, and heading or stable-anchor conventions
  when feature-story entries are affected.
- Canonical executable-plan locations for plan-homed correction entries or
  taken planned stories when they are affected.
- [Work item identity](references/identity.md), which is the single contract
  for what identifies an entry and what only navigates to it.
- [Record preparation facts](references/record-preparation.md), when
  decomposition, refinement, slice planning, plan refinement, execution,
  resume, or wrap-up writes or consumes structured preparation or readiness
  assessment in a canonical home through `record-state` / `read-state`.
- Decomposition, refinement, slice-planning, plan-refinement, execute-plan, and
  wrap-up workflows, when needed.
- Commit conventions, if a commit is authorized.

If the backlog or the canonical home required by an affected entry cannot be
identified, ask for the missing context and stop before editing. Do not require
seed conventions when every affected entry is a plan-homed correction. If a
required workflow is unavailable, stop that activity and ask for its guidance.

## File layout

- Place **Near-future direction** immediately after the title when it exists,
  then **Taken** immediately before **Backlog list**. Retain **Taken** when it is
  empty.
- Use bullet lists. Do not number items. Put the highest-priority queued item
  first. Preserve the order of entries already in **Taken** and append each
  newly taken entry.
- In **Taken** and **Backlog list**, include only each exact work title linked to
  its canonical active home and its recorded identity, as
  [work item identity](references/identity.md) defines them. A plan-homed
  correction links directly to its existing plan. Taken planned stories,
  including correction stories, also link directly to their slice plans. Keep details,
  estimates, dependencies, and status in the canonical home.
- Select work for the backlog list; do not inventory every candidate or turn
  the list into a roadmap or execution plan.

## Near-future direction

- Treat the direction as the short-term vision: focus effort on one customer
  value or goal.
- Use it as the most important input when deciding story scope. Include the
  outcomes needed to advance that value or goal; exclude unrelated expansion.
- Add or change the direction only on an explicit human instruction to do so.
- Otherwise preserve it exactly. If absent, leave it absent; do not infer or
  generate a direction during backlog maintenance.
- Use the direction to guide ordering. Most items should align with it; urgent
  fixes and urgent architecture changes may take priority.

## Canonical active homes

- Keep a feature story in one canonical section within its seed.
- A new bounded retrospective correction's canonical home is its minimal
  story, linked to its plan, under the correction-input contract in
  [planning scope and lifecycle](../dough-story-refinement/references/planning.md#choose-the-planning-level).
- A correction whose plan was already its canonical home stays there under its
  recorded identity. Do not migrate it or create a seed to queue it.
- For planned work with a story, queue that story and link its plan there. Do
  not also queue the plan. Treat references to either home as the same work
  when checking repetition and duplicates; `add` and `take` refuse a plan
  listed as separate work.

## Maintain the backlog list

- Read the backlog, its direction if present, and referenced canonical homes
  before changing order.
- Follow human priority instructions. Otherwise rank by direction alignment,
  user value, learning value, and genuine product prerequisites. Preserve
  unrelated order. Do not derive priority from seed IDs or order within a seed.
- Link from related documents; do not duplicate work details or list the same
  story or correction twice within or across **Taken** and **Backlog list**.
- When a story or correction is renamed or moved, update the entry's link and
  carry its recorded identity across unchanged, under
  [work item identity](references/identity.md). Update incoming links.
- Add a feature story only with a named beneficiary and evaluable outcome. If
  either is unresolved, use this project's decomposition workflow and route
  selected-story detail to refinement, then slice planning. Add a bounded
  correction only when its story and plan, or its plan-homed record, satisfy the
  correction-input contract above; otherwise name the missing field and leave
  the story, plan, and queue unchanged. Do
  not use decomposition to fabricate a story. Carry the direction into
  applicable workflows as the primary input for scope decisions.
- Place unfinished prerequisites before dependent work. If this conflicts with
  explicit human ordering, cite the affected entries and ask the human to resolve
  the conflict before changing their order. Do not invent technical preparation
  stories.
- Reprioritizing does not authorize execution or cancel other candidates.

## Take queued work for execution

Invoke the installed `scripts/product-backlog.mjs take` operation only as
execution of the selected authorized plan or explicitly planless quick story
starts. Refinement, planning, intent, or missing execution context or authority
leaves the entry queued. Follow
[execution and resume](references/record-preparation.md#execution-and-resume)
for readiness; Take and resume neither record nor infer it.

Preserve the title, canonical link, and identity. A planned story requires a
resolvable link to its slice plan or a section of it, including on resume.
Quick stories need no plan; plan-homed corrections need no duplicate plan link.

Move the entry to the end of **Taken** once. On resume, do not duplicate or
reorder it. Refuse an absent or ambiguous entry instead of fabricating one.

Leave started work in **Taken** across pauses, failures, resume, completion, and
retrospective; returning cancelled work requires an explicit backlog decision.

## Record a necessary blocking dependency

Keep stories externally valuable: shared code or convenience creates no wait.
Use common architectural direction, PFE, and reconciliation first; block only
when the consumer cannot start before supplier completion and explain why those
approaches are insufficient. Do not infer dependencies from prose, queue order,
or shared files.

Write the condition as the supplier outcome needed before the consumer can
start. Consuming or integrating it belongs in consumer scope and acceptance
examples; never require consumer implementation to unblock itself. For a mixed
condition, use the
[consumer-resolution procedure](references/supplier-dependencies.md#discover-and-judge-each-current-consumer)
to separate those responsibilities before judging fulfillment.

Use the installed `scripts/product-backlog.mjs read-dependencies --link <home>`
to read the consumer's canonical section and its dependency agreement `basis`.
Then use `update-dependency --identity <consumer-id> --link <home>
--dependency-file <json-path> --expect-dependencies <basis>`. Both endpoints
must name existing canonical homes; the supplier's `href` is relative to the
backlog directory, as the consumer's `--link` is. Missing or ambiguous homes,
incomplete fields, and stale agreements refuse with nothing written.

The input JSON supplies `supplier: {identity, href}`, `implementation`, `rationale`,
`condition`, and `state`; start with `waiting`. `satisfied` requires recoverable
`resolution: {revision, path, summary}` explaining fulfillment; `decision-needed`
requires the actual unresolved question in `decision`. Judge completion or correct
mixed agreements after cleanup through the [consumer-resolution procedure](references/supplier-dependencies.md).

The command updates one agreement in a versioned `json dough-story-dependencies`
block, preserving other dependencies, readiness reasons, and sibling stories.
An agreement edit (supplier, implementation, rationale, or condition) reports
changed content since review without renewing the judgment; state, resolution,
or decision changes leave the review unchanged. A dependency is not a
[readiness reason](references/record-preparation.md#criteria).

Start eligibility is derived, never stored: the assessment must be `ready` and
every dependency satisfied. `read-state` reports `startEligibility`; the dashboard
and start command show the same assessment, dependency, or unreadable-fact blockers.
Eligibility grants no permission and launches nothing. Unresolved relationships
block new execution, including queued one-shot starts and canonical admission;
refinement and planning remain possible. A blocker during existing execution
requires a developer decision; it does not interrupt that execution automatically.

## Remove completed items

- Route completed story or correction closure through
  [dough-story-wrap-up](../dough-story-wrap-up/SKILL.md). It removes the entry
  from its active list and owns applicable seed, plan, and proof cleanup.
- Standalone maintenance may remove a completed item from either active list
  when the human asks only for backlog maintenance. The applicable seed, plan,
  and proof remain available for later story wrap-up.
- Work a human drops rather than finishes is removed with `complete --dropped`,
  which removes the entry and releases its profile as below and leaves the done
  records to finished work.

Either path removes the entry with the installed `scripts/product-backlog.mjs
complete` operation. It also deletes the execution agent profile under
`agents/` beside the backlog that names the same identity, releasing that agent
name, and writes the work's done record under `done/` beside the backlog: its
identity, title, completion time, the developer configured in this workspace's
Git, and that profile's agent, host, and model when one existed. The same run
removes done records completed more than 30 days before, then rebuilds the done
catalog `done/.catalog.json` from the records that remain, and its report names
each file it wrote or removed. Commit those files with the backlog change; the
done record stays in the project as the published fact that the work was done.
A preparation assignment profile stays until its own release.

### Adopt or repair the done catalog

The done catalog lists each done record's file name, identity, completion time,
and Git blob hash, newest first, and names each unreadable record file with its
hash and no completion time, so a reader can order the records and read only
the ones it needs. Titles, developers, agents, hosts, and models stay in the
records. The catalog is derived from the record files: never edit or merge it
by hand. `complete` and the installed merge, rebase, and cherry-pick adapters
in [merge conflicts](references/merge-conflicts.md) keep it current: an
operation through an adapter that changes records also leaves a catalog
rebuilt from the resulting record files. Rebuild it with the installed
`scripts/product-backlog.mjs catalog-done [--file <backlog>]` and commit the
result when:

- done records exist beside the backlog with no catalog, because they were
  written before catalogs existed;
- record files were added, removed, or changed outside `complete` and those
  adapters, such as by raw Git, a hand edit, or an older installed copy of
  these scripts; or
- raw Git reports a conflict in `done/.catalog.json`: settle the record files
  first, then rebuild and stage the catalog.

`catalog-done` changes no record and no backlog entry, prunes nothing, and
writes no completion; with no record left it removes the catalog. Its report
names any unreadable record file, which stays for a person to read; the catalog
never makes up a completion time for it.

## Direct edits may be denied in Claude Code, Codex, or Cursor

An installed Claude Code project may deny a direct `Edit`/`Write`/
`MultiEdit`/`NotebookEdit` attempt on the resolved product backlog path,
an installed Codex project may deny an `apply_patch` attempt there, and an
installed Cursor project may deny a `Write`/`StrReplace`/`Delete` attempt
there. Each reports the denial before any bytes change. This is expected:
invoke the installed `scripts/product-backlog.mjs` operation instead of a
direct hand-edit. Reads, edits to other files, and shell-run commands (including
shell redirection into the backlog file) are unaffected.

## Merge, rebase, or cherry-pick the backlog across branches

An authorized merge, rebase, or cherry-pick that combines two sides of the
product backlog (often `PRODUCT-BACKLOG.md`) — not an ordinary same-branch
add/take/place/complete — is run through this project's installed product
backlog Git adapters from the start, before Git ever reports a conflict; a
clean Git result can still combine the backlog wrongly. Read and follow
[reconcile product backlog Git operations](references/merge-conflicts.md) for
how to resolve the installed adapters, run the matching operation, resolve a
real conflict, and validate a clean-but-disputed result, including its
fallback for when the adapters are unavailable or do not cover the conflict.
If neither the adapters nor that reference are available, preserve the
conflict and report the missing guidance.

## Check and report

- Check exact titles, links, duplicates across both active lists, and
  prerequisite order in the queue.
- Check section order, bullet formatting, and direction alignment when present.
  Confirm the direction is unchanged unless explicitly instructed by a human.
- Summarize changes and reasons briefly.
- Follow commit conventions when authorized. Backlog maintenance alone does not
  authorize a commit or push.

Supplier landing/wrap-up uses the shared [completion and consumer-resolution procedure](references/supplier-dependencies.md).
The generic `complete` command changes queue membership only.