name: closed-loop-delivery description: ALWAYS use this when a coding task needs to reach a real done state with acceptance criteria, implementation, verification, review follow-through, and runtime proof where applicable.
Closed-Loop Delivery
Selective Reading Rule
Start with:
references/usage-routing.mdreferences/quality-checklist.md
Then load only the inherited docs, scripts, assets, or examples that match the user's actual task.
Selective Reading Rule
Start with:
references/senior-master-standard.md
Start with references/definition-of-done-template.md.
Use it to define what counts as done before implementation gets too far ahead of verification.
Purpose
Drive a task to a proven outcome instead of stopping at code edits.
Workflow
- Define acceptance criteria.
- Isolate the work when risk warrants it.
- Implement the smallest change that can satisfy the criteria.
- Verify locally.
- Resolve review feedback or runtime issues.
- Repeat until the criteria are proven or the blocker is explicit.
Rules
- No vague completion claims.
- No skipping runtime proof when runtime behavior matters.
- No hiding unresolved blockers in a success summary.