Ralph Specum Triage Skill for Codex

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.

711 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

432

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

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

The instruction itself

6 sections, as written by the author

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

Check specs/.current-epic. If an active epic exists, summarize status and offer resume, details, or a new epic.
Resolve or create the epic directory and initialize research.md, epic.md, .progress.md, and .epic-state.json as needed.
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.

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
Persist .epic-state.json with each spec, its status, and dependencies.
Set specs/.current-epic to the active epic name.
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.

Other skills for the same job

different authors, same section of the catalogue

Skill Creator

by anthropics

vendor ×10

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

Replace with description of the skill and when Claude should use it.

35 tokens

Dispatching Parallel Agents

by ZhanlinCui

×5

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

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.

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Use when creating new skills, editing existing skills, or verifying skills work before deployment

26k tokens scripts

How to use it

Copy the folder

Take tzachbon/ralph-specum-triage from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.