epic-init

Decompose complex features into trackable sub-features with planning docs and tickets.

1|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/masta-g3/rules --skill epic-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epic-init
Source: https://github.com/masta-g3/rules/tree/main/skills/epic-init
Command: npx skills add https://github.com/masta-g3/rules --skill epic-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decompose a complex feature into trackable sub-features for an existing codebase to enable incremental delivery and clearer ownership.

Core Features & Use Cases

  • Atomic decomposition: Break down epics into small, testable features with clear outcomes.
  • Documentation & ticketing: Generate planning docs and register features via ticket-init, referencing related plans.
  • Multi-session planning: Supports coordinating work across sessions with feature IDs and dependencies.

Quick Start

Provide an epic description and I will decompose it into trackable features and generate the initial epic plan.

Frequently Asked Questions about epic-init

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

FAQPage Schema
How do I decompose a complex feature into trackable sub-features?

Decompose a complex feature by providing an epic description to generate atomic, testable sub-features with clear outcomes. This enables incremental delivery and establishes clearer ownership for an existing codebase.

How do I plan epics and generate documentation for multi-session development?

Plan epics and generate documentation by applying a stepwise workflow to multi-session development tasks. This generates initial epic plans and registers features with IDs and dependencies to coordinate work across sessions.

Can I integrate epic planning with ticket-init and reference existing planning docs?

Yes, epic planning integrates directly with ticket-init to register features and automatically references related planning docs. This ensures your atomic feature creation links directly to your ticketing system.

What is atomic feature decomposition and when do I need it for an existing codebase?

Atomic feature decomposition breaks down epics into small, testable features with clear outcomes. You need it when managing complex features in an existing codebase to enable incremental delivery and trackable sub-features.

Does epic planning support coordinating work across multiple development sessions?

Yes, epic planning supports coordinating work across multiple sessions by assigning feature IDs and mapping dependencies. This ensures multi-session development tasks remain synchronized and trackable.