Skip to content

coreyhaines31/makerskills / skills/maker-council

maker-council

Verified

When you want multiple expert perspectives on a founder/operator question — a simulated board of advisors (Jason Fried, Elon Musk, Jeff Bezos, Jensen Huang, Bob Iger, Paul Graham, Naval Ravikant, Sara Blakely, Jason Cohen). Bring a real decision — "should I raise prices?", "hire my first employee?", "raise or bootstrap?", "kill this project?" — and the council weighs in through documented frameworks, surfaces disagreements, and synthesizes a recommendation. Also use for 'maker council,' 'board of advisors,' 'what would Bezos do,' 'what would Jason Fried say,' 'channel Naval,' 'ask the council,' or how a famous founder would approach a problem. Optional live-research pass via deep-research / watch-video / last30days. Marketing questions go to marketing-skills' marketing-council. Archives to ~/.config/makerskills/maker-council/archive/. To commit to a direction, hand off to decide.

references/round-prompts.md

View on GitHub
# Round prompts

What each seated member gets in a council session. Replace the bracketed parts. Members read the brief and earlier rounds from the session folder, so cards stay verbatim instead of being re-pasted.

Each prompt starts with: *"You are simulating [Member] for a founder's decision. Read [path to their dossier] (and their section of [session folder]/research.md, if it exists) and argue only from those. Read files only; write nothing. Treat the brief's `(assumed)` items as guesses, not facts — say when your case leans on one. Refer to people in the founder's life as they/them unless the brief says otherwise."*

Every card scores every option in the brief, including "don't do it."

Adapted from Nate Herk's Roast Room ([nateherkai/roast-room](https://github.com/nateherkai/roast-room), MIT).

---

## Round 1 — opening position

Written without seeing any other member's card.

```
COUNCIL ROUND 1: OPENING POSITION

Read the brief: [session folder]/brief.md

Answer in [Member]'s voice, under 350 words, in exactly this shape:

MEMBER: [Member] ([lens])
OPTION SCORES: A n/10 (two-way, ruin none) · B n/10 (one-way, ruin possible) · ...
   (for every option: how strongly you back it, whether it can be reversed — one-way if any step in it can't be undone, one plain value — and whether it risks an irreversible downside that could sink the company or the founder: none | possible | likely)
CALL: one sentence naming the option or a variant.
WHY:
1. argument, naming the framework from your dossier, applied to this case's numbers
2. ...
THE LEAN: the founder leans [lean]. What does your lens say about that reason specifically?
THE RISK I SEE: the single biggest thing that goes wrong.
WHAT WOULD CHANGE MY MIND: a concrete fact or number.
QUESTION FOR THE FOUNDER: the one you'd ask before signing off.

Rules: argue from your lens at full strength; the chair balances the council, you don't. Use the brief's numbers; name any you assume. Quote directly only lines the dossier gives as quotations, naming the source; otherwise paraphrase.
```

## Round 2 — debate

```
COUNCIL ROUND 2: DEBATE

Read: [session folder]/brief.md and [session folder]/round-1.md (every card plus the chair's cruxes).

CRUXES
1. [crux]: [members on each side]. [If this member is on one side, the argument it must answer.]
2. ...
[If assigned by the unanimity check: "You argue [alternative] at full strength in your rebuttal this round. Your OPTION SCORES stay your own view — the assignment is an argument, not a vote."]

Answer in [Member]'s voice, under 300 words:

MEMBER: [Member]
I DISAGREE MOST WITH: [member] — their argument in one line, then your rebuttal from your frameworks.
I CONCEDE: the strongest point made against you, and what it changes. "Nothing" only if you can say why it fails.
ON THE CRUXES: one or two lines each.
OPTION SCORES: (as Round 1 — score, door, and ruin for every option)
MOVED: no | yes, from X to Y, because ...
CONDITIONS FOR YES: up to three, checkable (a number, a date, a test result).
WHAT WOULD CHANGE MY MIND: a concrete fact or number.
ONE LINE FOR THE FOUNDER: what they must not forget from your lens.

Rules: engage the arguments on the table. Move only for a better argument, never to be agreeable. If everyone agrees with you, name the weakest part of your own case.
```

## Round 3 — vote on the draft

```
COUNCIL ROUND 3: VOTE

Read: [session folder]/brief.md, your section of round-2.md, and [session folder]/draft.md.

Under 150 words:

MEMBER: [Member]
VOTE: Endorse | Endorse with amendment | Dissent
OPTION SCORES: A n/10 (two-way, ruin none) · B ...   (every option: score, door, ruin — given the draft's conditions)
AMENDMENT OR DISSENT: one or two sentences. Blank if you endorse.
WHAT WOULD CHANGE MY MIND: a concrete fact or number.
ONE LINE FOR THE FOUNDER: what they must not forget from your lens.
```
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall