Convert PRDs into structured prd.json files for Ralph.
npx skills add https://github.com/KSDaemon/ralphy --skill ralph-ksdaemon
Please help me install this Agent Skill. Skill: ralph Source: https://github.com/KSDaemon/ralphy/tree/main/skills/ralph Command: npx skills add https://github.com/KSDaemon/ralphy --skill ralph-ksdaemon
Manual conversion of product requirement documents (PRDs) into a machine‑readable format is time‑consuming and error‑prone. This Skill automates the transformation of PRDs into the prd.json schema required by the Ralph autonomous agent, ensuring consistency and readiness for single‑iteration development.
.ralph/tasks/ directory.prd.json with project metadata, branch naming, ordered user stories, and verifiable acceptance criteria.feat/, fix/, hotfix/, or chore/ prefixes based on PRD content.prd.json and progress files when switching features.Say “convert this prd to ralph format” to generate a prd.json file for the current project.
High-intent search queries and answers about installing and using this skill.
To convert a PRD into structured JSON, place the document in the .ralph/tasks directory and trigger the conversion. The system reads the newest PRD and outputs a prd.json file containing project metadata, branch naming, ordered user stories, and verifiable acceptance criteria.
Automating PRD parsing requires extracting project descriptions and user stories into a machine-readable prd.json schema. This ensures single-iteration development readiness by enforcing story size limits, dependency-first ordering, and verifiable acceptance criteria for autonomous agents.
Generating branch names from PRD content involves analyzing the document to apply standard prefixes like feat/, fix/, hotfix/, or chore/ based on the change type. This convention is embedded directly into the generated prd.json file for immediate repository integration.
PRD to JSON conversion supports archiving by safely moving previous prd.json and progress files when switching features. This ensures historical task data is preserved without manual intervention before generating the new structured JSON output.
User stories are sized and ordered for single-iteration development by enforcing strict size limits and applying dependency-first ordering. The conversion process performs checklist validation to ensure completeness, verifiability, and correct sequencing before saving the prd.json file.
You can validate acceptance criteria before saving through built-in pre-save checks. The conversion process performs checklist validation to ensure each user story includes verifiable acceptance criteria, confirming completeness and correct ordering prior to generating the final JSON output.
jellydnConvert Markdown or text PRDs into Ralph's prd.json format.
CElyousfiConverts Markdown files to editable ASTN JSON and vice versa with formatting preserved.
anishakodeCreate git feature branches with standardized naming conventions.
anahelenasilvaConvert Product Requirement Documents into Ralph's prd.json format.