| name | completion-gate |
| description | Use when requested behavior appears complete, optional polishing continues, perfectionism delays delivery, reviewers suggest non-blocking work, or the agent cannot stop after proof. |
Completion Gate
Core principle
Correct, complete, and verified beats theoretically perfect. Read perfectionism and completion avoidance.
Procedure
- Freeze new audits, refactors, optimizations, and improvements.
- List each finite Definition of Done condition with current proof.
- Fix only missing required conditions and known blocking regressions.
- Classify remaining concerns as optional or unrelated and record them.
- Run only mandatory proof that is absent or invalidated.
- Report created or changed behavior, exact validation, and deferred optional findings.
- Stop.
Quick reference
Near completion: scope expansion zero, optional exploration zero, targeted verification high. One more thing is a scope-classification trigger.
Common mistakes
- Running a fresh repository audit at finalization.
- Blocking on elegance or hypothetical edge cases.
- Skipping required security or regression proof in the name of speed.
- Saying done without current evidence.
Stop condition
Stop immediately when the objective, explicit requirements, relevant tests, mandatory gates, and absence of known blocking regression are proven.
