User Stories

Convert PRDs into INVEST-aligned user stories with acceptance criteria.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kurko/ai-company-os --skill user-stories-kurko
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: User Stories
Source: https://github.com/kurko/ai-company-os/tree/main/skills/user-stories
Command: npx skills add https://github.com/kurko/ai-company-os --skill user-stories-kurko

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams transform vague PRDs into concrete, actionable work by breaking requirements into discrete user stories with explicit acceptance criteria, ensuring smooth handoffs to development and clearer validation.

Core Features & Use Cases

  • Break PRDs into discrete, independently deliverable user stories that map to concrete product outcomes.
  • Apply the INVEST criteria to ensure stories are independent, negotiable, valuable, estimable, small, and testable.
  • Generate a reusable Story Output Template with context, individual stories, acceptance criteria, sizing, and dependencies.
  • Support a fast Quick Start that translates a PRD into ready-to-work backlog items for sprint planning.

Quick Start

Paste your PRD into the tool to generate INVEST-aligned user stories with acceptance criteria.

Frequently Asked Questions about User Stories

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a PRD into ready-to-build user stories for sprint planning?

To convert a PRD into user stories, paste your product requirements into the tool to generate discrete, INVEST-aligned stories with clear acceptance criteria sized for a single sprint.

What is the INVEST criteria for backlog refinement and how does it apply to story splitting?

INVEST criteria ensure backlog stories are Independent, Negotiable, Valuable, Estimable, Small, and Testable. The tool applies these rules during story splitting to verify each backlog item is independently deliverable.

How do I write testable acceptance criteria for product requirements?

Writing testable acceptance criteria involves breaking PRDs into discrete stories and generating explicit validation conditions. The tool outputs a template mapping each requirement to concrete, testable acceptance criteria.

Can I break down a large PRD into individual user stories without losing feature context?

Yes, you can break down a large PRD while preserving context. The tool generates a reusable Story Output Template that retains original context while splitting requirements into individual stories with dependencies.

What is the best way to size user stories for a single sprint?

The best way to size user stories for a single sprint is applying the INVEST criteria to ensure they are small and estimable. The tool sizes stories during backlog creation to fit within individual sprint boundaries.

Does this tool work for backlog creation when starting from scratch with only a vague PRD?

Yes, this tool works for backlog creation from vague PRDs by transforming broad requirements into concrete, actionable work items with explicit acceptance criteria, ensuring smooth handoffs to development.