I tried to open this as a PR and hit the collaborators-only restriction, so I'm filing it here instead. The branch is pushed and public — close this if it isn't a direction you want, no hard feelings.
Diff: main...Cameron-Conroy:skills:implement-frontier
3 files, +53/−0. GitHub reports it merges cleanly.
The gap
/to-tickets ends by naming the frontier — any ticket whose blockers are all done — and then nothing in the repo works it. ask-matt routes the reader to /implement per ticket, /clearing between each, so today the frontier gets walked one ticket at a time by hand even when three tickets are unblocked and independent.
The proposal
implement-frontier: a user-invoked skill that computes the frontier from the configured tracker, dispatches one sub-agent per frontier ticket in parallel (each in an isolated working copy), and reports back. It orchestrates only — each sub-agent runs /implement, then /code-review against its ticket and parent spec, applies one fix round, and opens a PR. The human still merges.
The run isn't complete until every frontier ticket has either a PR link or a named blocker, and it closes by naming the next frontier — the tickets those merges unblock.
What's in the branch
skills/in-progress/implement-frontier/SKILL.md + agents/openai.yaml (user-invoked)- one line in
skills/in-progress/README.md
Filed against in-progress/ deliberately, so per AGENTS.md there's no docs page, no top-level README.md entry and no .claude-plugin/plugin.json entry. ask-matt lists no in-progress/ skills today so I left it untouched. No changeset, since in-progress/ doesn't ship in the plugin — happy to add one.
Aware of #807; happy to rebase onto the drafts/ layout.
Drafted with Claude Code.
I tried to open this as a PR and hit the collaborators-only restriction, so I'm filing it here instead. The branch is pushed and public — close this if it isn't a direction you want, no hard feelings.
Diff: main...Cameron-Conroy:skills:implement-frontier
3 files, +53/−0. GitHub reports it merges cleanly.
The gap
/to-ticketsends by naming the frontier — any ticket whose blockers are all done — and then nothing in the repo works it.ask-mattroutes the reader to/implementper ticket,/clearing between each, so today the frontier gets walked one ticket at a time by hand even when three tickets are unblocked and independent.The proposal
implement-frontier: a user-invoked skill that computes the frontier from the configured tracker, dispatches one sub-agent per frontier ticket in parallel (each in an isolated working copy), and reports back. It orchestrates only — each sub-agent runs/implement, then/code-reviewagainst its ticket and parent spec, applies one fix round, and opens a PR. The human still merges.The run isn't complete until every frontier ticket has either a PR link or a named blocker, and it closes by naming the next frontier — the tickets those merges unblock.
What's in the branch
skills/in-progress/implement-frontier/SKILL.md+agents/openai.yaml(user-invoked)skills/in-progress/README.mdFiled against
in-progress/deliberately, so perAGENTS.mdthere's no docs page, no top-levelREADME.mdentry and no.claude-plugin/plugin.jsonentry.ask-mattlists noin-progress/skills today so I left it untouched. No changeset, sincein-progress/doesn't ship in the plugin — happy to add one.Aware of #807; happy to rebase onto the
drafts/layout.Drafted with Claude Code.