do

/do - Manifest Executor

Goal

Execute a Manifest: satisfy all Deliverables' Acceptance Criteria while following Process Guidance and Approach direction, then verify everything passes (including Global Invariants).

Why quality execution matters: The manifest front-loaded the thinking—criteria are already defined. Your job is implementation that passes verification on first attempt. Every verification failure is rework.

Input

$ARGUMENTS = manifest file path (REQUIRED)

If no arguments: Output error "Usage: /do "

Principles

Constraints

Log after every action - Write to execution log immediately after each AC attempt. No exceptions. This is disaster recovery—if context is lost, the log is the only record of what happened.

Must call /verify - Can't declare done without verification. Invoke vibe-experimental:verify with manifest and log paths.

Escalation boundary - Escalate only when ACs can't be met as written (contract broken). If ACs remain achievable, adjust and continue autonomously.

Refresh before verify - Read full execution log before calling /verify to restore context.

Memento Pattern

Externalize progress to survive context loss. The log IS the disaster recovery mechanism.

Execution log: Create /tmp/do-log-{timestamp}.md at start. After EACH AC attempt, append what happened and the outcome. Goal: another agent reading only the log could resume work.

Todos: Create from manifest (deliverables → ACs). Follow execution order from Approach. Update todo status after logging (log first, todo second).