loom-autopilot

Loom Autopilot — walk-away execution

You've been asked to run unattended. Drew is not watching. Work the plan to completion, self-correcting via the verification gate, and leave a clear log. Argument: $ARGUMENTS (a plan path or a goal).

Setup (first)

1. Confirm a plan exists on disk (the argument, a PLAN.md, or a spec). If none exists, WRITE one first with superpowers:writing-plans — never start implementing without it. There is no human to approve it, so the bar is "a clear, complete plan exists," then proceed (gate #1, no approval pause).
2. Arm the verification gate for this run: mkdir -p .loom && touch .loom/unattended, and ensure .loom/ is in .gitignore. The Stop hook now blocks turn-end until typecheck/build passes.
3. Start a run log at .loom/run-<date>.md in Drew's OVERNIGHT_LOG style: Goal, then timestamped actions, decisions, and outcomes.

Loop (per task in the plan)

1. Implement — dispatch a fresh subagent per independent task via superpowers:subagent-driven-development when tasks are parallelizable.
2. Verify with real evidence — run the build/typecheck/relevant command; capture the output. Never log "done" without it (gate #2).
3. Commit the increment via /commit (small, well-messaged — the run must be reviewable and rewindable).
4. Log the result.

Hard rules while unattended

• Do NOT use AskUserQuestion — there is no one to answer. (Loom sets disallowed-tools for this skill as a guard, but treat the rule as binding regardless of whether the runtime enforces it inline.) If you hit a genuinely ambiguous product decision, log it as BLOCKED: , skip that task, and continue with the rest.
• Do NOT take destructive / irreversible / outward-facing actions (no deploys, no force-push, no gh repo create, no dropping data). Log them as DEFERRED for Drew.
• No tests unless the plan explicitly calls for them.

Finish

1. rm -f .loom/unattended .loom/verify-attempts (disarm the gate and clear the retry counter so the next run starts fresh).
2. Write a summary at the top of the run log: what shipped, what's BLOCKED, what's DEFERRED, and the final verification evidence.
3. Use superpowers:finishing-a-development-branch to present integration options — but do NOT merge/PR/deploy autonomously (outward-facing; leave it for Drew).