| id | finished-audit |
| name | finished-audit |
| type | Capability Uplift |
| version | 1.0.0 |
| created | 20/03/2026 |
| modified | 20/03/2026 |
| status | active |
| triggers | ["are we done","is this finished","audit completion","verify done","check if complete","is it ready","can we ship","can we close this"] |
| description | > |
| context | fork |
Finished Audit Skill
Purpose: Systematically verify that "finished" is actually true.
No vague summaries. No optimistic assumptions. Evidence only.
When to Use
Use this skill when:
- A developer or agent claims a task, feature, or project is complete
- Before merging a PR or closing a milestone
- Before claiming production readiness
- Whenever a completion claim is made without accompanying proof
Banned Output Phrases
The following phrases indicate a false completion claim. Never output them:
| Banned Phrase | Reason |
|---|
| "Done!" | No evidence |
| "That's complete." | No evidence |
| "Everything is working." | No evidence |
| "You're production ready." | No evidence |
| "Finished." | No evidence |
| "It's ready." | Subjective |
| "Should be working." | Unverified |
| "Looks good." | Subjective |
| "Tests are passing." | No output shown |
Inputs
- The task, feature, or project description
- The Definition of Done criteria (from
definition-of-done-builder or provided)
- Any proof artifacts already provided
Procedure
Step 1: Load or generate DoD
If no DoD exists: activate definition-of-done-builder first.
If DoD exists: use it as the audit checklist.
Step 2: Verify each criterion
For each criterion in the DoD:
- Check if proof artifact exists
- If yes: classify as PROVEN (record the artifact)
- If artifact is claimed but not shown: classify as CLAIMED (not accepted)
- If no artifact: classify as UNKNOWN
- If definitively absent: classify as MISSING
| Status | Meaning | Accepted as proof? |
|---|
| PROVEN | Evidence exists, verified | Yes |
| CLAIMED | Evidence claimed but not shown | No |
|