Convert PRDs to prd.json format for ralph-tui execution. Creates JSON task files with user stories, acceptance criteria, and dependencies. Triggers on: create prd.json, convert to json, ralph json, create json tasks.

Ralph TUI Create JSON Tasks Converts PRDs to prd.json format for ralph tui autonomous execution. Note: This skill is bundled with ralph tui's JSON tracker plugin. Future tracker plugins (Linear, GitHub Issues, etc.) will bundle their own task creation skills. ⚠️ CRITICAL: The output MUST be a FLAT JSON object with "name" and "userStories" at the ROOT level. DO NOT wrap content in a "prd" object or use "tasks" array. See "Schema Anti Patterns" section below. The Job Take a PRD (markdown file or text) and create a prd.json file: 1. Extract Quality Gates from the PRD's "Quality Gates" section 2. Parse user stories from the PRD 3. Append quality gates to each story's acceptance criteria 4. Set up dependencies between stories 5. Output ready for ralph tui run prd <path Step 1: Extract Quality Gates Look for the "Quality Gates" section in the PRD: Extract: Universal gates: Commands that apply to ALL stories (e.g., pnpm typecheck ) UI gates: Commands that apply only to UI stories (e.g., browser verification) If no Quality Gates section exists: Ask the user what commands should pass, or use a sensible default like npm run typecheck . Output Format The JSON file MUST be a FLAT object at the root level: CRITICAL: Schema Anti Patterns (DO NOT USE) The following patterns are INVALID and will cause validation errors: ❌ WRONG: Wrapper object This wraps everything in a "prd" object. DO NOT DO THIS. The "name" and "userStories" fields must be at the ROOT level. ❌ WRONG: Using "tasks" instead of "userStories" The array is called "userStories" , not "tasks". ❌ WRONG: Complex nested structures Even if the PRD describes phases/milestones/sprints, you MUST flatten these into a single "userStories" array. ❌ WRONG: Using "status" instead of "passes" Use "passes": false for incomplete stories, "passes": true for completed. ✅ CORRECT: Flat structure at root Story Size: The 1 Rule Each story must be completable in ONE ralph tui iteration (~one agent context window). Ralph tui spawns a fresh agent instance per iteration with no memory of previous work. If a story is too big, the agent runs out of context before finishing. Right sized stories: Add a database column + migration Add a UI component to an existing page Update a server action with new logic Add a filter dropdown to a list Too big (split these): "Build the entire dashboard" → Split into: schema, queries, UI components, filters "Add authentication" → Split into: schema, middleware, login UI, session handling "Refactor the API" → Split into one story per endpoint or pattern Rule of thumb: If you can't describe the change in 2 3 sentences, it's too big. Dependencies with dependsOn Use the dependsOn array to specify which stories must complete first: Ralph tui will: Show US 002 as "blocked" until US 001 completes Never select US 002 for execution while US 001 is open Include "Prerequisites: US 001" in the prompt when working on US 002 Correct dependency order: 1. Schema/database changes (no dependencies) 2. Backend logic (depends on schema) 3. UI components (depends on backend) 4. Integration/polish (depends on UI) Acceptance Criteria: Quality Gates + Story Specific Each story's acceptance criteria should include: 1. Story specific criteria from the PRD (what this story accomplishes) 2. Quality gates from the PRD's Quality Gates section (appended at the end) Good criteria (verifiable): "Add status column to tasks table with default 'open'" "Filter dropdown has options: All, Open, Closed" "Clicking delete shows confirmation dialog" Bad criteria (vague): ❌ "Works correctly" ❌ "User can do X easily" ❌ "Good UX" ❌ "Handles edge cases" Conversion Rules 1. Extract Quality Gates from PRD first 2. Each user story → one JSON entry 3. IDs : Sequential (US 001, US 002, etc.) 4. Priority : Based on dependency order (1 = highest) 5. dependsOn : Array of story IDs this story requires 6. All stories : passes: false and empty notes 7. branchName : Derive from feature name, kebab case, prefixed with ralph/ 8. Acceptance criteria : Story criteria + quality gates appended 9. UI stories : Also append UI specific gates (browser verification) Output Location Default: ./tasks/prd.json (alongside the PRD markdown files) This keeps all PRD related files together in the tasks/ directory. Or specify a different path ralph tui will use it with: Example Input PRD: Output prd.json: Running with ralph tui After creating prd.json: Ralph tui will: 1. Load stories from prd.json 2. Select the highest priority story with passes: false and no blocking dependencies 3. Generate a prompt with story details + acceptance criteria 4. Run the agent to implement the story 5. Mark passes: true on completion 6. Repeat until all stories pass Checklist Before Saving [ ] Extracted Quality Gates from PRD (or asked user if missing) [ ] Each story completable in one iteration [ ] Stories ordered by dependency (schema → backend → UI) [ ] dependsOn correctly set for each story [ ] Quality gates appended to every story's acceptance criteria [ ] UI stories have browser verification (if specified in Quality Gates) [ ] Acceptance criteria are verifiable (not vague) [ ] No circular dependencies

ralph-tui-create-json