skill-role-breakdown-tasks

To break down user requirements into atomic subtasks, this Skill translates complex requests into a structured plan assigned to specific agents with explicit dependencies and parallelization. It uses a standardized schema including id, agent, module, scope, and depends_on.

Planning task handoffs and dependencies for agent orchestration requires a standardized subtask schema defining input_requires, output_produces, and depends_on. This Skill standardizes handoffs to enable consistent reviews and explicit parallel execution plans across multiple modules.

Yes, you can define parallel execution plans across multiple modules using the subtask schema. The schema includes can_run_parallel_with and depends_on fields to maximize throughput and handle simple to complex workflows spanning several modules.

The schema used to define subtasks for workflow planning includes id, title, agent, module, scope, file_target, description, input_requires, output_produces, depends_on, and can_run_parallel_with. This standardizes subtask format for consistent agent handoffs.

Yes, this task breakdown approach supports complex workflows spanning several modules. It translates complex user requests into an atomic subtasks plan assigned to appropriate agents, handling simple to complex workflows with clear dependencies and parallelization.