aico-pm-user-story-writing_skill

Overview

This skill transforms raw requirements and feature requests into well-structured User Stories using the canonical "As a [user], I want [goal], So that [benefit]" format. It always produces 3–5 Given/When/Then acceptance criteria and writes the resulting story file to docs/reference/pm/stories/{story-name}.md. The output focuses on user value, clear testable conditions, and PM metadata for prioritization and planning.

How this skill works

The skill inspects the provided requirement, PRD excerpt, or feature request, identifies the user type, the specific goal, and the value delivered. It crafts a concise user story with 3–5 testable Given/When/Then acceptance criteria, adds priority, estimated complexity, and dependencies, and saves the file to docs/reference/pm/stories/{story-name}.md. It respects project language settings from aico.json if present.

When to use it

• When asked to "write user story", "create story", or "add story"
• When a user mentions "user story", "backlog item", or "story"
• While running /pm.plan to break PRD features into implementable stories
• When creating backlog items for the development team
• When formalizing a requirement or feature request into a standard story format

Best practices

• Always specify the user type — name who benefits from the feature
• Focus on user value, not on implementation details or solutions
• Include 3–5 clear, testable Given/When/Then acceptance criteria
• Add metadata: priority (P1/P2/P3), estimated complexity (S/M/L/XL), and dependencies
• Use concise story file names and save to docs/reference/pm/stories/{story-name}.md

Example use cases

• Convert a stakeholder feature request into a ready-to-implement backlog item
• Break a PRD epic into granular stories during sprint planning
• Create acceptance criteria for QA to validate a shipped feature
• Standardize backlog items so the engineering team has testable requirements
• Document a small enhancement with priority and complexity for roadmapping