---
name: yogsoth-ai-conflict-resolution
description: "How do constraints conflict with each other? — Evaporating Cloud + assumption challenging + injection to resolve constraint conflicts"
license: "Apache-2.0"
metadata:
  decimalai-skill-id: "7299dc00-a9fe-4fa6-a951-1b85623ec037"
  decimalai-version-id: "ac382388-3186-4679-9a34-03c466189e07"
  decimalai-version: "1"
  decimalai-body-sha256: "c08add60200cb5e0b9e4f5a2b3629af6c29e0d45b40dcd713b09ff3e05da5e1e"
  decimalai-name: "yogsoth-ai/conflict-resolution"
  decimalai-format: "1"
  decimalai-invocation: "model"
  decimalai-category: "productivity"
  decimalai-source: "https://app.decimal.ai/s/yogsoth-ai-conflict-resolution@1/SKILL.md"
---
# Strategy: Conflict Resolution

## Methodology

Based on Goldratt's Evaporating Cloud (EC) and injection methodology:
- **Surface the conflict**: Express opposing demands in EC format
- **Challenge assumptions**: Each EC arrow rests on assumptions — find the invalid one
- **Inject**: Propose an action that invalidates the false assumption
- **Project future**: Use Future Reality Tree to verify injection resolves the conflict without creating new UDEs

Evaporating Cloud structure:
```
        B ←── D
       ↗         ↘ (conflict)
  A                    
       ↘         ↗ (conflict)
        C ←── D'
```
- A: Common objective both sides want
- B: Need that leads to wanting D
- C: Need that leads to wanting D'
- D and D': Mutually exclusive wants

## Execution Flow

1. **Extract Core Conflict** → call `core-conflict-extraction` SOP
   - Input: identified constraints that oppose each other
   - Output: Evaporating Cloud (A-B-C-D-D') with assumptions on each arrow

2. **Challenge Assumptions** → call `assumption-challenging` SOP
   - Input: assumptions underlying each EC arrow
   - Output: validity assessment, weakest assumptions identified

3. **Generate Injections** → synthesize from challenged assumptions
   - For each invalid assumption, propose an injection (action that makes the conflict disappear)

4. **Project Future Reality** → call `future-reality-projection` SOP
   - Input: proposed injections
   - Output: Future Reality Tree showing resolved conflict + any new UDEs

5. **Validate Resolution** → invoke `constraint-breaking` tactic
   - Orchestrate full resolution cycle

## Budget Gate

| Resource | Budget | Notes |
|----------|--------|-------|
| Subagent calls | ≤8 | 3 SOPs + injection generation + validation |
| Iterations | ≤3 | May need multiple injection attempts |
| Output size | ≤3000 tokens | EC + injection + FRT summary |

<!-- BEGIN available-tables (generated) -->

## Available Tactics

Optional, no fixed order; the final leaf is always a sop.

| Tactic | When to use |
| --- | --- |
| constraint-breaking | Orchestrate the full constraint-breaking cycle: extract conflict, challenge assumptions, project resolution |

## Available SOPs

Optional, no fixed order; the final leaf is always a sop.

| SOP | When to use |
| --- | --- |
| assumption-challenging | Challenge each assumption's validity — shared cross-repo SOP |
| core-conflict-extraction | Extract core conflict in Evaporating Cloud format (A-B-C-D-D') |
| future-reality-projection | Project solution effects using Future Reality Tree logic |

<!-- END available-tables (generated) -->