Chatbot Iterate

/chatbot-iterate

Glue skill that ties the existing pieces (/feature, /work, /octo:review, the Demerzel QA tribunal, /learnings, /ce-compound) into a single chatbot-scoped iteration loop. Emits a clear gate plan up front so the human knows what review the change will need before merging.

This is the Level 2 automation in our chatbot-development ladder (per the discussion in docs/automation/chatbot-loop.md): assistant drives end-to-end on one item, human reviews and merges. Not Level 3 (auto-merge on multi-LLM green) or Level 4 (failure-fed dark factory).

When to Run

• "Pick up the next chatbot thing" — moving down the chatbot backlog systematically.
• After shipping a chatbot feature, when the next item is queued and the assistant should keep the cadence.
• Not for general feature work — use /feature directly. This skill exists to enforce the chatbot-specific gates.

Iron Law

ANY PR touching the following paths REQUIRES Demerzel tribunal verdict
+ multi-LLM review (octopus or codex) BEFORE merge:

  Common/GA.Business.ML/Agents/**
  Common/GA.Business.ML/**/Mcp/**
  Apps/ga-server/GaApi/Mcp/**
  Common/GA.Business.DSL/**
  **/IChatClientFactory*
  **/AddGuitarAlchemistAi*

The "feedback_multi_llm_review_pays_off" memory documents that
multi-LLM review caught 9 real bugs in PR #151 alone that local
tests missed. This gate is load-bearing, not bureaucratic.

NEVER mark a PR ready-for-merge on a chatbot path until both gates
have been satisfied.

Process

Step 0: Killswitch + governance-directives check

Before doing ANYTHING, check the two halt signals.

A. Local killswitch (operator-owned):

if (Test-Path state/.loop-halted) {
    Write-Host "Loop halted — sentinel present. Aborting." -ForegroundColor Red
    Get-Content state/.loop-halted
    exit 0
}

To resume:

pwsh Scripts/loop-killswitch.ps1 -Reset

Status check (read-only):

pwsh Scripts/loop-killswitch.ps1 -Status