Agent Skills
› tzachbon/smart-ralph
› ralph-specum-tasks
ralph-specum-tasks
GitHub协调Ralph Specum任务阶段,解析规范并委托子代理生成tasks.md。合并状态、更新进度文件,并在非快速模式下等待用户审批,确保任务规划与执行分离。
Trigger Scenarios
用户显式请求使用$ralph-specum-tasks
用户明确要求Ralph Specum在Codex中运行任务阶段
Install
npx skills add tzachbon/smart-ralph --skill ralph-specum-tasks -g -y
SKILL.md
Frontmatter
{
"name": "ralph-specum-tasks",
"metadata": {
"action": "tasks",
"surface": "helper"
},
"description": "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."
}
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.mdanddesign.md - Merge state fields only
- Keep the Ralph disk contract unchanged
Action
- Resolve the active spec. If none exists, stop.
- Require
requirements.mdanddesign.md. Readresearch.mdwhen present,.progress.md, and current state. - Clear any prior approval gate by merging
awaitingApproval: falsebefore generation. - Respect
granularityfrom state. Allow--tasks-size fine|coarseto override it. In quick mode, default unset granularity tofine. - Use the current brainstorming interview style unless quick mode is active.
- Delegate task planning to a
task-plannersub-agent. Pass requirements, design, research, and interview context. The sub-agent writestasks.md. Do NOT write tasks.md yourself. - Read the sub-agent's output and validate it exists.
- Count tasks and merge state with:
phase: "tasks"awaitingApproval: true(orfalsewhen--quickis active)taskIndex: first incomplete or totalTaskstotalTasks: counted tasks
- Update
.progress.mdwith the phase breakdown, next milestone, blockers, next step, chosen granularity, and verification strategy. - 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, nametasks.mdand summarize the task plan briefly. - End with exactly one explicit choice prompt:
approve current artifactrequest changescontinue to implementation
- Treat
continue to implementationas approval oftasks.md.
Version History
- 1b33202 Current 2026-07-05 09:17


