mcpField
R
release-train-change-management-review

release-train-change-management-review

github.com/sylphxaiCloud & DevOps142 installsUpdated today
Repository

About release-train-change-management-review

This skill turns release-train and change-management questions into release plans and artifacts with owners, gates, metrics, and recovery paths. It classifies changes by type and risk, then covers staged rollouts, communication, monitoring, and rollback.

Key features

  1. 01Identify scope, cadence, dependencies, and risk
  2. 02Classify changes by type and risk
  3. 03Set calendars, freeze rules, and readiness gates
  4. 04Plan staged rollout, communication, and support readiness
  5. 05Produce plans, decision tables, and exception policies

Use cases

  1. 01Coordinate cross-team release calendars and dependencies
  2. 02Set gates for migrations, billing, or API changes
  3. 03Plan rollout monitoring and rollback paths
  4. 04Define exception handling for emergency fixes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill release-train-change-management-review

After installing, type/release-train-change-management-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/release-train-change-management-patterns.md

Details

From the project README

Release Train Change Management Review

Use this skill to convert a release trains, change calendars, risk classification, rollout gates, rollback, comms, and support readiness question into a concrete artifact with owners, gates, metrics, and recovery paths.

Workflow

  1. Identify release scope, cadence, owners, dependency graph, affected surfaces, risk class, customer visibility, and rollback mechanism.
  2. Read references/release-train-change-management-patterns.md.
  3. Classify each change as routine, experiment, migration, billing/auth/security, API contract, infra, content/event, or emergency fix.
  4. Define calendar, freeze rules, readiness gates, rollout stages, comms, support brief, monitoring, rollback, and post-release review.
  5. Produce release train plan, state machine, decision table, event schema, checklist, and exception policy.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not put billing, auth, migration, or public API changes on an ordinary release train without special gates.
  • Do not let release notes become the only support readiness artifact.
  • Do not continue a rollout after guardrails fail because the calendar says ship.
  • Do not rely on one human memory thread for cross-team release dependencies.

Output format

Release context:
Scope / cadence / risk class / rollback path:

Release train plan:
| Area | Decision | Evidence | Risk | Owner |
| --- | --- | --- | --- | --- |

Changes and gates:
- <item> -> <policy, metric, edge case, support note>

Exception and rollback policy:
- <trigger> -> <action, communication, owner>

Comments

Markdown supported