Implement Feature

High-level build orchestrator: turn a plan into a working, reviewed feature by decomposing it into tasks and delegating each to implement-and-review. You (the main agent, the Opus seat — model ids live only in shared/references/model-roster.md) own the breakdown, the dependency DAG and scheduling, cross-task integration, and the feature-wide final review. Per-task building — the FE/BE split, cross-model review, and TDD — is implement-and-review's job. Call it; don't reimplement it.

Pipeline: plan → to-tasks (vertical slices) → implement-and-review per task (parallel where independent) → integrate in dependency order → feature-wide full-review → green.

The detailed scheduling/integration commands are in references/feature-orchestration.md; read it before Phase 1.

Hard Rules

1. Decompose with to-tasks. Break the plan into tracer-bullet vertical-slice tasks, each with a machine-checkable acceptance contract, gate flags (lenses + security), and blocked_by deps.
2. Tasks are the unit of value and parallelism. Independent tasks run in parallel; dependent ones wait on their blockers.
3. Delegate each task to implement-and-review. Don't duplicate its FE/BE/TDD/cross-review logic — hand it the task, a per-task --slice namespace, and the base to build on.
4. Writes are gated. No code until the user approves the breakdown (skip only with --auto).
5. Integrate in dependency order. Each task must pass its acceptance contract before its dependents start.
6. Feature-wide final review. After all tasks integrate, run full-review across the whole feature (focused on cross-task seams; per-task review already happened), apply findings, leave green.
7. Bounded + escalate. A task whose implement-and-review hits its 3-cycle cap is escalated; it blocks only its dependents — independent tasks keep going.
8. Never fabricate a seat; degrade per Degrade Gracefully.