← ClaudeAtlas

murderboardlisted

Run the murderboard — the adversarial critical-review process — on a document deliverable before it ships. Use whenever the deliverable is an explainer, methods section, manuscript/abstract/cover-letter text, a figure or its caption/labels, a report, a slide deck, or a human-facing handoff. Also use when asked to "murderboard", "critically review", or "check this before I send it". Not for source code (that is the code-review path), quick conversational answers, or throwaway diagnostics.
syncytium2/murderboard · ★ 0 · AI & Automation · score 66
Install: claude install-skill syncytium2/murderboard
# Murderboard — call-up This skill is the **entry point**. It owns the mechanics of *invoking* the review correctly. It does **not** restate the review itself — the roles, their checklists, and every rule live in `doc_review_process.md`, which you will load in step 2 and follow. > **Why a skill exists at all.** The process file already carried the diagnosis — *"a rule > that depends on being remembered is not a gate"* — and applied it only to its own preflight. > Invocation stayed prose, so a review could be summoned late, run against a stale copy, fire > 7 of 11 roles, or target the generator instead of the built file, and every one of those > outcomes looked exactly like success. The steps below are the parts that must not depend on > anyone remembering them. ## Preflight — what this costs, before it costs it **Deliberately before step 0**, and unnumbered, because it gates whether the run happens at all rather than how it is done. A murderboard is a fan-out: one subagent per role, every role, always. On an expensive model that empties a usage window in minutes — and when it does, you get **no review and the full bill**, which is what happened on 2026-09-07 under Fable. **A `PreToolUse` hook should already have stopped you** if this model is blocked — `murderboard_model_gate.sh`, wired in the plugin and in consumers that vendored it. If you are reading this line, either it allowed the call or it is not installed here. Do not assume the second case means "no policy": ``