# Concept Decomposition

> Tactic for breaking compound concepts into atomic parts — split over-broad concepts, identify sub-components, create child pages.

- Skill: `yogsoth-ai/concept-decomposition-2` (Agent Skill)
- Install (CLI): `npx get-skill add yogsoth-ai/concept-decomposition-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/yogsoth-ai/concept-decomposition-2/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: yogsoth-ai (https://skillmd.com/u/yogsoth-ai)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/yogsoth-ai/concept-decomposition-2

---


# Concept Decomposition

Break compound or over-broad concepts into their atomic constituents. A concept that means too many things should become multiple focused concepts connected by edges.

## Available SOPs

- wiki-search — find existing sub-concepts
- concept-page-creation — create new atomic concept pages
- edge-batch-creation — connect parent to children
- alias-resolution — ensure no naming conflicts

## Guiding Principles

- **Atomic means testable.** If you can't write a one-sentence definition, the concept is too broad.
- **Preserve the parent.** Decomposition creates children; the parent becomes a container (component_of edges).
- **Stop at utility.** Don't decompose below the level where distinctions matter for the research.

## Minimum Yield

<HARD-GATE>
≥2 child concepts created per decomposition invocation.
If a concept cannot be meaningfully decomposed, report it as atomic and exit.
</HARD-GATE>

