Agent Skills
› tzachbon/smart-ralph
› ralph-specum-implement
ralph-specum-implement
GitHubRalph Specum实施协调技能,负责解析规范、管理任务状态及原型记录,并委派子代理执行具体开发任务。
Trigger Scenarios
用户明确要求使用$ralph-specum-implement
请求Ralph Specum以快速模式或显式继续运行实施
Install
npx skills add tzachbon/smart-ralph --skill ralph-specum-implement -g -y
SKILL.md
Frontmatter
{
"name": "ralph-specum-implement",
"metadata": {
"action": "implement",
"surface": "helper"
},
"description": "This skill should be used only when the user explicitly asks to use `$ralph-specum-implement`, or explicitly asks Ralph Specum in Codex to run implementation for approved tasks, quick mode, or an explicit continue request."
}
Ralph Specum Implement
You are a coordinator, not an executor -- delegate each task to a spec-executor sub-agent.
Contract
- Resolve the active spec by explicit path, exact name, or
.current-spec - Require
tasks.md - Recompute task counts from disk before execution
- Merge state fields only
- Reconcile prototype records before dispatch and block only dependent work
- Remove
.ralph-state.jsononly when all tasks are complete, verified, andactivePrototypesis empty
Action
- Resolve the active spec. If none exists, stop.
- Require
tasks.md. Read.progress.md, current state, and current task markers. - Parse
tasks.mdonce into ordered top-level task rows. Include only unindented checkboxes outside fenced example blocks whose next token is a concrete numeric task ID,V<number>,VE<number>, orVF; exclude nested and example checkboxes, completion criteria, and placeholder IDs. From that one list derivetotal, the completed count across all rows, andnext_indexas the zero-based position of the first incomplete row ortotalwhen none remains. Do not derivenext_indexfrom the completed count; non-prefix completion cases resume at the earliest incomplete row. - Resolve the dispatch task index before merging state. For fresh execution, use
next_index. For a prototype return, require a validated non-negativereturnTaskIndexand verify that it identifies the first eligible incomplete task. Merge state once with:phase: "execution"awaitingApproval: falsetotalTasks: total- taskIndex:
next_indexfor fresh execution, or the validatedreturnTaskIndexfor a prototype return - preserve
taskIteration,maxTaskIterations,globalIteration,maxGlobalIterations,commitSpec, andrelatedSpecs
- Before dispatch, run
prototype_records.py reconcilewhenever state exists and runselect-downstreamwheneveractivePrototypesis nonempty or prototype history exists. Request--target execution,--target "task:$TASK_INDEX", and--pathfor every declared current-task path. Stop when an active blocker or stale input targets the work, or when any matchingtargetDecisionsentry is not bothproofAvailable: trueandeligible: true. Missing dependency or approved-transfer proof blocks conservatively. Report the prototype ID and resume active work through$ralph-specum-prototype --resume <id>; route terminal staleness to its earliest affected phase or task. - On a prototype return, verify that the merged
taskIndexstill equals the validatedreturnTaskIndexand identifies the first eligible incomplete task before dispatch. - Delegate each task to a
spec-executorsub-agent. Pass the task description, file targets, success criteria, and context from.progress.md. The sub-agent implements the task and outputsTASK_COMPLETE. Do NOT implement tasks yourself. Execute tasks in order until complete or blocked. [P]tasks may batch only when file sets do not overlap and verification is independent.[VERIFY]tasks stay in the same run and must produce explicit verification evidence.- Marker syntax must be explicitly present in
tasks.md. If markers are absent, treat tasks as non-batchable by default. - VE tasks are valid quality tasks when the spec includes autonomous end-to-end verification.
- Native task sync metadata should be preserved when present.
- After each task or safe batch:
- mark the checkbox
- update
.progress.md - merge the state update
- use the task
Commitline unless commits were explicitly disabled
- Before any batching, generated-task, CI, review-fix, branch-publication, or PR-lifecycle push, apply the Prototype Evidence Push Gate in
../../references/workflow.md. Normal mode may ask at that boundary for separate explicit authorization naming every outbound**/prototypes/*.mdrecord. Quick mode asks no question and skips every push. A skipped or denied push ends the dependent remote lifecycle path: do not rungh pr create,gh pr merge,gh pr checks,gh pr view,gh api,gh run,gh issue, remote review polling, issue writes, or later remote steps that depend on that push. Quick mode continues or finishes locally and reportsRemote lifecycle skipped: prototype evidence stayed local.Preserve the existing normal remote lifecycle only after the gate completes the push. Never push an isolated prototype source branch.commitSpecauthorizes local commits only. - On failure or interruption, persist the current state and stop with a resumable summary.
- On full completion, reconcile again. If
activePrototypesremains nonempty, preserve.ralph-state.jsonand stop with its IDs. Otherwise remove state and report completion.
Resume Rules
- Resume from the persisted task state when execution was already in progress.
- If disk state and task checkboxes disagree, prefer
tasks.mdfor completion and repair state to match. - If approval is still pending for tasks, stop and get approval unless quick mode or explicit user direction says to continue.
- A stale task or dependent active prototype always wins over resume dispatch. An unrelated active prototype does not pause the current task.
Version History
-
183c1be
Current 2026-09-02 23:24
新增可选的原型阶段支持,增强任务依赖验证与原型记录协调机制。
- 1b33202 2026-07-05 09:17


