epic-doc-generator

Generate Epic markdown documents from a Spec Funcional and optional TDD.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/Avila-Tek/avila-tek-skill-pack --skill epic-doc-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epic-doc-generator
Source: https://github.com/Avila-Tek/avila-tek-skill-pack/tree/main/skills/planning-4-epic-generator
Command: npx skills add https://github.com/Avila-Tek/avila-tek-skill-pack --skill epic-doc-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Generates cohesive Epic documents from a Spec Funcional and an optional TDD to streamline sprint planning and backlog management.

Core Features & Use Cases

  • Reads the Spec Funcional (primary source) and optional TDD to extract epics
  • Creates standalone epic documents with sections: References, Objective, Scope, Happy Path, KPIs & Measurement, and User Stories
  • Outputs epics into the docs/epics/ directory with IDs like E-001 and a snake_case title for easy navigation
  • Reuses the canonical Epic template to ensure consistency and alignment with planning workflows
  • Supports [TO BE DEFINED] placeholders for any missing data

Quick Start

Provide a Spec Funcional (and optional TDD) and run the Epic Document Generator to generate epic documents.

Frequently Asked Questions about epic-doc-generator

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

FAQPage Schema
How do I generate epic documents from a functional spec for sprint planning?

Epic documents are generated by reading a Spec Funcional and optional TDD to extract epics, then creating markdown files with sections like Objective, Scope, and User Stories under docs/epics. This streamlines sprint planning and backlog management by producing cohesive epic documents.

What sections are included in an epic document for backlog management?

Epic documents include References, Objective, Scope, Happy Path, KPIs & Measurement, and User Stories sections. They are generated from a Spec Funcional and assign IDs like E-001 to support structured backlog management and sprint planning.

How are generated epic documents named and stored in the project directory?

Generated epic documents are stored as markdown files under docs/epics with directory names like E-001_<snake_case_title>/epic.md. ID assignments are sourced directly from the Spec Funcional to ensure consistent navigation and backlog tracking.

Can I generate epics from a Spec Funcional without a TDD document?

You can generate epic documents using only the Spec Funcional as the primary source, as the TDD is optional. The generator applies [TO BE DEFINED] placeholders for any missing data gaps to ensure the epic structure remains intact for sprint planning.

What happens when the functional spec has missing data for the epic scope?

When the Spec Funcional has missing data, the epic document generator inserts [TO BE DEFINED] placeholders for those gaps. This ensures the canonical epic template structure remains complete and consistent for subsequent backlog refinement.

Is this epic generator suitable for teams using standard sprint planning workflows?

This epic generator is designed for teams using standard sprint planning and backlog management workflows. It reuses a canonical Epic template to ensure consistency and alignment with planning processes by outputting structured markdown documents.