epic-plan

Name: epic-plan
Availability: InStock
Author: Telum

Generate technical specifications for epic implementation from requirements and research.

2|Updated Dec 21, 2025

Search Tags:#planning #architecture #research #software development #technical specification #epic

Ready to run

npx skills add https://github.com/telum-ai/speck --skill epic-plan-telum-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: epic-plan
Source: https://github.com/telum-ai/speck/tree/main/.cursor/skills/epic-plan
Command: npx skills add https://github.com/telum-ai/speck --skill epic-plan-telum-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill transforms high-level epic requirements into detailed technical specifications, ensuring a clear path from concept to actionable development tasks.

Core Features & Use Cases

Technical Specification Generation: Creates comprehensive blueprints for epic implementation.
Research Integration: Leverages just-in-time research for patterns, libraries, and strategies.
Architecture Decision Support: Guides whether a separate architecture deep-dive is needed.
Use Case: When a new major feature (epic) is defined, this Skill analyzes its requirements, researches necessary technologies, and outputs a detailed technical spec that developers can use to break down the work into stories.

Quick Start

Use the epic-plan skill to create a technical specification for the epic described in epic.md.

Frequently Asked Questions about epic-plan

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

FAQPage Schema

How do I create a technical specification for an epic from high-level requirements?▼

A technical specification for an epic is generated by analyzing high-level requirements, conducting just-in-time research on patterns, and scanning the existing codebase architecture to produce a durable, implementable blueprint for story breakdown.

What is the best way to break down a major feature into implementable development stories?▼

The best way to break down a major feature is to generate a technical specification that embeds just-in-time research and architecture decisions, creating a durable blueprint directly aligned with implementable development stories.

When do I need a separate architecture document for software development planning?▼

A separate architecture document is needed when the epic's complexity exceeds standard technical specification parameters. The planning process analyzes epic requirements and codebase scans to determine whether a standalone architecture deep-dive is necessary.

Can I integrate just-in-time research directly into a technical specification?▼

Yes, you can integrate just-in-time research directly into a technical specification. The process leverages just-in-time research for patterns, libraries, and strategies, embedding findings directly to support architecture decisions and story breakdown.

Does epic planning work with existing codebase scans and architecture?▼

Yes, epic planning works with existing codebase scans and architecture. The technical specification process explicitly considers existing codebase scans and architecture to ensure the resulting blueprint aligns with current system structures and constraints.

What are the limitations of using a generated technical specification for story breakdown?▼

The limitation of a generated technical specification is its dependence on initial epic requirements and codebase scans. If high-level requirements are vague or the codebase scan is incomplete, the resulting blueprint may require manual adjustments before story breakdown.