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. Derive `RALPH_CODEX_PLUGIN_ROOT` from this loaded skill by resolving two parent directories from the `SKILL.md` directory. Never derive it from the project working directory. ## 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. 6. Report prototype dependencies without mutating them: - Treat a missing `activePrototypes` field as an empty map. - When state exists, run `"$RALPH_CODEX_PLUGIN_ROOT/scripts/prototype_records.py" select-downstream --base-path "$BASE_PATH" --state "$BASE_PATH/.ralph-state.json"` using the selected spec's resolved `basePath`. - Show each blocker from `activeBlockers` with prototype ID, status, blocked artifact or transition, `returnPhase`, and `returnTaskIndex`. - Show `staleArtifacts` and `staleTaskIndexes` from the selection result. - Do not reconcile, remove active entries, edit records, or change blocker data. If no overlay or stale dependency exists, preserve the existing switch output.
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 generating spec artifacts (research.md, requirements.md, design.md, tasks.md), formatting agent output, structuring phase results, or when any Ralph agent needs guidance on concise, scannable output formatting. Applies to all Ralph spec phase agents.
Core principle that the main agent is a coordinator, not an implementer. All work must be delegated to subagents.
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 a Ralph phase must identify critical user decisions, run a layered grill, persist partial answers, obtain explicit approval, or resume an interrupted phase interview before delegating artifact work.
Internal Ralph Specum contract for Codex phase interviews, skill manifests, approval, and delegation gates. Phase coordinators load this skill directly; users do not invoke it as a workflow phase.
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.