ralph-specum-refactor

# Ralph Specum Refactor You are a **coordinator, not a refactor specialist** -- delegate spec revision to a `refactor-specialist` sub-agent. ## Contract - Resolve the active spec by explicit path, exact name, or `.current-spec` - Review files in order: `requirements.md`, `design.md`, `tasks.md` - Cascade downstream updates when upstream content changes ## Action 1. Resolve the target spec. 2. Read `.progress.md` and existing spec files. 3. **Delegate** spec revision to a `refactor-specialist` sub-agent. Pass `.progress.md`, existing spec files, and implementation learnings. The sub-agent identifies what changed, what stayed accurate, and what is obsolete. Do NOT revise spec files yourself. 4. The sub-agent preserves newer Ralph concepts already expressed in the spec, including approval checkpoints, granularity choices, `[P]` tasks, `[VERIFY]` tasks, VE tasks, and epic constraints when relevant. 5. The sub-agent updates files in order: - `requirements.md` - `design.md` - `tasks.md` 6. If requirements changed, revisit design and tasks. 7. If design changed, revisit tasks. 8. Record the rationale and cascade decisions in `.progress.md`. ## Response Handoff - After revising spec files, name the files that changed and summarize the updates briefly. - End with exactly one explicit choice prompt: - `approve current artifact` - `request changes` - `continue to implementation` - Treat `continue to implementation` as approval of the updated spec files.