roadmap-to-release-planlisted

# Roadmap To Release Plan ## Purpose Turn broad roadmap material into a release plan that teams can execute and inspect. ## Fit - Use when roadmap intent needs to become milestones, scope, dependencies, and release gates. - Do not use when the task is long-term vision strategy with no near-term release decision. ## Inputs - Roadmap notes, backlog themes, feature lists, or planning docs. - Target users, deadlines, staffing, and known dependencies if available. - Launch constraints, risk tolerance, and validation expectations. ## Workflow 1. Group work into coherent release themes. 2. Define included scope, deferred scope, and explicit non-goals. 3. Identify dependencies, sequencing constraints, and release gates. 4. Propose milestones with validation criteria. 5. Add rollout, monitoring, and rollback considerations. ## Output Produce Markdown with: - Release Goal - Scope And Non-Goals - Milestones - Dependencies - Validation Gates - Rollout Plan - Risks ## Validation - Each milestone has a concrete outcome. - Dependencies are not hidden inside task descriptions. - Non-goals prevent scope drift. - Validation gates are testable. - Risk notes include operational and user-facing concerns.