epic-analyze

Decompose large-scale projects into independent sub-tasks with dependency analysis and risk assessment.

1|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/kubrickcode/specvital --skill epic-analyze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epic-analyze
Source: https://github.com/kubrickcode/specvital/tree/main/.claude/skills/epic-analyze
Command: npx skills add https://github.com/kubrickcode/specvital --skill epic-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill breaks down large, complex projects into smaller, manageable, and independent sub-tasks, making them easier to plan, execute, and track.

Core Features & Use Cases

  • Project Decomposition: Splits epics into minimal, session-independent work units.
  • Dependency Mapping: Identifies task dependencies and parallelizable workstreams.
  • Risk Assessment: Highlights technical uncertainties and external dependencies.
  • Use Case: When faced with a new feature request that involves significant development across multiple teams, use this Skill to define clear, actionable sub-tasks for each team, ensuring a smooth and coordinated rollout.

Quick Start

Use the epic-analyze skill to decompose the project described in the following text.

Frequently Asked Questions about epic-analyze

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

FAQPage Schema
How do I decompose large-scale projects into manageable sub-tasks?

To decompose large-scale projects, parse the project description to identify logical task boundaries, map dependencies, and assess technical risks. This process splits epics into minimal, session-independent work units suitable for phased workflow execution.

What is epic breakdown in project management and when do I need it?

Epic breakdown is the process of splitting complex initiatives into smaller, independent work units with clear dependency mapping and risk assessment. You need it for large feature requests involving multiple teams to ensure smooth, coordinated, and phased execution.

How do I identify parallelizable workstreams and task dependencies?

Identify parallelizable workstreams by parsing project descriptions and mapping task dependencies. This highlights which sub-tasks can run concurrently and which have external dependencies, ensuring clear work unit definition for coordinated execution.

Can I use task decomposition for complex multi-team feature rollouts?

Yes, you can use task decomposition for complex multi-team feature rollouts. It defines clear, actionable sub-tasks for each team by identifying logical boundaries, mapping dependencies, and highlighting technical uncertainties to ensure a coordinated rollout.

How do I assess technical risks and external dependencies during workflow planning?

Assess technical risks during workflow planning by parsing project descriptions to identify logical task boundaries and highlighting external dependencies. This risk assessment highlights uncertainties to ensure smooth execution of phased workflows.