skills.rest
IsKenKenYa
IsKenKenYaCOMMUNITY
Explore all skills by this author →
GitHub

implement-spec

Implements a full spec as one PR using concurrent subagents on a ticket task graph.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a multi-ticket spec into a single coherent pull request requires coordinating many dependent tasks, which is slow and error-prone when done sequentially by one agent. ## Core Features & Use Cases - Task Graph Execution: Treats tickets as a dependency graph with blocking relationships, always working the current 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. - Sparse Communication: Coordinates agents through context pointers to the spec, tickets, research notes, and commits instead of duplicating information. - Use Case: Given a spec issue with ten interdependent tickets, the Skill creates a draft PR, fans out implementer subagents as tickets unblock, merges their work, runs a code review pass, and marks the PR ready. ## Quick Start Ask the agent to implement the spec from 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 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 on the frontier of unblocked tickets. Merge each completed ticket into the PR branch and finish with a code review pass.

How do I run coding subagents in parallel on related tasks?▼

Give each implementer subagent its own git worktree and branch so their work stays isolated. Use a merger subagent to integrate completed work into the shared PR branch, and kick off new subagents whenever the ticket frontier advances.

What is a ticket task graph with a frontier?▼

Tickets are treated as nodes with blocking relationships rather than a sequential list. The frontier is the set of tickets whose blockers are all complete, making them ready to be worked on concurrently.

Can this skill be triggered automatically by the AI model?▼

No. The skill sets disable-model-invocation to true and its agent policy disallows implicit invocation, so it only runs when the user explicitly invokes it.

What happens after all tickets are implemented?▼

A code review is run on the PR branch and all raised issues are fixed in a single implementer subagent. The PR is then marked ready for review and all implementer worktrees are cleaned up.

Related Skills

Explore More Software Engineering Skills→
ArcReelArcReel
4.3k

wayfinder

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

Official
Advanced
richard-jh-mccraerichard-jh-mccrae

code-review

Reviews code changes since a reference point against standards and spec requirements.

Community
Intermediate
vishirivishiri
401

fantasia-worldbuilding-domain

Align AI suggestions with Fantasia Archive's worldbuilding domain terminology and data models.

Community
Intermediate
CasaPerksCasaPerks

sdd

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

Official
Advanced