epic-discover

Analyze code and documentation to define project epics.

2|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/telum-ai/speck --skill epic-discover
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epic-discover
Source: https://github.com/telum-ai/speck/tree/main/.cursor/skills/epic-discover
Command: npx skills add https://github.com/telum-ai/speck --skill epic-discover

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the identification and definition of epics within a software project by analyzing existing code and documentation, streamlining project planning.

Core Features & Use Cases

  • Code Analysis: Scans codebase structure, semantic patterns, and dependencies to identify potential epic boundaries.
  • Documentation Review: Incorporates existing project documentation to inform epic definitions.
  • Use Case: When starting a new large feature, use this Skill to automatically suggest how to break it down into manageable epics based on your current codebase.

Quick Start

Use the epic-discover skill to analyze the current project and identify potential epics.

Frequently Asked Questions about epic-discover

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

FAQPage Schema
How do I discover epics from existing code and documentation?

Epic discovery evaluates candidate boundaries using structural and semantic code analysis, measuring cohesion, independence, and value to generate specifications. It supports domain-driven and legacy codebases to streamline project planning.

Can I use code analysis to break down a large feature into manageable epics?

Yes, code analysis scans your codebase structure, semantic patterns, and dependencies to suggest how to break down a large feature into manageable epics based on your current project architecture and existing documentation.

Does epic discovery work with legacy codebases or only domain-driven projects?

Epic discovery supports both legacy codebases and domain-driven projects. It performs structural and semantic code analysis to evaluate epic candidates based on cohesion and independence, recommending next steps for refinement and planning.

What is the best way to define project epics from a codebase?

The best way to define project epics is to analyze structural patterns and dependencies, evaluate potential boundaries for cohesion and value, and generate epic specifications that inform agile project planning and requirements gathering.

When do I need automated epic discovery for project planning?

You need automated epic discovery when starting a new large feature or streamlining agile planning, using structural and semantic code analysis to identify potential epic boundaries and define project specifications from existing codebases.