feature

Coordinate parallel feature development by splitting the backlog into independent waves and integrating changes only after passing deterministic verification. This structured approach prevents the slow, expensive failure mode of letting a single model handle all thinking and coding inline for large changes.

Plan a subsystem redesign by sizing the work into a multi-wave effort based on reversibility and blast radius. The process turns rough requests into a pinned contract defining shared interfaces, file boundaries, dependency order, and verify commands before dispatching execution.

Contract pinning and dependency-linked tickets are needed when executing multi-part changes or migrations that require explicit risk management. They ensure planning, execution, review, and integration stay aligned by defining file boundaries and review depth before dispatching independent work waves.

Size code review depth for multi-wave migrations by evaluating architectural ambiguity and blast radius during the initial scoping phase. The workflow requires sized review depth and deterministic verify commands to be established in the contract before integration of dispatched waves.

Yes, the Sidequest board workflow can size work down to a single ticket if the change has low blast radius and high reversibility. It dynamically decides whether a feature request requires one wave, multiple waves, or a single ticket based on architectural ambiguity.