Multi-consultant voting protocol (architect/cto/ceo as advisors, not deciders)

[ZaxShen]

Context

Decided in conversation after PR #41:

The decision chain is Human → bro → SWE. Bro is the planner. SWE is the executor. All other agents (architect, cto, ceo, domain specialists) are CONSULTANTS, not deciders. They produce analyses and recommendations; bro summarizes; Human decides.

This issue tracks the multi-consultant case: when the Human asks for multiple opinions or bro spawns more than one consultant for a second opinion.

Raw thinking (Zax, 2026-04-25)

• Single planner (bro) is the default.
• Multi-planner case → consultants vote.
• Bro summarizes the votes + tensions, surfaces a recommendation, Human decides.
• Consultants never write to MCP decision rows or spawn SWE — only bro does.

Open questions

1. Vote mechanism. Sequential (each consultant reads prior votes) or parallel (independent positions)? Sequential gives convergence; parallel gives independent reads.
2. Tie-breaking. Bro picks based on its own read? Surfaces tie to Human? Weighted by consultant role (cto outweighs ceo on technical questions)?
3. MCP capture. Does each consultant write a kind='vote' discussion row? Where does the summary land — kind='summary'? kind='recommendation'?
4. Spawn topology. Bro spawns N consultants in parallel via the Task tool, awaits all, summarizes. Cost is N×subagent-cold-start, so cap N at 3-4.
5. When does multi-consultant fire? Triggered by Human request ("get me a second opinion from cto"), by bro detecting a contested decision, or never automatically?

Acceptance

• A consultant-vote skill (or extension to architect-workflow) describing the voting protocol.
• MCP support for capturing votes (likely just a new kind value in discussions, not a new table).
• bro prompt section explaining when/how to invoke multi-consultant mode.
• A worked example for the most common case ("Human asks bro for second opinion on a design call").

Dependencies

Blocked by the larger redesign that removes architect from the default chain (in flight). After that lands, this issue picks up — architect is just one of many possible consultants in the new world.