FREESKILL v1.0UPDATED 2026-08

Done

Done is not a dashboard color. It is a shared completion contract with observable criteria, named evidence, verification, handoff, and an explicit decision owner.

Teams often call work done when the deliverable exists, even though review, acceptance, documentation, or observation is still missing. That shortcut turns unfinished risk into somebody else's surprise.

This playbook defines the finish line before the result is known, then audits completion claims against the same evidence. It separates producing the work from proving it works and handing it to the people who depend on it.

A confident assertion is not verification. Done follows evidence.

SIGNALS YOU NEED THIS

Projects turn green while approvals or tests are still open.

Two reviewers use different definitions of complete.

A release is treated as the finish line even though handoff or observation remains.

REPLACES

Vague finish lines, subjective ready labels, and completion claims based on activity.

PAIRS WITH

Standard Operating Procedures, Weekly Status Updates, Post Mortems, and Correction of Errors.

0 of 4 steps complete

STEP 01Name the outcome and boundary

State who receives value, what will be true, what is included, and what is excluded. The finish line cannot stay stable if the outcome or scope is implicit.

OUTCOME
  Help content is available in the new structure without losing existing access.

IN SCOPE
  Published pages, old-link resolution, search indexing, and support handoff.

OUT OF SCOPE
  Evidence needed.

STEP 02Write observable completion criteria

Separate deliverable, quality, documentation, handoff, operations, and domain checks. Give every criterion evidence, a verifier, and a verification date.

CRITERION
  Every old link resolves to the intended moved article.
  Evidence: redirect-check report
  Verifier: Verifier needed
  Verification date: Date needed
  Status: ready for verification

STEP 03Add handoff, observation, and exceptions

Record approvals, dependencies, limitations, recovery needs, and the signals to observe after release or handoff. An unmet gate stays an exception until the authorized person accepts its risk.

OBSERVATION
  Period: Duration needed
  Signals: search result success and unresolved-link failures

EXCEPTION
  Criterion: none accepted
  Risk owner: Owner needed
  Review date: Date needed

STEP 04Make the status decision from evidence

Choose Not done, Ready for verification, or Evidence supports Done. Preserve a claimed status without endorsing it, name blockers first, and do not turn pressure into proof.

CLAIMED STATUS
  Green today

VERDICT
  Not done

BLOCKER
  Verification evidence is missing. No approval or exception was supplied.

Download the folder into your agent's skills directory. It uses only the material you provide and makes no remote calls.

skills/done

done/
├── SKILL.md                         ← define and audit modes
├── meta.yaml                        ← version, sources, test prompts, changelog
├── LICENSE.md                       ← MIT
├── assets/
│   ├── definition-of-done-template.md ← completion contract
│   └── done-audit-scorecard.md      ← evidence-backed audit
└── references/
    └── stage-gates.md               ← work states and transition evidence

INVOKE IT LIKE THIS

"Write the definition of done for this project."

Download skill v1.0 View source files

WORKS WITHClaude Code