본문 바로가기
How-to · 2026.10.05

Implement a spec's tickets in parallel with subagents, and hand off opening a session per ticket and tracking order to a single orchestrator

The /implement-spec Skill — Matt Pocock (AI Hero) · Read the original ↗

This page is a translation of the Korean original. Read the Korean original →

What you get

  • Tickets whose blockers are cleared run at the same time, so the shape of the graph, not the ticket order, sets the pace
  • Each implementer works from the integration branch and merges back at the end, landing as a fast-forward
  • If the tracker does not close work through PRs, work ends on the integration branch, so you can run offline with a local markdown tracker

When to use it

Use it when you want to land, in one go, a spec whose tickets are split by blocking edges. If the work is not yet split into tickets, it says to run to-tickets first; for small work with no real graph, use implement directly.

How to do it

  1. Install the skill set.
  2. Configure the issue tracker and setup-matt-pocock-skills first. If they are not configured, the skill stops and tells you to run that first.
  3. Prepare a harness that runs subagents in the background and gives each one its own git worktree.
  4. Clear the context and start the run by entering /implement-spec with a spec pointer (an issue number or file path).
  5. If blocked tickets do not start on GitHub even after their blockers are merged, instruct the orchestrator to track the tickets merged into the integration branch itself and compute the frontier.

Try it now

Install the skill first, pick one ticket spec that includes blocking edges, clear the context and run it. Check whether multiple implementers run at the same time, whether each ticket's trace shows tdd with a failing test first, and whether merges are fast-forwards. If some tickets touch shared files, it is safer to add blocking edges or pin down names in the exploration notes.

npx skills@latest add mattpocock/skills --skill=implement-spec
Background — what the original covers

This card covers the implementation stage of Matt Pocock's skill collection. The skill grew out of the hassle of opening a session for each ticket and instructing them one by one on specs with more than five tickets. It reads tickets as a graph of blocking relationships and handles whatever can run in parallel first. It also documents real problems that come up in parallel runs, such as file conflicts, naming mismatches and delayed unblocking, along with how to deal with them.

#Coding#Agents

← All practitioner tips