Pantheon Andon Cord — Development skill for Claude Code
Invoke the Andon Cord Protocol — pause all work, identify root cause, do not resume until blocker is resolved.
How to install Pantheon Andon Cord
Installs to ~/.claude/skills/dkschrei-pantheon-pantheon-andon-cord/SKILL.md
mkdir -p ~/.claude/skills/dkschrei-pantheon-pantheon-andon-cord && curl -fsSL https://raw.githubusercontent.com/dkschrei/pantheon/HEAD/commands/pantheon-andon-cord.md -o ~/.claude/skills/dkschrei-pantheon-pantheon-andon-cord/SKILL.md Restart Claude Code, or start a new session, for it to be picked up.
What Pantheon Andon Cord does
description: Invoke the Andon Cord Protocol — pause all work, identify root cause, do not resume until blocker is resolved
Andon Cord Protocol
Invoking the Andon Cord. All current tasks are pausing.
What happens now
- All current tasks PAUSE — no exceptions, nothing continues until the blocker is identified
- Acknowledge the stop in exactly one sentence — no defending prior strategy, no explaining, no apologizing
- Ask one question only: "What broke and what
Alternatives in Development
- Root Cause Tracing — Use when errors occur deep in execution and you need to trace back to find the original trigger 102.5k ★
- Engage.Crash — Crash → root cause → reachability → empirical exploitability verdict (native bugs) 348 ★
- Cloud Run Debug — Diagnose a failing Cloud Run service — Antigravity (agy/Gemini) digests the error logs cheaply, Claude infers 284 ★
Full documentation available on GitHub
View Source RepositoryRelated Skills
Pantheon Vessel And Soul
Invoke the Vessel and Soul Protocol — ask the decay rate, route to the matching tier, extract the soul before
Buzz
Profile Lean declarations, find the slow ones, trace-diagnose the root cause, and fix them until each elaborat
Claude Usage Guard
Pause Claude before its next tool call when your 5-hour or weekly plan usage runs hot with lots of window left
Five Whys
Walk the five-whys root-cause analysis protocol when something broke unexpectedly.
Cad Debug
Scientific root-cause debugging protocol (No panic-coding).
Review Fix Loop
Run a review, fix the findings, and review again until no blocker or major findings remain. Use when the user
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
Sc Root Cause Analyst
Systematically investigate complex problems to identify underlying causes through evidence-based analysis and