ralph-specum-switch
The ralph-specum-switch skill switches the active specification in a Ralph Specum project by reading configuration from `.claude/ralph-specum.local.md`, resolving the target spec by name or path, and updating the `.current-spec` file accordingly. Use this when a user explicitly requests to change which specification is currently active in the Codex workflow.
git clone --depth 1 https://github.com/tzachbon/smart-ralph /tmp/ralph-specum-switch && cp -r /tmp/ralph-specum-switch/plugins/ralph-specum-codex/skills/ralph-specum-switch ~/.claude/skills/ralph-specum-switchSKILL.md
# Ralph Specum Switch Use this to switch the active spec. ## Contract - Read `.claude/ralph-specum.local.md` when present - Parse `specs_dirs` from frontmatter to discover all spec roots - Treat the first `specs_dirs` entry as the default root - Default specs root is `./specs` - `.current-spec` lives in the default specs root - Do not guess on ambiguous names ## Action 1. Resolve the requested target by full path or exact name. 2. If no target was provided, list available specs grouped by root. 3. If the name is ambiguous across roots, stop and require a full path. 4. Update `.current-spec`: - bare name for the default root - full path for non-default roots 5. Read the target spec state and summarize phase, progress, approval state, and present files.
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.