03-definition-of-ready
Installation
SKILL.md
Definition of Ready Skill
Use When
- Use when defining the evidence a backlog item needs before sprint commitment, including acceptance criteria, sizing, dependencies, and design clarity. Use definition-of-done for completion criteria and sprint-planning for the sprint commitment.
Do Not Use When
- Do not use when a more specific upstream or downstream skill owns the task, or when the required project context has not been prepared.
- Do not use this skill to fabricate missing project facts, legal conclusions, test results, approvals, or certification claims.
Required Inputs
| Artefact | Source or provider | Required? | Missing-input behaviour |
|---|---|---|---|
| Candidate backlog items; acceptance criteria; sizing method; dependency map; design evidence; product priority and sprint horizon | Product owner, analysts, designers, and delivery team | Yes | Stop dependent work; name the missing item, owner, and decision impact. A review check remains not assessed. |
| Scope, audience, baseline/version, and accountable decision owner | Requester or project context | Yes | Ask for or record the gap; do not infer authority or scope. |