frd-generation

Decompose PRDs into actionable FRDs with acceptance criteria and dependencies.

Updated Dec 30, 2025

Search Tags:#templates #specification #requirements #decomposition #prd #frd #feature-requirements

Ready to run

npx skills add https://github.com/henrybravo/developer-readiness-portal --skill frd-generation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: frd-generation
Source: https://github.com/henrybravo/developer-readiness-portal/tree/main/.github/skills/frd-generation
Command: npx skills add https://github.com/henrybravo/developer-readiness-portal --skill frd-generation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks down high-level Product Requirements Documents (PRDs) into focused Feature Requirements Documents (FRDs) that can be independently implemented by development teams.

Core Features & Use Cases

Read and analyze a PRD from specs/prd.md
Decompose high-level requirements into discrete features
Create one FRD file per feature in specs/features/ using kebab-case naming
Maintain traceability to PRD requirements and support living documents

Quick Start

Submit the PRD at specs/prd.md to generate FRDs.

Frequently Asked Questions about frd-generation

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

FAQPage Schema

How do I decompose a PRD into actionable feature requirements documents?▼

To decompose a PRD into actionable FRDs, place your high-level PRD at specs/prd.md. The system analyzes the requirements and generates discrete, independently implementable Feature Requirements Documents as MD files in specs/features/.

What is the difference between a PRD and an FRD in requirements decomposition?▼

In requirements decomposition, a PRD contains high-level product requirements, while an FRD breaks those down into focused, discrete features with acceptance criteria and dependencies. FRDs enable independent feature implementation by development teams.

How do I structure FRD files from a PRD for independent feature implementation?▼

FRD files generated from a PRD are structured as individual MD files in specs/features/ using kebab-case naming. This structure maintains traceability to PRD requirements and supports living documents for ongoing development.

Can I generate multiple FRDs from a single PRD file?▼

Yes, you can generate multiple FRDs from a single PRD file. The system reads your PRD from specs/prd.md and creates one FRD file per discrete feature, enabling independent implementation by separate development teams.

What file format and naming convention do generated feature requirements documents use?▼

Generated feature requirements documents use the MD file format and kebab-case naming convention. Files are output directly into the specs/features/ directory to maintain consistent structure across the feature specifications.

Do I need any dependencies or specific components to turn PRDs into FRDs?▼

No dependencies or specific components are required to turn PRDs into FRDs. You only need to provide your high-level PRD at specs/prd.md to generate actionable feature requirements documents for your development teams.