Agent skill

ralph-specum-triage

This skill should be used only when the user explicitly asks to use `$ralph-specum-triage`, or explicitly asks Ralph Specum in Codex to triage a large effort into multiple specs.

View SKILL.md on GitHub Repository
Stars 278
Forks 15

Install this agent skill to your Project

npx add-skill https://github.com/tzachbon/smart-ralph/tree/main/plugins/ralph-specum-codex/skills/ralph-specum-triage

Metadata

Additional technical details for this skill

action
triage
surface
helper

SKILL.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.

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

tzachbon/smart-ralph

MCP Integration

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.

278 15
Explore
tzachbon/smart-ralph

Command Development

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.

278 15
Explore
tzachbon/smart-ralph

Plugin Settings

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.

278 15
Explore
tzachbon/smart-ralph

Plugin Structure

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.

278 15
Explore
tzachbon/smart-ralph

Hook Development

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.

278 15
Explore
tzachbon/smart-ralph

Skill Development

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.

278 15
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results