epic-plan

Creates an execution roadmap with phases, milestones, and per-task guides from epic analysis documents.

1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/kubrickcode/cine-mirror --skill epic-plan-kubrickcode
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: epic-plan
Source: https://github.com/kubrickcode/cine-mirror/tree/main/.agents/skills/epic-plan
Command: npx skills add https://github.com/kubrickcode/cine-mirror --skill epic-plan-kubrickcode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After analyzing a large epic into sub-tasks, teams struggle to coordinate execution across multiple independent AI sessions that share no context. This Skill converts an epic analysis into a concrete execution plan with ordered phases, milestones, and self-contained task guides. ## Core Features & Use Cases - Execution Ordering: Finalizes phase structure and sequential/parallel task order based on dependencies from the analysis document. - Cold-Start Task Guides: Writes per-task execution guides specifying what to read, what prior tasks produced, key constraints, and the exact /workflow-analyze invocation. - Milestone Checkpoints: Defines 2-4 verification milestones with check conditions and fallback actions if conditions are not met. - Use Case: After running epic-analyze on a legacy migration project, run this Skill to produce docs/epic/{project}/plan.md so each sub-task can start in a fresh session with full context. ## Quick Start Run /epic-plan with your project name, for example "/epic-plan LEGACY-MIGRATION prioritize task 3", after completing epic-analyze.

Frequently Asked Questions about epic-plan

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

FAQPage Schema
How do I create an execution plan for a large epic?▼

Run /epic-plan with your project name after completing epic analysis. It reads docs/epic/{project}/analysis.md and generates plan.md with phases, milestones, and per-task execution guides for independent sessions.

How to coordinate multiple AI coding sessions on one project?▼

Write a plan document where each task guide specifies what to read, what prior tasks produced, key constraints, and the exact start command. This lets each session cold-start without prior conversation context.

When should tasks run in parallel versus sequentially?▼

Default to sequential execution. Only parallelize when tasks share no files, have no git merge conflict risk, no logical dependency, and touch truly independent domains of the codebase.

What happens if I run epic-plan before epic-analyze?▼

The command checks for docs/epic/{project-name}/analysis.md and errors with "Run /epic-analyze first" if it is missing. The analysis document is a mandatory prerequisite.

What are the limitations of epic-plan?▼

It cannot redefine or add sub-tasks beyond what analysis.md contains, does not estimate time in hours or days, and does not specify implementation details, which belong to the workflow-analyze step.