user-story-writing_skill

Overview

This skill creates well-structured user stories in the 'As a / I want / So that' format with clear, testable acceptance criteria and a simple complexity estimate. It helps teams communicate requirements, focus on user value, and break features into implementable pieces. The output is ready for sprint planning and handoff to development or QA.

How this skill works

I identify the user role or persona, define the goal they want to achieve, and state the business or user value. I then produce 3–5 specific acceptance criteria that are measurable and list a lightweight complexity estimate (story points or T-shirt size). The result is a concise story ready for backlog grooming and sprint inclusion.

When to use it

• Defining a new feature from the user perspective
• Breaking a large feature into smaller, implementable stories
• Preparing items for sprint planning or backlog refinement
• Communicating requirements clearly to developers and QA
• Creating acceptance tests and definition of done

Best practices

• Keep each story small and focused — ideally completable in 1–3 days
• Write from the user perspective; avoid system-internal language
• Make acceptance criteria specific, measurable, and testable
• Avoid implementation details; capture intent and constraints instead
• Include a simple complexity estimate to help prioritization

Example use cases

• Turn a product idea into a prioritized, testable backlog item
• Split a monolithic feature into multiple, deliverable stories
• Create acceptance criteria for QA to validate feature completeness
• Prepare developer-ready tasks for a sprint planning session
• Document user-facing behavior for cross-functional alignment