ralph-convert-prd
将产品需求文档转换为Ralph自主代理系统使用的prd.json格式。用于准备Ralph执行的产品需求文档、将特性分解为原子用户故事,或当用户提及Ralph、prd.json或自主代理工作流程时。
📖 中文导读:将产品需求文档转换为Ralph自主代理系统使用的prd.json格式。用于准备Ralph执行的产品需求文档、将特性分解为原子用户故事,或当用户提及Ralph、prd.json或自主代理工作流程时。 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。
name: ralph-convert-prd description: Converts Product Requirements Documents into prd.json format for the Ralph autonomous agent system. Use when preparing PRDs for Ralph execution, breaking down features into atomic user stories, or when the user mentions Ralph, prd.json, or autonomous agent workflows. model: claude-opus-4-5 context: fork
Transform existing Product Requirements Documents into the structured `prd.json` format used by the Ralph autonomous agent system. Each story must be completable in one LLM context window to prevent broken code from context overflow. 1. Read the user's PRD or feature requirements 2. Break down into atomic user stories (one context window each) 3. Order stories by dependency (schema → backend → UI → dashboard) 4. Output valid `prd.json` with verifiable acceptance criteria **Critical Rule**: Each story must be completable in ONE Ralph iteration (one context window).Stories that are too large cause the LLM to run out of context before completion, resulting in broken code.
Right-sized stories:
- Add a database column
- Create a UI component
- Update server actions
- Implement a filter
Too large (split these):
- Build entire dashboards
- Add authentication systems
- Refactor entire APIs
- Schema/database changes
- Server actions and backend logic
- UI components
- Dashboard/summary views
Never reference something that doesn't exist yet.
Each criterion must be verifiable and specific. Avoid vague language.Good criteria:
- "Add status column with values: 'pending' | 'in_progress' | 'done'"
- "Filter dropdown includes: All, Active, Completed"
- "Clicking delete shows confirmation dialog"
Bad criteria (too vague):
- "Works correctly"
- "Good UX"
- "Handles edge cases"
UI-focused stories MUST also include: "Verify in browser using dev-browser skill"
Field requirements:
id: Sequential US-001, US-002, etc.title: Short, descriptive actiondescription: User story format (As a... I want... so that...)acceptanceCriteria: Array of specific, verifiable criteriapriority: Execution order (1 = first)passes: Alwaysfalseinitiallynotes: Empty string initially
Before outputting the final prd.json, verify:
- Previous runs archived (if applicable)
- Each story completable in one iteration
- Stories ordered by dependency (no forward references)
- All stories include "Typecheck passes"
- UI stories include browser verification criterion
- Acceptance criteria are verifiable, not vague
- No story depends on later stories
- All features from PRD are captured as user stories
- Each story is atomic (one context window)
- Stories are properly ordered by dependency
- All acceptance criteria are specific and verifiable
- Mandatory criteria ("Typecheck passes") present on all stories
- UI stories include browser verification
- Valid JSON structure with all required fields
- Pre-save checklist passes