skills.rest
ilove323
ilove323COMMUNITY
Explore all skills by this author →
GitHub

change-request

Generate structured change requests with impact analysis and rollback plans.

1|Updated Mar 30, 2026
Search Tags:#impact analysis#risk assessment#change management#change-request#itsm#rollback plan#communication plan
One-click install
npx skills add https://github.com/ilove323/comlan-skills --skill change-request-ilove323
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: change-request
Source: https://github.com/ilove323/comlan-skills/tree/main/operations/skills/change-request
Command: npx skills add https://github.com/ilove323/comlan-skills --skill change-request-ilove323

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many change initiatives fail or cause disruptions because requests lack structured impact analysis, clear communication plans, risk mitigation, and a defined rollback procedure; this Skill standardizes change documentation to reduce risk and speed approvals.

Core Features & Use Cases

  • Structured Templates: Generates a complete change request including description, business rationale, impact analysis, risk assessment, implementation steps, communication plan, and rollback procedures.
  • Stakeholder & Execution Focus: Helps identify affected audiences, assign owners, and map timelines and dependencies for operational and IT changes.
  • Use Case: Prepare a change request for a system upgrade that links to implementation tasks, outlines mitigation steps, and provides a clear rollback plan for the release window.

Quick Start

Draft a change request titled "Replace payment gateway" that includes a concise description, business rationale, impact analysis by audience and system, risk assessment with mitigations, a step-by-step implementation timeline with owners, a communication plan, and a rollback procedure.

Frequently Asked Questions about change-request

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a change request for a system upgrade?▼

To write a change request for a system upgrade, define the business rationale, identify affected stakeholders, and map implementation tasks with owners and timelines to ensure clear rollout approvals.

What should be included in an ITSM rollback plan?▼

An ITSM rollback plan should include stepwise rollback procedures, risk mitigations, and a communication plan to restore systems if a change fails during the release window.

How do I perform an impact analysis for a process change?▼

Perform an impact analysis for process changes by generating an impact matrix that evaluates effects by audience and system, identifying dependencies, and outlining mitigation steps for operational disruptions.

Can I use this for ITIL change management documentation?▼

Yes, you can use this for ITIL change management documentation because it produces templated markdown output with risk assessments and implementation steps suitable for ITSM or project tracker integration.

Why do change requests fail during IT operations?▼

Change requests often fail during IT operations because they lack structured impact analysis, clear communication plans, risk mitigation, and defined rollback procedures, causing unmanaged disruptions.

What is the best way to structure communication plans for rollout approvals?▼

The best way to structure communication plans for rollout approvals is to identify affected audiences, assign owners, and map timelines and dependencies to align stakeholder expectations during the release window.

Related Skills

Explore More Product & Management Skills→
yuyuxinliyuyuxinli
1

roadmap-planning

Convert feature requests into prioritized epics and sequenced Now/Next/Later roadmaps.

Official
Intermediate
rkz91rkz91
264

pmstudio-comms

Generate stakeholder communications in Markdown from project context.

Community
Intermediate
bradtaylorsfbradtaylorsf
8

technical-planning

Generate sprint planning templates with story point estimation and capacity calculation.

Community
Intermediate
xenitV1xenitV1
132

deployment-procedures

Guide production deployments through a 5-phase process with rollback strategies.

Community
Basic