User Stories
Break a feature into INVEST-compliant user stories with Card–Conversation–Confirmation structure, design links, and testable acceptance criteria.
Overview
User Stories is an agent skill most often used in Build (also Validate) that creates INVEST-aligned user stories with the 3 C’s, design links, and acceptance criteria.
Install
npx skills add https://github.com/phuryn/pm-skills --skill user-storiesWhat is this skill?
- 7-step process from feature analysis through structured story output
- 3 C’s framework: Card title, Conversation intent, Confirmation acceptance criteria
- INVEST checks: Independent, Negotiable, Valuable, Estimable, Small, Testable
- Parameterized inputs: PRODUCT, FEATURE, DESIGN links, and ASSUMPTIONS
- Plain-language stories with explicit design file references (Figma, Miro, etc.)
- 7-step step-by-step process documented in the skill
- 3 C’s framework (Card, Conversation, Confirmation)
- INVEST criteria set of six attributes
Adoption & trust: 1.2k installs on skills.sh; 12.3k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have a feature and designs but no consistent, testable user stories your agent or devs can implement against.
Who is it for?
Solo builders and indie PMs translating a scoped feature plus Figma/Miro links into a clean backlog before coding sprints.
Skip if: Open-ended opportunity discovery with no feature boundary, or regulated contexts that mandate a different story schema your org already standardized.
When should I use this skill?
Use when writing user stories, breaking down features into stories, creating backlog items, or defining acceptance criteria; supply $PRODUCT, $FEATURE, $DESIGN, and $ASSUMPTIONS.
What do I get? / Deliverables
You get a set of structured stories with roles, intents, linked designs, and acceptance criteria ready for estimation and implementation planning.
- Structured user stories with title, role/action/outcome narrative
- Acceptance criteria suitable for test and agent implementation checks
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Build/pm is the canonical shelf because output is backlog-ready stories for implementation planning, though the same ritual starts during validation. Pm subphase matches feature decomposition, acceptance criteria, and handoff to engineering estimates.
Where it fits
Split a landing-page experiment into small testable stories before committing engineering time.
Produce Jira-ready stories from a Figma flow for the next solo sprint.
Refresh acceptance criteria on stories entering QA so confirmation matches shipped behavior.
How it compares
Use instead of ad-hoc bullet lists in chat when you need INVEST and 3 C’s discipline—not a code generator or test runner.
Common Questions / FAQ
Who is user-stories for?
Solo founders and small teams who own backlog quality and want agent help formatting stories with acceptance criteria and design traceability.
When should I use user-stories?
Use in Validate when scoping a feature into negotiable increments; in Build/pm when writing stories, splitting work, or defining acceptance criteria before implementation.
Is user-stories safe to install?
It is documentation-style PM guidance; still review the Security Audits panel on this Prism page and avoid pasting secrets into PRODUCT/ASSUMPTIONS arguments.
SKILL.md
READMESKILL.md - User Stories
# User 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 1. **Analyze the feature** based on provided design and context 2. **Identify user roles** and distinct user journeys 3. **Apply 3 C's framework:** - Card: Simple title and one-liner - Conversation: Detailed discussion of intent - Confirmation: Clear acceptance criteria 4. **Respect INVEST criteria:** Independent, Negotiable, Valuable, Estimable, Small, Testable 5. **Use plain language** a primary school graduate can understand 6. **Link to design files** for visual reference 7. **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:** 1. [Clear, testable criterion] 2. [Observable behavior] 3. [System validates correctly] 4. [Edge case handling] 5. [Performance or accessibility consideration] 6. [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:** 1. The 'Recently viewed' section is displayed at the bottom of the product page for every user who has previously viewed at least 1 product. 2. It is not displayed for users visiting the first product page of their session. 3. The current product itself is excluded from the displayed items. 4. The section showcases product cards or thumbnails with images, titles, and prices. 5. Each product card indicates when it was viewed (e.g., 'Viewed 5 minutes ago'). 6. 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 - [How to Write User Stories: The Ultimate Guide](https://www.productcompass.pm/p/how-to-write-user-stories)