User Story Writing

This skill acts as a specialized assistant for Product Owners, Business Analysts, and software engineering teams, designed to bridge the gap between abstract user needs and technical implementation. By enforcing the standard 'As a/I want/So that' (Role-Goal-Benefit) framework, it ensures that every task serves a clear business purpose and is aligned with user-centric outcomes rather than just technical output.

The assistant helps decompose complex feature requests into smaller, actionable units of work that can be completed within standard sprint cycles. It focuses on crafting precise and testable acceptance criteria, which are essential for QA engineers and developers to validate success. By ensuring that technical details are separated from requirement definitions, the skill helps maintain focus on delivering genuine value to the user while keeping the development process organized and transparent.

• Standardized Story Structure: Automatically formats input into the classic 'As a/I want/So that' Agile syntax for consistency.

• Testable Acceptance Criteria: Generates comprehensive checklists (Gherkin-style or bulleted) that define the 'Definition of Done' for every story.

• Value-Driven Analysis: Encourages articulation of business value and user benefits, ensuring the 'So that' component is always meaningful.

• Complexity Estimation: Supports optional complexity assessment using relative sizing techniques like story points or T-shirt sizing (e.g., S, M, L, XL).

• Persona Development: Identifies and defines the target persona for each story to ensure empathy and context during development.

• Best Practices: Stories should ideally be small enough to deliver in 1-3 days. Focus on 'what' the user needs rather than 'how' the system builds it.

• Input/Output: Provide a rough feature idea, a target persona, or a project goal; receive a refined user story block including a title, user story statement, acceptance criteria list, and an optional complexity estimate.

• Usage: Ideal for sprint planning, backlog grooming, and requirement gathering sessions within a Jira, GitHub, or Azure DevOps context.

• Constraints: Avoid injecting low-level technical implementation details; keep the focus on functional requirements to maintain cross-team accessibility.