What problem does it solve? Teams and solo builders lose track of whether a backlog item or story is genuinely ready to start, leading to half-specified work entering development without testable acceptance criteria, test plans, or verified premises. This Skill enforces a mechanical Definition of Ready gate so nothing is silently promoted to ready. ## Core Features & Use Cases - DoR checklist enforcement: Walks every Definition of Ready item (strategic linkage, testable ACs, paired testplan, runnable test commands, dependencies, estimate, risks, premise verification) and reports PASS/FAIL with reasons. - Gap reporting without auto-fixing: When any item fails, it stops, lists the gaps and smallest fixes, and asks the user before patching — it never invents ACs or fabricates test cases. - Premise verification: Resolves claims about other artefacts' statuses (e.g. "STORY-X is superseded") against actual frontmatter to catch contradictions before promotion. - Sunset rule: Proposes wontfix or archived for items sitting not-started for over 90 days. - Use Case: You have a not-started story and want to know if it can be pulled into work. Run the refinement gate to get a per-item pass/fail table, a usage estimate written into the story, and a status flip to ready only if every check passes. ## Quick Start Ask the assistant to refine a specific story or backlog item by path, for example: run the Definition of Ready gate on STORY-15.1.02 and tell me what is missing before it can be marked ready.
