Pantheon Feynman Clarity — Testing skill for Claude Code
Run the Feynman Clarity Test — stop all tools, explain the system in plain English until the gap surfaces, fix the root cause not the symptom.
How to install Pantheon Feynman Clarity
Installs to ~/.claude/skills/dkschrei-pantheon-pantheon-feynman-clarity/SKILL.md
mkdir -p ~/.claude/skills/dkschrei-pantheon-pantheon-feynman-clarity && curl -fsSL https://raw.githubusercontent.com/dkschrei/pantheon/HEAD/commands/pantheon-feynman-clarity.md -o ~/.claude/skills/dkschrei-pantheon-pantheon-feynman-clarity/SKILL.md Restart Claude Code, or start a new session, for it to be picked up.
What Pantheon Feynman Clarity does
description: Run the Feynman Clarity Test — stop all tools, explain the system in plain English until the gap surfaces, fix the root cause not the symptom
Feynman Clarity Test
Stopping all tools. We are going to explain our way to the root cause.
No more logs, no more debuggers, no more Stack Overflow until Step 5.
Step 1 — State the goal
In one sentence, plain English (no jargon):
"This system should **[do X]** when **[Y happens]**."
Write it out. If it takes more tha
Alternatives in Testing
- Loki Grill — Interrogate a spec with Loki's Devil's-Advocate grill before building, and summarize the hardest questions it 1.1k ★
- Adversarial Spec — A Claude Code plugin that iteratively refines product specifications by debating between multiple LLMs until a 514 ★
- Test Login And Upload — End-to-end test of the CLI on the dev environment 97 ★
Full documentation available on GitHub
View Source RepositoryRelated Skills
Assemble
Assemble the film — narrate, ASR-verify pronunciation, build, test, check — looping until green or reporting i
Aegis Coverage Screen
Tool-boundary screen — warn user about ANY project where AEGIS coverage < 100%, list every gap. Mandatory at /
Hatch3r Bug Pipeline
Run a known-cause bug fix through a 3-phase test-first pipeline -- reproduce + root-cause, regression-test + f
J Debug
Systematic bug investigation — root cause analysis, not random fixes. Use when a test fails, a bug appears, or
Quick Debug
Structured bug investigation — reproduce, root-cause, fix, regression-test. Uses the debugger subagent for iso
Root Cause Fix
Root-cause-first TDD loop for any bug or data fix. Forces a failing reproduction test BEFORE touching producti
Related Agents
Hank
The investigator. Deep debugging and relentless root cause analysis. Use when normal investigation hasn't foun
Ndv Diagnose
Debugging specialist. Use when you have a bug, failing test, stack trace, unexpected behavior, or anything bro
Explain
This agent should be invoked to explain code, changes, pull requests, or concepts in plain English. This inclu