definition-of-done

Run this Skill after your product, design, and architecture docs exist. It scans those docs, suggests verifiable criteria per category (code quality, testing, behavior, deployment, documentation, non-functional), and confirms each with you before writing docs/05_scrum/definition_of_done.md.

It reads the product goal, product principles, UX spec, UI spec, backend and frontend architecture docs, and risk docs from the docs folder. Each source informs specific criteria, such as testing strategy from architecture docs and UI states from the UX spec.

Yes. The Skill interviews you category by category, presenting suggested criteria and asking whether to adjust them. You can provide free-text replacements, accept the suggestions, or mark categories like deployment as not applicable.

A good criterion is verifiable, not subjective. The Skill enforces this by requiring concrete checks like "tests pass", "PO verified", or "deployed to staging" rather than vague statements like "good quality", and it derives non-functional criteria from actual project constraints.

The output is written to docs/05_scrum/definition_of_done.md, and the folder is created if missing. The Skill first detects the docs folder location and asks which one to use if multiple docs directories exist.