run

Invoke /ticket:run with the path to the feature spec. The orchestrator computes the unblocked ticket frontier, dispatches one fresh subagent per ticket with an inline brief, and updates a resumable ledger after each ticket until the frontier is empty.

After a subagent commits, the orchestrator dispatches two parallel reviewers: one checks the diff against documented repo standards and a Fowler smell baseline, the other checks it against the spec and ticket. Reports are written to files and returned to the implementing subagent to apply via git amend.

Sequential execution is the default because tickets collide on shared files and build caches. Parallelism is allowed only when the frontier partitions into clusters sharing no files, each cluster running in its own mandatory git worktree.

The ledger in .scratch/ticket-run records every ticket's status, SHA, and timestamps. On restart, the retomada reference reconciles ledger lines, git log, and ticket status so completed work is never reimplemented; ambiguous states escalate to the user.

It escalates on tickets with foreign assignees, bodies ending in open design decisions, SPEC_DESIGN conflicts between spec and code, BLOCKED subagents, and any return outside the defined status contract. It never guesses a resolution.

It requires the mattpocock-skills plugin for the TDD skill and a repo with documented conventions for test layers, tracker states, and quarantine location. Tickets with unresolved blockers or dependency cycles remain unreachable and are reported at the end.