agentleFS
link7373link7373/agentic-pmo/.claude/skills/manage-change/SKILL.md

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.

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
  1. Very specific:

    Start from templates/change-request.md.

    line 47
  2. Very specific:

    If knowledge/integrations.md configures Jira/Linear, offer to adjust the affected tickets after the re-baseline.

    line 52

≈ “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.

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

/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

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. Get the named approval per knowledge/governance.md. No CR is approved without a named approver and a date.
  6. 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.
  7. 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

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.