prd
PRD Generator
Create detailed Product Requirements Documents that are clear, actionable, and suitable for implementation.
Prerequisites
Before writing a PRD, verify that planning has been completed:
- Check for planning summary: Look for
tasks/planning-[feature].mdfrom the/planningskill - If no planning exists: STOP. Tell the user to run
/planningfirst to explore requirements - If planning exists: Reference it to inform the PRD structure
Why this matters: PRDs written without planning often miss edge cases, have vague requirements, or solve the wrong problem. The planning skill forces 5 rounds of questions that surface critical details.
The Job
More from harrymunro/ralph-wiggum
ralph
Convert PRDs to prd.json format for the Ralph autonomous agent system. Use when you have an existing PRD and need to convert it to Ralph's JSON format. Triggers on: convert this prd, turn this into ralph format, create prd.json from this, ralph json.
13planning
Deep requirements exploration before creating a PRD. Use when starting any new feature to ensure requirements are fully understood. Triggers on: plan this feature, explore requirements, planning session, before I write a prd.
12