nitro agent tasks backlog orchestration (wave pipeline)

One orchestrator, delegated workers, nitro agent tasks as the single source of truth. Command mechanics live in the nitro-task, nitro-mail, and nitro-memory skills; this skill is the operating model on top. If nitro itself is not found, the CLI is not installed — stop and tell the user to install it: https://chillicream.com/docs/nitro/cli/installation. Do not attempt to install it yourself.

The roles

• Orchestrator (you, the main session): never writes feature code. Owns the backlog, the schedule, the environment, and all task closures. Everything else is delegated.
• Planner: turns user feedback or a parity goal into tasks. Each task gets: problem, concrete file scope, fix direction, verification requirements, non-goals, priority. Planners inspect the live app and the code before writing tasks, and link epics with parent-child deps. Usually a separate session running the nitro-task-planner skill, not a subagent you spawn.
• Implementer: one task per agent. Reads the task with nitro agent tasks show <id> --output json including comments (comments carry binding decisions). Implements exactly the scope, verifies, reviews its own diff on the reviewer's three axes and fixes what it finds, commits, reports structured results.
• Reviewer: reads the actual diff. Three axes: correctness (root cause, not suppression), scope creep (anything beyond the task is a finding even if the code is good), verification gaps (claims that do not hold up). Verdict pass only with zero blocker/major findings.
• Verifier: only runs when the review fails. Adversarially confirms or dismisses each finding with evidence, then writes a minimal correction plan. This kills plausible-but-wrong findings before they cause churn.
• Fixer: applies the verified plan exactly, nothing more. Then re-review. Cap at 3 cycles, then escalate to the planner.

Roles are capabilities, not model names. Read the harness reference for model selection, spawning, isolation, and wake mechanics: Claude Code, Codex, or Venti. On Venti, run the supplied C# wave workflow with role-based model selection and typed results; serialize writers in the shared working directory. On any other harness, match these classes: implementer and fixer on a Sonnet-class model at high effort; the reviewer on an Opus-class model at medium effort; the verifier and the planner on a Fable-class model at medium effort.

Mail identity (planner channel)

Planners and the orchestrator communicate over nitro agent mail (mechanics in the nitro-mail skill); this is the protocol.