agent-as-function

Multi-agent workflow coordination via artifact handoff decomposes monolithic prompts into per-phase skills, allowing subagents to communicate exclusively through filesystem artifacts rather than shared conversation context. This enforces clean boundaries between orchestrator and subagent contracts.

The subagent-as-function pattern treats phase skills as just-in-time loaded components with scratchpad state, defining strict input and output artifact contracts. Subagents communicate exclusively via filesystem artifacts, ensuring clean separation between orchestrator logic and subagent execution.

Decomposing a monolithic agent prompt involves breaking it into per-phase skills using artifact handoff templates. The skill provides templates for phase transitions, audit workflows, and domain knowledge integration to help refactor existing agents or create orchestrators from scratch.

Yes, you can refactor existing agent orchestrators by applying the subagent-as-function contracts and artifact handoff patterns. The skill provides audit workflows and integration guidelines to convert monolithic agent prompts into cleanly separated per-phase skills with filesystem artifact boundaries.

Structuring phase transitions in a multi-agent orchestrator is best handled using artifact handoff templates that define input and output artifacts for each phase. This enforces subagent-as-function contracts and maintains scratchpad state across just-in-time loaded phase skills.

Filesystem artifacts for subagent communication may not suit workflows requiring real-time context sharing or minimal latency between phases. This artifact handoff pattern enforces clean boundaries but adds overhead for reading and writing state between each orchestrator and subagent transition.