skills.rest
YougLin-dev
YougLin-devCOMMUNITY
Explore all skills by this author →
GitHub

prd-converter

Convert PRDs into the prd.json schema for Aha Loop.

182|33|Updated Feb 1, 2026
Search Tags:#automation#prd#converter#prd.json#aha-loop
One-click install
npx skills add https://github.com/YougLin-dev/Aha-Loop --skill prd-converter
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd-converter
Source: https://github.com/YougLin-dev/Aha-Loop/tree/main/.agents/skills/prd-converter
Command: npx skills add https://github.com/YougLin-dev/Aha-Loop --skill prd-converter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts PRDs into a prd.json format suitable for automated execution in Aha Loop, enabling a seamless handoff from planning documents to actionable runtime configurations.

Core Features & Use Cases

  • PRD to JSON: Transform textual PRD content into the standardized prd.json schema used by Aha Loop.
  • Branch & Metadata Generation: Generate branch names and descriptive fields that align with project workflows; supports both new PRDs and migrated documents.
  • Use Case: Take a markdown PRD and produce a ready-to-run prd.json in scripts/aha-loop for immediate integration.

Quick Start

Run the skill on a PRD markdown file to produce prd.json in the scripts/aha-loop 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 a PRD to prd.json for Aha Loop automation?▼

To convert a PRD to prd.json, run the skill on a markdown PRD file to output a structured prd.json with version, prdId, project, branchName, and userStories in the scripts/aha-loop directory.

What is the prd.json schema needed for autonomous execution in Aha Loop?▼

The prd.json schema is a machine-readable PRD representation containing version, prdId, project, branchName, and userStories, enabling Aha Loop to autonomously execute planning documents and roadmaps.

Can I use existing markdown planning documents to generate a prd.json file?▼

Yes, you can use existing markdown planning documents to generate a prd.json file, as the skill handles both new PRDs and migrated documents by transforming textual PRD content into the standardized schema.

Do I need external libraries to convert PRDs into machine-readable runtime configurations?▼

No, you do not need external libraries to convert PRDs into machine-readable runtime configurations, as the solution requires no dependencies and outputs a properly structured prd.json independently.

How does branch and metadata generation work when migrating PRDs to JSON?▼

Branch and metadata generation works by creating branch names and descriptive fields that align with project workflows, supporting both new and migrated documents during the PRD to JSON conversion.

Related Skills

Explore More Product & Management Skills→
AlejandroFiginiAlejandroFigini

ralph

Convert Markdown or plain-text PRDs into Ralph's prd.json schema.

Community
Intermediate
YougLin-devYougLin-dev
182

research

Extract research topics from prd.json and document findings in the knowledge base.

Community
Advanced
TacuchiTacuchi

tools

Generate CLI tool code and documentation under docs/tools within plan-exec-loop workflows.

Community
Intermediate
zhongjiszhongjis

jc

Convert command-line interface output into structured JSON for programmatic analysis.

Community
Basic