sdd-to-ralph

name	sdd-to-ralph
description	This skill should be used when the user wants to convert completed CCSDD specs into Ralph execution artifacts. Use when user says "bridge spec to ralph", "convert sdd to ralph", "sdd to ralph", "generate ralph from spec", "prepare spec for ralph", or wants to take a cc-sdd feature spec and run it through Ralph for autonomous implementation.
allowed-tools	Read, Write, Glob, AskUserQuestion

SDD to Ralph Bridge

Convert completed CCSDD (cc-sdd) spec artifacts into Ralph execution artifacts for autonomous implementation.

• Input: .kiro/specs/<feature>/ — requirements.md, design.md, tasks.md
• Output: .ralph/PROMPT.md, .ralph/fix_plan.md, updated .ralphrc, .ralph/specs/

Prerequisites

Verify both systems are installed before proceeding:

1. Ralph enabled: .ralph/ directory and .ralphrc file exist
   • If missing: instruct user to run ralph-enable
2. CCSDD installed: .kiro/ directory exists with at least one spec
   • If missing: instruct user to run npx cc-sdd@latest --claude

If either prerequisite fails, stop and report the issue.

Step 1: Detect and Select Feature Spec

Glob for .kiro/specs/*/spec.json to find available specs.

If 0 specs found:

If `tasks.md` does not exist or is empty, stop and report: "Cannot generate fix_plan.md without tasks. Run `/kiro:spec-tasks ` first." - Summarize, don't dump — Ralph reads PROMPT.md every loop, so it must be concise - Full specs are in `.ralph/specs/` for reference when Ralph needs detail - Include version numbers for all technologies - Make principles actionable — things Claude can verify - Keep Requirements Summary to titles and key criteria only - Design Reference should focus on architecture decisions that affect implementation The operational instructions section is MANDATORY. Without it: - Claude won't output the RALPH_STATUS block that Ralph parses for exit signals - Claude won't know when to set EXIT_SIGNAL: true vs false - Ralph will either never exit or exit prematurely - The circuit breaker and response analyzer depend on structured status output - Only include leaf tasks — parent tasks are organizational groupings, not implementable units - Preserve the task ordering from tasks.md (respects dependency structure via P0/P1/P2 ordering) - The /kiro:validate-impl task is always last — it closes the spec→implementation→validation loop