ralph-specum-help
Ralph Specum Help provides guidance on using the Ralph Specum workflow system in Codex, covering its primary skill, ten helper skills for phase-specific control, and standard execution flows including triage for complex efforts and quick mode for autonomous generation. Use this skill when users explicitly request help understanding Ralph Specum commands or need clarification on workflow stages, approval requirements, and disk storage conventions.
git clone --depth 1 https://github.com/tzachbon/smart-ralph /tmp/ralph-specum-help && cp -r /tmp/ralph-specum-help/plugins/ralph-specum-codex/skills/ralph-specum-help ~/.claude/skills/ralph-specum-helpSKILL.md
# Ralph Specum Help Use this to explain the Ralph Specum surface in Codex. ## Cover - Primary skill: `$ralph-specum` - Helper skills: `$ralph-specum-start`, `$ralph-specum-triage`, `$ralph-specum-research`, `$ralph-specum-requirements`, `$ralph-specum-design`, `$ralph-specum-tasks`, `$ralph-specum-implement`, `$ralph-specum-status`, `$ralph-specum-switch`, `$ralph-specum-cancel`, `$ralph-specum-index`, `$ralph-specum-refactor`, `$ralph-specum-feedback`, `$ralph-specum-help` - Normal flow: start, stop, research, approval, requirements, approval, design, approval, tasks, approval, implement - Large effort flow: triage, then start each unblocked spec - Quick mode: generate missing artifacts and continue into implementation in one run only when the user explicitly asks for quick or autonomous flow - Disk contract: `./specs` or configured roots, `.current-spec`, optional `.current-epic`, per-spec markdown files, `.ralph-state.json` ## Guidance - Recommend `$ralph-specum` as the default entrypoint. - Recommend `$ralph-specum-triage` when the user describes a large, multi-part, or dependency-heavy effort. - Mention helper skills when the user wants explicit phase control. - Explain that Ralph does not self-advance by default. The user must approve the current artifact, request changes, or explicitly continue to the next step. - Mention optional bootstrap assets only when the user wants repo-local guidance.
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.