skills.rest
alex-jordan547
alex-jordan547COMMUNITY
Explore all skills by this author →
GitHub

implement-spec

Implements a specification as a single PR using concurrent subagent workers.

Updated Jul 3, 2026
Search Tags:#code review#pull request#subagents#worktree#parallel workflow#task graph#spec implementation
One-click install
npx skills add https://github.com/alex-jordan547/agent-setup --skill implement-spec-alex-jordan547
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement-spec
Source: https://github.com/alex-jordan547/agent-setup/tree/main/archive/2026-09-10/implement-spec
Command: npx skills add https://github.com/alex-jordan547/agent-setup --skill implement-spec-alex-jordan547

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written specification with many interdependent tickets into working code requires coordinating parallel work, managing branches, and keeping merges consistent, which is slow and error-prone when done manually. ## Core Features & Use Cases - Task Graph Execution: Treats tickets as a dependency graph and always works the current frontier of unblocked tickets for maximum concurrency. - Subagent Orchestration: Runs exploration, implementer, and merger subagents, each implementer in its own worktree and branch, with sparse context-pointer communication. - End-to-End PR Workflow: Creates a draft PR linked to the spec issue, merges completed ticket branches, runs code review, fixes findings, and cleans up worktrees. - Use Case: Given a spec issue with ten tickets, some blocking others, the Skill spins up implementer subagents for all ready tickets in parallel, merges each as it finishes, and delivers one reviewed PR implementing the entire spec. ## Quick Start Implement the spec in issue #42 and its associated tickets as a single pull request using parallel implementer subagents.

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 for each ready ticket in its own worktree. Merge completed work with merger subagents and finish with a code review pass.

How do I parallelize ticket implementation across subagents?▼

Treat tickets as a task graph with blocking relationships and always work the frontier of unblocked tickets. Run each implementer subagent in the background in its own worktree and branch, kicking off new subagents whenever merges unblock more tickets.

Can this workflow run on Codex?▼

Yes. On Codex, implementers and mergers run as native workers each in its own worktree, exploration runs as a read-only scout, and small pre-designed edits run as editor-fast, routed via the codex-orchestrator skill.

How should subagents share context during implementation?▼

Communicate through context pointers to the spec, tickets, research notes, and previous commits rather than duplicating information. Exploration notes should be saved as markdown files in a shared directory outside the repo accessible to all subagents.

What happens after all tickets are implemented?▼

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

Related Skills

Explore More Software Engineering Skills→
ArcReelArcReel
4.3k

wayfinder

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

Official
Advanced
RachasumanthRachasumanth

prepare-pr

Rebases GitHub PRs onto main branch and commits reviewed fixes with automated checks.

Community
Advanced
johwerjohwer

triage-issue

Explore codebases to identify bug root causes and create Jira tickets with TDD fix plans.

Community
Advanced
CasaPerksCasaPerks

sdd

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

Official
Advanced