ralph-specum-cancel
This skill should be used only when the user explicitly asks to use `$ralph-specum-cancel`, or explicitly asks Ralph Specum in Codex to stop execution or remove a spec.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install tzachbon-smart-ralph-ralph-specum-cancel
Repository
Skill path: platforms/codex/skills/ralph-specum-cancel
This skill should be used only when the user explicitly asks to use `$ralph-specum-cancel`, or explicitly asks Ralph Specum in Codex to stop execution or remove a spec.
Open repositoryBest for
Primary workflow: Ship Full Stack.
Technical facets: Full Stack.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: tzachbon.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install ralph-specum-cancel into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/tzachbon/smart-ralph before adding ralph-specum-cancel to shared team environments
- Use ralph-specum-cancel for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
--- name: ralph-specum-cancel description: This skill should be used only when the user explicitly asks to use `$ralph-specum-cancel`, or explicitly asks Ralph Specum in Codex to stop execution or remove a spec. metadata: surface: helper action: cancel --- # Ralph Specum Cancel Use this to stop execution and optionally remove a spec. ## Contract - Resolve the target by explicit path, exact name, or `.current-spec` - Always clear execution state when the user wants to stop execution - Confirm before deleting a spec directory - Do not guess on ambiguous names ## Action 1. Resolve the target spec. If none exists, report that there is nothing to cancel. 2. Read `.ralph-state.json` when present and summarize the current phase and progress. 3. Safe cancel is the default. Delete `.ralph-state.json` only and keep the spec files unless the user asked for full removal. 4. If the user wants full removal, confirm first, then delete the spec directory and clear `.current-spec` when it points to that spec. 5. If the removed spec belongs to the active epic, keep epic files intact unless the user explicitly asked to remove epic planning too. 6. Report exactly what was removed.