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 / Use
npx skills add tzachbon/smart-ralph --skill ralph-specum-triageInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
LegalSupported Platforms
Tags
Our assessment of ralph-specum-triage
ralph-specum-triage scores 81/100 on our quality scale, 185th of 210 Legal skills we index.
Its SKILL.md is 6.5 KB long, split into 6 sections and no code examples: a thorough specification that gives an agent plenty to work with.
It has 550 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so ralph-specum-triage is actively maintained.
- Our last check on 2026-11-08 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-05. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
ralph-specum-triage compared with similar skills
All 4 of these similar skills score higher than ralph-specum-triage; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| ralph-specum-triage (this skill)by tzachbon | 81 | 550 | 2mo ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 57d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 57d ago | SKILL.md |
| prospectingby coreyhaines31 | 100 | 60.1k | 7d ago | SKILL.md |
| ad-creativeby coreyhaines31 | 100 | 60.1k | 7d ago | SKILL.md |
Frequently asked questions
- How do I install ralph-specum-triage?
- Run
npx skills add tzachbon/smart-ralph --skill ralph-specum-triage. The install tabs above show the steps for each supported agent. - Which AI agents does ralph-specum-triage work with?
- It is written for OpenAI Codex, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is ralph-specum-triage safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is ralph-specum-triage still maintained?
- The repository was last updated about 2 months ago, so ralph-specum-triage is actively maintained.
Skill content
View source on GitHubname: ralph-specum-triage
description: 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.
metadata:
surface: helper
action: triage
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
- Parse exact
--quickand exact--interactivetokens before routing. Reject both together,-q, variants, and natural-language substitutes. - Check
specs/.current-epic. If an active epic exists, load its.epic-state.jsonasSTATEand normalize mode before any possible question. With exact--quick, resume the matching active epic without prompting; an explicit different epic must include its goal. In interactive mode, summarize status and offer resume, details, or a new epic. - Validate the resolved epic name against
^[a-z0-9]+(-[a-z0-9]+)*$before constructing any path. Reject invalid names. Ifspecs/_epics/<epic-name>/.epic-state.jsonalready exists, reuse and resume it without replacing state or progress. If the directory exists without a valid state, stop and require a different name or an explicit user-authorized reset. Only a missing directory may be initialized. - Resolve or create only the epic directory,
.progress.md, and.epic-state.json. Serialize the name and goal through a JSON encoder such asjq --arg. Use.epic-state.jsonasSTATEfor every phase gate command with phasetriage. Use.epic-state.jsonasSTATEfor every writer. After that, do not require.ralph-state.json. Create noresearch.md,epic.md, or generatedplan.mdbefore approval. - For a new epic, run
scripts/phase_gate.py mode STATEwith the exact parsed mode flag, then registerspecs/.current-epicbefore discovery. Exact quick mode asks no setup question; missing required name or goal is an input error. - Resolve the output destination from explicit input and configuration. In exact quick mode, use local Spec files as the deterministic default and ask nothing. Only interactive mode may ask one administrative destination question when the destination remains ambiguous; that answer never satisfies the interview gate.
- Ensure skill discovery pass 1 exists for the epic goal. Collect plugin, project
.agents/skills, project.claude/skills, and current harness catalog entries. Select explicitly named skills and record shadowed duplicates. - Load
skills/interview-framework-codex/SKILL.md, its required algorithm and domain-modeling references, and every selected domain contract in both interactive and quick mode. In interactive mode, follow the algorithm for critical decomposition boundaries, stable cross-spec contracts, dependency choices, and sequencing risks. Ask no storage, naming, branch, or discoverable question. - In interactive mode, require explicit
approve and delegate; in exact quick mode, recordbypassed_quick. In both modes, runphase_gate.py check-delegationwith phasetriageand the current loaded-manifest identity before every artifact-producing child. Apply the shared hard-transition invariant before every triage artifact writer. A failedcheck-delegationin either mode stops this invocation before phase transition, child dispatch, or target-artifact write; after a normal-mode failure, only the next explicit invocation creates a fresh manifest/interview identity. After an exact--quickdelegation failure, the next explicit invocation reruns discovery, records a freshphaseSkillLoadand interview identity, and does not reuse a terminalbypassed_quickinterview or its discovery revision. Only a matching in-progresscollectingorawaiting_confirmationinterview is resumable. Exact--quickretains its existing question-and-approval bypass and discovery, manifest, delegation, and writer checks. - Read-only exploration children may inspect seams, constraints, and existing boundaries, but they write no epic artifact.
- Keep the existing epic-state, read-only exploration, and multiwriter flow, plus each child packet, identity tuple, and receipt behavior, unchanged. Use separate unique gated writer dispatches as needed:
- a triage research writer for
research.md - a triage plan writer for
epic.mdand generated specplan.mdfiles - a fresh revision writer for every artifact-review revision
Pass the absolute gate helper path, epic state path, identity tuple, unique teammate dispatch identity, and verbatim
phaseSkillLoadmanifest to each writer. Each writer records its manifest loads and passescheck-agent-writewith its unique identity before its first filesystem artifact write.
- The coordinator does not assemble, format, or revise artifact content. Validate the gated writer outputs and persist
.epic-state.jsonwith each spec, its status, dependencies, and gate receipts. - Keep
specs/.current-epicset to 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 exact
--quick: Record the quick bypass and continue directly to the first unblocked spec.
Response Handoff
- After writing
epic.md, nameepic.mdand summarize the epic plan briefly. - When normalized
quickModeis false, end with exactly one explicit choice prompt:approve current artifactrequest changescontinue to the next spec
- Treat
continue to the next specas approval ofepic.md. - With exact
--quick, do not show this prompt; continue directly to the first unblocked spec after the gates succeed. - During artifact review,
apply the changesimmediately delegates already-recorded feedback through a fresh unique gated revision writer, redisplays the artifacts, and stays at this approval gate. Ask one focused change question only when no feedback is pending. Control-onlycontinue,proceed, andgo aheadapprove nothing.
Related Skills
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
prospecting
60.1kWhen the user wants to find and qualify prospects for outbound, or asks who to target first, which signal to prioritize, or where to spot buyers with the problem: buying signals, enrichment, verification, account research.
ad-creative
60.1kWhen the user wants to write or judge ad creative, or asks which ad, hook, or angle to run or kill: headlines, primary text, and variations for Google, Meta, LinkedIn, and TikTok, fresh angles when creative fatigues. Test hypotheses name the metric, comparison, and expected direction.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
