---
name: yogsoth-ai/constraint-tree-building
source: https://app.decimal.ai/s/yogsoth-ai-constraint-tree-building@1/SKILL.md
source_sha256: 514afbf69be3
---

# Tactic: Constraint Tree Building

## Orchestration Pattern

1. **List UDEs** → spawn `undesirable-effect-listing`
   - Collect all observable symptoms of system underperformance
   - Ensure each UDE is specific, observable, and evidenced
   - Minimum 5 UDEs for a meaningful tree

2. **Trace Causal Chains** → spawn `causal-chain-tracing`
   - Input: UDE list from step 1
   - For each UDE, trace backward: IF [cause] THEN [effect] BECAUSE [assumption]
   - Connect UDEs that share common causes
   - Identify convergence points (multiple chains meeting at one cause)

3. **Extract Core Conflict** → spawn `core-conflict-extraction`
   - Input: convergence points from step 2
   - If root cause is a dilemma, express as Evaporating Cloud
   - If root cause is a single constraint, express as binding constraint statement

## Decision Criteria

- **When to iterate**: If the tree has disconnected components (UDEs not linked to any chain), return to step 2 with those UDEs
- **When to stop**: All UDEs connect to at most 3 root causes, and root causes are expressed as constraints or conflicts
- **When to escalate**: If >10 UDEs found, prioritize top-5 by severity before tracing
- **Quality gate**: Every causal link must have a BECAUSE clause (the underlying assumption)

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

## Available SOPs

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

| SOP | When to use |
| --- | --- |
| causal-chain-tracing | Trace UDE to root cause via IF...THEN...BECAUSE logic chains |
| core-conflict-extraction | Extract core conflict in Evaporating Cloud format (A-B-C-D-D') |
| undesirable-effect-listing | List current Undesirable Effects (UDEs) — observable symptoms of system underperformance |

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