user-stories
Scannednpx machina-cli add skill phuryn/pm-skills/user-stories --openclawUser Stories
Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria. Generates stories with descriptions, design links, and acceptance criteria.
Use when: Writing user stories, breaking down features into stories, creating backlog items, or defining acceptance criteria.
Arguments:
$PRODUCT: The product or system name$FEATURE: The new feature to break into stories$DESIGN: Link to design files (Figma, Miro, etc.)$ASSUMPTIONS: Key assumptions or context
Step-by-Step Process
- Analyze the feature based on provided design and context
- Identify user roles and distinct user journeys
- Apply 3 C's framework:
- Card: Simple title and one-liner
- Conversation: Detailed discussion of intent
- Confirmation: Clear acceptance criteria
- Respect INVEST criteria: Independent, Negotiable, Valuable, Estimable, Small, Testable
- Use plain language a primary school graduate can understand
- Link to design files for visual reference
- Output user stories in structured format
Story Template
Title: [Feature name]
Description: As a [user role], I want to [action], so that [benefit].
Design: [Link to design files]
Acceptance Criteria:
- [Clear, testable criterion]
- [Observable behavior]
- [System validates correctly]
- [Edge case handling]
- [Performance or accessibility consideration]
- [Integration point]
Example User Story
Title: Recently Viewed Section
Description: As an Online Shopper, I want to see a 'Recently viewed' section on the product page to easily revisit items I considered.
Design: [Figma link]
Acceptance Criteria:
- The 'Recently viewed' section is displayed at the bottom of the product page for every user who has previously viewed at least 1 product.
- It is not displayed for users visiting the first product page of their session.
- The current product itself is excluded from the displayed items.
- The section showcases product cards or thumbnails with images, titles, and prices.
- Each product card indicates when it was viewed (e.g., 'Viewed 5 minutes ago').
- Clicking on a product card leads the user to the corresponding product page.
Output Deliverables
- Complete set of user stories for the feature
- Each story includes title, description, design link, and 4-6 acceptance criteria
- Stories are independent and can be developed in any order
- Stories are sized for one sprint cycle
- Stories reference related design documentation
Further Reading
Source
git clone https://github.com/phuryn/pm-skills/blob/main/pm-execution/skills/user-stories/SKILL.mdView on GitHub Overview
This skill generates user stories using Card, Conversation, and Confirmation, aligned with INVEST criteria. It helps break features into backlog items, attach design links, and define acceptance criteria to guide development.
How This Skill Works
Inputs include product, feature, design link, and assumptions. The workflow applies the 3 C's: Card (title and one-liner), Conversation (detailed intent), Confirmation (acceptance criteria). It enforces INVEST principles and outputs a complete, sprint-sized set of stories with design references and testable criteria.
When to Use It
- When writing user stories to describe a feature from a user perspective.
- When breaking down features into backlog items that can be developed independently.
- When defining acceptance criteria to ensure testability.
- When attaching or referencing design files for visual reference.
- When sizing work for a single sprint and ensuring stories are independent and estimable.
Quick Start
- Step 1: Define $PRODUCT, $FEATURE, $DESIGN, and $ASSUMPTIONS (Context for the story).
- Step 2: Draft the Card, Conversation, and Confirmation sections and write 4-6 Acceptance Criteria.
- Step 3: Attach design references and ensure the story is sized for a single sprint.
Best Practices
- Follow the 3 C's structure for every story: Card, Conversation, Confirmation.
- Keep stories Independent, Negotiable, Valuable, Estimable, Small, and Testable (INVEST).
- Use plain language suitable for a primary school graduate.
- Attach a Design link for visual reference (Figma, Miro, etc.).
- Write 4-6 clear Acceptance Criteria per story, covering edge cases and integration points.
Example Use Cases
- Recently Viewed Section: a complete user story example with design link and acceptance criteria.
- Passwordless Login Flow: story outlining user intent, design reference, and testable criteria.
- Add to Wishlist: backlog item breaking down a wishlist feature with clear acceptance tests.
- Onboarding Tour: micro-story guiding new users through key features with success criteria.
- Accessible Form Validation: story focused on keyboard navigation and screen reader compatibility.
