assign-to-workforce

What problem does it solve?

It prevents slow, sequential implementation work by turning a converged dependency graph into parallel, test-driven task execution across isolated worktrees, while keeping human approval confined to the intended gates.

Core Features & Use Cases

• Dependency-wave fan-out: Converts devague plan waves scheduling metadata into a human-reviewable implementation split plan.
• Isolated worktrees per task: Assigns one agent per task per wave in separate git worktrees to avoid clobbering shared files.
• TDD-gated reconciliation: Ensures every task merge is validated by running tests before and after merging into the main branch.
• Three human gates only: Requires approval for the exported spec, the implementation split plan (go/no-go), and the final PR—no per-task human pauses.

Quick Start

Ask your AI operator to run assign-to-workforce split-plan for the current plan, review the proposed table, then approve to fan out the waves for TDD-gated merges.