prd-converter

Convert Markdown PRDs into structured prd.json files with strict schema fields.

Updated Dec 15, 2025
One-click install
npx skills add https://github.com/flight505/sdk-bridge --skill prd-converter-flight505
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd-converter
Source: https://github.com/flight505/sdk-bridge/tree/main/skills/prd-converter
Command: npx skills add https://github.com/flight505/sdk-bridge --skill prd-converter-flight505

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts existing PRDs to the prd.json format used by SDK Bridge's autonomous agent system, enabling deterministic execution from natural-language inputs.

Core Features & Use Cases

  • Converts Markdown PRDs or text into a structured prd.json with standard fields like project, branchName, description, and userStories.
  • Enforces the prd.json schema, including new fields like depends_on, related_to, implementation_hint, and check_before_implementing, and provides guidance for validation.
  • Supports automated workflows that transform product requirements into actionable stories for the SDK Bridge agent.

Quick Start

Convert a Markdown PRD to prd.json by running the converter on your project directory.

Frequently Asked Questions about prd-converter

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

FAQPage Schema
How do I convert Markdown PRDs to prd.json for SDK Bridge?▼

Converting Markdown PRDs to prd.json requires running the converter on your project directory. It transforms natural language product requirements into a structured JSON format with fields like project, branchName, description, and userStories for deterministic agent execution.

What is the prd.json schema used by SDK Bridge?▼

The prd.json schema used by SDK Bridge enforces standard fields like project and userStories alongside strict structural fields including depends_on, related_to, implementation_hint, check_before_implementing, and validation rules for archiving and verification.

Can I transform plain text product requirements into userStories for autonomous agents?▼

Yes, you can transform plain text product requirements into userStories. The converter processes text inputs to generate a structured prd.json file that enables SDK Bridge's autonomous agent system to execute tasks deterministically from natural-language inputs.

What's the best way to structure implementation hints and dependencies in prd.json?▼

The best way to structure implementation hints and dependencies is to use the enforced prd.json schema fields depends_on, related_to, implementation_hint, and check_before_implementing during the Markdown conversion process to ensure autonomous agent validation.

Do I need specific validation rules when converting PRDs to JSON format?▼

Yes, you need specific validation rules when converting PRDs to JSON format. The converter implements a strict schema that provides guidance for validation, including rules for archiving and verification to support automated SDK Bridge workflows.