Paseo Committee
- 2.3k installs
- 12.1k repo stars
- Updated August 4, 2026
- getpaseo/paseo
paseo-committee is an agent skill for Form a committee of two high-reasoning agents to step back, do root cause analysis, and produce a plan. Use when stuck,
About
The paseo-committee skill 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. It covers one planning/research-strength provider. Key workflows include one contrasting high-reasoning provider. Developers invoke paseo-committee when the task matches the triggers and reference files in SKILL.md for grounded, stepwise execution. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation.
- one planning/research-strength provider
- one contrasting high-reasoning provider
- No edits. Every prompt to a committee member ends with the no-edits suffix:
- You are the middleman. Drive plan → implement → review without yielding to the user, except for divergences that need th
- High-level goal and acceptance criteria
Paseo Committee by the numbers
- 2,296 all-time installs (skills.sh)
- +210 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #258 of 1,879 Marketing & SEO skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
paseo-committee capabilities & compatibility
- Capabilities
- one planning/research strength provider · one contrasting high reasoning provider · no edits. every prompt to a committee member end · you are the middleman. drive plan → implement → · high level goal and acceptance criteria
- Use cases
- seo · marketing · copywriting
What paseo-committee says it does
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.
Two agents from contrasting providers, fresh context, planning a solution in parallel. They stay alive for review after implementation.
npx skills add https://github.com/getpaseo/paseo --skill paseo-committeeAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2.3k |
|---|---|
| repo stars | ★ 12.1k |
| Security audit | 2 / 3 scanners passed |
| Last updated | August 4, 2026 |
| Repository | getpaseo/paseo ↗ |
What problem does paseo-committee solve for developers using the documented workflows?
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.
Who is it for?
Developers working with paseo-committee patterns described in the skill documentation.
Skip if: Skip when docs are empty or the task is outside the skill documented scope.
When should I use this skill?
Use when 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
What you get
Actionable paseo-committee guidance grounded in SKILL.md workflows and reference files.
- implementation plan
- root-cause analysis
- post-implementation review session
By the numbers
- Deploys a committee of two contrasting-provider high-reasoning agents
Files
Committee Skill
Two agents from contrasting providers, fresh context, planning a solution in parallel. They stay alive for review after implementation.
The purpose is to step back, not double down. The committee may propose a completely different approach.
User's additional context: $ARGUMENTS
Prerequisites
Read the paseo skill. Before choosing committee members, read ~/.paseo/orchestration-preferences.json unless the user explicitly named providers in this request. Do not create committee agents until you have read it.
Contrast is the point of a committee, so pick across providers deliberately using the configured preferences rather than hardcoded defaults.
Composition
Two members with different reasoning styles, selected from orchestration preferences:
- one planning/research-strength provider
- one contrasting high-reasoning provider
Override 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 wait. Do not poll, send hurry-ups, or interrupt. GPT-5.4 can reason 15–30 minutes; Opus does extended thinking. Long waits mean it found something worth thinking about.
- You are the middleman. Drive plan → implement → review without yielding to the user, except for divergences that need their call.
Phase 1: Plan
Write a problem-level prompt:
- High-level goal and acceptance criteria
- Constraints
- Symptoms (if a bug)
- What you tried and why it failed
- Explicit: "do root cause analysis"
- Explicit: "state assumptions, ask why three levels deep, check whether you're patching a symptom or removing the problem"
Create both agents in parallel via Paseo with [Committee] <task> titles and the same prompt. Wait for both — not just whichever finishes first.
Read both responses. Challenge them — do not accept at face value:
- "Why does <underlying thing> happen? Symptom or cause?"
- Verify any assumption the plan makes about the code.
- "What did you considered and reject?"
Send follow-ups until the plan addresses root cause.
Synthesize:
- Convergence → unified plan.
- Significant divergence → involve the user.
Confirm the merged plan with both members. Multi-turn until consensus.
Phase 2: Implement
Default: implement yourself. If the user said "delegate", launch one impl agent and pass the merged plan.
The committee stays clean — not involved in implementation.
Phase 3: Review
Send the diff to the committee:
Implementation is done. Review changes against the plan. Flag drift or missing pieces. <no-edits suffix>
Apply feedback yourself, or send to the impl agent. Repeat 2 → 3 until consensus.
After ~10 iterations without convergence, start a fresh committee with the full history of what was tried — the current committee's context may have drifted too far.
Related skills
Seo AuditRun structured SEO audits on their SaaS site or content hub and receive a prioritized action plan.173k42.2kCopywritingGenerate, rewrite, or strengthen persuasive website and landing-page copy that converts visitors into users.164k42.2k
Viral Short FormQuickly generate high-retention hooks, scripts, and outlines for TikTok, Reels, YouTube Shorts, and carousels.132k67Viral HooksWrite and critique viral hooks for short-form video opening sequences.123k67Viral Captions And CtasOptimize social media captions and CTAs for viral short-form video reach and saves.123k67Viral Youtube ShortsWrite and diagnose YouTube Shorts for Shorts Feed and long-form funnel.123k67How it compares
Use for stuck planning with contrasting agents; use single-agent skills when the task scope is clear and execution—not re-planning—is the bottleneck.
FAQ
Who is paseo-committee for?
Developers and software engineers working with paseo-committee patterns described in the skill documentation.
When should I use paseo-committee?
When 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.
Is paseo-committee safe to install?
Review the Security Audits panel on this page before installing in production.