Determine parallel Agent Teams versus sequential subagent orchestration for subtasks.
npx skills add https://github.com/josix/agent-flow --skill team-decision
Please help me install this Agent Skill. Skill: team-decision Source: https://github.com/josix/agent-flow/tree/main/skills/team-decision Command: npx skills add https://github.com/josix/agent-flow --skill team-decision
This Skill helps you decide whether to run decomposed work as parallel Agent Teams or as sequential subagent orchestration, preventing conflicts and wasted overhead.
Use the team-decision skill when planning a multi-part coding or planning task and you must choose between parallel Agent Teams and sequential execution.
High-intent search queries and answers about installing and using this skill.
Choosing parallel agent teams requires checking task independence, file ownership boundaries, and dependency structure to prevent conflicts. You must compare the overhead of spawning and merging against expected time savings to ensure cost-effective parallelism.
Use parallel subagent orchestration when decomposed subtasks are truly independent, such as adding multiple separate endpoints. Apply safety-first eligibility checks to confirm that file ownership does not overlap and merge conflict risk is low.
Avoiding merge conflicts in parallel agent teams involves strict file ownership checks and dependency structure analysis. If tasks modify overlapping resources or share semantic dependencies, default to sequential subagent orchestration.
Parallel execution causes wasted overhead when context duplication, spawn setup, and conflict resolution costs exceed expected time savings. A cost-benefit analysis must verify that decomposed tasks are independent before committing to parallel teams.
Sequential subagent orchestration works better for refactoring when subtasks share context or modify overlapping resources. It acts as a fail-safe fallback under uncertainty, reducing semantic dependency errors and merge risk.
Parallel execution limitations include merge conflicts from overlapping file ownership and semantic dependency errors. If dependency structures are unclear or tasks share context, the system must fallback to sequential mode to ensure safety.
ssccioDecompose software tasks into parallel subtasks with file ownership partitioning.
Miss-PinkElfApply approved tasks from tasks.md through SPARK-workflow debugging, review, and verification gates.
build000rDecompose complex tasks into independent parallel agents with conflict checks.
tmalcolm-0607Orchestrate wave-based parallel feature implementation across isolated git worktrees.
