Ticket flow

The lead plans, decides, verifies, and reports. Workers gather facts, implement the decided change, and review it. Read the installed orchestrator skill and its shared conventions and brief template first. If the current task does not grant coordinator authority, stop and use the assigned terminal role skill.

1. Frame

Confirm the requested outcome, non-goals, acceptance checks, and whether the user wants planning only or a shipped change. Inspect repository instructions and dirty state. Extract a ticket ID from the branch only when the project uses one; never invent it.

Before the first delegation, let the authorized harness allocate one task context. Keep exploration, planning, implementation, review, fixes, and re-review in that context. The active harness skill owns the mechanics.

2. Explore

Start one or two terminal explore workers when the code path or cause is not already known. Ask for paths and lines, the runtime mechanism, competing explanations, a minimal fix, and risks. Keep each brief read-only and bounded.