Percerno Skillsbeta
← everything it can do · engineering

Implement Spec TEXT

Executes a multi-ticket software specification by orchestrating parallel subagents to implement, merge, and review code on a dedicated integration branch.

2 uses this weeksource mattpococklicence MIT
Quality gate: FAIL · better answers · measured 2026-10-23
Blind-judged against the bare model on 2 requests: average lift -16.0 points (specificity, structure, method, fit).
won 0/2, lift -16.0, tokens ×40.02
Security scan: clean · 2026-10-24 · 2 files · ran in sandbox
no network calls, shell tricks, credential access or instruction tampering found in its files.

Try asking

Say it in your own words; the assistant finds this recipe by itself. Examples:

“Implementér specifikationen for brugerlogin med de tilknyttede tickets.”
“Kør implementerings-workflowet for betalingsgatewayen.”
“Specen og tickets er klar. Start integrationsgrenen og byg funktionen.”
“Implement the user authentication spec using the tickets in the tracker.”
“Run the implementation workflow for the payment gateway feature.”
“I have the spec and tickets ready. Please start the integration branch and build the feature.”
Try this skill from Claude, ChatGPT or a chat on your own page. Free plan, no credit card.Get started free

Good for

implementationspecificationorchestrationsubagentsintegration-branchtask-graphcode-reviewworkflow

Not for

Do not use this skill if the user only wants to generate a specification or tickets without implementation; use /to-spec or /to-tickets instead. It is not suitable for simple, single-file bug fixes or trivial changes that do not require a multi-agent orchestration workflow.

Details

When it is the right choice

Use this skill when a user has a completed specification and associated tickets that need to be turned into working code. It is ideal for complex features that can be broken down into a task graph with dependencies, allowing for concurrent implementation. It handles the entire lifecycle from reading the spec to final code review and cleanup.

The full recipe the assistant reads

You have been provided a spec. This spec should have tickets associated with it, describing how to implement the spec.

The issue tracker should have been provided to you. If not, tell the user to run /setup-matt-pocock-skills.

The goal is the entire spec implemented on a single integration branch, with every ticket resolved the way the issue tracker closes work.

The tickets are not a list of steps. They are a task graph with blocking relationships between them. This means there is always a frontier of tickets which are ready to be grabbed.

Communication to and from subagents should be sparse. Communicate primarily through context pointers: to the spec, tickets, research notes, and previous commits. Don't duplicate information already available via pointers.

Implementer subagents should be run in the background where possible for maximum concurrency.

Steps

  1. Read the spec and tickets to understand the task graph.

  2. (optional) Use an exploration subagent to conduct any exploration required by the tickets - relevant codebase files or external documentation. Ensure the exploration subagent can save files - it should save its markdown notes in a directory outside the repo, accessible by all future subagents. This lets implementer subagents focus on implementation rather than exploration.

  3. Create the integration branch. If the issue tracker closes work through PRs, or the user asks for one, open a draft PR after the first merge in step 5 (a branch with no commits ahead of main can't open one), marked as closing the spec and tickets.

  4. Use implementer subagents to implement each ticket, each in its own worktree on its own branch. Each implementer subagent:

  5. confirms its worktree is based on the integration branch before starting, and resets onto it if not;
  6. calls the Skill tool with tdd to build the ticket;

  7. merges the integration branch tip into its own branch before reporting done

  8. Once an implementer subagent completes, merge its work to the integration branch with a merger subagent.

  9. If this changes the frontier of available tickets, kick off more implementer subagents to work on the new tickets. This allows for maximum concurrency.

  10. Once all tickets are complete, call the Skill tool with code-review on the integration branch. Fix all issues raised by the code review in a single implementer subagent.

  11. If a draft PR exists, mark it ready for review. Otherwise, resolve each ticket the way the issue tracker closes work, and report the integration branch.

  12. Clean up all implementer subagent worktrees.

Files in this skill (3)
  • LICENSE
  • SKILL.md
  • agents/openai.yaml
Where it comes from

Vendored from mattpocock/skills, commit 5beb35b040e3, path skills/engineering/implement-spec, licence MIT. The upstream licence file ships inside the skill.