create-epics-and-stories

Decompose product requirements into epics and stories with acceptance criteria.

9|66|Updated Oct 13, 2025

Search Tags:#workflow #planning #requirements #validation #epics #stories

Ready to run

npx skills add https://github.com/salazarsebas/Cougr --skill create-epics-and-stories

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-epics-and-stories
Source: https://github.com/salazarsebas/Cougr/tree/main/.claude/skills/create-epics-and-stories
Command: npx skills add https://github.com/salazarsebas/Cougr --skill create-epics-and-stories

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides teams in breaking down product requirements into epics and stories, ensuring each work item is user-value oriented and independently deliverable.

Core Features & Use Cases

Step-file driven workflow with strict sequential execution to maintain process integrity
Generates epic and story artifacts from FRs, NFRs, and UX inputs when provided
Frontmatter-based progress tracking and persistent facts to support iterative refinement
Templates and conventions that ensure consistent formatting and documentation
Interactive validation and approval loops to align with product strategy

Quick Start

Begin by loading this skill and following Step 1 to validate prerequisites and extract requirements.

Frequently Asked Questions about create-epics-and-stories

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

FAQPage Schema

How do I decompose product requirements into epics and stories?▼

Decomposing product requirements into epics and stories involves mapping PRD, architecture, and UX artifacts into structured work items with clear acceptance criteria and frontmatter-tracked progress to ensure complete coverage of FRs, NFRs, and UX considerations.

What is the best way to break down product requirements for organized development planning?▼

Breaking down product requirements for organized development planning is best achieved through a step-file driven workflow with strict sequential execution, ensuring each epic and story is user-value oriented and independently deliverable with consistent formatting.

Can I map non-functional requirements and UX constraints into development stories?▼

Yes, you can map non-functional requirements and UX constraints into development stories. The workflow generates epic and story artifacts from FRs, NFRs, and UX inputs, ensuring complete coverage by architecture constraints and UX considerations with interactive validation.

How do I track progress and maintain iterative refinement when creating epics and stories?▼

You track progress and maintain iterative refinement when creating epics and stories by using frontmatter-based progress tracking and persistent facts within the generated artifacts, applying templates and conventions that ensure consistent formatting and documentation.

Do I need a PRD to start generating epics and stories?▼

You do not strictly need a PRD to start, but you must validate prerequisites and extract requirements in the first step. The workflow applies to PRD, architecture, and UX artifacts, generating structured epics and stories from available FRs, NFRs, and UX inputs.

How does interactive validation work when mapping requirements to epics?▼

Interactive validation when mapping requirements to epics works through approval loops that align the generated stories with your product strategy, verifying that each work item is user-value oriented and independently deliverable before activation.