Agent or flowchart? Find the box you can’t finish drawing
At a glance
Learnable test: keep deterministic paths in code; put the agent loop only on the flowchart box whose next step depends on discoveries (multi-source state, content-driven checks, unencoded domain knowledge)—else it’s an API call in a badge. This workflow is listed under learnable-paradigm, agent-design, workflows, architecture, tool-use.
AWS Labs open-source (5k+★): one harness-neutral core turns Claude Code/Codex/Cursor/Copilot/Kiro/opencode into structured, verifiable delivery workflows via `aidlc config --harness` + doctor—install script, not a new agent.
Open method: Blast/Mid/Inner write at system/subsystem/local altitude, then fixed T1 structural → T2 bug/ops → T3 adversarial gates with handoff packets—agents get AGENTS.md + prompt files, not a vague “please be careful.”
Bitbucket Cloud pattern for large monorepos: a matcher agent maps changed paths to the right review docs via Bitbucket MCP, then a fresh reviewer comments only against that short list—humans still approve.
Official Muse Code docs: request a workflow to fan out up to 1,000 child tasks (active cap ~16) for audits, migrations, or research→verify→synthesize. `/workflows` control room cancel/pause/skip; save reusable JS under `.agents/workflows/` via `muse workflows save`; settings auto|explicit|off. Note: some Apple silicon builds omit the workflow engine.