work
/work (aliases: /ultracode, /quality-orchestrator) — Full Quality Workflow Orchestrator
This is the central orchestrator that makes the entire quality pattern system practical and automatic.
Workflow execution model (name the shape before you fan out)
There is no JS orchestration engine — "workflow mode" is a discipline the agent executes by hand: spawn a sub-agent (with the right sub-agent role, in an isolated worktree, in the background), wait for all, then collect its result. Before any fan-out, state the shape out loud in your harness's todo/plan tool / the decision record. There are exactly three:
- PIPELINE (default) — each item flows through its stages independently, no barrier between stages (verify finding A while finding B is still being reviewed). Wall-clock = slowest single-item chain. This is most multi-stage quality work.
- PARALLEL / BARRIER — block until all of stage N-1 is done, justified only by a real cross-item dependency: dedup/merge over the full set, early-exit-on-zero, or cross-item comparison (judge ranking all candidates, synthesis over all verdicts). "It's cleaner" is not a justification — when in doubt, pipeline.
- LOOP (until-dry / until-budget) — unknown-cardinality work: repeat rounds until K≥2 consecutive rounds yield zero new unique items (until-dry) or remaining budget < cost of another useful round (until-budget). Each round is a fan-out + a dedup barrier against a persistent
seen[].
The full model — mechanics, smell tests, the canonical Review harness — lives in references/workflow-mode.md. The failure modes these shapes defend against live in references/anti-error-lessons.md (L1–L8, summarized and wired into the phases below). Do not restate those docs here; reference them.