Skill

Skill: change-request

Generate a formal change request document when a delivery commitment needs to change — scope, timeline, or budget — requiring stakeholder approval.

Install

npx claudepluginhub devmuslim/pdm-skills --plugin pdm-toolkit

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Generate a formal change request document when a delivery commitment needs to change — scope, timeline, or budget — requiring stakeholder approval.

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.0k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

ui-ux-pro-max

Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.

ui-ux-pro-max

57.6k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 9, 2026

Actions

View Source View Plugin View on GitHub View README

Skill: change-request

Purpose

Generate a formal change request document when a delivery commitment needs to change — scope, timeline, or budget — requiring stakeholder approval.

When to Use

Release date needs to move
Significant scope must be added or removed
Budget overrun requires additional funding approval

Framework: Change Request

Change Request Template

Change Request ID: CR-[number] Date Submitted: [Date] Submitted By: [PDM Name] Approval Required From: [Name / Role] Decision Needed By: [Date]

Change Summary (one sentence):

"Request to [extend timeline by 3 weeks / add Feature X to scope / increase budget by $50K] for [Release Name]."

Current Baseline:

Scope: [description]
Timeline: [committed date]
Budget: [committed amount]

Proposed Change:

Scope: [new scope description]
Timeline: [new date]
Budget: [new amount]

Reason for Change: [2–3 sentences explaining what changed and why.]

Impact of NOT Approving: [What happens if this change is rejected — business risk, quality risk, team impact.]

Impact of Approving: [What downstream effects the change has — other projects, teams, customers.]

Options:

Option	Description	Impact
A	Approve as requested	Timeline extends, quality maintained
B	Partial approval (scope only)	Date holds, scope reduced
C	Reject	Current plan maintained, quality risk accepted

Recommended Option: [A/B/C with rationale]

Approval: Approved / Rejected / Deferred by: _______________ Date: _______________ Comments: _______________

Output Format

Completed change request document (ready for signature)
Summary email to accompany the formal document
Suggested next command: /status-update or /steering-deck