← ClaudeAtlas

refine-backloglisted

Refine a BACKLOG item or not-started STORY by running the SOP §6 Definition of Ready checklist. Use when the user asks to refine the backlog, refine an item, promote to ready, run DoR, gate a story, do a Friday review, or invokes /tandem:refine-backlog. Operates as PM hat. Either flips status to ready (if all DoR items pass) OR stops, lists gaps, and asks — never silently promotes.
DATA-AI-XYZ/Tandem · ★ 0 · Code & Development · score 70
Install: claude install-skill DATA-AI-XYZ/Tandem
# Tandem: refine-backlog (PM hat) Operate as **PM hat**. The user wants to take a BACKLOG entry or a `not-started` STORY through the Definition of Ready gate — either promoting it to `ready` (eligible to pull into work) or surfacing exactly what's missing. This skill is the slash-command wrapper for the kit's canonical refinement prompt. The prompt is the source of truth; this file is the entry point. ## Source of truth @_00-Project-Management/92-Prompts/05-refine-backlog-to-ready.md Follow that prompt verbatim. The sections below add only the slash-command-specific glue + the DoR enforcement contract — do not re-declare the prompt's content here. ## Definition of Ready (DoR) — what we're gating against Per SOP §6, a story is `ready` only when **all** of the following are true. The skill walks each item; missing items abort the promotion with a clear gap list. - [ ] **Linked to a Feature → Epic → OKR or PRD.** Story frontmatter `feature:` and `epic:` set; parent Epic has `okr:` or `prd_section:` populated. - [ ] **AC written as testable checkboxes.** Each AC verifiable by a machine, not by vibes. - [ ] **Paired TESTPLAN exists at the mirrored path.** `33-Testplans/EPIC-NN/FEAT-NN.M/TESTPLAN-NN.M.PP-<slug>.md`. - [ ] **Every AC maps to ≥1 TC in the TESTPLAN.** Coverage matrix complete. - [ ] **Every TC has a runnable `Command:`.** No "have a human verify" steps. - [ ] **Dependencies listed and either done or scheduled.** No floating "depends on TBD". - [ ] **Estimate s