Use when a coding task must be completed against explicit acceptance criteria with minimal user re-intervention across implementation, review feedback, deployment, and runtime verification.
Treat each task as incomplete until acceptance criteria are verified in evidence, not until code is merely changed.
Core rule: deliver against DoD (Definition of Done), not against code diff size.
Use this skill when:
Do not use this skill for:
Before execution, define these once:
dev by default)2If acceptance criteria are missing, request them once. If user does not provide, propose a concrete default and proceed.
Before execution, prefer using create-issue-gate.
ready and execution gate is allowed, continue.draft, do not execute implementation/deploy/review loops.Define DoD
Implement minimal change
Verify locally
Review loop
Dev deploy + runtime verification
dev when runtime behavior matters.Completion decision
Avoid noisy short polling by default. Use batched windows:
3m, collect delta comments/reviews6m, collect delta again10m, collect all remaining visible comments/reviewsAt each round:
10m round, stop waiting and proceed with all comments visible at that pointIf CI is still running, align polling to check completion boundaries instead of fixed rapid polling.
Require explicit user confirmation for:
Stop and escalate with a concise blocker report when:
2 default)Escalation report must include:
When claiming completion, always include:
Do not claim success without evidence.