Ralph Specum Refactor Skill for Codex
This skill should be used only when the user explicitly asks to use `$ralph-specum-refactor`, or explicitly asks Ralph Specum in Codex to revise spec artifacts after implementation learnings.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/tzachbon/smart-ralph --skill ralph-specum-refactorThe instruction itself
4 sections, as written by the authorRalph 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
- Resolve the target spec.
- Read
.progress.mdand existing spec files. - Delegate spec revision to a
refactor-specialistsub-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. - 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. - The sub-agent updates files in order:
requirements.mddesign.mdtasks.md- If requirements changed, revisit design and tasks.
- If design changed, revisit tasks.
- 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 artifactrequest changescontinue to implementation- Treat
continue to implementationas approval of the updated spec files.
Other skills for the same job
different authors, same section of the catalogue
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping
Comprehensive GitHub code review with AI-powered swarm coordination
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.
Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.
Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.
How to use it
Take tzachbon/ralph-specum-refactor from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.