ralph-specum-cancel
The ralph-specum-cancel skill stops execution of Ralph Specum specifications and optionally removes spec files. Use it when users explicitly request cancellation of spec execution or removal of a specification within the Ralph Specum workflow. The skill safely halts execution by clearing state files, confirms before permanent deletion, and maintains epic planning files unless explicitly requested otherwise.
git clone --depth 1 https://github.com/tzachbon/smart-ralph /tmp/ralph-specum-cancel && cp -r /tmp/ralph-specum-cancel/plugins/ralph-specum-codex/skills/ralph-specum-cancel ~/.claude/skills/ralph-specum-cancelSKILL.md
# 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.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.
This skill should be used when the user asks to "add MCP server", "integrate MCP", "configure MCP in plugin", "use .mcp.json", "set up Model Context Protocol", "connect external service", mentions "${CLAUDE_PLUGIN_ROOT} with MCP", or discusses MCP server types (SSE, stdio, HTTP, WebSocket). Provides comprehensive guidance for integrating Model Context Protocol servers into Claude Code plugins for external tool and service integration.
This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable. Documents the .claude/plugin-name.local.md pattern for storing plugin-specific configuration with YAML frontmatter and markdown content.
This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices.
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
Generate a custom checklist for the current feature based on user requirements.