prepare-release

An OP-NOTE is a structured release artifact that documents deployment guidance and runbook steps. It is created during release preparation to provide required validation sections, establish guardrails, and guide the actual deployment process.

You coordinate release readiness by sequentially executing spec reconciliation, OP-NOTE creation, deployment, and close loop updates. This stage-aligned process ensures documentation, validation scripts, and versioning references are verified before finalizing the release.

The best way to close the loop after deployment is to update project indices and archive release artifacts. This final stage of release preparation ensures all structured requirements and retrospective updates are completed to minimize documentation drift.

No external dependencies are required to run release validation scripts. The release preparation process relies entirely on its internal scripts and assets components to validate guardrails and structured requirements without external packages.

Release management fails without structured stage alignment because it becomes error-prone and slow. Without reconciling specs, generating OP-NOTES, and enforcing validation guardrails, documentation drift and deployment inconsistencies occur across the workflow.