skills.rest
pnewsam
pnewsamCOMMUNITY
Explore all skills by this author →
Website𝕏@paultakumaGitHub

plan-epic

Decompose an initiative into independently reviewable work units with dependencies and integration proof.

1|Updated Apr 15, 2026
Search Tags:#pull request#project planning#initiative#epic planning#dependency graph#sequencing#work decomposition
One-click install
npx skills add https://github.com/pnewsam/skills --skill plan-epic-pnewsam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-epic
Source: https://github.com/pnewsam/skills/tree/main/registry/plan-epic
Command: npx skills add https://github.com/pnewsam/skills --skill plan-epic-pnewsam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Large initiatives are hard to execute when they arrive as one undifferentiated block of work. This Skill breaks an agreed initiative into independently reviewable units (normally one PR each), maps their dependencies, and defines the integration evidence needed to prove the whole effort succeeds. ## Core Features & Use Cases - Work Unit Decomposition: Splits an initiative into units with stable identities, acceptance summaries, dependencies, and delivery boundaries, avoiding horizontal splits that leave behavior broken. - Dependency Sequencing: Represents dependency edges and satisfaction conditions, detects cycles or blocked prerequisites, and plans integration checkpoints beyond individual unit tests. - Initiative Record Management: Creates or updates a single epic record (using the references/epic-record.md template) preserving existing IDs, completed history, and source observation coverage. - Use Case: A team agrees to migrate a dashboard to a new API. Use this Skill to produce a dependency graph of reviewable PR-sized units, identify the next ready unit, and define the combined acceptance criteria before any code is written. ## Quick Start Use plan-epic to decompose the dashboard migration initiative into reviewable work units with dependencies and integration checkpoints.

Frequently Asked Questions about plan-epic

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

FAQPage Schema
How do I break an epic into smaller pull requests?▼

Define each unit around an independently reviewable outcome with a stable identity, acceptance summary, dependencies, and delivery boundary. Avoid horizontal splits that leave required behavior broken until a future unit, and keep atomic changes together in one PR.

How do I manage dependencies between work units in an epic?▼

Represent each dependency as an edge with a satisfaction condition, such as an API contract on a branch or a prerequisite merged. Detect cycles before execution, and use stacked branches only when the repository and request permit them.

When should I use epic planning versus planning a single task?▼

Use epic planning when an initiative spans several coordinated work units that need sequencing and integration proof. A single bounded outcome belongs to plan-work, and shape-initiative applies only when the direction remains materially unclear.

Does epic planning require fully detailed plans for every unit upfront?▼

No. Write enough child scope to begin, and detail future children just in time while keeping their boundaries and dependency conditions explicit. Use plan-work just before executing a child when details depend on earlier results.

What are the limitations of epic decomposition?▼

This Skill does not implement or publish changes, and creating external projects or issues is a separate requested effect handled through runbooks. Individual green units do not establish integration, so combined acceptance must be verified separately.

Related Skills

Explore More Product & Management Skills→
jamestexasjamestexas
2

work-scope

Decompose feature work into reviewable, single-purpose pull requests.

Community
Advanced
divad12divad12
25

autopilot

Coordinate parallel worktree agents through implement, critique, deep-review, and ship cycles.

Community
Advanced
v20227v20227
3

sakura-verify

Validates software changes through executable tests, builds, and runtime evidence.

Community
Advanced
sumitakesumitake

orchestrate

Coordinate multi-step tasks through a bounded dependency graph with acceptance checks and operator gates.

Community
Advanced