breakdown-plan

Generate project breakdown plans with Epic, Feature, Story/Enabler, and Test hierarchies.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/voidrot/agents --skill breakdown-plan-voidrot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: breakdown-plan
Source: https://github.com/voidrot/agents/tree/main/skills/meta/breakdown-plan
Command: npx skills add https://github.com/voidrot/agents --skill breakdown-plan-voidrot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill aids in breaking down complex projects or GitHub issues into a structured hierarchy of epics, features, stories/enablers, and tests, ensuring a clear and organized plan with dependencies and tracking artifacts.

Core Features & Use Cases

  • Project Decomposition: Automatically decompose projects or issues into a comprehensive breakdown plan.
  • Hierarchy Creation: Build a structured hierarchy of epics, features, stories/enablers, and tests.
  • Dependency Tracking: Manage dependencies and priorities between different project components.
  • Tracking Artifacts: Generate tracking artifacts for project management and progress tracking.
  • Use Case: For a software development project, use this Skill to create a detailed plan starting from the epic level down to individual tasks and tests.

Quick Start

Generate a breakdown plan for a new project 'project-x' by running the breakdown-plan skill.

Frequently Asked Questions about breakdown-plan

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

FAQPage Schema
How do I break down a complex project into epics, features, and stories?

To break down a complex project into epics, features, and stories, this Skill automates project decomposition into a structured hierarchy. It generates a comprehensive breakdown plan that includes dependencies, priorities, and tracking artifacts for clear organization.

What is the best way to decompose a GitHub issue into a structured hierarchy for tracking?

The best way to decompose a GitHub issue into a structured hierarchy is by automating issue breakdown plans. This Skill transforms issues into Epic > Feature > Story/Enabler > Test layers, managing dependencies and priorities to produce detailed tracking artifacts.

Can I use this project decomposition tool to generate tracking artifacts for software development?

Yes, you can use this project decomposition tool to generate tracking artifacts for software development. It automatically creates detailed plans and issue tracking artifacts from your project inputs, ensuring organized progress tracking across the entire Epic to Test hierarchy.

How does dependency tracking work when creating a breakdown plan from an epic to tests?

Dependency tracking in a breakdown plan works by mapping relationships across the Epic > Feature > Story/Enabler > Test hierarchy. It automatically identifies and manages dependencies and priorities between different project components to ensure a coherent execution sequence.

What do I need to start generating a breakdown plan for a new software project?

To start generating a breakdown plan for a new software project, you need to provide the initial project or issue details. The Skill then automatically decomposes these inputs into a structured plan with dependencies, priorities, and tracking artifacts without requiring external dependencies.

Are there limitations when using automated issue breakdown plans for large scale projects?

Automated issue breakdown plans for large scale projects rely entirely on the initial project or issue details provided. While it automatically structures epics, features, stories, and tests with dependencies, the accuracy of the generated tracking artifacts depends on the clarity of your base inputs.