deliver-feature

name

deliver-feature

description

The team-standard "how we ship" capability. Run any well-formed feature issue through the delivery loop's five recurring capabilities — Discover, Plan, Execute, Verify & Recover, Complete — with a human gate before Execute (approve the plan) and after Complete (authorize the merge). This skill IS the protocol: it is the policy source the `/loop` prompt invokes on every tick. Issue-agnostic on purpose — you build the loop once and every future issue rides the same rails.

Skill: Deliver a Feature Through the Loop

This skill is the reusable protocol the loop runs. It mentions no specific feature on purpose: you build the loop once, and every future issue rides the same rails.

You do not prompt the agent. You design the loop that prompts the agent — a recurring, verifiable workflow that carries context from an issue all the way to a governed merge, and then repeats for the next issue.

When to use

Use this whenever a feature issue labeled loop needs to be delivered. Assume the issue was filed with the feature-loop.yml template, so it arrives loop-ready with a goal, requirements, and a machine-checkable acceptance checklist.

How it is driven

The loop is driven from GitHub Copilot CLI with the /loop command, which schedules .github/prompts/deliver-feature.loop.md to re-run on an interval for the session. Each tick advances the loop by exactly one capability, then stops — so the two human gates are always respected. Close the terminal and the loop stops; that is the point of a session-scoped, human-steered loop.

Everything durable lives in the issue and PR thread. That thread is the loop's only memory: on every tick, reconstruct where you are from the thread — never from assumptions.

The five capabilities

Every iteration of the loop passes through these. Read .github/copilot-instructions.md first — it carries the repository conventions every capability must respect.