# Boundary Setting

> Boundary Setting

- Skill: `sethdford/boundary-setting` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add sethdford/boundary-setting`
- Raw SKILL.md: https://api.skillmd.com/api/skills/sethdford/boundary-setting/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: sethdford (https://skillmd.com/u/sethdford)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/sethdford/boundary-setting

---

# Boundary Setting

Boundaries describe what you will do to protect capacity and values—not commands you issue to others. Clear, brief, and repeatable beats long justifications.

## When to Use
- Chronic overcommitment, resentment after saying yes, or repeated scope creep.
- You need scripts and principles for time, energy, information, or emotional labor.

## Workflow
1. **Own your side**: “I won’t be available after 6pm” works better than demanding others never ping you—pair with how urgent items can escalate if needed.
2. **Be clear and short**: state the limit once; optional one-line context, not a defense brief.
3. **No over-explaining**: you do not owe a novel for every no; “doesn’t work for me” can be enough.
4. **Anticipate pushback**: prepare a calm repeat of the boundary and a redirect (“Here is what I can do…”).
5. **Common domains**: time (hours, response SLA), energy (meeting load), information (what you share), emotional labor (what you absorb), scope (what is in/out).
6. **Scripts**: “I’m not able to take that on,” “I need time to decide,” “That doesn’t work for me.”
7. **Guilt**: expect it; it signals care, not that the boundary is wrong.

## Examples
**Example 1:** Manager adds weekend work—“I don’t work Sundays. I can deliver X by Monday 10am or scope Y for Friday—your call.”

**Example 2:** Relative asks intrusive questions—“I’m not discussing that topic. How was your trip?”—hold steady if they push.