Skip to content
SkillModel-led572 tokens in use

Implement Spec

Implements a whole spec on one integration branch by running implementer subagents in parallel across the ready tickets.

328,754 stars on the repository MIT Licensemattpocock/skills · skills/engineering/implement-spec
claude plugin install mattpocock-skills@claude-plugins-official
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing Implement Spec costs

18tokens idle
572tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts and code blocks. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Fair
  • Frontmatter8/15
  • Structure18/25
  • Examples0/15
  • Output2/15
  • Size15/15
  • Resources0/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity96
  • Maintenance100
  • Community56
  • Maturity32
  • Momentum40

Implement Spec takes a spec and its tickets, treats the tickets as a task graph with blocking relationships, and works the frontier of ready tickets with fresh implementer subagents, each in its own worktree on its own branch. Merger subagents land each result on a single integration branch.

When every ticket is done it calls code-review on the integration branch and fixes the issues in one fresh implementer subagent.

What You Get

  • One integration branch holding the entire spec
  • A draft pull request opened after the first merge when the tracker closes work through PRs or you ask for one, marked ready at the end
  • Tickets resolved the way the issue tracker closes work
  • Optional exploration notes saved outside the repo for every subagent to read
  • Cleaned-up implementer worktrees

Common Use Cases

  • Building a multi-ticket spec with maximum concurrency
  • Letting independent tickets proceed in parallel while blocked ones wait
  • Finishing a spec with one review pass over the integration branch

What Makes It Unique

It communicates with subagents through context pointers to the spec, tickets, notes and commits, and keeps messages sparse. Each implementer confirms its worktree sits on the integration branch, drives tdd, and merges the integration tip into its own branch before reporting done. New tickets start as soon as a merge changes the frontier.

Under The Hood

SKILL.md is Markdown with no scripts. The model starts background subagents for exploration, implementation and merging, creates git worktrees and branches, merges them, may open a draft pull request through your tracker’s workflow, and calls tdd and code-review. All of that writes to your repository and its tracker. When no issue tracker was provided, the skill tells you to run setup-matt-pocock-skills.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers