Agent Skills
› tzachbon/smart-ralph
› ralph-specum-triage
ralph-specum-triage
GitHub用于协调大型工作项(Epic)的多规格分解任务。通过解析模式标志,验证并管理Epic状态,集成技能发现与面试框架,最终将分解工作委派给子代理执行。
Trigger Scenarios
用户显式调用 $ralph-specum-triage
请求 Ralph Specum 对大型工作进行规格分解
Install
npx skills add tzachbon/smart-ralph --skill ralph-specum-triage -g -y
SKILL.md
Frontmatter
{
"name": "ralph-specum-triage",
"metadata": {
"action": "triage",
"surface": "helper"
},
"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."
}
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.
Version History
-
ac7251a
Current 2026-09-08 21:26
修复:强制执行严格的面试阶段门控检查
-
183c1be
2026-09-02 23:25
新增对 --quick/--interactive 令牌解析及 epic 名称校验逻辑;强化技能发现与面试框架加载流程,替代旧版直接生成内容模式。
- 1b33202 2026-07-05 09:17


