code-create-staged-plan

To plan large codebase changes as staged steps, generate a dependency-ordered staged plan that includes a parent plan document, per-stage scope docs, global invariants, and safety considerations to enable incremental delivery and revertibility.

A dependency-ordered staged plan sequences multi-step code fixes by creating a parent plan document and per-stage scope docs with parity gates and flag-off byte-identical behavior to ensure safe gating and traceability.

Scope refactors and feature ports by generating per-stage scope docs with validation criteria, maintaining dated agent_logs under notes directories, and establishing a borrow-map to track dependencies across complex repositories.

Yes, staged planning applies to kernel and performance changes by enforcing safety invariants, parity gates, and go-no-go validation criteria within per-stage scope docs to ensure safe, incremental delivery.

Maintain traceability during large code refactors by keeping dated agent_logs and evidence breadcrumbs under notes/<codebase>/ directories alongside the parent plan document to ensure a single source of truth.

You need a parent plan document for code changes when sequencing substantial refactors, multi-step fixes with parity requirements, or feature ports to establish goals, scope, and evidence as a single source of truth.