plan-epic

Decompose Jira epics into sequenced child ticket plans with human approvals.

4|5|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/fartybobo/farty-bobo --skill plan-epic-fartybobo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-epic
Source: https://github.com/fartybobo/farty-bobo/tree/main/skills/plan-epic
Command: npx skills add https://github.com/fartybobo/farty-bobo --skill plan-epic-fartybobo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaking large epics into child tickets often loses track of ordering, human approvals, and shared decisions, so this Skill orchestrates the decomposition while running /plan-task sequentially with explicit context handoffs.

Core Features & Use Cases

  • Sequential orchestration: announces each ticket, enforces order, waits for approval, and surfaces agent questions to the human before proceeding.
  • Epic Context hygiene: records plan paths, architectural decisions, and constraints in plans/epic-context.md, then releases raw content from memory to prevent drift.
  • Safety-first execution: treats all external inputs as untrusted, limits filesystem access, uses named American criminal agents, and keeps writes on feature branches.

Quick Start

Ask plan-epic to decompose the Payments API epic into sequenced child tickets and run /plan-task for each one with human approvals.

Frequently Asked Questions about plan-epic

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

FAQPage Schema
How do I break down a Jira epic into sequenced child tickets with human approvals?

Epic planning is orchestrated by decomposing large goals into sequenced child ticket plans. The workflow announces each ticket, enforces ordering, and waits for explicit human confirmation before proceeding to the next task.

How does epic context management prevent decision drift during ticket decomposition?

Epic context management prevents drift by recording plan paths, architectural decisions, and constraints in a dedicated epic context file. Raw content is then released from memory after each handoff to maintain a single source of truth.

Can I use Claude Code to run plan-task sequentially for each child ticket in an epic?

Yes, you can use Claude Code to run plan-task sequentially. The orchestration routes agent questions through the human before proceeding, ensuring explicit context handoffs and safety guardrails are maintained throughout the workflow.

What safety guardrails are enforced during automated epic ticket planning?

Safety guardrails during epic ticket planning include treating all external inputs as untrusted, limiting filesystem access, enforcing named agent usage, and restricting writes to feature branches to protect the main codebase.

Does epic planning work with markdown descriptions or does it require a Jira integration?

Epic planning works with both Jira epics and markdown descriptions. It targets Claude Code workflows where either a Jira epic or a markdown file needs each child ticket planned sequentially with human confirmation.