AFK Implementation

AFK Implementation runs one bounded delivery slice without mid-run steering. It uses the same spec, backlog, plan, worker-wave, validation, review, and docs responsibilities as manual Implementation, but stops at the explicit review and delivery-resume boundaries.

• Use this when: the decision frontier is closed, the spec is agent-ready, and the goal can finish without a new human decision.
• It gives you: unattended delivery through plan-derived worker waves with automatic evidence.
• It ends with: completed scope or a concrete blocker, plus checks, review, docs output, and residual risk.
• Wrapped phase/skills: $goalify, $delivery-phase, $write-backlog, $create-plan, $implement-spec, $review-phase, optional $debugging-phase, and $docs-ingest-phase.

Starting Contract

The goal names one objective, exact scope and non-goals, read-first sources, the agent-ready spec, required skills, automatic validation, blocker conditions, and final report expectations. If a human decision or missing source is required, the run stops and reports it.

Autonomous Run

agent-ready SPEC.md
  -> optional write-backlog projection
  -> create-plan
  -> full-parallel worker waves
  -> validation
  -> review_due and stop
  -> explicit review-phase invocation
  -> retained review_routed and stop
  -> explicit delivery resume

implement-spec launches every unblocked task with a disjoint write scope. Shared files have one owner. Failed validation blocks dependent tasks, while independent tasks may continue only when their premises remain valid.

Flow

1. Use $goalify when the objective needs a compaction-safe goal prompt.
2. Confirm the spec is agent-ready and dependency evidence is available.
3. Let $delivery-phase project backlog items when required and create the execution plan.
4. Execute the plan through dependency-aware worker waves.
5. Run the declared validation, then let $delivery-phase persist review_due and stop.
6. The operator explicitly invokes $review-phase; review returns retained review_routed and stops.
7. The operator explicitly resumes $delivery-phase. Delivery consumes the route and uses $debugging-phase only when runtime evidence establishes a failure. Fixes 1 and 2 return to review_due; fix 3 uses focused validation without review 4.
8. Run $docs-ingest-phase or record why no docs changed.
9. Stop when the objective is complete or a blocker invalidates safe continuation.

At the review gate, $delivery-phase persists review_due and stops. The operator explicitly invokes $review-phase; review returns retained review_routed and stops. The operator then explicitly resumes $delivery-phase from the retained route. A single AFK goal does not cross these explicit boundaries automatically.

Stack-Aware Work

Delivery records the current branch before implementation and keeps the complete run on that branch. It updates that branch's existing PR or creates one only when none exists; conflicting branch or PR intent blocks the run.

Terminal Outcome

The final report includes changed paths, worker-wave ownership, checks, browser or manual evidence, review status, docs metadata changes, blockers, and remaining risk.

See Goal Mode And AFK, Full-Parallel Delivery, and Validation Gates.