agent-analyst

Task breakdown for complex software requirements involves analyzing the context and generating atomic subtasks with clear dependencies. This process outputs a structured YAML plan detailing execution groups and module-to-agent assignments without writing code.

Mapping modules to agents requires analyzing available agents and stack context to assign subtasks accurately. The result is a YAML execution plan with parallel groups and guardrails ensuring clear module-to-agent coordination across multiple scopes.

Generating a YAML execution plan with parallel groups involves structuring analyzed subtasks and their dependencies into parallel execution phases. The output includes defined guardrails to manage execution flow and ensure safe orchestration.

This task breakdown approach only outputs execution plans and does not write code. It strictly focuses on analyzing user requirements to produce a structured YAML file containing subtasks, dependencies, and execution guardrails.

You need an orchestrator for task breakdown when handling complex requests that require clear module-to-agent mapping across multiple scopes. It analyzes your stack and available agents to generate atomic subtasks with defined dependencies.

Yes, you can use task breakdown for multi-scope projects as it reads the context of available agents and modules. It analyzes the stack to generate an execution plan that accurately assigns subtasks to the correct agents.