Topic
Source-linked workflows that name workflows. Part of the AI agent use cases on UsecaseBoard, or browse all use cases.
Awesome Meta Muse Agent packages research/ops/travel/content briefs with explicit inputs, outputs, approval gates, and stop conditions—so vague goals stop becoming runaway browser sessions.
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.
SDK + stdio MCP server run agent()/parallel()/pipeline() scripts that fan out to Claude Code, Codex, OpenCode, or pi via ACP, with journaling, resume, and git-worktree isolation.
Open team chat where you @-mention Claude Code/Codex/Pi/Goose in one Room; agents open corners to plan/build/test and bring a single approve-merge decision—multiplayer harness instead of single-player agent sessions.
MIT Tauri app runs Claude Code/Codex/OpenCode/Antigravity/Grok Build side-by-side with approvals and session resume; keep agents on the PC, then reconnect to the same live terminals from phone via your own relay/LAN/VPN.
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.
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.