escalate-to-workflows

escalate-to-workflows (stuck-debugging swarm)

Launchable from the superkit:iterate-to-green stall gate, or directly when stuck on a complex bug. It returns a diagnosis + proposed patch; the caller applies it and re-verifies — this skill never declares the suite green itself.

1. Preflight: are dynamic workflows available?

Dynamic workflows need Claude Code ≥ v2.1.154 and the feature enabled in /config. Check the version with claude --version (Bash). If unavailable or uncertain:

• Degrade to superpowers:dispatching-parallel-agents (a handful of parallel investigators) and tell the user how to enable workflows (/config → Dynamic workflows). Continue with the degraded path; do not stop.

2. Scope the problem

Collect ONLY: the failing test names/output and pointers to the implicated source/spec. Never dump the whole specs//.superkit/ tree (superkit:respecting-the-spec-contract).

3. Fan out (workflows path)

Ask the user how many investigation agents to fan out, warning about token cost (the runtime caps at 16 concurrent / 1,000 total per run). Then request a dynamic workflow — prefix the request with ultracode, or ask in plain language to "run a workflow" — that:

• spawns N agents, each forming and testing a DISTINCT root-cause hypothesis for the red suite, each in its own throwaway worktree;
• runs an adversarial cross-check phase where agents critique each other's findings;
• synthesizes the best-supported diagnosis + a proposed patch and returns it.

4. Hand back

Return the diagnosis + patch to the caller (iterate-to-green applies it and re-runs the suite). Optionally tell the user they can save the generated script via /workflows → s as a reusable /<name> command.