ce-release-planner

To create a vX.Y.Z implementation plan, extract the target milestone from your master RELEASE_PLAN_v1.md and assemble a canonical vX.Y.Z_plan.md document. This structured plan captures goals, status, references, steps, and verification criteria to align stakeholders.

Align release tasks by cross-referencing governing ADRs, STD files, and existing version plans during the planning workflow. This ensures consistency across milestones and satisfies requirements to reference architectural decisions and standards within the generated plan.

Coordinate CE versioning by applying a repeatable workflow that derives implementation plans from the master release plan. This process maps release gates and milestones into a structured document with verification criteria, ensuring all governance requirements are met.

Yes, you can apply this workflow to ADR-gap closure alongside planning for upcoming versions and release gates. The process extracts milestones and cross-references existing ADRs to identify and document gaps within the canonical vX.Y.Z_plan.md output.

You need a master RELEASE_PLAN_v1.md file, governing ADRs, and STD files as inputs. The release planner extracts the target milestone from the master plan and cross-references these dependencies to render the canonical vX.Y.Z_plan.md document.

Yes, the release planning workflow operates without external dependencies, relying solely on your existing master release plan, ADRs, and standards files. It assembles the structured vX.Y.Z implementation plan directly from these local governance documents.