developpeur

Feature development orchestration uses a prime planner to compress codebase context into actionable plans that three parallel builders execute. It coordinates functional slices iteratively from planning to build execution.

A functional slice is a single iteration unit, like Auth or Dashboard, processed by a prime planner and three builders. The pipeline handles one slice at a time to ensure focused development and continuity.

State continuity across iterative feature slice builds is maintained via a disk-backed slice registry. This registry stores progress on disk, ensuring context persists between separate slice invocations.

Builders can run in parallel or sequential mode depending on architecture maturity. The orchestration adapts execution order based on how mature the underlying software architecture is.

Contract-first planning is enforced during iterative functional slice development. The prime planner establishes contracts before the database, backend, and frontend builders execute their respective tasks.

Sequential execution should be used when architecture maturity is low or dependencies require strict ordering. Parallel execution is suited for mature architectures with independent builder tasks.