ever-works/orgs/definition-of-done
Claude Code and agent skill by ever-works/orgs
- community
Checking that the SKILL.md file is still in the repository.
Use when declaring any slice, Task, or release finished — run the done checklist and either pass it in full or name the exact gaps. "Done" is a verifiable state, not a feeling of completion.
Install
npx vskill@latest install ever-works/orgs/definition-of-doneSKILL.md
Definition of Done
One shared checklist so "done" means the same thing to the person who built it, the person who reviewed it, and the person who ships it.
The checklist
A unit of work is done only when every line below is true or its exception is written down and accepted by the responsible owner:
- Criteria met — every acceptance criterion from the plan is demonstrated by a passing automated test or a recorded manual verification. Not "should work": shown working.
- Tests first and green — new behavior arrived with tests that failed before the implementation existed; the full suite passes now, not just the new tests.
- Reviewed — an independent reviewer approved this exact version. Changes made after approval void the approval.
- QA exercised — the running change survived deliberate hostile testing, and every defect found is fixed or explicitly accepted with a written reason.
- Scope honest — everything promised is present; everything cut is listed as cut, with the requester's awareness, not silently dropped.
- No debris — no leftover debug output, dead code, commented-out blocks, TODOs without owners, or temporary configuration riding along.
- Docs current — anything a user or the next builder needs to know (changed behavior, new setup, new limits) is written where they will actually look.
- Shippable — the artifact builds reproducibly from clean sources, and a rollback path exists and is written down.
- Traceable — the change links back to its Task, and the Task links forward to the release that carries it.
How to run it
- Run the checklist top to bottom and record a verdict per line: pass, fail, or accepted-exception with the acceptor's name. No line may be skipped as "obviously fine".
- The checklist is binary at the end: all lines pass or the work is not done. "90 percent done" means not done.
- Whoever finds a gap routes it to the owner of that line — builder for tests, reviewer for approval, QA for verification, release for shippability — rather than fixing it out of lane.
Output format
A short done-report: the unit of work, the verdict per checklist line, the list of accepted exceptions with reasons and acceptors, and a final DONE or NOT DONE with the blocking lines named.
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingcompanies/craftsman-dev-shop/skills/definition-of-done/SKILL.md
Popularity
- Repository stars
- 2
- 7-day trend score
- 10
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/ever-works/orgs/definition-of-done)