Agent skill · operations · sickn33
closed-loop-delivery
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.
Why this skill is useful
Provides a structured workflow for end-to-end task completion that includes acceptance criteria verification, which the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Closed-Loop Delivery Overview 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. When to Use Use this skill when: user gives a coding/fix task and expects end-to-end completion task spans code + tests + PR comments + dev deploy + runtime checks repeated manual prompts like "now test", "now deploy", "now re-check PR" should be avoided Do not use this skill for: pure Q&A/explanations prod deploy requests without explicit human approval tasks blocked by missing secrets/account access that cannot be inferred Required Inputs Before execution, define these once: task goal acceptance criteria (DoD) target environment (dev by default) review cadence/budget when requested; a default review cadence is not a task-completion limit If acceptance criteria are missing, request them once. If user does not provide, propose a concrete default and proceed. Issue Gate Dependency If the project already uses create-issue-gate, respect its current contract; otherwise derive acceptance criteria from the authorized task without inventing a mandatory issue. If issue status is ready and execution gate is allowed, continue. A real project-required draft gate can block dependent actions; it does not forbid independent discovery or already-authorized work under a different applicable workflow. Use available task context to formulate testable criteria; clarify only when a missing decision materially changes the outcome. Default Workflow 1. Define DoD Convert request into testable criteria. Example: checkout task DoD = "checkout endpoint returns a valid, openable third-party payment URL in dev". 2. Implement minimal change Keep scope tight to task goal. 3. Verify locally Run focused tests first, then broader checks if needed. 4. Review loop Fetch PR comments/reviews. Classify valid vs non-actionable. Fix valid items, re-run verification. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/closed-loop-delivery