definition-of-done

From the author

Use to verify a feature/story meets all Definition of Done criteria before marking complete.

Install

npx skills add haabe/mycelium --skill definition-of-done -a claude-code

Installs to .claude/skills/definition-of-done/ · Each command fetches the skill straight from GitHub with the open skills CLI.

Download .zip

Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.

Want your agent to suggest skills while you type? See how to use skills from your IDE.

Safety checks on SKILL.md

No warnings.

Why 82

Security100

Provenance60

Maintenance100

Licence100

Adoption31

aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.

Similar skills

Closest to this one by what they do and when they are used.

define-donehaabe/myceliumPin a measurable, outcome-based Definition of Done for a diamond — a behaviour-change that creates value, not a build-list. Problem-first Socratic sequence; writes definition_of_done to the diamond at birth or retrofits it when missing.Writing★ 50
verificationa5c-ai/babysitterVerification-before-completion discipline ensuring all success criteria are met, tests pass, and reviews complete before declaring work done.Testing★ 1.9K
kiro-verify-completiongotalab/cc-sddVerify completion and success claims with fresh evidence. Use before claiming a task is complete, a fix works, tests pass, or a feature is ready for GO.Testing★ 3.7K
checkescoffier-labs/brigadeUse when about to claim anything works, is fixed, is complete, or passes - before committing, replying to the user, or moving to the next task. Also use when relaying a subagent's or tool's success report, and especially at the end of a long session when the pull to say "done" is strongest.Productivity★ 81
verification-before-completionmvschwarz/openrigUse when about to claim work is complete, fixed, or passing, or before committing or creating PRsOther★ 8.5K
completion-verificationcbrock84/headcountVerifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was satisfied rather than approximated. Use this before saying something is done, fixed, or passing; before committing or opening a pull request; and whenever a claim of success has not been backed by command output.Engineering★ 2.6K

Ratings & reviews

—

no reviews

Tried this skill? Rate it to help others. Sign in

Discussion

Join the discussion. Sign in