014-agile-user-story
This Claude Code skill guides the interactive creation of agile user stories and Gherkin feature files by asking structured questions about user personas, goals, and acceptance criteria, then generating both a Markdown user story document and a separate feature file with Given-When-Then scenarios. Use it when you need to develop user stories, define BDD acceptance criteria, or author feature files for testing purposes.
git clone --depth 1 https://github.com/jabrena/cursor-rules-java /tmp/014-agile-user-story && cp -r /tmp/014-agile-user-story/skills/014-agile-user-story ~/.claude/skills/014-agile-user-storySKILL.md
# Create Agile User Stories and Gherkin Feature Files Guide the agent to ask targeted questions to gather details for a user story and its Gherkin acceptance criteria, then generate a Markdown user story and a separate Gherkin `.feature` file. **This is an interactive SKILL**. **What is covered in this Skill?** - User story core details: title, persona, goal, benefit - Gherkin feature file: Feature name, background steps, scenarios - Acceptance criteria: Given / When / Then with data examples - File naming and linking between user story and feature file - INVEST quality validation before finalization (Independent, Negotiable, Valuable, Estimable, Small, Testable) ## Constraints Before generating artifacts, gather all required information through structured questions. Use exact wording from the template and wait for user responses. - **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**: Repeat scenario questions for each additional scenario when user indicates more scenarios - **MUST**: Validate the final user story against INVEST and present a pass/fail checkpoint for each criterion before finalizing ## When to use this skill - Create a user story - Write a user story - I need to write a user story ## Workflow 1. **Gather story and scenario details** Run the interactive questionnaire in strict order and wait for user responses before moving to the next question block. Step constraints: - Use the exact wording from the referenced template - Repeat scenario questions for each additional scenario requested by the user 2. **Generate the two artifacts** Create the user story Markdown and Gherkin `.feature` content using only gathered inputs, including links between files and scenario tags. 3. **Validate quality before finalizing** Check output completeness and provide an INVEST pass/fail checkpoint with concrete evidence for each criterion. ## Reference For detailed guidance, examples, and constraints, see [references/014-agile-user-story.md](references/014-agile-user-story.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 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
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
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