prd-to-stories

Extracts PRDs and generates structured Markdown stories with acceptance criteria.

2|1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/mattstruble/skills --skill prd-to-stories-mattstruble
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-to-stories
Source: https://github.com/mattstruble/skills/tree/main/prd-to-stories
Command: npx skills add https://github.com/mattstruble/skills --skill prd-to-stories-mattstruble

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decompose a behavioral PRD into independently deliverable stories with technically specific acceptance criteria, enabling teams to plan, estimate, and implement in small, verifiable increments.

Core Features & Use Cases

  • Break PRD capabilities into discrete stories with clearly defined acceptance criteria.
  • Generate Markdown story files under docs/stories for easy review and tracking.
  • Surface Open Questions when cross-group dependencies or edge cases arise.

Quick Start

Provide a PRD document and choose a scope, and the tool will generate the corresponding stories under docs/stories.

Frequently Asked Questions about prd-to-stories

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

FAQPage Schema
How do I decompose a PRD into actionable development stories?

To decompose a PRD into actionable development stories, you extract capability groups from the PRD and convert them into independently deliverable stories with technically specific acceptance criteria stored as Markdown files.

How do I generate verifiable acceptance criteria for product requirements?

Generating verifiable acceptance criteria for product requirements involves enforcing concrete criteria during PRD decomposition, ensuring teams can plan, estimate, and implement capabilities in small, verifiable increments.

What is the best way to break down product requirements for agile teams?

The best way to break down product requirements for agile teams is to map PRD capabilities to individual stories, maintaining source traceability while surfacing Open Questions when cross-group dependencies or edge cases appear.

Can I generate Markdown files for my product stories directly from a PRD?

Yes, you can generate Markdown files for your product stories directly from a PRD by applying the decomposition tool to capability groups, which produces individual story files stored under the docs/stories directory.

How does PRD decomposition handle cross-group dependencies and edge cases?

PRD decomposition handles cross-group dependencies and edge cases by surfacing Open Questions, alerting teams to potential integration conflicts before implementation begins on the independently deliverable stories.

Do I need a specific format for my PRD to extract actionable stories?

You need a behavioral PRD document to extract actionable stories, allowing the decomposition process to identify capability groups, enforce verifiable acceptance criteria, and maintain source mapping for traceability.