stage-07-phase-sequencing

Split a large PRD into token-budgeted build phases by defining self-contained file sandboxes, explicit build orders, and dependency mappings to enable modular and auditable implementation across multiple teams.

File sandboxing in phase-based PRD planning restricts file access per phase using NEW/MODIFY, READ-ONLY, and FORBIDDEN lists, ensuring phases remain self-contained and preventing unauthorized modifications.

Enforce a build order following Martin's four-layer pattern by sequencing phases through Core logic, State, UI, and Integration layers, generating a mandatory_build_order with explicit phase dependencies.

Generating token-budgeted phases requires Stage 2–6 inputs including scope_contract, drift_anchor, mechanism lists, dependencies, wireframes, design tokens, and tech stack to produce the stage_7 outputs.

Phase sequencing is applicable for large PRDs requiring staged development across multiple teams, providing traceable handoffs and checkpoints through token-budgeted phases and enforced build orders.

Phase sequencing outputs stage_7.token_budget, stage_7.phases, and mandatory_build_order, along with files_allowed, files_read_only, and files_forbidden lists to guide modular implementation.