ralph-specum-status
The ralph-specum-status skill reports the current state of Ralph Specum across configured specification roots by reading configuration files and inspecting spec directories. Use it when explicitly requested to check Ralph Specum status or active spec progress, providing details on the active spec, current phase, artifacts present, task completion, and pending approvals.
git clone --depth 1 https://github.com/tzachbon/smart-ralph /tmp/ralph-specum-status && cp -r /tmp/ralph-specum-status/plugins/ralph-specum-codex/skills/ralph-specum-status ~/.claude/skills/ralph-specum-statusSKILL.md
# Ralph Specum Status Use this to report Ralph state across configured spec roots. ## Contract - Read `.claude/ralph-specum.local.md` when present - Default specs root is `./specs` - `.current-spec` lives in the default specs root - Hidden directories do not count as specs ## Action 1. Resolve configured roots. 2. Read `.current-spec` to identify the active spec. - If `.current-spec` is missing or empty, report that there is no active spec and continue listing specs across roots. 3. Read `specs/.current-epic` when present and summarize epic status. 4. For each spec directory, inspect: - `.ralph-state.json` - `research.md` - `requirements.md` - `design.md` - `tasks.md` 5. If `tasks.md` exists, count completed and incomplete tasks. 6. Group results by spec root. 7. Show the active spec, current phase, backlog state, approval state, granularity when present, and which artifacts exist. ## Output - Specs in the default root can be shown by name. - Specs in other roots should include the root suffix for disambiguation. - Include the next likely command when it is obvious. - If an epic is active, include the next unblocked spec. - If approval is pending, explicitly tell the user to approve the current artifact, request changes, or continue to the named next step.
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.