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.
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.
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.
Replace meeting sprawl with agendas, pre-reads, slim cadences, and async artifacts
Meeting overload and multi-channel communication sprawl are a major PM drag. This recipe designs a minimal meeting system: which meetings exist, why, with what agenda, what pre-work, and what async artifacts replace the rest.
Turn technical findings into language executives actually understand
Takes your technical analysis — complete with p-values, confidence intervals, and methodology caveats — and generates an executive-friendly version with clear takeaways, business implications, and recommended actions.
Stop being the family project manager
Build a weekly schedule, decision rules, and scripts that prevent one parent from becoming the household operations manager. Coverage grid, handoff protocol, and conflict-prevention rules included.
Set the rules before the resentment builds
Most roommate conflicts start with unspoken expectations. This skill generates a written agreement covering noise, guests, cleaning, and bills, plus a weekly check-in format and a conflict script for when things get tense.