transformation-workflow
Practical application guide for HUMMBL's 6 transformations (Perspective, Inversion, Composition, Decomposition, Recursion, Meta-Systems). Includes when to use each transformation, combination patterns, analysis templates, output formats, real-world examples, and common pitfalls. Essential for applying mental models effectively in problem-solving and analysis.
npx skills add majiayu000/claude-skill-registry --skill transformation-workflow-hummbl-dev-hummbl-unified-tier-3 --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Practical guide for applying HUMMBL's 6 transformations to real-world problems. Provides step-by-step workflows, combination patterns, templates, and examples for effective mental model usage.
How it works
- Transformation set: Perspective (P), Inversion (IN), Composition (CO), Decomposition (DE), Recursion (RE), Meta-Systems (SY).
- Transformation Workflows: Each workflow prescribes inputs, a sequence of steps, and an output format for different analytical purposes (e.g., Perspective Analysis, Inversion Analysis, Composition Strategy, Decomposition Analysis, Recursion Analysis, Meta-Systems Strategy).
- For each workflow, it lists problem indicators or triggers, guiding questions, and best-use cases to determine when to apply a given transformation.
- Transformation Patterns: Provides patterns that combine multiple transformations in a sequence (e.g., P → DE → CO, P → IN → SY, DE → IN → CO, and a full cycle All 6 in Sequence) with concrete use cases and example narratives.
- Output templates: Each workflow includes explicit Markdown-formatted output structures to document findings, including problem statements, stakeholder perspectives, lenses, root causes, components, interconnections, iterative improvements, and strategic recommendations.
When to use it
- Use Perspective to frame ambiguous problems, map stakeholders, apply multiple lenses, identify first principles, and document context.
- Use Inversion to challenge assumptions, run premortems, identify what to STOP doing, and seek disconfirming evidence.
- Use Decomposition to break a complex system into parts, identify root causes, locate bottlenecks, and perform Pareto analysis.
- Use Composition to integrate components into a cohesive whole, identify synergies, define integration points, and plan orchestration.
- Use Recursion to analyze feedback loops, identify virtuous/vicious cycles, plan iterative improvements, and assess second-order effects.
- Use Meta-Systems to assess strategic questions, apply second-order thinking, find leverage points, anticipate unintended consequences, and select appropriate models.
What it can touch
- Tools: claude-code (as declared in the skill).
- It specifies workflows and templates but does not enumerate executable scripts beyond the formatted outputs and examples.
Caveats
- License: MIT.
- Declared tools: claude-code.
- The content assumes the user will apply the six transformations in the provided sequences and adapt the templates to concrete problems; it does not guarantee outcomes.
# Transformation Workflow Skill Practical guide for applying HUMMBL's 6 transformations to real-world problems. Provides step-by-step workflows, combination patterns, templates, and examples for effective mental model usage. ## Overview The 6 HUMMBL transformations represent different cognitive operations: 1. **Perspective (P):** Frame and name what is 2. **Inversion (IN):** Reverse assumptions 3. **Composition (CO):** Combine parts into wholes 4. **Decomposition (DE):** Break wholes into components 5. **Recursion (RE):** Iterate, feedback, self-reference 6. **Meta-Systems (SY):** Coordinate systems-of-systems ## When to Use Each Transformation ### Perspective (P) - Use When: **Problem Indicators:** - ✅ Problem statement unclear or ambiguous - ✅ Stakeholders have conflicting views - ✅ Need to understand different viewpoints - ✅ Framing feels wrong or limiting - ✅ Context not fully understood **Trigger Questions:** - "How do different people see this?" - "What am I missing in how I frame this?" - "Whose perspective matters here?" - "What context am I ignoring?" **Best For:** - Requirements gathering - Stakeholder analysis - Problem definition - User research - Strategic framing ###
- Overview
- When to Use Each Transformation
- Perspective (P) - Use When:
- Inversion (IN) - Use When:
- Composition (CO) - Use When:
- Decomposition (DE) - Use When:
- Recursion (RE) - Use When:
- Meta-Systems (SY) - Use When:
- Transformation Workflows
- Workflow 1: Perspective Analysis
- Workflow 2: Inversion Analysis
- Workflow 3: Composition Strategy
- Workflow 4: Decomposition Analysis
- Workflow 5: Recursion Analysis
What does the transformation-workflow skill do?
Practical application guide for HUMMBL's 6 transformations (Perspective, Inversion, Composition, Decomposition, Recursion, Meta-Systems). Includes when to use each transformation, combination patterns, analysis templates, output formats, real-world examples, and common pitfalls. Essential for applying mental models effectively in problem-solving and analysis.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill transformation-workflow-hummbl-dev-hummbl-unified-tier-3 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
