implement-epic

Implements a GitHub epic as stacked PRs, one PR per child issue via gh stack.

3|Updated Feb 15, 2025
One-click install
npx skills add https://github.com/mark-torres10/ai_tools --skill implement-epic-mark-torres10
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-epic
Source: https://github.com/mark-torres10/ai_tools/tree/main/skills/implement-epic
Command: npx skills add https://github.com/mark-torres10/ai_tools --skill implement-epic-mark-torres10

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating the implementation of a large GitHub epic across many child issues is error-prone: branches get tangled, PRs lose traceability to issues, and CI failures cascade. This Skill automates the entire flow by turning each child issue into one stacked PR using gh stack, with an orchestrator agent per child. ## Core Features & Use Cases - Stacked PR Generation: Creates one PR per child issue on a gh stack branch chain, keeping each PR independently mergeable. - Per-Child Orchestration: Spawns a fresh orchestrator agent per child that runs create-implementation-plan, implement-plan-and-open-pr, and post-PR review subagents. - CI Gating and Traceability: Waits for GitHub checks after each PR, stops on failures, and links every PR with "Fixes #child" and "Part of #parent". - Final Cross-Stack Review: Runs a simplification and consistency review pass across the whole stack and opens a revision PR if needed. - Use Case: You have a parent issue with five filed child issues from create-epic. Run /implement-epic to get five stacked, CI-verified PRs plus a summary table, without writing orchestration logic yourself. ## Quick Start Run /implement-epic with the URL of a parent GitHub issue that already has child issues filed, then approve the proposed branch plan.

Frequently Asked Questions about implement-epic

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

FAQPage Schema
How do I implement a GitHub epic as stacked PRs?

Run /implement-epic with the parent issue URL. The skill lists the child issues, proposes a branch plan, and after your approval creates one stacked PR per child using gh stack, waiting for CI to pass before starting the next child.

How do I set up gh stack for stacked pull requests?

Install the extension with gh extension install github/gh-stack. The skill then runs gh stack init for the first child branch and gh stack add for subsequent branches, submitting each PR with gh stack submit --open.

What happens if CI fails on one PR in the stack?

The skill stops immediately and does not start the next child. Already-opened PRs are left as they are, and the checkpoint report shows which child failed so you can fix it before resuming.

When should I not use stacked PR implementation?

Do not use it when the epic and children have not been filed yet (use create-epic first), when you want a single plan and single PR (use implement-plan-and-open-pr), or when you need per-step approval before each commit (use interactive-implementation).

Does implement-epic merge or edit the parent issue?

No. The skill never merges PRs, never edits the parent issue body, and never uses a closing keyword on the parent. Each child PR body includes Fixes #child and Part of #parent for traceability only.