From pdm-toolkit
Generate a formal change request document when a delivery commitment needs to change — scope, timeline, or budget — requiring stakeholder approval.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pdm-toolkit:change-requestThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate a formal change request document when a delivery commitment needs to change — scope, timeline, or budget — requiring stakeholder approval.
Generate a formal change request document when a delivery commitment needs to change — scope, timeline, or budget — requiring stakeholder approval.
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:
Proposed Change:
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: _______________
/status-update or /steering-decknpx claudepluginhub devmuslim/pdm-skills --plugin pdm-toolkitCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.