stories-create

Extract user workflows from PRDs into testable stories with traceability.

11|Updated Sep 5, 2025
One-click install
npx skills add https://github.com/thrawn01/claude-dotfiles --skill stories-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stories-create
Source: https://github.com/thrawn01/claude-dotfiles/tree/main/skills/stories-create
Command: npx skills add https://github.com/thrawn01/claude-dotfiles --skill stories-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating comprehensive, testable user stories from a PRD to accelerate agile teams and ensure traceability across features.

Core Features & Use Cases

  • Generate user workflow stories for each persona described in the PRD, with observable acceptance criteria.
  • Derive negative and boundary-case stories based on correctness constraints, ensuring edge conditions are covered.
  • Output the final documentation to docs/features/{feature}/user-stories.md with traceability notes back to the PRD.

Quick Start

Paste or reference the PRD path, then generate and save the user stories to docs/features/{feature}/user-stories.md.

Frequently Asked Questions about stories-create

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

FAQPage Schema
How do I generate user stories from a PRD?

Generate user stories from a PRD by extracting user workflows for each persona and converting them into discrete, testable stories with observable acceptance criteria. The resulting stories are saved to docs/features/{feature}/user-stories.md with traceability notes back to the source PRD.

How do I write acceptance criteria that are mechanically verifiable?

Mechanically verifiable acceptance criteria are generated by aligning testable story conditions with the PRD's correctness constraints. This ensures each criterion can be objectively validated and covers both expected behavior and boundary-case edge conditions.

Can I ensure traceability between user stories and the source PRD?

Traceability is ensured by outputting generated stories to docs/features/{feature}/user-stories.md with explicit reference notes linking each story back to its corresponding sections within the source PRD.

How do I cover edge cases and negative scenarios when writing user stories?

Edge cases and negative scenarios are covered by deriving additional boundary-case stories directly from the correctness constraints defined in the PRD, ensuring comprehensive validation of unexpected or invalid user workflows.

What is the best way to structure agile user story documentation?

Structure agile user story documentation by saving generated stories into docs/features/{feature}/user-stories.md. This file stores discrete persona workflows, mechanically verifiable acceptance criteria, and traceability links back to the PRD.

Do I need a complete PRD to generate testable user stories?

A complete PRD with defined personas and correctness constraints is required to extract user workflows and generate testable stories. Without these PRD elements, deriving mechanically verifiable acceptance criteria and boundary-case coverage is not possible.