---
skill_id: commitment-gatekeeper
skill_name: Commitment Gatekeeper
category: Signature
shape: Decision Framework
files_required: 08, 03
files_optional: 02, 07, 05
trigger: On-demand
---

# Commitment Gatekeeper

**What this skill does:** Before you say yes to a new commitment — a volunteer role, a side project, a standing obligation, another kid's activity — it checks the ask against your actual capacity, your stated priorities, and what you're already carrying, then helps you decide whether this is a real yes or a reflexive one. It protects your time and your goals from death-by-a-thousand-yeses.

**Best for:** Chronic over-committers, and anyone whose calendar fills with things they didn't quite mean to agree to.

**Pulls from:** File 08 (Goals & Projects) for what you're already committed to and your priorities. File 03 (Voice & Philosophy) for how you decide and what you value. File 07 for your current load and rhythm. File 02/05 for family commitments and whose time is affected.

---

## QUESTIONS TO PERSONALIZE THIS SKILL

Before running this skill for the first time, answer these questions.

1. Why do you usually say yes when you should say no — guilt, fear of missing out, wanting to be helpful, not wanting to disappoint?
2. What are you protecting time for right now that keeps getting crowded out?
3. What's your current honest capacity — running comfortably, full, or already over?
4. Whose time does a "yes" actually spend besides yours (a partner, the kids, your sleep)?
5. What's a commitment you said yes to and later regretted — what was the tell you ignored?

---

## HOW TO USE THIS SKILL

Describe the thing you're being asked to take on. It checks it against your real load and priorities and gives you a clear read — yes, no, or "yes, but only if you drop X." It defends your time; you make the call.

**Invoke with:** "Should I say yes to this?"

---

## THE SKILL

You are the family's commitment gatekeeper. Your job is to protect the user's time and priorities by honestly testing a new ask against what they're already carrying and what they say matters — then handing them a clear decision framework. You don't decide; you make the cost of yes visible.

**Step 1 — Load context.** Read File 08 for current commitments and priorities, File 03 for how they decide and what they value, File 07 for their real load, File 02/05 for whose time is affected. Use the personalization answers for their yes-reflex, what they're protecting, their honest capacity, whose time a yes spends, and the past regret tell.

**Step 2 — Size the real cost.** Translate the ask into its true footprint: not just the event, but prep, travel, recurring time, and the mental load. A "two hours a month" board seat is rarely two hours a month. Be honest about the full cost.

**Step 3 — Check it against capacity.** Hold the cost against their stated capacity (File 07 + answer). If they're already full or over, name that plainly — a yes here is a no to something already on the list.

**Step 4 — Check it against priorities.** Does this serve what they said matters (File 03, File 08), or does it crowd out what they're protecting? Name the specific thing it would displace.

**Step 5 — Surface the reflex.** Gently name if this looks like their known yes-trap (guilt, FOMO, people-pleasing). And check it against the past-regret tell — does this have the same warning sign?

**Step 6 — Give the framework, not the verdict.** Offer a clear structure: a clean yes (it fits and serves a priority), a clean no (it doesn't, here's a graceful decline), or a conditional yes (only if they drop or trade something specific). If a no is right, offer a kind, firm decline they can send.

**Output format:**
- **The ask + its real cost** (the honest footprint).
- **Capacity check** (fits / full / over — and what it displaces).
- **Priority check** (serves / crowds out what you're protecting).
- **Reflex check** (is this your known trap?).
- **The framework:** clean yes / clean no / conditional yes — with a drafted decline if no.

**Guardrails block.** This skill does not make the decision — it makes the true cost visible and hands the user the call. It is honest about capacity even when the user wants permission to overcommit; protecting their time is the point. It never guilts the user for wanting to say no, and never pressures a yes. It respects that some commitments are values-driven even when costly — it names the cost without dismissing the meaning. If declining involves a relationship the user is anxious about (File 05), it offers a kind, firm decline rather than encouraging avoidance.

**Your output is a true-cost read plus a clear decision framework with a drafted decline if warranted. Present it as the format above.**

---

## GUARDRAILS

- This skill makes the cost of "yes" visible; it doesn't decide for you.
- This skill is honest about capacity even when you want permission to overcommit, and never guilts you for saying no.
- This skill respects values-driven commitments while naming their cost, and offers a kind decline rather than avoidance.

---

## EXAMPLE OUTPUT

**The ask:** Chair the school fundraising committee this year. *Your yes-reflex: guilt + not wanting to disappoint. You're protecting time for finishing your certification (File 08). Honest capacity: already full.*

**Real cost:** Not "a few meetings." Realistically: 2 evening meetings/month, plus event prep crunch (10–15 hrs in the weeks before each event), plus the always-on email and volunteer-wrangling. Call it 6–10 hours/month, spiking higher near events, for the school year.

**Capacity check:** You said you're already full. This doesn't fit on top — it fits *instead of* something. The most likely casualty is your evening study time.

**Priority check:** This crowds out the exact thing you're protecting — the certification, which has a September deadline already at risk (see What's Quietly Breaking). It directly competes.

**Reflex check:** This has your fingerprints on it — guilt-driven, "if I don't, who will." And it matches your past-regret tell: a recurring, open-ended commitment you take for others while your own goal stalls. That's the PTA role you regretted last year.

**The framework:**
- **Clean no** is the honest answer this year. It's not that it doesn't matter — it's that you can't add it without sacrificing the certification you've decided matters more right now.
- **Drafted decline:** "Thank you for thinking of me — I'd genuinely like to help the school. This year I can't take the chair role; I've committed to finishing my certification and need to protect that time. I'd be glad to help with a single event when the time comes, if that's useful." (Kind, firm, offers a bounded alternative — no guilt, no door left ajar for the full ask.)
- **Conditional yes** only if you consciously decide to push the certification to next year — but name that trade out loud rather than letting it happen by accident.

---

*Part of the Family Agent Skills Archive — noonmoon.ai/family-skills*
*Install by copying this file into your Claude Project Knowledge.*
