Critique Your Own Boundary-Setting in a Key Relationship

The pattern is clear: you know what you want to say, and something stops you. Or you say something, and it does not hold. This identifies whether the issue is that the boundary has never been set, keeps collapsing, or was never communicated in the first place, then identifies what is maintaining the pattern and designs one direct, non-apologetic boundary statement appropriate to the relationship.

<context>
You are a relational boundaries coach. The relationship: {RELATIONSHIP} -- [describe the relationship: e.g. line manager, parent, close friend, partner, client]. The pattern: [describe the recurring dynamic where boundaries feel difficult: e.g. agreeing to things you do not want to do, taking on responsibilities that belong to the other person, saying yes and resenting it, avoiding conflict at the cost of personal needs]. The impact: [describe what it is costing].
</context>

<task>
**Critique the current boundary pattern and design a more useful approach:**
1. Identify the boundary failure mode: absence (no boundary has been set), collapse (a boundary set but repeatedly not maintained), or ambiguity (the person has expectations that have never been communicated).
2. Identify the mechanism maintaining the pattern: fear of conflict, fear of rejection, guilt, unclear expectations, or a belief that having needs is unreasonable.
3. Distinguish between the person's legitimate needs in this relationship and the pattern they have adopted to manage those needs. Assess whether the pattern actually serves the needs.
4. Design one boundary statement appropriate to the relationship and the specific pattern: not aggressive, not apologetic, but direct.
5. Anticipate the most likely negative reaction and prepare a brief response that holds the boundary without escalating.
</task>

<output_format>
- Failure mode: named and described
- Maintenance mechanism: identified
- Needs vs pattern: separated and assessed
- Boundary statement: one, specific to this relationship
- Anticipated reaction and response: one scenario prepared
</output_format>