team-swarm

What problem does it solve?

It solves the challenge of turning an ambiguous or multi-step task into organized parallel work, with clear ownership, dependency ordering, and cross-validation across specialized agent roles.

Core Features & Use Cases

• Department-scoped collaboration: Breaks work into Architecture, Implementation, QA & Review, Documentation, and (optionally) Research, staffing the right number of agents for task size.
• Dependency-driven execution: Creates tasks upfront, wires them with blockedBy/addBlocks relationships, and prevents premature execution until prerequisites are complete.
• Structured coordination & validation: Runs staged kickoff/standup/review/closing protocols, using cross-validation rules to catch mismatches and regressions before finalization.
• Use Case: Plan and deliver a non-trivial change to Nimbus (or any codebase) by orchestrating design, implementation, QA review, and documentation updates without agents stepping on the same file/module.

Quick Start

Use team-swarm to break your task into departments and coordinate parallel implementation and QA, by asking it to create a team and produce a completed execution plan for the change you want.