scope-changelisted
Install: claude install-skill teodstr/workbench
# 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
```markdown
### Change request <n>: <title> (requested by <who>, <date>)
Why: … | Urgency: …
Impact: +… days | +… cost | qualit