Flow template · Research
Council
Different AIs answer from four roles; one that didn’t argue writes the answer.
5 chats1 noteSpread over the AIs you've connected
Shared by MrApers · 25 October 2026
What it does
Four chats on different AIs answer your question from four roles: builder, skeptic, simplifier and user advocate. A writer that didn’t argue waits for all four and writes one answer: what they agree on, where they disagree, what nobody checked, and a recommendation.
Each step
- Builder: Answer from the builder’s side: the best concrete answer or plan, and how to carry it out.
- Skeptic: Answer from the skeptic’s side: what is wrong, risky or unproven in the obvious answer, and what would have to be true for it to work.
- Simplifier: Answer from the simplifier’s side: the simplest thing that works, and what to cut.
- User advocate: Answer for the person who will use the result: what they need, what would confuse them, what it costs them.
- Writer: You get several answers to one question, each from a different role. Write one combined answer with exactly these headings: ## Agreed, ## Disagree, ## Nobody checked, ## Recommendation. Under the first three, short bullets naming who said what where it matters; under Recommendation, a few lines on what to do. You did not argue: be fair to each.
- Decision: A note: every answer that reaches it is added at the end, under who sent it and when.
How the work moves
- Start hands what you type to Builder, Skeptic, Simplifier and User advocate at once.
- Writer waits until Builder, Skeptic, Simplifier and User advocate have all answered, then gets their answers together.
- Writer's answer is added to Decision, a note.
What you need
- Any AI Morphy connects: Claude Code, Codex and the rest
Use it
- In Morphy: Settings → Community → Playground → Flow templates, pick Council and click Use this flow. It's built on your canvas.
- Or from the file: download council.flow.json and, on the same page, click Import a file…. It's yours to change, too.
- Start it: click Start on the flow and say what it should do.
More templates
Small change
A builder in its own copy opens a pull request; a reviewer reads it on GitHub until it’s ready for you to merge.
Development · 2 chatsPlanned feature
A spec you approve, two builders in their own copies opening pull requests, and QA that tests both before you merge.
Development · 4 chatsNew product
Concept, docs, prototype, validation, build and QA, and you decide at every turn before the next one starts.
Development · 7 chatsTeam
Chats share a list of tasks: each task goes to a free one, one line per task.
Other · 3 chats
