manage-change
Skill1 starsChanged 3 months agoMITView on GitHub
Run a change request against an approved baseline — assess impact on scope, schedule, cost and risk separately, present options with a recommendation, get the named approval, and re-baseline. Use whenever approved scope, schedule or cost would move. Dispatches the project-manager.
In this repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- build-business-caseSkill
- build-roadmapSkill
- capture-feedbackSkill
- close-projectSkill
- coordinate-programSkill
- define-metricsSkill
- define-strategySkill
- design-dashboardSkill
- elicit-requirementsSkill
- groom-backlogSkill
- make-deliverableSkill
- manage-resourcesSkill
- plan-capacitySkill
- plan-launchSkill
- plan-portfolio-automationSkill
- plan-projectSkill
- plan-sprintSkill
- powerbiSkill
- prioritizeSkill
- review-okrsSkill
- review-portfolio-intakeSkill
- run-ceremonySkill
- run-discoverySkill
- run-gate-reviewSkill
- setup-pmoSkill
- track-financialsSkill
- track-portfolioSkill
- track-statusSkill
- write-prdSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
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
- Very specific: line 47
Start from templates/change-request.md.
- Very specific: line 52
If knowledge/integrations.md configures Jira/Linear, offer to adjust the affected tickets after the re-baseline.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/manage-change — Control the baseline
When to use
Whenever something would move approved scope, schedule, or cost. Work that fits inside the baseline is not a change — don't inflate the log with normal backlog churn. But when in doubt, log it: an unrecorded re-baseline makes every later variance report meaningless.
Dispatches
project-manager (lead) + financial-analyst (cost impact and re-baselining) + governance-lead (policy,
and any change crossing projects) + program-manager (where other projects are affected).
Inputs
The change request or the event that triggered it, the project plan in knowledge/projects/,
knowledge/financials.md (cost baseline), knowledge/governance.md (thresholds and approvers),
knowledge/raid-log.md, knowledge/change-log.md (prior changes and cumulative drift).
Steps
- Check it's actually a change, and whose. Compare against the approved baseline. Below the threshold in
knowledge/governance.md, the project manager just decides — say so and stop. Above it, or crossing projects, continue. - Capture the change and why now. What is moving, and what prompted it — new information, a missed requirement, an external event, a discovered defect. "The stakeholder asked" is a source, not a reason.
- Assess each dimension separately — scope, schedule, cost, risk, resources, quality/NFRs, and other projects. A change that "has no impact" usually means the impact hasn't been looked for. State the do-nothing consequence too.
- Present options, not just the request. Reject/absorb, approve as requested, approve with modification — each with its impact. Recommend one plainly; the approver is agreeing or disagreeing, not deciding from scratch.
- Get the named approval per
knowledge/governance.md. No CR is approved without a named approver and a date. - Re-baseline. This is the step that gets skipped. Update the project plan, the cost baseline in
knowledge/financials.md, the schedule and milestones, and the backlog. Then update the cumulative baseline-movement table so the drift from the original approval stays visible. - Communicate and log. Tell the affected stakeholders what changed, and record the decision.
Methods
knowledge/methods/governance-and-change.md (change control, the two failure modes, re-baselining),
knowledge/methods/project-management.md (triple constraint, change control),
knowledge/methods/financial-management.md (cost baseline integrity).
Output
Start from templates/change-request.md. Record the request in knowledge/change-log.md (open, then moved to
decided), update the affected plan and baselines, and log the decision in knowledge/decision-log.md. Follow
standards/document-standards.md.
Optional sync
If knowledge/integrations.md configures Jira/Linear, offer to adjust the affected tickets after the
re-baseline. Files remain source of truth; skip if not configured.
Created by Colin Beck<br>
LinkedIn: https://www.linkedin.com/in/beckcolin/<br>
GitHub: https://github.com/link7373
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
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.

