AugmentClaude
Apache-2.0PMRoadmaps

Agile Epic Creator

Create comprehensive agile epics with business value, success criteria, and user stories.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/012-agile-epic-jabrena/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives. This should trigger for requests such as Create an agile epic; Write an epic; I need to create an epic; Define an epic; Epic definition. Part of cursor-rules-java project

What this skill does

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

Workflow

  1. Get current date

Run date before starting and use it to replace all date placeholders in the generated epic document.

  1. Gather epic information

Ask the template questions in strict order, using exact wording and waiting for user responses before continuing.

Step constraints:

  • Read the question template fresh before asking
  • Do not skip or reorder required questions
  1. Generate epic document

Create the epic Markdown with all required sections (scope, value, features, dependencies, risks, and success criteria) and apply the actual current date.

  1. Provide follow-up recommendations

Close with actionable next steps for story breakdown, planning, and epic tracking.

Reference

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

Related skills