definition-of-ready

Run the Skill after your product, design, and architecture docs exist. It scans those docs, suggests criteria per category (story description, acceptance criteria, UX, technical preconditions, size, process), and confirms each with you before writing docs/05_scrum/definition_of_ready.md.

It reads the PRD, product principles, domain model, business rules, UX spec, and backend/frontend architecture docs if they exist. Each doc informs specific criteria, such as API contract requirements from backend architecture or screen states from the UX spec.

Each criterion must be checkable with a binary yes/no answer and reference a concrete doc rather than require judgment calls. The Skill enforces this with a quality check before writing, including an explicit size limit and a named owner for the Ready confirmation process.

Yes. The Skill adapts its suggestions based on which docs exist, falling back to simpler criteria like describing UX in the story itself. You can also mark a category as not required during the interview.

It is written to docs/05_scrum/definition_of_ready.md, and the folder is created if missing. The Skill auto-detects your docs folder with a find command and asks which one to use if multiple exist.