MVP 2: Single-model auto-spec refinement loop

t-682·WorkTask·
·
·
Created1 month ago·Updated1 month ago·pipeline runs →

Description

Edit

Parent epic: t-679 Depends on: MVP 1 (executor gate)

Goal

When the executor says NO-GO, instead of bouncing to the user, automatically feed the questions back to Opus to amend the spec. The loop closes without human intervention for easy cases.

Mechanism

1. Executor says NO-GO and lists questions 2. Questions + original spec sent to Opus with prompt: "Amend this task spec to answer these questions. Incorporate answers directly into the spec, don't answer in a side channel." 3. Opus produces amended spec 4. Send amended spec back to executor for another GO/NO-GO check 5. Repeat until GO or 5 passes (circuit breaker) 6. If still NO-GO after 5 passes: bounce to user with full question history

Key behaviors

  • Opus triages executor questions: amend spec for correctness-affecting questions, ignore pedantic style questions (variable naming, etc.)
  • Each pass amends the spec in-place (the spec accumulates all context)
  • User reviews the final amended spec before coder runs (at least initially — can relax this later)

New metric

  • Passes-to-convergence per task

Acceptance criteria

  • Auto-spec loop runs without human intervention
  • Spec amendments are visible in task history (comments or description edits)
  • Passes-to-convergence is tracked
  • Circuit breaker at 5 passes works
  • User can review amended spec before execution
  • Compare first-attempt success rate against MVP 0/1 baselines

Timeline (0)

No activity yet.