domains / families / devops / closed-loop-delivery

closed-loop-delivery

authentic

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.

When to use

• 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
• pure Q&A/explanations
• prod deploy requests without explicit human approval
• tasks blocked by missing secrets/account access that cannot be inferred

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Source