epic-planning

Name: epic-planning
Availability: InStock
Author: aidensbvevo

Decompose project epics into PR-sized Linear issues with acceptance criteria.

1|Updated Jul 5, 2026

Search Tags:#workflow #planning #project management #agile #decomposition #linear

Ready to run

npx skills add https://github.com/AidenSbVevo/claude-code-starter --skill epic-planning-aidensbvevo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: epic-planning
Source: https://github.com/AidenSbVevo/claude-code-starter/tree/main/skills/epic-planning
Command: npx skills add https://github.com/AidenSbVevo/claude-code-starter --skill epic-planning-aidensbvevo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of poorly defined project epics that lead to scope creep, vague requirements, and misaligned development efforts by enforcing a structured decomposition process.

Core Features & Use Cases

Structured Decomposition: Breaks down high-level goals into PR-sized Linear issues with clear acceptance criteria and verification steps.
Dependency Mapping: Ensures tasks are ordered logically and blocking relations are explicitly recorded.
Use Case: When starting a new feature area, use this skill to investigate the codebase, define concrete acceptance criteria, and generate a set of ready-to-implement tickets in Linear.

Quick Start

Invoke the epic-planning skill by asking the assistant to decompose your current epic goal into actionable Linear issues.

Frequently Asked Questions about epic-planning

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

FAQPage Schema

How do I decompose project epics into actionable Linear issues?▼

Decomposing project epics into actionable Linear issues requires investigating your codebase architecture to break high-level goals into granular, PR-sized tickets with defined acceptance criteria and verification commands. This structured decomposition prevents scope creep and misaligned development efforts.

What is the best way to map dependencies for multi-week development cycles?▼

Mapping dependencies for multi-week development cycles involves identifying codebase entry points and establishing logical blocking relations between tasks. This ensures newly created Linear issues are ordered correctly and explicitly records what blocks downstream development work.

How do I generate ready-to-implement tickets with clear acceptance criteria?▼

Generating ready-to-implement tickets with clear acceptance criteria requires investigating your codebase architecture and breaking down epics into PR-sized Linear issues. Each issue receives defined acceptance criteria and specific verification commands to ensure implementation readiness.

Can I review Linear issues before they are created to align with team taxonomy?▼

You can review Linear issues before they are created because the decomposition process requires explicit user approval. This ensures the generated PR-sized tickets align with your team taxonomy and project goals before any tickets are actually created in Linear.

When do I need structured epic decomposition for agile project management?▼

Structured epic decomposition for agile project management is needed when starting a new feature area with poorly defined project epics. It prevents vague requirements and scope creep by enforcing a process to investigate the codebase and generate concrete, actionable tickets.

Why does epic decomposition require investigating the codebase architecture?▼

Epic decomposition requires investigating the codebase architecture to identify entry points and establish dependency chains for multi-week development cycles. This investigation grounds the generated Linear issues in your actual technical structure rather than abstract planning.