goal-loop

Invoke the goal loop with the ADO ID, for example /goal-loop ADO-1847. It sequences planning, ICEA drafting, tech spec, approval, and implementation, pausing at each gate for your SAVE or APPROVE keyword.

The loop runs inside the implementation step: generated code is scored against the approved Acceptance Criteria, revised, and re-scored until all criteria pass or a hard iteration ceiling is reached. If it escalates, unmet criteria are surfaced in the write-pending prompt.

No. The orchestrator never issues APPROVE, SAVE, or any gate keyword on your behalf. Every gate — SAVE PLAN, SAVE ICEA, SAVE TECH, APPROVE, and WRITE PENDING — requires explicit human input to preserve the Feature-Gate and Write-Gate integrity boundary.

Yes. It checks for an approved ICEA document on disk for the work item and skips directly to the approval and implementation phases. Only missing or unapproved ICEAs trigger the full planning flow.

It owns no logic of its own — it only sequences existing skills and never drafts specs, generates code, or writes to disk. The self-scoring loop applies only to implementation; the ICEA and Tech Spec are never self-scored to avoid circular evaluation.