mcpField
R
release-planning

release-planning

github.com/aj-geddesCloud & DevOps373433 installsUpdated 34w ago
Repository

About release-planning

release-planning is a skill for coordinating production releases with timelines, communication, and rollback procedures. It provides planning guidance and reference material for checklists, versioning, rollout, and monitoring.

Key features

  1. 01Release timelines and milestones
  2. 02Stakeholder communication planning
  3. 03Staged rollout guidance
  4. 04Rollback planning
  5. 05Post-release review guidance

Use cases

  1. 01Planning major feature releases
  2. 02Coordinating deployments across systems
  3. 03Managing database or infrastructure changes
  4. 04Preparing a release for a high-traffic period

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/aj-geddes/useful-ai-prompts --skill release-planning

After installing, type/release-planningin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
release-checklist.md
rollout-monitoring.md
versioning-strategy.md
templates/
process-template.md

Details

From the project README

Release Planning

Table of Contents

Overview

Release planning ensures coordinated deployment of features to production with minimal risk, clear communication, and established rollback procedures.

When to Use

  • Planning major feature releases
  • Coordinating multi-system deployments
  • Managing database migrations
  • Rolling out infrastructure changes
  • Planning go-live strategies
  • Coordinating customer communication
  • Preparing for high-traffic periods

Quick Start

Minimal working example:

Release Plan:

Release: v2.5.0 - Customer Portal Redesign
Target Release Date: February 15, 2025
Status: Planning
Owner: Product Manager

---

## Executive Summary

This release delivers the redesigned customer portal with improved
UX, performance, and mobile experience. Includes database optimization
and infrastructure scaling.

Business Impact:
  - 25% improvement in user conversion
  - 40% faster load times
  - Mobile-first experience
  - Estimated $500K revenue impact

---

## Release Contents

// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

GuideContents
Release ChecklistRelease Checklist
Versioning StrategyVersioning Strategy
Rollout & MonitoringRollout & Monitoring

Best Practices

✅ DO
  • Plan releases with clear timeline and milestones
  • Communicate early and often with stakeholders
  • Test thoroughly in staging environment
  • Use phased rollout to reduce risk
  • Monitor metrics continuously during rollout
  • Have clear rollback procedure
  • Document all changes and decisions
  • Conduct post-release review
  • Include support team in planning
  • Plan releases during lower-traffic periods
❌ DON'T
  • Release without adequate testing
  • Deploy Friday afternoon
  • Release without monitoring in place
  • Skip UAT/acceptance testing
  • Release all major changes together
  • Deploy without rollback plan
  • Surprise customers with breaking changes
  • Release without support team readiness
  • Make unreviewed last-minute changes
  • Ignore performance or error metrics

Comments

Markdown supported