Scope Change Gatekeeper
Convert "quick asks" into logged change requests with impact analysis and approvals
Scope creep is a margin killer and a schedule killer. This recipe creates a strict-but-practical change control loop: capture request, classify, analyze impact (time/cost/scope/risk), propose options, and route for approval. It keeps a change log so Slack decisions don't silently rewrite the project.
INGREDIENTS
PROMPT
Create a skill called "Scope Change Gatekeeper". Input: a change request (often informal) + current baseline summary (scope/schedule/resources). Output: a logged Change Request with impact analysis and decision-ready options. Required behavior: - Convert the request into a clear, testable description of work. - Produce an impact statement (time/cost/scope/risk) using ranges when uncertain. - Offer options: Accept (adjust baseline), Defer, Reject, or Swap. - Generate a short approval message that I can paste to stakeholders. - Maintain a Change Log format (CR-ID, title, status, decision date, link to artifacts). Guardrails: - Never approve changes yourself. - If baseline is missing, ask for it or build a minimal baseline from context. - Prefer conservative estimates and explicitly list assumptions.
How It Works
When someone says "can't you just add this one thing?" — paste the request here along
with your current baseline. The recipe rewrites the ask into a testable statement of work,
classifies it (defect, enhancement, new scope), estimates impact in ranges, and gives you
2–4 decision-ready options to present to stakeholders.
What You Get
- Change Request record: ID, description, requester, date, rationale
- Impact statement: schedule delta, cost delta, risk delta, quality/tech-debt notes
- Decision options: accept and adjust, defer, reject, or swap scope
- Approval message: a ready-to-paste message for stakeholders
- Change log: running record of all CRs with status and decision dates
Setup Steps
- Have your baseline scope document handy (charter, SOW, or backlog snapshot)
- Paste the informal change request (Slack message, email, meeting note)
- Review the impact analysis and choose an option
- Send the generated approval message to the decision-maker
Tips
- Set an auto-approve threshold for tiny changes (e.g., under 2 hours effort)
- Use T-shirt sizing, story points, or day ranges — the recipe adapts
- Governance can be lite, standard, or formal depending on your org
- Every CR gets an ID, so you build an audit trail over time