plan-epic

Decompose high-level requirements into vertically-sliced GitHub sub-issues.

3|Updated Jul 30, 2023
One-click install
npx skills add https://github.com/danielcopper/dotfiles --skill plan-epic-danielcopper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-epic
Source: https://github.com/danielcopper/dotfiles/tree/main/claude/.claude/skills/plan-epic
Command: npx skills add https://github.com/danielcopper/dotfiles --skill plan-epic-danielcopper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill bridges the gap between vague project ideas and actionable development tasks, ensuring that complex features are broken down into manageable, independently mergeable sub-issues.

Core Features & Use Cases

  • Structured Planning: Converts unstructured discussions or ideas into a formal epic with clear goals and constraints.
  • Vertical Slicing: Automatically suggests tracer-bullet sub-issues that maintain system integrity throughout the development process.
  • Native Integration: Publishes epics and sub-issues directly to your GitHub project board with proper linking and prioritization.

Quick Start

Invoke the plan-epic skill by providing a topic or issue number to begin the collaborative planning process.

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 high-level project requirements into actionable GitHub sub-issues?

To break down high-level requirements into GitHub sub-issues, the skill structures project epics by decomposing conceptual ideas into vertically-sliced, independently mergeable tasks. It facilitates the transition from formal planning to native GitHub project board management.

What is vertical slicing in project planning and how does it apply to epics?

Vertical slicing in project planning divides epics into tracer-bullet sub-issues that maintain system integrity throughout development. This technique ensures complex features are broken down into manageable, independently mergeable tasks rather than horizontal architectural layers.

Do I need GitHub CLI integration to publish epics and sub-issues to my project board?

Yes, GitHub CLI integration is required to publish epics and sub-issues directly to your GitHub project board. This native integration generates and links the formal task management items with proper prioritization.

Can I convert unstructured project discussions into structured epics automatically?

Yes, you can convert unstructured discussions into structured epics by invoking the skill with a topic or issue number. It transforms loose ideas into formal epics with clear goals and constraints through a collaborative planning process.

What's the best way to transition from conceptual discussion to formal task management on GitHub?

The best way to transition from conceptual discussion to formal task management on GitHub is using an epic structuring workflow that bridges vague ideas with actionable development tasks. It automatically suggests vertical slices and publishes them natively with proper linking.