Skip to content
Back to skills

Constraint Tree Building

ASecurity

Build Current Reality Tree from UDEs through causal chains to core conflicts

  • 417 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added June 2, 2026
researchgoexpressperformance

Security analysis

A100/100

Scanned June 2, 2026

npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill constraint-tree-building --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Constraint Tree Building?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Constraint Tree Building
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-constraint-tree-building/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-constraint-tree-building)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: constraint-tree-building
description: "Build Current Reality Tree from UDEs through causal chains to core conflicts"
version: 1.0.0
category: experiment-execution
type: tactic
used-by: constraint-analysis
orchestrates:
  - undesirable-effect-listing
  - causal-chain-tracing
  - core-conflict-extraction
---

# 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)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…