skills.rest
The13thNode
The13thNodeCOMMUNITY
Explore all skills by this author →
GitHub

change-management

Coordinate scope changes, pivots, and incident communications with documented decisions.

3|Updated Mar 26, 2026
Search Tags:#change-management#incident-response#team-alignment#stakeholder-management#scope-change#pivot-communication
One-click install
npx skills add https://github.com/The13thNode/VibeCorp_PromptCEO --skill change-management-the13thnode
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: change-management
Source: https://github.com/The13thNode/VibeCorp_PromptCEO/tree/main/skills/public/change-management
Command: npx skills add https://github.com/The13thNode/VibeCorp_PromptCEO --skill change-management-the13thnode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manages scope changes, strategic pivots, incident communication, and team alignment when direction changes. Trigger phrases include "we need to pivot", "scope change request", "how do I tell investors we're changing direction", "incident communication", "team doesn't understand the new direction", or "customer wants something outside scope".

Core Features & Use Cases

  • Framework 1: Scope Change Request Process — When a customer, investor, or team member requests something outside the approved scope, follow a gate pattern to ensure a written decision before changes. This includes documenting requestor, impact assessment, recommendations, and a decision-by date.
  • Framework 2: Pivot Communication — Internal Pivot Announcement and Investor Pivot Communication templates to clearly describe what's changing, what's not, why, and the expected impact across teams.
  • Framework 3: Incident Response Communication — Severity levels and a standard customer communication template to manage production incidents and post-incident reporting.
  • Framework 4: Managing Team Resistance to Change — Diagnostic of information/trust/capability/values gaps with guiding principles for change communication and role assignment.
  • Integration: Scope changes → product-manager; Pivot communication → investor-relations; Incident communication → security-auditor; Team communication → stakeholder-management.

Quick Start

Initiate the Scope Change Request Process when a change is requested to ensure a documented decision and clear stakeholder alignment.

Frequently Asked Questions about change-management

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

FAQPage Schema
How do I manage a scope change request when a customer wants something outside the approved boundaries?▼

Scope change request management requires a gate pattern to document the requestor, assess impact, and set a decision-by date before any changes. This ensures written decisions and clear stakeholder alignment across product and engineering teams.

What's the best way to communicate a strategic pivot to investors and internal teams?▼

Pivot communication uses structured templates to clearly describe what is changing, what is not, why, and the expected impact. This framework ensures internal pivot announcements and investor updates maintain consistent messaging across all teams.

How do I handle incident response communication for production incidents?▼

Incident response communication applies severity levels and standard customer communication templates to manage production incidents. This framework structures customer notifications and coordinates post-incident reporting across engineering and leadership teams.

Why does my team resist new direction changes and how do I diagnose the alignment gap?▼

Team resistance to change is diagnosed by identifying information, trust, capability, or values gaps. The framework provides guiding principles for change communication and assigns specific roles to address these alignment issues across the team.

Can I use a single framework to coordinate scope changes, pivots, and incident communications together?▼

Yes, this change management framework integrates scope changes, pivot communication, incident response, and team alignment. It applies governance, templates, and guardrails to trigger and document decisions across product, engineering, and leadership teams.

When do I need a formal scope change process instead of just approving a quick request?▼

A formal scope change process is needed whenever a customer, investor, or team member requests something outside approved scope. Following a gate pattern ensures a documented decision with impact assessment and stakeholder alignment before implementation.

Related Skills

Explore More Product & Management Skills→
samjhechtsamjhecht
4

initialize-governance

Generate Constitution, Roadmap, and process documentation templates for project governance.

Community
Advanced
ricablericable

internal-comms

Create internal status reports, leadership updates, and incident reports in company-approved formats.

Community
Intermediate
zenobi-uszenobi-us
68

incident-responder

Coordinate incident response for security breaches and operational incidents.

Official
Advanced
chekoschekos
5

moderation-rules

Codify moderation rules, escalation paths, and response templates for Discord-style communities.

Community
Basic