‹ 首页

ralph-specum-triage

@tzachbon · 收录于 1 周前

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.skill双击,或拖进 Claude 桌面版 / Cowork,即完成安装↓ .skill↓ .zip
用别的 agent?下载 .zip 解压,把文件夹放进它的技能目录
Claude Code~/.claude/skills/(项目级 .claude/skills/)
Codex CLI~/.codex/skills/
Cursor自动读取上面两处目录
其他工具见其文档的「skills」目录;两个下载是同一份文件,只是名字不同
/ 通过 npx 安装 校验哈希
npx oh-my-skill add tzachbon/smart-ralph/ralph-specum-triage
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- tzachbon/smart-ralph/ralph-specum-triage
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify tzachbon/smart-ralph/ralph-specum-triage
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
419GitHub stars
~541最小装载
~541含声明引用
~607文本包总量
镜像托管

怎么用

技能原文 SKILL.md作者撰写 · MIT · 1b33202

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:
  4. exploration research on seams, constraints, and existing boundaries
  5. brainstorming and decomposition into specs
  6. validation of dependencies, contracts, and scope
  7. finalization of epic outputs Do NOT decompose or generate epic content yourself.
  8. Assemble epic.md by aggregating and formatting the sub-agent's output (without altering substantive content) into:
  9. vision and scope
  10. spec list with goals and size
  11. dependency graph
  12. interface contracts and sequencing notes
  13. Persist .epic-state.json with each spec, its status, and dependencies.
  14. Set specs/.current-epic to the active epic name.
  15. 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.
按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。
…