agentleFS
Sign inStart free
teodstrteodstr/workbench/skills/scope-change/SKILL.md

scope-change

Skill0 starsChanged yesterdayMITView on GitHub

Handle a new request in the middle of a project without letting the scope creep: write the request down, measure its impact on time, cost, quality and risk, give the decision to the right person, say yes, no or later with the trade-off made visible, and update the plan and the change log. Use when a client, a boss, a partner or a family member asks for "just one more thing", or when a project keeps growing. Triggers: "scope creep", "change request", "can we also add", "new requirement", "dérive du périmètre", "demande de modification", "on peut aussi ajouter", "avenant", "solicitud de cambio", "ampliación del alcance", "podemos añadir también".

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    When a new request arrives after the scope was agreed (project-charter).

    line 21
  2. Distinctive:

    When a client or a partner keeps adding "small" things.

    line 22
  3. Very specific:

    Not when the whole project is off track: use project-recovery.

    line 23
  4. Distinctive:

    Propose options: add it with its cost and delay, swap it for something of similar size that is removed, do it later in a second phase, or …

    line 35
  5. Distinctive:

    No request is accepted without its impact on time and cost.

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Scope change

Projects rarely blow up in one day; they grow one small request at a time. This skill gives every request a visible price in time and money, so that the person who decides can say yes knowingly.

When to use

  • When a new request arrives after the scope was agreed (project-charter).
  • When a client or a partner keeps adding "small" things.
  • Not when the whole project is off track: use project-recovery.

Inputs

  1. The request, and who made it.
  2. The current scope, schedule and budget.
  3. Any contract or agreement that frames changes (for example a quote that lists what is included).

Method

  1. Write the request down in one or two sentences, with the reason behind it and its urgency.
  2. Measure its impact: extra tasks, days, cost, effect on quality and on the risk register, and what else gets delayed.
  3. Propose options: add it with its cost and delay, swap it for something of similar size that is removed, do it later in a second phase, or decline it with the reason.
  4. Send it to the decision owner named in the charter, not to whoever happens to be in the room.
  5. Record the decision in a change log: request, impact, decision, date, who decided.
  6. Update the plan: scope, schedule, budget and, for outside suppliers, a written amendment to the quote or contract before the work starts.

Output

### Change request <n>: <title> (requested by <who>, <date>)
Why: … | Urgency: …
Impact: +… days | +… cost | quality: … | risks: …
Options: add / swap for … / later / decline
Decision: … by <owner> on <date>

### Change log
| # | Request | Impact | Decision | Date | Decided by |
|---|---|---|---|---|---|

Quality bar

  • No request is accepted without its impact on time and cost.
  • The decision owner decides, and the decision is logged.
  • Work for an outside supplier changes only after a written amendment.
  • Written in the user's language, with the terms below.

Terminology

EnglishFrançaisEspañol
Scope creepDérive du périmètreAmpliación descontrolada del alcance
Change requestDemande de modificationSolicitud de cambio
Change logRegistre des modificationsRegistro de cambios
AmendmentAvenantAdenda, modificación del contrato
Trade-offArbitrageCompromiso
Change controlGestion des changementsControl de cambios

Sources

  • Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK Guide) (7th ed.). Project Management Institute.

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.

Check your setup, free