/do - Manifest Executor

Goal

Execute a Manifest: satisfy all Deliverables' Acceptance Criteria while following Process Guidance and using Approach as initial direction (adapting when reality diverges), 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), optionally with execution log path and --mode <level>

If no arguments: Output error "Usage: /do [log-file-path] [--mode efficient|balanced|thorough]"

Execution Mode

Resolve mode from (highest precedence first): --mode argument → manifest mode: field → default thorough .

Invalid mode value → error and halt: "Invalid mode ''. Valid modes: efficient | balanced | thorough"

If mode is not thorough : read references/BUDGET_MODES.md for routing rules, escalation logic, and parallelism overrides. Follow those rules for the remainder of this /do run.

Existing Execution Log

If input includes a log file path (iteration on previous work): treat it as source of truth. It contains prior execution history. Continue from where it left off—append to the same log, don't restart.

Principles

Principle Rule

ACs define success Work toward acceptance criteria however makes sense. Manifest says WHAT, you decide HOW.

Approach is initial, not rigid Approach provides starting direction, but plans break when hitting reality. Adapt freely when you discover better patterns, unexpected constraints, or dependencies that don't work as expected. Log adjustments with rationale.

Target failures specifically On verification failure, fix the specific failing criterion. Don't restart. Don't touch passing criteria.

Verify fixes first After fixing a failure, confirm the fix works before re-running full verification.

Trade-offs guide adjustment When risks (R-) materialize, consult trade-offs (T-) for decision criteria. Log adjustments with rationale.

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 manifest-dev:verify with manifest, log paths, and the resolved mode: /verify <manifest> <log> --mode <level> .

Escalation boundary - Escalate when: (1) ACs can't be met as written (contract broken), (2) user requests a pause mid-workflow, (3) you discover an AC or invariant should be amended (use "Proposed Amendment" escalation type), or (4) mode-specific fix-verify loop limit is reached (see references/BUDGET_MODES.md ). If ACs remain achievable as written and no user interrupt, continue autonomously. Approach pivots don't require escalation — log adjustments with rationale and continue.

Mode-aware loop tracking - Track fix-verify iteration count and escalation count in the execution log. When mode limits are reached, follow the escalation rules in references/BUDGET_MODES.md . In efficient mode, also track total escalations and suggest mode switch after 3.

Stop requires /escalate - During /do, you cannot stop without calling /verify→/done or /escalate. If you need to pause (user requested, waiting on external action), call /escalate with "User-Requested Pause" format. Short outputs like "Done." or "Waiting." will be blocked.

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

Refresh between deliverables - Before starting a new deliverable, re-read the manifest's deliverable section and relevant execution log entries. Context degrades gradually across a long session — don't rely on what you remember from D1 when starting D3.

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). Start with execution order from Approach (adjust if dependencies require). Update todo status after logging (log first, todo second).

Collaboration Mode

When $ARGUMENTS contains a TEAM_CONTEXT: block, read references/COLLABORATION_MODE.md for full collaboration mode instructions. If no TEAM_CONTEXT: block is present, ignore this — all other sections apply as written.