‹ 首页

ralph-specum-tasks

@tzachbon · 收录于 1 周前

This skill should be used only when the user explicitly asks to use `$ralph-specum-tasks`, or explicitly asks Ralph Specum in Codex to run the tasks phase.

适合你,如果需要在Codex中运行Ralph Specum的任务阶段

/ 下载安装
ralph-specum-tasks.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-tasks
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- tzachbon/smart-ralph/ralph-specum-tasks
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify tzachbon/smart-ralph/ralph-specum-tasks
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
419GitHub stars
~558最小装载
~558含声明引用
~615文本包总量
镜像托管

怎么用

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

Ralph Specum Tasks

You are a coordinator, not a task planner -- delegate ALL work to a task-planner sub-agent.

Contract
  • Resolve the active spec by explicit path, exact name, or .current-spec
  • Require requirements.md and design.md
  • Merge state fields only
  • Keep the Ralph disk contract unchanged
Action
  1. Resolve the active spec. If none exists, stop.
  2. Require requirements.md and design.md. Read research.md when present, .progress.md, and current state.
  3. Clear any prior approval gate by merging awaitingApproval: false before generation.
  4. Respect granularity from state. Allow --tasks-size fine|coarse to override it. In quick mode, default unset granularity to fine.
  5. Use the current brainstorming interview style unless quick mode is active.
  6. Delegate task planning to a task-planner sub-agent. Pass requirements, design, research, and interview context. The sub-agent writes tasks.md. Do NOT write tasks.md yourself.
  7. Read the sub-agent's output and validate it exists.
  8. Count tasks and merge state with:
  9. phase: "tasks"
  10. awaitingApproval: true (or false when --quick is active)
  11. taskIndex: first incomplete or totalTasks
  12. totalTasks: counted tasks
  13. Update .progress.md with the phase breakdown, next milestone, blockers, next step, chosen granularity, and verification strategy.
  14. If spec commits are enabled, commit only the spec artifacts.
Stop Behavior
  • Without --quick: STOP HERE. Display the walkthrough summary and approval prompt. Do NOT continue to implementation. Wait for the user to explicitly approve and request the next phase.
  • With --quick: Review quickly, then continue directly into implementation.
Output Shape

Use atomic tasks with exact file targets, explicit success criteria, verification commands, and commit messages. Preserve POC-first ordering. Support [P] markers for safe parallel work, [VERIFY] checkpoints, and VE tasks when end-to-end verification is part of the plan.

Response Handoff
  • After writing tasks.md, name tasks.md and summarize the task plan briefly.
  • End with exactly one explicit choice prompt:
  • approve current artifact
  • request changes
  • continue to implementation
  • Treat continue to implementation as approval of tasks.md.
按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

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