| name | do |
| description | Manifest executor. Iterates through Deliverables satisfying Acceptance Criteria, then verifies all ACs and Global Invariants pass. |
/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
If no arguments: Output error "Usage: /do [log-file-path]"
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. Use the skill tool: skill({ name: "verify" }) with manifest and log paths.
Escalation boundary - Escalate when: (1) ACs can't be met as written (contract broken), or (2) user requests a pause mid-workflow. If ACs remain achievable and no user interrupt, continue autonomously.
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.
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).
