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.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/ralph-specum-triage-tzachbon-smart-ralph
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
- 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.jsonas needed. - Delegate triage work to a
triage-analystsub-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.mdby 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.jsonwith each spec, its status, and dependencies. - Set
specs/.current-epicto the active epic name. - Show the next unblocked spec and route back to
$ralph-specum-startfor 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, nameepic.mdand summarize the epic plan briefly. - End with exactly one explicit choice prompt:
approve current artifactrequest changescontinue to the next spec
- Treat
continue to the next specas approval ofepic.md.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?