Opinionated Pi workflow for executive deliberation
Turn briefs into structured board debate.
Boardroom is a Pi-native workflow pack that runs CEO and specialist board deliberations from structured briefs, then produces ranked recommendations, tradeoffs, and final decision memos. It is a Justin Clark Network product.
$ npm install @justynclark/boardroom
$ npx boardroom start
> ceo-begin 2026-03-18-engineering-path
Board assembled: 6 members
Revenue · Product Strategist · Technical Architect
Contrarian · Compounder · Moonshot
Brief: engineering-path
Budget: $1.00–$5.00 | Time: 2–5 min
Running deliberation...
✓ Vote: 5 accept / 1 defer | $0.19 | 1m 54s
Memo: .pi/ceo-agents/memos/engineering-path-3nnsni/memo.md
Workflow
How it works
Brief
Write the brief
Author a structured brief with situation, stakes, constraints, and a key question. The brief frames the decision for the board.
→ .pi/ceo-agents/briefs/{id}/brief.md
Deliberation
Run the board
Six specialist agents deliberate in parallel rounds. Each brings a distinct optimization lens - revenue, product, architecture, dissent, compounding, and upside.
→ .pi/ceo-agents/deliberations/{id}/conversation.jsonl
Dissent
Capture disagreement
The Contrarian stress-tests consensus. Follow-up rounds probe weak points. Votes are captured with rationale, not just tallied.
→ .pi/ceo-agents/deliberations/{id}/board/*.md
Memo
Get the memo
The CEO synthesizes all positions into a final decision memo with ranked recommendations, conditions, risks, and next moves.
→ .pi/ceo-agents/memos/{id}/memo.md
The Board
Six specialist perspectives
Each board member optimizes for a different dimension. The CEO synthesizes their positions into a final decision.
Revenue
ARR, margin, cash conversion, pricing power
Challenge anything that improves narrative but weakens economics.
Product Strategist
Product moat, roadmap leverage, user value, market fit
Push on clarity of pain, adoption friction, portfolio logic.
Technical Architect
System quality, maintainability, tech debt, team leverage
Demand explicit tradeoffs, failure modes, boring durable designs.
Contrarian
Assumptions, weak evidence, timing risk, narrative traps
Look for avoided arguments and disconfirming evidence.
Compounder
Long-term value, future optionality, learning, resilience
Ask if the decision makes the next decision easier or harder.
Moonshot
Upside asymmetry, bold underexplored moves
Call out underreaching or conservative bias.
Outputs
Real artifacts, not promises
Every deliberation produces deterministic, versioned artifacts you can review, diff, and audit.
Brief
.pi/ceo-agents/briefs/{id}/brief.md Structured input with situation, stakes, constraints, and key question.
Transcript
.pi/ceo-agents/deliberations/{id}/conversation.jsonl Full event log of every converse call, response, and state change.
Board Outputs
.pi/ceo-agents/deliberations/{id}/board/*.md Individual final position from each board member with vote and rationale.
State
.pi/ceo-agents/deliberations/{id}/state.json Persistent run state: costs, votes, member statuses, lifecycle tracking.
Memo
.pi/ceo-agents/memos/{id}/memo.md Final CEO decision with recommendations, conditions, risks, and next moves.
Examples
Real decisions, real outputs
Sanitized examples from actual Boardroom runs.
Engineering Path
Which engineering path compounds capability over time?
Product Direction
Should we pursue platform or vertical-first?
Acquisition Offer
Evaluate an inbound acquisition at 4x ARR.
Launch Strategy
Go broad on launch or narrow with design partners?
Solo Plugin Bet
Should we build the integration ourselves or partner?
Start running board deliberations.
Boardroom runs inside Pi, is published on npm as @justynclark/boardroom, and is open source under Apache 2.0. Read the docs to get started, or jump straight to the package.