skills.rest
Fatih0234
Fatih0234COMMUNITY
Explore all skills by this author →
WebsiteGitHub

implement-spec

Implements a specification as a single PR using concurrent subagents and ticket task graphs.

Updated Aug 27, 2026
Search Tags:#code review#pull request#concurrency#subagents#git worktree#task graph#spec implementation
One-click install
npx skills add https://github.com/Fatih0234/mattpocock-skills-pi --skill implement-spec-fatih0234
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement-spec
Source: https://github.com/Fatih0234/mattpocock-skills-pi/tree/main/skills/in-progress/implement-spec
Command: npx skills add https://github.com/Fatih0234/mattpocock-skills-pi --skill implement-spec-fatih0234

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written specification into working code usually requires manually coordinating many tickets, branches, and reviews. This Skill orchestrates that entire process, driving a spec from tickets to a ready-for-review pull request. ## Core Features & Use Cases - Task Graph Execution: Treats tickets as a dependency graph with blocking relationships, always working the frontier of ready tickets. - Concurrent Subagents: Runs implementer subagents in parallel worktrees on separate branches, with merger subagents integrating completed work. - Built-in Review Loop: Runs a code review on the PR branch and fixes all raised issues before marking the PR ready. - Use Case: Given a spec issue with linked implementation tickets, the Skill creates a draft PR, fans out implementer subagents across the ticket graph, merges their work, resolves review findings, and hands back a clean PR. ## Quick Start Ask the agent to implement the spec in issue #42 as a single PR using its associated tickets.

Frequently Asked Questions about implement-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a spec as a single pull request?▼

Provide the spec and its tickets, then the Skill reads the task graph, creates a branch and draft PR, and dispatches implementer subagents per ticket. Completed work is merged into the PR branch until all tickets are done.

How does the ticket task graph control execution order?▼

Tickets carry blocking relationships, so only the frontier of unblocked tickets is worked at any time. When a merger subagent integrates finished work, newly unblocked tickets trigger additional implementer subagents.

Can implementer subagents run concurrently on the same repo?▼

Yes. Each implementer subagent works in its own git worktree on its own branch, so parallel work does not conflict. A separate merger subagent then merges each completed branch into the PR branch.

Does the workflow include code review before merging?▼

Yes. After all tickets complete, the Skill runs a code review on the PR branch and fixes every raised issue in a single implementer subagent before marking the PR ready for review.

When should I not use spec-based subagent implementation?▼

Avoid it for small single-file changes where subagent and worktree overhead exceeds the work itself, or when tickets lack clear blocking relationships. It is designed for multi-ticket specs with parallelizable work.

Related Skills

Explore More Software Engineering Skills→
ArcReelArcReel
4.3k

wayfinder

Plan large efforts as decision tickets tracked on an issue tracker.

Official
Advanced
JhabbigJhabbig

review-agent-setup

Configure human approval gates for AI review actions with Cedar policies.

Community
Advanced
AbildtoftAbildtoft
2

kramme:verify

Run formatting, linting, type-checking, builds, and tests on affected code.

Community
Intermediate
mattpocockmattpocock
242.8k

implement-spec

Implements a specification as a single PR using concurrent subagents and ticket task graphs.

Community
Advanced