promotelisted

# /promote — Readiness-Gated Promotion to Backlog Move a discovery item from `docs/spec/discovery/D###-*.md` into `docs/spec/backlog.md` as an enriched, sprint-ready row. The Definition-of-Ready gate is non-negotiable: incomplete items stay in discovery. ## Token budget (MANDATORY) - Read only the target discovery detail file in full; use Grep for everything else. - `Grep` `docs/spec/backlog.md` for duplicates (do not full-Read it). - `Grep` the discovery index for the row's current state; do not full-Read. ## Usage - `/promote D###` — promote a specific discovery item - `/promote` — list refined items, let the user pick ## Steps 1. **Read** the discovery detail file `docs/spec/discovery/D<###>-<slug>.md` (full read — small file). 2. **Validate state** — item must not already be `promoted` or `dropped`. 3. **Definition of Ready gate** — every required field must pass: - Problem statement present - ≥1 user story - ≥3 acceptance criteria - Dependencies declared - No open blocking questions - Complexity estimate - Affected components / services listed - Cross-cutting concerns noted (multi-tenant, RBAC, observability, etc., as applicable to {{PROJECT_NAME}}) 4. **Duplicate scan** — `Grep` `docs/spec/backlog.md` for similar titles / problem keywords. If a dup exists, prefer linking the discovery item to it instead of promoting. 5. **Gather metadata** with the user: `Priority`, `Complexity`, `Target Sprint`. 6. **Allocate the next backlog ID** — `Grep