User Story Refinement with AI

This skill refines user stories using AI to ensure clarity, completeness, and alignment with product goals, reducing ambiguity and improving development efficiency.

תחום: ניהול מוצר

מתי להשתמש

Invoke when you have initial user stories that need to be improved for clarity, completeness, and adherence to best practices before being passed to development.

תגיות: user-stories, product-management, ai-refinement, agile, requirements-gathering

SKILL.md

--- name: User Story Refinement with AI description: This skill refines user stories using AI to ensure clarity, completeness, and alignment with product goals, reducing ambiguity and improving development efficiency. --- ## Overview This skill leverages AI to critically analyze and refine user stories. It checks for common pitfalls such as ambiguity, missing acceptance criteria, lack of clear user value, and misalignment with established product principles or technical constraints. The output provides suggestions for improvement, ensuring user stories are "ready" for development. ## When to use Use this skill immediately after drafting initial user stories or when reviewing existing user stories before a sprint planning meeting. It is particularly useful for product managers and business analysts looking to enhance the quality and readiness of their backlog items. ## How it works 1. **Input User Story**: Provide the user story you want to refine, along with any relevant context (e.g., product goal, persona, epic). 2. **AI Analysis**: The AI analyzes the user story against best practices for user story writing (INVEST criteria, clear acceptance criteria, implicit assumptions, etc.). It can also cross-reference with provided product documentation or a knowledge base. 3. **Identify Improvements**: The AI identifies areas for improvement, such as vague language, missing "As a... I want to... So that..." structure, lack of specific acceptance criteria, or potential technical dependencies. 4. **Suggest Refinements**: The skill outputs a revised user story or specific, actionable suggestions for improvement, including potential questions to ask stakeholders. 5. **Output Recommendations**: The output includes a refined user story, a list of identified issues, and suggested acceptance criteria. ## Example usage ```claude {{call_skill "User Story Refinement with AI" user_story="As a user, I want to log in quickly." context="Product goal: Increase user engagement by reducing friction in core workflows. Persona: New user."}} ``` **Example Output:** ```text **Original User Story:** As a user, I want to log in quickly. **AI Refinement Suggestions:** * **Ambiguity**: "Quickly" is subjective. Suggest defining a measurable metric. (e.g., "within 2 seconds on a standard broadband connection") * **Missing Acceptance Criteria**: No clear criteria for success. Add conditions such as "User is successfully authenticated," "User sees dashboard," "Error messages are clear for invalid credentials." * **Missing User Value (So that)**: While implied, explicitly state the benefit. (e.g., "So that I can access my personalized content without delay.") **Revised User Story:** As a new user, I want to log in within 2 seconds using my email and password, So that I can quickly access my personalized dashboard and begin my session without frustration. **Acceptance Criteria:** * Given I am on the login page, When I enter valid credentials and click "Login", Then I am redirected to my dashboard within 2 seconds. * Given I am on the login page, When I enter invalid credentials, Then I see a clear error message: "Invalid email or password." * Given I am on the login page, When I try to log in without entering credentials, Then I see an error message for each empty field. ``` ## References * [INVEST in Good User Stories](https://www.mountaingoatsoftware.com/agile/scrum/user-stories/invest) * [User Story Best Practices](https://www.atlassian.com/agile/project-management/user-stories) * [How to Write Acceptance Criteria](https://www.productplan.com/glossary/acceptance-criteria/)