mattpocock/implement-spec
skills/in-progress/implement-spec/SKILL.md
Implement a specification in code.
$ install --global
skillsauthnpx skillsauth add mattpocock/skills implement-specInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Aug 26, 2026, 2:38 AM190.4s2 files scanned
SKILL.md
- name:
- implement-spec
- description:
- Implement a specification in code.
- disable-model-invocation:
- true
You have been provided a spec. This spec should have tickets associated with it, describing how to implement the spec.
The goal is a PR which implements the entire spec on a single branch.
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
-
Read the spec and tickets. Read enough to understand the task graph.
-
(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.
-
Create a branch, and a draft PR. The PR should be marked as 'closing' the spec issue and tickets.
-
Use implementer subagents to implement each ticket. Each implementer subagent should work in its own worktree, on its own branch.
-
Once an implementer subagent completes, merge its work to the PR branch with a merger subagent.
-
If this changes the frontier of available tickets, kick off more implementer subagents to work on the new tickets. This allows for maximum concurrency.
-
Once all tickets are complete, run /code-review on the PR branch. Fix all issues raised by the code review in a single implementer subagent.
-
Mark the PR as ready for review.
-
Clean up all implementer subagent worktrees.
Related Skills
mattpocock/retro
tools
VerifiedTrustedCommunity
Conduct a retrospective on a coding session.
250,603SKILL.mdUpdated Sep 5, 2026
mattpocock/writing-for-agents
documentation
VerifiedTrustedCommunity
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
226,844SKILL.mdUpdated Aug 18, 2026
mattpocock/wait-what
data-ai
VerifiedTrustedCommunity
Stop. That last message did not land: re-pitch it.
226,844SKILL.mdUpdated Aug 18, 2026
mattpocock/to-questionnaire
testing
VerifiedTrustedCommunity
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
226,844SKILL.mdUpdated Aug 18, 2026