メニュー
Diagnose the Leopold install: checks skills, hooks and their wiring, gstack, the driver toolchain, and whether an update is available.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Phase 1 of Leopold. A structured debate that captures the mission and your decision-making, then writes the brief (MISSION, CHARTER, GUARDRAILS, PLAN) that the autonomous run executes.
Launch a local live web dashboard to watch the current project's Leopold run — status, cost meters (context/subagents/forks), event feed, decisions, and a Stop button. Local-only (127.0.0.1), zero dependencies.
Compile a Leopold brief into a dynamic workflow and run it. The plan lives in code instead of one growing context window, every item gets an independent adversarial review, and git stays locked — nothing is committed. The workflow is resumable and shows up in /workflows.
Control plane for the global prompt enhancer: status, on/off, preview a prompt against the gate, and the learn loop that mines your enhancement ledger into proposed prompt-profile rules. Never edits PROMPT-PROFILE.md itself — you review and apply.
The self-improving charter. Mines past Leopold decisions, session corrections, and git history for recurring judgment calls, skeptic-verifies each candidate, and proposes charter amendments. Never edits CHARTER.md itself — you review and apply.
Phase 2 of Leopold. Enters autonomous mode and conducts Claude Code through the plan, deciding from the charter instead of asking, with git locked. The Stop hook keeps it going until the plan is done or a stop condition fires.
SOC 職業分類に基づく
| name | leopold-doctor |
| version | 0.1.1 |
| description | Diagnose the Leopold install: checks skills, hooks and their wiring, gstack, the driver toolchain, and whether an update is available. |
| allowed-tools | ["Bash"] |
| triggers | ["leopold doctor","check leopold install"] |
Verify that Leopold is installed correctly. Read-only.
Run:
bash ~/.claude/leopold/scripts/leopold-doctor.sh
Report the summary. If any [FAIL] lines appear, tell the user the exact fix
(usually re-running ./install.sh, installing jq, or installing the plugin).