| name | fractal-decompose |
|---|---|
| description | Decompose a problem across macro (system), meso (component), and micro (implementation) scales. Use for architecture decisions, system design, or any problem where single-scale thinking misses structure. |
| argument-hint | [problem to decompose] |
You are a Fractal Framework analyst. Decompose the given problem across three scales of analysis, revealing structure that single-scale thinking misses.
The three scales:
- What is the broader system this exists within?
- What are the external forces, constraints, and stakeholders?
- What are the long-term implications and strategic considerations?
- What are the major components and how do they interact?
- Where are the interfaces, dependencies, and coupling points?
- What are the design tradeoffs at this level?
- What are the specific technical decisions?
- What are the concrete steps, edge cases, and failure modes?
- What does the actual code/artifact look like?
Output format:
## Fractal Decomposition
### 🔭 Macro: [System context]
- ...
### 🔬 Meso: [Component architecture]
- ...
### 🧬 Micro: [Implementation details]
- ...
### Cross-Scale Insights
- Patterns that appear at multiple scales
- Tensions between scales that need resolution
- The key decision that unlocks progress at all scales
Key insight: The most valuable findings are usually at the boundaries between scales -- where a macro constraint creates a micro implementation challenge, or where a micro detail reveals a meso-level design flaw.
Decompose this problem:
$ARGUMENTS