ralph-specum-triage
The ralph-specum-triage skill coordinates the decomposition of large software efforts into multiple specifications by delegating research and analysis to a sub-agent, then assembling results into structured epic documentation. Use this skill when explicitly requested to triage an epic, organize dependencies between specs, and establish execution sequencing before beginning per-spec implementation work.
git clone --depth 1 https://github.com/tzachbon/smart-ralph /tmp/ralph-specum-triage && cp -r /tmp/ralph-specum-triage/plugins/ralph-specum-codex/skills/ralph-specum-triage ~/.claude/skills/ralph-specum-triageSKILL.md
# Ralph Specum Triage You are a **coordinator, not a triage analyst** -- delegate decomposition work to a `triage-analyst` sub-agent. ## Contract - Epic data lives under `specs/_epics/<epic-name>/` - Track the active epic in `specs/.current-epic` - Do not guess on ambiguous epic or spec names - Triage produces a plan for multiple specs. It does not implement them ## Action 1. Check `specs/.current-epic`. If an active epic exists, summarize status and offer resume, details, or a new epic. 2. Resolve or create the epic directory and initialize `research.md`, `epic.md`, `.progress.md`, and `.epic-state.json` as needed. 3. **Delegate** triage work to a `triage-analyst` sub-agent. The sub-agent runs the four-stage triage flow: - exploration research on seams, constraints, and existing boundaries - brainstorming and decomposition into specs - validation of dependencies, contracts, and scope - finalization of epic outputs Do NOT decompose or generate epic content yourself. 4. Assemble `epic.md` by aggregating and formatting the sub-agent's output (without altering substantive content) into: - vision and scope - spec list with goals and size - dependency graph - interface contracts and sequencing notes 5. Persist `.epic-state.json` with each spec, its status, and dependencies. 6. Set `specs/.current-epic` to the active epic name. 7. Show the next unblocked spec and route back to `$ralph-specum-start` for per-spec execution. ## Output Shape The result should make it clear: - what belongs in each spec - which specs can start now - which specs are blocked by dependencies - what contracts must stay stable across specs ## Stop Behavior - **Without `--quick`**: STOP HERE. Display the epic summary and approval prompt. Do NOT continue to the next spec until the user explicitly approves or requests changes. - **With `--quick`**: Continue directly to the first unblocked spec. ## Response Handoff - After writing `epic.md`, name `epic.md` and summarize the epic plan briefly. - End with exactly one explicit choice prompt: - `approve current artifact` - `request changes` - `continue to the next spec` - Treat `continue to the next spec` as approval of `epic.md`.
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.