Create Agile Epics

Guide the agent to systematically gather information and generate a comprehensive epic definition in Markdown format. An epic represents a large body of work that can be broken down into smaller user stories, features, or tasks. This is an interactive SKILL.

What is covered in this Skill?

• Epic core details: title/ID, owner, business value, target users
• Epic scope and context: problem statement, solution overview, success criteria, dependencies
• Epic breakdown: key features and components (3-7 high-level items)
• Risk assessment: risks, assumptions, and unknowns
• Documentation linking: related documents and epic filename
• Next steps and recommendations for epic management

Constraints

Before generating the epic document, gather all required information through structured questions. Use exact wording from the template and wait for user responses. Always get current date before starting.

• MANDATORY: Get current date using terminal command before starting the epic creation process
• MANDATORY: Ask questions from the template one-by-one in strict order before generating any artifacts
• MUST: Read the reference template fresh and use exact wording—do not use cached questions
• MUST: Wait for user response after each question or block before proceeding
• MUST: Replace all date placeholders with actual current date in the generated document

When to use this skill

• Create an agile epic
• Write an epic
• I need to create an epic
• Define an epic
• Epic definition

Reference

For detailed guidance, examples, and constraints, see references/012-agile-epic.md.