prd-to-features

Convert PRD documents into prioritized features.json files with BDD test cases.

3|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/BaqiF2/Synapse-Agent --skill prd-to-features
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-to-features
Source: https://github.com/BaqiF2/Synapse-Agent/tree/main/.codex/skills/prd-to-features
Command: npx skills add https://github.com/BaqiF2/Synapse-Agent --skill prd-to-features

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Convert PRD documents into a features.json file containing verifiable BDD test cases.

Core Features & Use Cases

  • Convert PRDs into a prioritized features.json structure with verifiable BDD test cases.
  • Split PRD sections into independently testable features following the 6-phase workflow.
  • Output to plans/ with a prd-features.json manifest suitable for downstream testing.

Quick Start

Provide a PRD document to generate a prioritized features.json with BDD test cases.

Frequently Asked Questions about prd-to-features

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

FAQPage Schema
How do I convert a PRD into BDD test cases?

Yes, a PRD document is the required input to generate verifiable BDD test cases. The Skill processes the document through a 6-phase workflow to output a structured prd-features.json manifest.

What is the best way to generate a features.json file from product requirements?

The best way to generate a features.json file from product requirements is applying a 6-phase workflow that splits PRD sections into independently testable features and prioritizes them for output.

Does converting PRDs to BDD features require any external dependencies?

No, converting PRDs to BDD features requires no external dependencies. The Skill independently processes the PRD document to output the structured features.json manifest directly.

How are product requirements prioritized when generating testable features?

Product requirements are prioritized during the conversion process by splitting PRD sections into independently testable features and ordering them for the final features.json output.

Can I use this BDD conversion process for downstream requirements management?

Yes, you can use this BDD conversion process for downstream requirements management because it outputs a structured prd-features.json manifest in the plans/ directory, suitable for subsequent testing workflows.