executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
ralph-loopExecute exactly one explicitly assigned Kanban task to a validated queued commit. Use only when the user explicitly requests ralph-loop.
Independent GitHub snapshot · Automated classification · Original documentation governs
Read references/implement.md completely and follow it.
Stay within the assigned task. Do not select unrelated work, edit tasks.md, auto-tag releases, push, deploy, mutate production, or broaden scope because another issue is noticed. Record a bounded related Kanban follow-up when necessary.
Keep durable instructions concise and evidence-backed. Status belongs in the task response and runtime receipts, not AGENTS.md.
Controller checkpoints are best-effort local durability warnings after terminal metadata is durable. They never gate yy pi, yy task, yy merge, product commits, candidates, or releases.
Treat the following as the complete user-assigned request. Preserve task references and directives literally; resolve them only through the normal agent workflow.
$ARGUMENTS