prd-to-spec

Convert PRD.md documents into structured SPEC.md specifications with user stories and tasks.

Updated Mar 9, 2026

Search Tags:#automation #specification #task breakdown #PRD #user stories

Ready to run

npx skills add https://github.com/hheydaroff/common-agent-skills --skill prd-to-spec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd-to-spec
Source: https://github.com/hheydaroff/common-agent-skills/tree/main/skills/prd-to-spec
Command: npx skills add https://github.com/hheydaroff/common-agent-skills --skill prd-to-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the conversion of unstructured PRD documents into detailed, organized SPEC.md files that outline user stories, acceptance criteria, and development tasks, reducing manual planning efforts.

Core Features & Use Cases

PRD Parsing and Extraction: Reads a project's PRD.md to identify key project objectives, features, requirements, and success criteria.
Structured Specification Generation: Creates a comprehensive SPEC.md document with user stories, acceptance criteria, technical components, and vertical slices.
Use Case: When a product manager has a detailed PRD, use this Skill to generate a ready-to-implement feature specification for development teams.

Quick Start

Use the prd-to-spec skill to convert your existing PRD.md into a structured Spec document that guides development tasks.

Frequently Asked Questions about prd-to-spec

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

FAQPage Schema

How do I convert a PRD into development specifications automatically?▼

To convert a PRD into development specifications, this Skill parses your PRD.md file to extract project objectives and requirements, automatically generating a structured SPEC.md document with user stories and task decomposition.

What is the best way to generate user stories from a product requirements document?▼

Generating user stories from a product requirements document involves extracting key features and success criteria. This Skill reads your PRD.md and structures the data into a SPEC.md format containing user stories and acceptance criteria.

Can I use this to break down PRD features into vertical slices for development?▼

Yes, you can break down PRD features into vertical slices. The Skill processes your PRD.md to identify technical components and workflows, outputting a structured SPEC.md that organizes features into actionable development tasks and slices.

Does this tool require any specific dependencies to parse PRD.md files?▼

No specific dependencies are required to parse PRD.md files. The Skill operates independently to read your product requirements document and output the structured development specification without needing external components.

How do I structure acceptance criteria from an unstructured PRD document?▼

To structure acceptance criteria from an unstructured PRD document, the Skill automates the extraction of key information and requirements, organizing the data into a comprehensive SPEC.md file that outlines clear acceptance criteria.

When should I not use an automated PRD to spec conversion process?▼

You should not use an automated PRD to spec conversion process if your product requirements document is incomplete or lacks clear objectives, as the Skill relies on parsing detailed PRD.md content to generate accurate development tasks.