create-epics

Decompose approved elicitation documents into outcome-shaped epic markdown files.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/4797pnkkx5-gif/AI-Augmented-RE --skill create-epics-4797pnkkx5-gif
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-epics
Source: https://github.com/4797pnkkx5-gif/AI-Augmented-RE/tree/main/skills/create-epics
Command: npx skills add https://github.com/4797pnkkx5-gif/AI-Augmented-RE --skill create-epics-4797pnkkx5-gif

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts an approved Elicitation Document into a structured set of Epics so teams can move from raw stakeholder inputs to outcome-shaped, reviewable delivery containers.

Core Features & Use Cases

  • Decomposes approved requirements: Reads Accepted BUCs, FRs, NFRs, and constraints from the Elicitation Document and organizes them into Epic files.
  • Applies merge/split heuristics safely: Proposes merges or splits based on BUC coupling signals only at seeding time, using Open Questions for human confirmation.
  • Enforces coverage and immutability rules: Ensures Accepted FRs are assigned exactly once (cross-cutting NFRs allowed), validates key integrity checks, and protects Accepted/Rejected Epics from unintended regeneration.
  • Rebuilds an always-current index: Produces artifacts/02-epics/index.md with an Epic map, coverage matrices, aggregated Open Questions, and acceptance overview.

Quick Start

Run the create-epics skill after the elicitation document is approved by typing: /create-epics.

Frequently Asked Questions about create-epics

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

FAQPage Schema
How do I decompose approved requirements into epics for release planning?

To decompose approved requirements, this Skill translates Accepted BUCs and linked FRs, NFRs, and constraints from an approved elicitation document into outcome-shaped epic artifacts with per-epic markdown files.

What is BUC to epic mapping and how does it handle requirement traceability?

BUC to epic mapping organizes approved requirements into outcome-shaped delivery containers, ensuring requirement traceability by validating that Accepted FRs are assigned exactly once while permitting cross-cutting NFRs.

How do I merge or split epics based on requirement coupling?

Proposing to merge or split epics relies on BUC coupling signals at seeding time, generating Open Questions for human confirmation to safely restructure delivery containers.

How do I generate an epic index with coverage matrices and validation checks?

Generating an epic index rebuilds an always-current markdown file containing an epic map, coverage matrices, aggregated Open Questions, and acceptance overview by enforcing approval integrity gates and validation checks.

Can I regenerate pending epic content without overwriting accepted epics?

Regenerating Pending epic content from current epic files preserves approval integrity, as immutability rules protect Accepted and Rejected Epics from unintended regeneration during the rebuild process.

When should I not use automated epic generation for requirements decomposition?

Avoid automated epic generation when your elicitation document lacks approved BUCs or Accepted FRs, as the Skill enforces approval integrity gates and requires human confirmation for merge or split proposals.