Turn the frontier — the tickets whose blockers are all closed — into draft PRs with correct titles and bodies, then hand each to GitHub Copilot. Copilot writes wrong PR titles and bodies when it opens the PR itself; here you own the PR and Copilot only writes the code.

Frontier tickets are mutually unblocked, so they are parallelisable: open one PR per frontier ticket in the same run.

The tracker is the remote that hosts the issues and PRs — read it from (the upstream org repo, not a personal fork). The spec is the parent issue whose tickets you are delegating; take it from the user's argument, or ask for the issue number.

Done when: you have the tracker and the spec issue number.

List the spec's open tickets — the issues whose body references the spec. For each, read its section: a ticket is on the frontier when every issue it names there is closed (a ticket that names none is on the frontier). Drop any ticket that already has an open PR that it — it is already delegated.

Done when: you have the list of frontier tickets, each with every blocker closed and no open PR, and you can name why every non-frontier ticket was excluded.

First learn the tracker's PR conventions so the PRs pass its checks, not just read as the ticket: read any PR-title rule (Conventional Commits type prefix, allowed scopes) and if present — commonly documented in or . A raw ticket title and a bare body will fail a repo's title/body CI checks.

For each frontier ticket, off the tracker's default branch:

Done when: every frontier ticket has exactly one labelled draft PR whose title passes the repo's title convention and whose body links , carries its acceptance criteria, and fills every template section the repo requires for that title type.

On each PR from step 3, post one comment: followed by the body of the

implement

skill (, everything below the frontmatter), read live so an edit to that skill flows straight into the handoff.

The Copilot coding agent has cloned the tracker repo, so it can open any skill markdown committed there. Make the nested skills followable: in the pasted body, replace every reference with the repo-relative path to its committed markdown — becomes . Replace rather than annotate, because is a pi slash-command the Copilot agent cannot run; leaving it in the text is noise. Pointing at the file rather than restating its content keeps the instruction valid across edits. Replace only references whose is committed to the tracker; a reference with no committed markdown cannot be followed, so leave it as-is and tell the user which skill is missing.

Done when: every frontier PR carries exactly one comment in which every reference that resolves to a committed markdown has been replaced by that markdown's repo-relative path, and no runnable slash token remains.

Frontier rule. Blocked by means another issue must close first. Resolve each reference to its issue state; all closed ⇒ frontier, any open ⇒ hold the ticket for a later run.

PR body shape. The repo's PR template () populated from the ticket: in Metadata, a Summary of the ticket's purpose, its acceptance-criteria checklist copied verbatim, and every other section the template marks required for the title's Conventional Commits type. No template ⇒ + one purpose line + the acceptance-criteria checklist. Keep it aligned to the ticket so the PR is reviewable against it.

Handoff message. , with each committed reference replaced by its path so the Copilot agent opens the live markdown from its clone instead of hitting an unrunnable slash-command. The mention triggers Copilot on the PR's branch; the PR's gives it the ticket as context.