agentleFS
LwhieldonLwhieldon/claude-project-mgmt-playbook/.claude/skills/change-request/SKILL.md

change-request

Skill4 starsChanged 34 days agoMITView on GitHub

Draft a formal change request document from a description of a proposed scope change, with impact assessment, assumptions, exclusions, and an approval block. Use when a scope change needs to be documented and approved. Usage - /change-request describe what is changing and why

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the impact figures were not provided, leave them as [NEEDS INPUT].

    line 20
  2. Very specific:

    Change Description: Add a custom inventory aging report to the data warehouse delivery.

    line 68

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Change Request

Draft a formal change request document from a description of the proposed change. Produces a structured document ready for client review and approval signature.

Input

$ARGUMENTS describes the change: what is changing, why, and any known impact on scope, timeline, or cost. Helpful inputs:

  • Who is requesting the change (client or firm)
  • Known impact: additional effort (hours or days), timeline shift, cost delta
  • Optional: the original SOW for baseline context. Read it if a path is given.

If the impact figures were not provided, leave them as [NEEDS INPUT]. Do not estimate effort or cost on the delivery lead's behalf; those numbers are commitments.

Output

Change Request CR Number: CR-[###] Date: [Today's date] Project: [Project name from CLAUDE.md] Requested By: [Client or firm] Status: Pending Approval


1. Change Description Clear, specific description of what is changing and what is not changing. No vague language.

2. Reason for Change Business or technical justification. Why is this change necessary or beneficial? If the request is contested (the client believes it was always in scope), state both positions plainly.

3. Impact Assessment

DimensionBaselineRevisedDelta
Scope[Original][Revised][Added / Removed]
Timeline[Original end date][Revised end date][+/- days]
Estimated Cost[Original][Revised][+/- $]

4. Assumptions List assumptions underlying this change estimate.

5. Out of Scope Explicitly state what this change does NOT include to prevent scope creep on the change itself.

6. Approval

RoleNameSignatureDate
Client Sponsor
Engagement Lead
Client PM

Drafted with Claude Code on YYYY-MM-DD; reviewed by [NAME]

Example Output

CR Number: CR-004 Change Description: Add a custom inventory aging report to the data warehouse delivery. The original SOW included 12 standard reports; this adds one additional report with custom aging buckets (30/60/90/120+ days) defined by the client's finance team.

Impact Assessment:

DimensionBaselineRevisedDelta
Scope12 standard reports13 reports (12 standard + 1 custom)+1 custom report
TimelineJun 30, 2025Jul 14, 2025+14 days
Estimated Cost$485,000$512,000+$27,000

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.