skills.rest
MSC72m
MSC72mCOMMUNITY
Explore all skills by this author →
𝕏@MSC72mGitHub

implement-spec

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

Updated Aug 22, 2026
Search Tags:#code review#pull request#parallel agents#subagents#git worktree#task graph#spec implementation
One-click install
npx skills add https://github.com/MSC72m/DevForge --skill implement-spec-msc72m
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement-spec
Source: https://github.com/MSC72m/DevForge/tree/main/skills/implement-spec
Command: npx skills add https://github.com/MSC72m/DevForge --skill implement-spec-msc72m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written specification with multiple tickets into working code requires coordinating many dependent tasks, branches, and reviews, which is slow and error-prone when done sequentially by hand. ## 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, each in its own git worktree and branch, with merger subagents integrating completed work. - End-to-End PR Workflow: Creates a draft PR linked to the spec issue, runs code review on completion, fixes findings, and cleans up worktrees. - Use Case: Given a spec issue with eight interdependent tickets, the Skill spins up parallel implementer agents, merges their branches as tickets unblock, and delivers one reviewed PR implementing the entire spec. ## Quick Start Ask the agent to implement the spec from the linked issue and its tickets as a single pull request.

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 with multiple tickets as one PR?▼

Read the spec and tickets to understand the task graph, create a branch and draft PR closing the spec issue, then run implementer subagents in parallel worktrees for each ready ticket. Merge completed work and kick off newly unblocked tickets until all are done.

How to run coding subagents in parallel on the same repository?▼

Give each implementer subagent its own git worktree and branch so concurrent work never conflicts. A separate merger subagent then integrates each finished branch into the shared PR branch.

Can subagents share exploration notes during implementation?▼

Yes. An exploration subagent saves markdown research notes to a directory outside the repo that all later subagents can read. This keeps implementer subagents focused on code rather than repeated exploration.

What happens after all spec tickets are implemented?▼

Run a code review on the PR branch, fix every raised issue in a single implementer subagent, mark the PR as ready for review, and clean up all implementer worktrees.

When should tickets not be implemented in parallel?▼

Tickets with blocking relationships must wait until their dependencies merge. Only the frontier of unblocked tickets should be worked concurrently, since implementing a blocked ticket early risks rework against changing code.

Related Skills

Explore More Software Engineering Skills→
willdadywilldady
63

to-tickets

Decomposes specs and plans into structured vertical-slice tickets with dependency mapping for GitHub or Linear.

Community
Advanced
bravrosbravros
3

finish

Merge approved pull requests, close plans, and route homolog-to-main decisions.

Official
Advanced
tense-itense-i
1

requesting-code-review

Dispatch a code-reviewer subagent after each task before merging to main.

Community
Intermediate
CasaPerksCasaPerks

sdd

Execute implementation plan tasks via isolated subagents with spec-first review.

Official
Advanced