agile-coordinator

You can automate backlog task execution by orchestrating multiple worker agents to implement groomed tasks. The coordinator reads your backlog, filters ready tasks by priority and dependencies, then spawns sequential or parallel workers to execute them.

Merge coordination maintains a filesystem-based merge queue to perform sequential squash or no-ff merges. It runs build and test verification after merging, handling any conflicts with automated retries or human-in-the-loop resolution.

You need git access to a repository, a context network backlog structure containing groomed tasks, and Claude Code's Task tool for spawning workers and managing filesystem-based progress and merge queues.

Yes, you can run batch implementation of ready tasks across a repository. The coordinator orchestrates the workers, ensures build and test verification during merges, and updates backlog epic files to reflect completed work and unblock dependent tasks.

Completed tasks are persisted by updating backlog epic files and project status files on the filesystem. This ensures completed work is accurately tracked, preventing lost progress or duplicated task execution across worker batches.

The coordinator reads the context-backed backlog, filters for ready tasks, and sorts them by priority while respecting task dependencies to produce a safe execution plan before spawning any worker agents.