plan-reopen-stage-core

To reopen a frozen stage in a multi-stage plan workflow, provide the target stage number and plan context. The system reinstates the stage, updates the manifest and state files, invalidates affected downstream stages, and generates paired markdown and json reports.

When you reopen a frozen plan stage, affected downstream stages are invalidated to maintain plan integrity. The system automatically updates the state machine, marks the target stage as reopened, records the rationale, and preserves ownership as defined in planning templates.

A state machine handles manifest updates for reopened stages by transitioning the target stage from frozen to reopened, writing the change to the manifest file, and documenting the rationale alongside next valid commands to ensure stakeholders remain aligned.

Yes, you can generate reports after reinstating a frozen stage in a planning workflow. The process outputs paired reopen-stage-<n>-report.md and reopen-stage-<n>-report.json files, alongside updated manifest and state files, to keep stakeholders aligned.

Reopening a plan stage requires invalidating downstream stages because changing a previously frozen stage alters the plan baseline. Invalidating downstream stages enforces state machine safeguards, ensuring dependent stages are reviewed and updated against the new plan context.

Yes, planning templates are required to manage stage ownership when reopening stages. The reopening process abides by template-defined ownership rules to preserve permissions and applies safeguards to downstream stages during the state and manifest update.