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
- Resolve the active spec. If none exists, stop.
- Require
requirements.md and design.md. Read research.md when present, .progress.md, and current state.
- Clear any prior approval gate by merging
awaitingApproval: false before generation.
- Respect
granularity from state. Allow --tasks-size fine|coarse to override it. In quick mode, default unset granularity to fine.
- Use the current brainstorming interview style unless quick mode is active.
- 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.
- Read the sub-agent's output and validate it exists.
- Count tasks and merge state with:
phase: "tasks"awaitingApproval: true (or false when --quick is active)taskIndex: first incomplete or totalTaskstotalTasks: counted tasks
- Update
.progress.md with 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, name tasks.md and summarize the task plan briefly.
- End with exactly one explicit choice prompt:
approve current artifactrequest changescontinue to implementation
- Treat
continue to implementation as approval of tasks.md.
1---2name: ralph-specum-tasks-23description: 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.4---56# Ralph Specum Tasks78You are a **coordinator, not a task planner** -- delegate ALL work to a `task-planner` sub-agent.910## Contract1112- Resolve the active spec by explicit path, exact name, or `.current-spec`13- Require `requirements.md` and `design.md`14- Merge state fields only15- Keep the Ralph disk contract unchanged1617## Action18191. Resolve the active spec. If none exists, stop.202. Require `requirements.md` and `design.md`. Read `research.md` when present, `.progress.md`, and current state.213. Clear any prior approval gate by merging `awaitingApproval: false` before generation.224. Respect `granularity` from state. Allow `--tasks-size fine|coarse` to override it. In quick mode, default unset granularity to `fine`.235. Use the current brainstorming interview style unless quick mode is active.246. **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.257. Read the sub-agent's output and validate it exists.268. Count tasks and merge state with:27 - `phase: "tasks"`28 - `awaitingApproval: true` (or `false` when `--quick` is active)29 - `taskIndex: first incomplete or totalTasks`30 - `totalTasks: counted tasks`319. Update `.progress.md` with the phase breakdown, next milestone, blockers, next step, chosen granularity, and verification strategy.3210. If spec commits are enabled, commit only the spec artifacts.3334### Stop Behavior3536- **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.37- **With `--quick`**: Review quickly, then continue directly into implementation.3839## Output Shape4041Use 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.4243## Response Handoff4445- After writing `tasks.md`, name `tasks.md` and summarize the task plan briefly.46- End with exactly one explicit choice prompt:47 - `approve current artifact`48 - `request changes`49 - `continue to implementation`50- Treat `continue to implementation` as approval of `tasks.md`.
majiayu000