claudecodeguide.dev

Patterns

The Crucible

Stress-test any decision with a council of 16 AI personas that argue, rebut, and vote. Turn one perspective into sixteen, on demand.

On this page (9 sections)

You keep arguing with yourself

You sit down with a hard decision. Should I ship this? Pivot that? Hire now or wait? After twenty minutes of brainstorming alone, you notice something uncomfortable: you are mostly arguing with your own blind spots. And you do not know which ones.

This is the problem every product manager, founder, and builder hits. Hard decisions need many perspectives. Your brain only carries one.

The Crucible fixes this. It is a Claude Code skill that convenes a council of sixteen specialized AI personas, runs them against your question in parallel, and hands you back a structured verdict with a mandatory dissenting voice. Different voices, different angles, one clean read.

A quick Crucible run between meetings

What a Crucible run looks like

Every run has the same shape. Four phases, one chair, honest debate.

Phase 1: Intake. The chair restates your question in one sentence and asks you to confirm. Mis-framed questions produce sharp answers to the wrong thing, so this step is cheap insurance.

Phase 2: Openings. Selected personas write their take in parallel, blind to each other. Each one has a concrete rubric. The Contrarian must name a hidden assumption and attack it. The Steelman must name a non-obvious benefit. No vibes. Only deliverables.

Phase 3: Duels. Pairs of personas rebut each other. Steelman against Contrarian. Ambition Stretcher against Pre-mortem Pessimist. Success Vision against Downside Floor. The friction is the point.

Phase 4: Verdict. The chair reads everything, writes the full transcript to disk, and gives you a one-paragraph inline call: PROCEED, REFRAME, or KILL. Plus a mandatory minority report, because even when the council agrees, the strongest dissent has to surface by name.

The sixteen personas

Each persona has a role, a rubric, and a model tier (Haiku, Sonnet, or Opus) matched to the weight of its job.

BenchPersonas
Core 4 (always convened)Contrarian, Steelman, Pre-mortem Pessimist, Operator
Personal (career and moonlight)Archivist, Values Compass, Success Vision, Downside Floor
Strategic (business and market)Economist, Competitor, Second-Order Thinker, Historian
Creative (reframing and ambition)Ambition Stretcher, Reframer
Conditional (activated when relevant)Naive Outsider, Regulator

The chair picks six to ten for any given run, based on the kind of question you asked. Not all sixteen every time. A product launch question pulls in the Naive Outsider. A halal-finance or platform-policy question pulls in the Regulator. A career question pulls in the Archivist.

The four modes

Not every question needs a ten-persona council. Crucible has four tiers so you can match the weight to the question.

ModePersonasDuelsWall timeUse for
Quick3None~30 secondsDaily sanity checks between meetings
PM Daily4None~60-90 secondsFeature direction, research design, bounded ideation
Decision6-10FullA few minutesReal decisions with real money or time at stake
Existential16FullLongerLife-scale decisions. Guardrailed: once-per-quarter warning

Start with Quick. Most days, that is the mode you need. Decision mode is for twice-a-month questions.

Install it

Crucible is three markdown files. No build step. No dependencies.

Installing Crucible

The skill hooks straight into Claude Code's slash-command system, which you already know from the Building Skills pattern.

If you do not use Claude Code yet, the persona rubrics in personas.md are portable. You can paste any single persona prompt into Claude.ai or ChatGPT and run that lens by hand. You lose the orchestration, you keep the rubric.

When to use it

SituationMode to use
"I just thought of X, is it dumb?"Quick
"What is the sharpest first experiment for this discovery?"PM Daily
"Should I keep building this side project?"Decision
"Should I leave my job to ship this full time?"Existential
One-off tactical question with a clear answer in five minutesSkip Crucible. Just think.

Crucible is deliberately not an auto-trigger skill. It fires only when you invoke it. The reason: a ten-persona council is expensive, and the best guard against procrastination-via-ritual is making invocation explicit.

Guardrails worth knowing about

Two built-in checks exist because the skill kept catching itself making errors, and the fixes became structural.

The motivated-convening check. Before firing a Decision or Existential council, the chair asks three questions at intake: has a similar question been convened in the last thirty days? What decision does a verdict produce in the next fourteen days? What new information has arrived since the last time you thought about this? If the answers add up to "none, I just have renewed energy," the chair names that out loud. This is the single best defence against Crucible becoming an elaborate form of procrastination.

The Archivist ownership classification. The Archivist persona reads your own files and cites patterns from your history. It is required to label every cited project as personal moonlight, client work, collaborative work, or day-job work before drawing any conclusion across them. This exists because one early run confused a piece of client work for a personal choice, and the correction is now built into the rubric.

The full story

If you want the build narrative (why this came out of two retired side projects, how the persona rubrics were designed, what the first two runs actually killed, and why the minority report matters), read the origin story on Substack:

The Crucible: A PM's Answer to Wicked Problems

Repo is at github.com/mshadmanrahman/crucible. MIT licensed. Star it if it saves you an argument.

Questions worth running through it

Pick one, run it today. You do not need a big decision to start.

QuestionMode
"Is this feature worth building?"Quick
"Should I hire this role now or wait a quarter?"PM Daily
"Which one of my side projects do I keep?"Decision
"Is the positioning of my product still right?"PM Daily
"What is the strongest case against my roadmap?"Decision
"What am I doing that looks like strategy but is actually just busywork?"PM Daily
"Should I take the new job?"Existential

Start with Quick. Thirty seconds. Three voices. One question you actually have.

New guides, when they ship

Guides, templates, and real workflows. No fluff. Unsubscribe whenever.

Or follow on Substack