paseo-committee

getpaseo/paseo

Form a two-agent committee for root-cause analysis and planning when stuck or facing hard problems.

What is paseo-committee?

Paseo Committee creates a pair of high-reasoning agents with contrasting profiles to step back, analyze problems from different angles, and produce a consensus plan. Use it when you're looping, tunnel-visioning, or need fresh perspective on a difficult planning challenge.

Spawns two agents with different reasoning styles from configured profiles
Conducts parallel root-cause analysis from contrasting perspectives
Resolves disagreements between agents to reach consensus
Produces a joint plan without editing or creating files
Supports extended reasoning sessions (15–30 minutes)

How to install paseo-committee

npx skills add https://github.com/getpaseo/paseo --skill paseo-committee

Prerequisites

Paseo skill installed and configured
At least two agent profiles configured (or access to provider discovery fallback)
Read the paseo skill documentation

Claude Code

Cursor

Windsurf

Cline

How to use paseo-committee

1.Call `list_profiles` to see available agent profiles
2.Select two profiles with contrasting reasoning styles from different provider families if possible
3.Write a clear problem-level prompt describing the issue or planning challenge
4.Create both committee agents in parallel using Paseo with `[Committee] <task>` titles and your prompt
5.Wait for both agents to complete their analysis (do not interrupt)
6.Review their responses and note where they diverge
7.If needed, pass disagreements between agents for resolution until consensus emerges
8.Share the final consensus plan with the user, summarizing divergence points and how they resolved

Use cases

Good for

Breaking out of circular debugging loops by getting fresh analysis
Planning complex features or refactors from multiple angles
Investigating root causes of recurring issues
Making architectural decisions with competing viewpoints
Recovering from tunnel-vision on a hard problem

Who it's for

Developers stuck on complex problems
Teams needing structured second opinions
Anyone using Paseo agents for planning or analysis

paseo-committee FAQ

Can I choose which agents form the committee?

Yes. If you name specific profiles, those will be used. Otherwise, the skill picks two contrasting profiles from configured agents, preferring different provider families.

What if I don't have two suitable profiles configured?

Paseo's provider discovery fallback will materialize a missing member automatically, and you'll be notified.

Can the committee edit files or write code?

No. Every prompt to committee members ends with a no-edits suffix. They perform analysis only.

How long can agents reason?

Models can reason for 15–30 minutes. Trust the finish notification and do not interrupt or poll.

What should I do if the agents disagree?

Pass their arguments between each other to resolve the disagreement, repeating until they converge into a consensus response.

Full instructions (SKILL.md)

Source of truth, from getpaseo/paseo.

name: paseo-committee description: Form a committee of two high-reasoning agents to step back, do root cause analysis, and produce a plan. Use when stuck, looping, tunnel-visioning, or facing a hard planning problem. user-invocable: true

Committee Skill

Two agents from contrasting profiles, fresh context, planning a solution in parallel.

User's additional context: $ARGUMENTS

Prerequisites

Read the paseo skill. Call list_profiles before choosing committee members. Do not create committee agents until you have read the configured profiles and their notes.

Contrast is the point of a committee, so pick profiles from different provider families when possible. Materialize each profile into create_agent.

Composition

Two members with different reasoning styles, selected from configured Agent profiles:

one whose notes fit planning, research, or root-cause analysis
one contrasting high-reasoning profile from another provider family

If the user names profiles, use those. If fewer than two suitable profiles are configured, use Paseo's provider discovery fallback for the missing member and tell the user. Override the selection only when the user explicitly asks for different members.

Hard rules

No edits. Every prompt to a committee member ends with the no-edits suffix:

This is analysis only. Do NOT edit, create, or delete any files. Do NOT write code.

Trust the finish notification. Do not poll, send hurry-ups, or interrupt. Models can reason for 15–30 minutes. You can go idle and Paseo will notify you.

Workflow

Write a problem-level prompt
Create both agents in parallel via Paseo with [Committee] <task> titles and the same prompt
Wait for both responses
Resolve disagreements by passing their arguments between each other
Keep going until they converge into a response

Share the consensus with the user. Summarize where the agents diverged and how they resolved it.