architect.default

Agent goal decomposition involves breaking down complex objectives into structured sub-tasks and designing interfaces. This approach outlines specific execution orders and data flows to guide implementation by other agents.

Designing data flows and interfaces requires specifying structured design artifacts and documenting trade-offs. This process defines how components interact and establishes clear handoffs for subsequent implementation and testing phases.

Non-implementation task decomposition produces design documents that decide architecture and document rationale. It guides agent lifecycles by structuring capabilities and outlining interfaces without directly writing implementation code.

Yes, specifying explicit dependencies and execution order is a core function of agent design. It structures the required sub-tasks and data flows to ensure subsequent implementation phases follow the correct sequence.

You need to create design artifacts when planning complex agent capabilities that require clear handoffs. It is necessary when structuring data flows, specifying interfaces, and documenting architectural trade-offs for implementation.

Yes, this design approach provides clear handoffs to coder.default for implementation. It outputs structured design artifacts, specified interfaces, and task decompositions that directly guide the coding process.