epic-author

Generate structured epic documentation and update the epic index for multi-PR initiatives.

18|Updated Feb 14, 2020
One-click install
npx skills add https://github.com/subroh0508/colormaster --skill epic-author
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epic-author
Source: https://github.com/subroh0508/colormaster/tree/main/.claude/skills/epic-author
Command: npx skills add https://github.com/subroh0508/colormaster --skill epic-author

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual overhead of setting up multi-PR epics, keeping epic documentation, index pages, and roadmap tracking consistent from the start.

Core Features & Use Cases

  • Epic Skeleton Generation: Creates a new docs/epics/EPIC-NNN-<slug>/ folder from the template with README, roadmap, open-questions, decisions, and progress files.
  • Index Maintenance: Updates docs/epics/INDEX.md so new epics are discoverable and organized.
  • Roadmap Handoff: Immediately triggers roadmap-tracker so the new epic is incorporated into the overall delivery plan.
  • Use Case: Use it when a large initiative is being promoted from a plan into a formal epic and needs a standard documentation trail.

Quick Start

Ask the epic-author skill to create a new epic from the template, update the epic index, and hand it off to roadmap tracking.

Frequently Asked Questions about epic-author

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

FAQPage Schema
How do I generate structured documentation for a new multi-PR epic?

To generate epic documentation, you can trigger the epic skeleton generation process. This creates a standard folder structure under docs/epics/ containing README, roadmap, open-questions, decisions, and progress files for your multi-PR initiative.

What is the best way to keep an epic index current when adding new initiatives?

Keeping an epic index current requires updating the docs/epics/INDEX.md file whenever a new initiative is added. The automation handles this index maintenance automatically, ensuring new epics remain discoverable and organized without manual markdown editing.

How does epic documentation integrate with roadmap tracking?

Epic documentation integrates with roadmap tracking through an immediate handoff. After creating the standard epic file set, the process triggers roadmap-tracker to incorporate the newly documented initiative into the overall delivery plan.

Do I need to update frontmatter when promoting a plan to an epic?

Yes, promoting a plan to an epic requires frontmatter updates. You must update the status, promoted_to, and expected_modules fields within the generated documentation to ensure proper tracking and alignment throughout the initiative's lifecycle.

When should I use an automated epic skeleton instead of manual documentation?

Use an automated epic skeleton when a large initiative is being promoted from a plan into a formal epic. It removes the manual overhead of setting up multi-PR epics and ensures documentation, index pages, and roadmap tracking remain consistent from the start.