Mk Autobuild

mk:autobuild — Autonomous Multi-Hour Build Orchestration

Step-file workflow that runs the complete generator/evaluator harness pipeline as an autonomous build. Handles green-field product builds (planner stage → contract stage → evaluator loop → ship decision) with adaptive scaffolding density based on detected model tier.

When to Use

Activate when:

• User runs the autobuild skill "build a X" (or any green-field product description)
• Existing kit detection routes a green-field "build me an app" intent here instead of mk:cook
• A multi-hour autonomous build is requested with no manual handholding

Skip when:

• The task is a single feature, bug fix, or refactor → use the cook skill instead
• The task is a doc update → use the existing doc skills
• The request is "explain X" or "review Y" → use the appropriate single-shot skill

Hard Constraints

1. Adaptive density — picks scaffolding density via mk:scale-routing (or density-select.sh); honors MEOWKIT_AUTOBUILD_MODE env override
2. Budget caps — warns at $30 spent, requires explicit approval at $100, hard-blocks at user-set --budget value
3. 6-hour wall-clock timeout — hard limit per Anthropic's observed runs ; checkpoints every step for resumability
4. Max 3 iteration rounds between generator and evaluator before escalating to human (configurable via --max-iter)
5. Run report mandatory — every autobuild run produces tasks/autobuild-runs/YYMMDD-{slug}/run.md with full audit trail
6. Coexists with mk:cook — does not replace it; both route through Gate 1 + Gate 2
7. TDD opt-in (parallel to cook): autobuild respects --tdd like other flows. Default: no RED-phase gate. With --tdd: writes the .meowkit/state/tdd-mode sentinel and the developer waits on tester before each generator iteration. Active-verification HARD GATE (Rule 8 of harness-rules.md) is independent of TDD mode and always applies.

Workflow

Execute via workflow.md. Step-file architecture — load one step at a time.

Step 0: Tier Detection      → call mk:scale-routing; pick density (MINIMAL|FULL|LEAN)
Step 1: Plan                → invoke mk:plan-creator --product-level
Step 2: Contract            → invoke mk:sprint-contract (skipped if LEAN + small)
Step 3: Generate            → spawn developer sub-task w/ 4-subphase pattern
Step 4: Evaluate            → invoke mk:evaluate
Step 5: Iterate or Ship     → PASS → shipper; FAIL → loop to step-3 (max --max-iter)
Step 6: Run Report          → write the audit trail

Density Modes

Cursor agents run with model: inherit — there is no per-call model-id string to auto-detect, so density never self-selects LEAN. LEAN is reachable only via an explicit --tier lean flag or MEOWKIT_AUTOBUILD_MODE=LEAN; see references/adaptive-density-matrix.md for the full rationale and override sources.

Run Report Schema

Every run writes tasks/autobuild-runs/YYMMDD-{slug}/run.md:

---
run_id: 260408-1450-build-todo
density: LEAN
model: inherit (tier set via --tier lean)
budget_cap: 50
budget_spent: 12.40
iterations: 1
status: PASS | WARN | FAIL | ESCALATED | TIMED_OUT
started: 2026-04-08T14:50:00Z
ended: 2026-04-08T15:18:00Z
---

# Autobuild Run — {task description}

## Density Decision
- Tier: {tier}
- Model: inherit ({model-hint if user supplied one via --model, else "not detectable"})
- Density: {MINIMAL|FULL|LEAN}
- Source: scale-routing | env-override | --tier flag

## Per-Step Artifacts
- step-00: {tier-detection result}
- step-01: tasks/plans/{plan-dir}/plan.md
- step-02: tasks/contracts/{contract}.md (or "skipped — LEAN small sprint")
- step-03: handoff at tasks/handoff/{slug}-sprint-1.md
- step-04: verdict at tasks/reviews/{slug}-evalverdict.md
- step-05: iteration count + final action
- step-06: this file

## Budget Trail
| Step | Spent | Cumulative |
|---|---|---|
| ... | ... | ... |

## Final Verdict
{PASS/FAIL/ESCALATED summary + next action}

Gotchas

• Don't run on a non-green-field task. Use mk:cook for single features, bug fixes, refactors. The autobuild workflow is for "build me an app" scope.
• Density override stays in scope. MEOWKIT_AUTOBUILD_MODE=LEAN does NOT skip Gate 2. Review verdict is still mandatory before ship.
• Iteration loops are bounded. Max 3 by default. After round 3, escalate — don't keep iterating blindly.
• Budget check is authoritative. If budget-tracker.sh says block, the autobuild workflow halts even mid-iteration.
• Run reports are append-only. Don't edit prior steps' entries — the report is the audit trail.
• Resumable. If the autobuild workflow is killed mid-run, the autobuild skill --resume {run-id} picks up at the last completed step.

--advice (composable, off by default)

Opt-in strategic supervision for one run. At named macro checkpoints — GUIDE at the Plan/Contract boundary, RESCUE on a plateau or scope drift, REVIEW after the terminal evaluator verdict and before the Gate 2 question, RECHECK after a correction; hard cap 5 — the athena agent assesses the situation, recommends an operational path inside the locked scope, and may return the work for correction.

It never approves. Gate 2 stays human, the evaluator keeps its verdict and its active-verification hard gate, and the iteration cap and budget thresholds keep their own schedules. Checkpoints are macro boundaries — never per generated artifact and never per evaluator iteration, so a five-round build makes no more calls than a one-round build.

Without the flag there are zero calls and no state is written.

Checkpoints: references/advice-checkpoints.md. Contract: .cursor/rules/domain-advice-supervision.mdc (load only when the flag is present).

References

Start

Read and follow workflow.md.