implement-epic

Implements all child tickets of an epic sequentially with gate-checked pipelines.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/ttnhan18062000/rpg-based-simulation --skill implement-epic-ttnhan18062000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-epic
Source: https://github.com/ttnhan18062000/rpg-based-simulation/tree/main/.agents/skills/implement-epic
Command: npx skills add https://github.com/ttnhan18062000/rpg-based-simulation --skill implement-epic-ttnhan18062000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large initiatives split across many tickets are tedious to execute one by one, and it is easy to lose track of which tickets are done, which failed a gate, and what remains. This Skill orchestrates the full implementation of every ticket in a folder or epic, sequentially and with per-ticket gate enforcement. ## Core Features & Use Cases - Epic and folder discovery: Accepts a ticket folder path, an existing epic ID, or a natural-language request that creates a new epic ticket first. - Sequential gated execution: Runs the full implement-ticket pipeline for each pending ticket in order, stopping on the first gate failure and reporting which ticket blocked and why. - Resumable batches: Re-checks tickets/done/ on every run so already-completed tickets are skipped automatically after a fix. - Batch monitoring: Writes per-ticket monitoring records plus one batch record (EPIC-{id} or FOLDER-{path}), and moves completed folders from tickets/todos/ to tickets/done/. - Use Case: You have a monitoring epic with eight child tickets in tickets/todos/monitoring/. Run the skill with that folder to implement each ticket through its gated pipeline, get a DONE/failure summary, and resume later if a gate blocks ticket four. ## Quick Start Ask the agent to implement the epic by running implement-epic with folder=tickets/todos/monitoring/ and let it execute each child ticket sequentially.

Frequently Asked Questions about implement-epic

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

FAQPage Schema
How do I implement all tickets in an epic at once?

Run implement-epic with a folder path, an epic_id, or a natural-language request. It discovers pending tickets, runs the full implement-ticket pipeline for each one sequentially, and reports DONE counts, gate failures, and remaining tickets.

How do I resume an epic after a ticket gate failure?

Fix the blocking issue, then re-run implement-epic with the same folder or epic_id. The Discover phase re-checks tickets/done/ each run, so already-completed tickets are skipped and execution resumes from the first pending ticket.

Does implement-epic run child tickets in parallel?

No. Child tickets execute strictly sequentially, one fully completed before the next starts. The workflow stops on the first non-DONE result and reports which ticket blocked the batch and why.

What happens when I pass a natural-language request instead of a folder?

The skill creates a new epic ticket from the request and returns EPIC_CREATED without implementing anything. Re-run it with the new epic_id to start the actual implementation loop.

Can I edit a gate artifact to make a failing check pass?

No. The Gate Integrity rule forbids editing gate-relevant artifacts to force a check to pass, whether directly or through any delegated sub-agent. The failure must be fixed in the underlying work, not the gate.