Individual skill
radical-simplification
Cognitive moves for collapsing complexity — reframe, clarify, reduce, decompose, invert, constrain, transfer, generalize, audit — distilled from the working method of mathematicians, physicists, and software engineers known for turning hard problems into simple solutions (Pólya, Feynman, Hamming, Brooks, Knuth, Dijkstra, Lamport, Tao, Grothendieck, Munger, Hofstadter). Use when stuck on a complex problem, when a proposed design feels overengineered, when reviewing code that has accreted accidental complexity, or when the user wants an elegant solution to a hard engineering or product problem. Triggers on phrases like "this feels too complicated", "we are going in circles", "there must be a simpler way", "interview me about this plan", "find the underlying problem", and on stuck-state moments where forward search has run out and the agent needs a different angle.
skills/.curated/radical-simplification/SKILL.md
Source commit cf93c57cac89d6fc3e4194686000411567f5caf3
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 222
- Repository last updated
- Aug 15, 2026
- License
- MIT
Observed agent integration: codex
- engineering Derived category
- design Derived category
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
AGENTS.mddoc · 6,370 bytesSKILL.mdcore · 9,568 bytesSKILL.mdcore · 9,568 bytesSKILL.mdcore · 9,568 bytesassets/templates/_template.mddoc · 990 bytesmetadata.jsonasset · 2,078 bytesreferences/_sections.mddoc · 4,417 bytesreferences/audit-fermi-sanity-check.mddoc · 1,780 bytesreferences/audit-feynman-technique.mddoc · 2,152 bytesreferences/audit-name-the-confusion.mddoc · 1,966 bytesreferences/clarify-interview-one-at-a-time.mddoc · 3,259 bytesreferences/clarify-prefer-source-over-asking.mddoc · 2,487 bytesreferences/constrain-dimensional-check.mddoc · 2,166 bytesreferences/constrain-name-the-invariant.mddoc · 1,717 bytesreferences/decomp-orthogonal-axes.mddoc · 1,785 bytesreferences/decomp-what-vs-how.mddoc · 1,676 bytesreferences/frame-essential-vs-accidental.mddoc · 1,807 bytesreferences/frame-find-decision-point.mddoc · 1,321 bytesreferences/frame-restate-problem.mddoc · 1,507 bytesreferences/gen-rising-sea.mddoc · 2,288 bytesreferences/invert-assume-failure.mddoc · 1,933 bytesreferences/invert-work-backwards.mddoc · 1,638 bytesreferences/reduce-limit-cases.mddoc · 1,664 bytesreferences/reduce-pareto-compress.mddoc · 1,546 bytesreferences/reduce-toy-case-first.mddoc · 1,537 bytesreferences/transfer-cross-domain-analogue.mddoc · 2,070 bytesreferences/transfer-suspect-vocabulary-lock-in.mddoc · 2,244 bytes
Read excerpt
# Radical Simplification — Cognitive Moves for Collapsing Complex Problems
Distillation of the documented working method of mathematicians, physicists, and engineers who consistently turn complex problems into simple solutions. The skill is not a step list — it is a toolbox of **cognitive moves**, each correcting a specific wrong default a capable model has when faced with complexity. The moves are mostly orthogonal; pick the one that matches the symptom.
This is the **thinking layer** that sits above refactoring (`code-simplifier`), metric design (`deterministic-metric-design`), and reviews (`design-review`). Those skills apply a methodology to a known shape of artifact. This skill is the methodology itself — how to arrive at the simple shape in the first place.
## When to Apply
Use this skill when:
- The user says the problem feels too complicated, that the team is going in circles, or that there must be a simpler way
- A proposed design has accreted parameters, dependencies, or branches and feels overengineered
- A plan has been drafted but unresolved decisions remain, and the agent is about to commit to assumed answers
- A bug investigation has tried several variants of the same approach without progress
- A review surfaces complexity that may be accidental (Brooks) rather than essential