012-agile-epic
This Claude Code skill guides systematic creation of comprehensive agile epics through structured questioning. Use it when you need to define large bodies of work, establish business value and success criteria, break features into user stories, or document strategic initiatives for software development projects.
git clone --depth 1 https://github.com/jabrena/cursor-rules-java /tmp/012-agile-epic && cp -r /tmp/012-agile-epic/skills/012-agile-epic ~/.claude/skills/012-agile-epicSKILL.md
# 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 0. **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 2. **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. 3. **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](references/012-agile-epic.md).
Use when you need to generate a checklist document with Java system prompts, following the embedded template exactly and producing INVENTORY-SKILLS-JAVA.md in the project root. This should trigger for requests such as Create Java system prompts checklist; Generate INVENTORY-SKILLS-JAVA.md; Use @001-skills-inventory. Part of cursor-rules-java project
Use when you need to generate a checklist document with embedded agents inventory, following the embedded template exactly and producing INVENTORY-AGENTS-JAVA.md in the project root. This should trigger for requests such as Create embedded agents inventory checklist; Generate INVENTORY-AGENTS-JAVA.md; Use @002-agents-inventory. Part of cursor-rules-java project
Use when you need to install the embedded robot agents into either .cursor/agents or .claude/agents, selecting the destination interactively and copying the embedded agent definitions from project assets. This should trigger for requests such as Install embedded agents; Bootstrap .cursor/agents; Bootstrap .claude/agents; Copy robot agents. Part of cursor-rules-java project
Guides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an epic into feature files, derive features with scope and acceptance criteria, or plan feature documentation for stakeholders or engineering. This should trigger for requests such as Create features from an epic; Split epic into features; Feature files from epic; Derive features from epic. Part of cursor-rules-java project
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project
Use when you need to generate Architecture Decision Records (ADRs) for a Java project through an interactive, conversational process that systematically gathers context, stakeholders, options, and outcomes to produce well-structured ADR documents. This should trigger for requests such as Generate ADR; Create Architecture Decision Record; Document architecture decision; Architecture Decision Record for Java. Part of cursor-rules-java project
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for functional requirements covering CLI, REST/HTTP APIs, or both. Use when the user wants to document command-line or HTTP service architecture, capture functional requirements, create ADRs for CLI or API projects, or design interfaces with documented decisions. This should trigger for requests such as Create ADR for functional requirements; Document functional requirements; Capture functional requirements; Generate functional requirements in an ADR. Part of cursor-rules-java project
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for non-functional requirements using the ISO/IEC 25010:2023 quality model. Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture, or design systems with measurable quality criteria. This should trigger for requests such as Create ADR for Non-functional requirements; Document Non-functional requirements; Capture Non-functional requirements; Generate Non-functional requirements in an ADR. Part of cursor-rules-java project