loop-statuslisted

The autonomous-loop dashboard. Consolidates every loop surface — phase-runner progress, auto-apply outcomes + per-key revert rates, cooled-down keys, the armed revert watch, learning-report findings, and the opt-in cross-project signal — into one read-only view, and writes a durable .vibeflow/reports/loop-status.md audit. Where /vibeflow:flow-status gives a quick inline glance, /vibeflow:loop-status is the full pane of glass. Read-only — never changes config or source.
mytechsonamy/VibeFlow · ★ 0 · AI & Automation · score 75

Install: claude install-skill mytechsonamy/VibeFlow

# Loop Status — the autonomous-loop dashboard (Sprint 30) After Sprints 20–29, the autonomous loop's state lives across several files. `/vibeflow:flow-status` shows a quick *inline* glance; this skill is the **full pane of glass** — one consolidated, read-only dashboard, plus a durable written audit. ## Step 1 — Read the consolidated audit ```bash bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/loop-audit.sh" ``` `loop-audit.sh` (read-only, fully guarded) returns one JSON document with every loop surface: `autoApply` (applied/held/reverted + armedWatch + cooldowns), `perKey` (per-key counts + `revertRate` + `cooledDown`), `learning` (finding count), `recentDecisions`, `phaseRunner` (the Sprint-21 progress ledger), and `crossProject` (the Sprint-28 signal, when `globalLearning.enabled`). ## Step 2 — Render the dashboard Render the JSON as a single human dashboard, in this order: ``` VibeFlow Autonomous Loop — <project> @ <currentPhase> Phase-runner: <phaseRunner.status> · step <currentStep> · attempt <attempt>/<maxConvergenceAttempts> <stepsDone>/<stepsTotal> steps (or "idle — no run" when phaseRunner is null) Auto-apply: applied <A> · held <H> · reverted <R> per key: <key> a/h/r revertRate=<r> [cooled-down] [⚠ candidate for removal] Cooled-down: <autoApply.cooldowns…> Armed watch: <autoApply.armedWatch.keys> @ <phase> (or "none") Learning: <learning.findingCount> findings → /vibeflow:learning-loop-engi