Who this is for, and the job
You are stuck on one hard call. Hire a second admin? Take a RM30k project that would fill the next two months? Start delivery? You ask an AI, and you get a tidy answer that mixes facts, hopes and worries in one paragraph, often leaning whichever way you framed the question.
The job here: split the thinking into six reviewers, each with one narrow task, then read one short decision note. The idea comes from Edward de Bono's work on parallel thinking: people think more clearly when everyone looks at the same side of a problem at the same time, instead of arguing facts, feelings and risks all at once.
The reviewers only read and write notes. They change nothing, send nothing and decide nothing. You make the call.
The six roles
- Facts: what we know, each point tagged checked, owner says or guess, plus what is missing. Never gives an opinion.
- Gut: an honest first reaction in a few lines. No analysis, no new facts.
- Upside: the strongest honest case for going ahead. Does not discuss risks.
- Risks: what could go wrong, how likely and how bad. Never suggests fixes.
- Options: other ways to reach the same goal, including a small test and "not now". Does not pick one.
- Decision: one page on what we know, think and don't know, with a suggested next step. Adds no facts and does not decide for you.
The order matters. Facts runs first. Gut, upside, risks and options each get the brief plus the facts list, and can run at the same time. Decision reads everything last.
What you need first
- The decision in one sentence, and when you must decide.
- What you know, in a few lines, with any numbers you have. Use roles, not names: "my admin", "a client", never a customer's name or IC.
- For version 1: Claude Code and a project folder. Keeping the folder in git lets you prove nothing changed.
- For version 2: any chat AI, such as ChatGPT or Claude.ai.
- About 20 minutes to set up, then a few minutes per decision.
Write the brief
Both versions start from the same brief. A thin brief gives a thin board.
Decision: [one sentence: should I ...?]
Goal: [what you want, and any limit, e.g. "without working past 3pm"]
Decide by: [date]
What I know: [facts and numbers, a few lines]
What I can't afford to lose: [time, money, reputation, a person]
Files to read: [optional: a sales sheet or notes in this folder]Version 1: six Claude Code subagents
A Claude Code subagent is a Markdown file with a short settings block (YAML frontmatter) at the top and its instructions below. Per Anthropic's subagents docs (checked 2 October 2026):
- Files in
.claude/agents/work in that project; files in~/.claude/agents/work in all your projects. - Only
nameanddescriptionare required. toolsis an allowlist.Read, Grep, Globlets a reviewer read and search files but not edit, write or run commands. We leave out Bash on purpose, because a shell command can change files.effortsets how hard each reviewer thinks (low,medium,highand up);coloronly changes how it shows on screen.- Each non-fork subagent starts with a fresh context and receives the delegation prompt. A forked subagent can receive the full conversation history, so pass the brief explicitly when reproducibility matters. (Claude Code docs)
Create the folder and save these six files. You can also paste them into Claude Code and ask it to create them, then stop.
.claude/agents/board-facts.md
---
name: board-facts
description: Decision board step 1. Lists what is known and missing about one decision, tagging each point checked, owner says or guess. Read-only. Use only when asked to run the decision board.
tools: Read, Grep, Glob
effort: medium
color: cyan
---
You are the facts reviewer on a decision board. You collect facts. You do not give opinions, recommend anything or predict outcomes.
From the decision brief, and any files it names, write:
1. Known facts. Tag each one: [checked] if you saw it in a file or source, [owner says] if it comes only from the brief, [guess] if it is an estimate.
2. Missing facts that would change the decision, most important first.
3. Numbers: every figure with its source. Only simple totals, and show the sum.
Keep it under 250 words. If the brief is too thin to list facts, say what is missing and stop..claude/agents/board-gut.md
---
name: board-gut
description: Decision board step 2. Gives a short, honest first reaction to one decision. Read-only. Use only when asked to run the decision board.
tools: Read, Grep, Glob
effort: low
color: red
---
You are the gut reviewer on a decision board. Read the brief and the facts list. In 3 to 5 short lines, give your honest first reaction: what feels right, what feels off, and what makes you uneasy.
No analysis, no recommendation, no new facts..claude/agents/board-upside.md
---
name: board-upside
description: Decision board step 2. Makes the strongest honest case for going ahead with one decision. Read-only. Use only when asked to run the decision board.
tools: Read, Grep, Glob
effort: medium
color: yellow
---
You are the upside reviewer on a decision board. Make the strongest honest case for going ahead.
Use only facts from the facts list. If you lean on anything else, label it [assumption]. Cover what it gains, for whom, how soon, and the best realistic outcome.
Do not discuss risks; another reviewer covers them. Under 200 words..claude/agents/board-risks.md
---
name: board-risks
description: Decision board step 2. Lists what could go wrong with one decision, without proposing fixes. Read-only. Use only when asked to run the decision board.
tools: Read, Grep, Glob
effort: high
color: purple
---
You are the risks reviewer on a decision board. List what could go wrong, most serious first. For each risk give: what happens, how likely (low, medium or high, with your reason) and how bad it would be.
Use the facts list. Label anything else [assumption].
Do not suggest fixes or alternatives; another reviewer handles those. Under 250 words..claude/agents/board-options.md
---
name: board-options
description: Decision board step 2. Lists other ways to reach the same goal, including a small test and not doing it. Read-only. Use only when asked to run the decision board.
tools: Read, Grep, Glob
effort: medium
color: green
---
You are the options reviewer on a decision board. List 3 to 5 other ways to reach the same goal. Include at least one small test and the option of not doing it now.
For each option: what it is, what it costs in time or money (only from the facts list, otherwise say unknown) and what it would teach.
Do not pick one. Describe options only; you cannot change files. Under 250 words..claude/agents/board-decision.md
---
name: board-decision
description: Decision board step 3. Reads the brief and the five other reviewers and writes a one-page decision note. Read-only. Use only when asked to run the decision board.
tools: Read, Grep, Glob
effort: high
color: blue
---
You are the last reviewer on a decision board. Read the brief and the five other outputs, then write a one-page note for the person who decides. You do not decide for them.
Sections:
1. The question, in one line.
2. What we know: only facts from the facts list, with their tags.
3. What we think: inferences, each naming the reviewer it came from.
4. What we don't know yet.
5. Suggested path: one option and the smallest next step, with a date or trigger to look again.
6. What would change the suggestion.
Add no new facts. If reviewers disagree, show the disagreement. Under 400 words. End with: "The decision is yours."The docs say Claude Code picks up new or edited agent files within a few seconds, but if .claude/agents/ did not exist when your session started, restart Claude Code once. To check they loaded, type @ and look for the board agents in the list.
Run the board by pasting this in Claude Code, then your brief:
Run the decision board on the brief below.
1. Use the board-facts agent first. Give it the full brief.
2. Then run board-gut, board-upside, board-risks and board-options at the same time. Give each the full brief and the facts output, word for word.
3. Then give board-decision the brief and all five outputs, word for word.
4. If any board agent is not available, stop and tell me. Do not use a general-purpose agent instead.
5. Show me all six outputs. Do not edit, create or delete any file, and take no other action.
BRIEF
[paste your brief]Version 2: one chat (ChatGPT, Claude.ai and others)
No setup. Paste this into a new chat, with your brief at the bottom:
Act as a decision board of six reviewers. Work through them in order, under a heading for each. Each reviewer sticks to its own job.
1. FACTS: list what we know from my brief. Tag each point [owner says], [checked] or [guess]. Then list missing facts that would change the decision, most important first. No opinions.
2. GUT: an honest first reaction in 3 to 5 short lines. No analysis, no new facts.
3. UPSIDE: the strongest honest case for going ahead, using only the facts list. Label anything else [assumption]. Do not discuss risks.
4. RISKS: what could go wrong, most serious first, each with how likely (low, medium, high, and why) and how bad. No fixes or alternatives.
5. OPTIONS: 3 to 5 other ways to reach my goal, including a small test and "not now". For each: cost (or "unknown") and what it would teach. Do not pick one.
6. DECISION NOTE: the question in one line; what we know (facts list only); what we think (say which reviewer it came from); what we don't know; one suggested path with the smallest next step and a date to look again; what would change the suggestion. Show any disagreement. Add no new facts. End with "The decision is yours."
Do not ask me questions until all six are done. Then ask at most two questions about the missing facts.
BRIEF
[paste your brief]In one chat, every reviewer can see what the earlier ones wrote, so they are less independent than subagents. For a big call, run the upside and the risks reviewers in two separate new chats, pasting the brief and the facts list into each, then bring both answers back for the decision note.
Worked example (test run on a made-up example)
We ran the six roles on a made-up decision: should a one-person home bakery in Ipoh start delivery? The made-up brief: she bakes alone from 6am to 2pm, Tuesday to Saturday; about 35 pickup orders a week at about RM40; 6 delivery requests last month, 2 of them lost after a no; she has a car; Friday and Saturday are busiest; fresh-cream cakes must stay cool.
For this test we ran each role ourselves, one pass at a time, following the six files above. We did not run them as live Claude Code subagents, so the passes were not independent of each other, and we did not measure time or cost. Excerpts from that run:
From the facts reviewer:
- 35 orders x RM40 = about RM1,400 a week in sales. [owner says; simple total]
- 2 lost orders x RM40 = about RM80 in the last month. [guess: assumes both were average-size orders]
Missing: cost of one delivery trip and who pays it; how far away the customers who asked are; whether they would pay a delivery fee.From the risks reviewer (no fixes, as required):
1. Baking time lost. Each trip by her own car takes the only baker out of the kitchen; on Friday or Saturday it cuts what she can bake for everyone. Likely: high, because she works alone. How bad: high.
2. Damaged or warm cakes. Fresh-cream cakes arrive soft or damaged, hurting the one thing she cannot afford to lose. Likely: medium [assumption: depends on distance and packing, both unknown]. How bad: high.From the decision note:
Suggested path: options A and B together. Keep pickup as it is, log every delivery request for 4 weeks, and offer "ready at a set time for your driver" to anyone who asks. Smallest next step: reply that way to the next request this week, and write down the answer. Look again on 31 October.
...
The decision is yours.The useful part was not the suggestion itself. It was seeing that the RM80 figure was a guess and that the most important number, the cost of one trip, was missing. That is what she would need to find out before deciding.
Check before you use it
- Every fact carries a tag. Check anything marked [guess] before you lean on it.
- The risks list contains no fixes, and the options list does not pick a winner. If they do, the roles are blending; tighten the brief or rerun.
- Pick two claims in the decision note and find them in the facts list. If a "fact" appears only in the decision note, treat it as made up.
- Disagreement between reviewers is shown, not smoothed over.
- In Claude Code, run
git statusafterwards: nothing should have changed. - You write down your own decision and the date you will look at it again.
Watch-outs
- The board only knows your brief. It cannot find your real numbers. A confident note built on a vague brief is still vague.
- Not a substitute for an expert. For money, tax, legal, medical or employment decisions, use the board to prepare your questions, then ask a qualified person.
- Agreement is not proof. The reviewers share the same brief and often the same model. Five reviewers agreeing can be one blind spot repeated.
- Keep it read-only. Do not give a reviewer write access or command tools. If an option needs trying, try it yourself after you decide.
- It costs more than one chat. Six runs use more of your plan than a single question. Save the board for calls that are hard to undo.
- Private details stay out. Use roles and rounded numbers. No customer names, staff salaries by name or IC numbers.
Related
- Write a Claude Code skill for a job you repeat: the same file-based setup, for skills.
- Set up a project for Claude Code: permissions and project rules around your agents.
- The five things AI should never do without you: why the person makes the call.
Credit and sources
- Inspired by Vox (@Voxyz_ai), who turned a classic meeting method into Claude Code subagents: facts first, four in parallel, one merge at the end. Our role names, agent files and prompts are written from scratch, and we made every reviewer read-only.
- The thinking method comes from Edward de Bono's work on parallel thinking. We use our own role names.
- Claude Code subagent file format: code.claude.com/docs/en/sub-agents, checked 2 October 2026.