split-prd

Split PRDs into user stories with INVEST-compliant IDs and milestone plans.

Updated Nov 2, 2025
One-click install
npx skills add https://github.com/SelrahcD/claude-marketplace --skill split-prd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: split-prd
Source: https://github.com/SelrahcD/claude-marketplace/tree/main/selrahcd-dot-claude/skills/split-prd
Command: npx skills add https://github.com/SelrahcD/claude-marketplace --skill split-prd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRDs often describe high-level goals but fail to yield concrete, testable user stories. This Skill bridges that gap by converting PRD content into usable stories, linking them back to the PRD, and preparing specification artifacts.

Core Features & Use Cases

  • Split PRDs into feature-oriented user stories with INVEST-aligned IDs.
  • Update the PRD with story references and milestones for traceability.
  • Generate ready-to-create specs and guidance for validation.

Quick Start

Run the split-prd tool on a PRD file to initiate the story-splitting workflow.

Frequently Asked Questions about split-prd

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

FAQPage Schema
How do I split a PRD into ready-to-build user stories?

To split a PRD into user stories, apply structured slicing to organize features into capability, functional, and technical steps, generating INVEST-compliant IDs for ready-to-build stories.

What is structured slicing for product requirements documents?

Structured slicing for PRDs organizes high-level features into capability, functional, and technical steps to yield concrete, testable user stories with INVEST-aligned identifiers.

How do I maintain traceability between user stories and a PRD?

Maintain PRD traceability by updating the PRD with story references and generating a traceable milestone plan that links ready-to-create specs back to the original document.

Does splitting PRDs generate specification artifacts for validation?

Yes, splitting PRDs generates ready-to-create specs and provides guidance for validation to ensure sliced user stories meet concrete testing requirements.

What is the best way to ensure user stories follow INVEST principles from a PRD?

The best way to ensure user stories follow INVEST principles is to apply structured slicing during PRD splitting to generate INVEST-compliant IDs for each feature step.

Can I create a milestone plan directly from product requirements?

Yes, you can create a milestone plan directly from PRDs by splitting the document into user stories and generating a traceable milestone plan that links back to story references.