What problem does it solve?
When executing a queue of tickets or plan tasks, it is easy to blur ownership: the controller implements work itself, commits mix unrelated changes, and failed items get silently repaired or reassigned. This Skill enforces a strict orchestration discipline where one implementation subagent owns each work item end to end.
Core Features & Use Cases
- Dependency-ordered queueing: Groups supplied tickets into atomic work items that can each validate in a separate behavior-preserving commit.
- Single-owner delegation: Spawns one implementation subagent per item with a decision-complete packet, and returns failed acceptance evidence to that same owner instead of repairing in the controller.
- Independent acceptance gates: Verifies HEAD advanced with a task-scoped commit, inspects the full diff, reruns required checks, and confirms the worktree matches the recorded pre-existing state before advancing.
- Use Case: Given a plan with five tickets, the controller processes them one at a time, accepting each task-scoped commit before starting the next, and reports the final item-to-commit mapping.
Quick Start
Use the implement-with-subagents skill to implement these tickets through sequential implementation subagents with per-task commit acceptance.
