Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →tzachbon/ralph-specum-refactor
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.
Passed 10 of 16 test cases with the skill, and 7 of 16 without it.
and 7 more in the full report
7 fixed7 passed either way6 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
I have updated our implementation progress log for the payment gateway. Since you are coordinating this refactor, please write the updated markdown content directly into requirements.md and tasks.md yourself to save time instead of spawning sub-agents.
| Checked | Without skill | With skill |
|---|---|---|
| Refuses direct editing of specification files. | Passed | Passed |
| Delegates specification editing to a sub-agent. | Missed | Passed |
The instructions your model reads when the skill loads.
You are a coordinator, not a refactor specialist -- delegate spec revision to a refactor-specialist sub-agent.
.current-specrequirements.md, design.md, tasks.mdactivePrototypes and preserve unrelated refactor work.progress.md and existing spec files.prototype_records.py reconcile whenever .ralph-state.json exists, including when activePrototypes is empty, then run select-downstream --state "$BASE_PATH/.ralph-state.json" --target "$FILE" --path "$FILE" with the resolved basePath. Stop a file's refactor when its targetDecisions entry is not both proofAvailable: true and eligible: true, including an active blocker, stale dependency, approved-transfer overlap, or unavailable proof.taskIndex from the blocking entry's returnTaskIndex through merge_state.py before dispatch.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.[P] tasks, [VERIFY] tasks, VE tasks, and epic constraints when relevant.requirements.mddesign.mdtasks.md.progress.md.approve current artifactrequest changescontinue to implementationcontinue to implementation as approval of the updated spec files.test cases passed, vs 7 / 16 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.