Launch Delivery Pipeline
Yeachan-Heo/oh-my-claudecode
Delivery pipeline from mission brief to verified change: writes a spec, splits it into tickets, runs them in parallel, verifies and reports a decision log after a repo audit gate.
Forms a two-agent committee with contrasting profiles to analyze a stuck problem in parallel, reconcile their views and return a consensus plan without editing files.
Install Paseo Committee
$ npx skills add getpaseo/paseo --skill paseo-committee -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install getpaseo/paseo paseo-committee --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/getpaseo/paseo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/paseo-committee .claude/skills/paseo-committee && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "paseo-committee" agent skill from https://github.com/getpaseo/paseo/tree/main/skills/paseo-committee into .claude/skills/paseo-committee/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paseo-committee", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/getpaseo/paseo/tree/main/skills/paseo-committeeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add getpaseo/paseo --skill paseo-committee -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install getpaseo/paseo paseo-committee --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getpaseo/paseo.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/paseo-committee .agents/skills/paseo-committee && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "paseo-committee" agent skill from https://github.com/getpaseo/paseo/tree/main/skills/paseo-committee into .agents/skills/paseo-committee/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paseo-committee", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add getpaseo/paseo --skill paseo-committee -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install getpaseo/paseo paseo-committee --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getpaseo/paseo.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/paseo-committee .cursor/skills/paseo-committee && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "paseo-committee" agent skill from https://github.com/getpaseo/paseo/tree/main/skills/paseo-committee into .cursor/skills/paseo-committee/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paseo-committee", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/getpaseo/paseo.git --path skills/paseo-committee--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add getpaseo/paseo --skill paseo-committee -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install getpaseo/paseo paseo-committee --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getpaseo/paseo.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/paseo-committee .gemini/skills/paseo-committee && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "paseo-committee" agent skill from https://github.com/getpaseo/paseo/tree/main/skills/paseo-committee into .gemini/skills/paseo-committee/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paseo-committee", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install getpaseo/paseo paseo-committeeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add getpaseo/paseo --skill paseo-committee -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/getpaseo/paseo.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/paseo-committee .github/skills/paseo-committee && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "paseo-committee" agent skill from https://github.com/getpaseo/paseo/tree/main/skills/paseo-committee into .github/skills/paseo-committee/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paseo-committee", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add getpaseo/paseo --skill paseo-committee -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install getpaseo/paseo paseo-committee --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getpaseo/paseo.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/paseo-committee .opencode/skills/paseo-committee && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "paseo-committee" agent skill from https://github.com/getpaseo/paseo/tree/main/skills/paseo-committee into .opencode/skills/paseo-committee/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paseo-committee", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
paseo-committee- GitHub stars
- 20k
- Used in
- 1 other repo
- Token cost
- ~496 tokens
- SKILL.md length
- 237 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Forms a two-agent committee with contrasting profiles to analyze a stuck problem in parallel, reconcile their views and return a consensus plan without editing files.
- Works in 5 steps: Write a problem-level prompt → Create both agents in parallel via Paseo… → Wait for both responses → …
- A debugging session keeps looping without progress
- SKILL.md covers Prerequisites, Composition, Hard rules and Workflow
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
When work is looping or tunnel-visioned, the agent reads the paseo skill, calls `list_profiles` and reads each configured profile's notes before creating anyone. It picks two members: one whose notes suit planning, research or root-cause analysis, and a contrasting high-reasoning profile from another provider family. Profiles you name take priority, and if fewer than two suitable profiles exist, Paseo's provider discovery fills the gap and you are told.
The committee is analysis only, so every prompt ends with a no-edits suffix. The agent writes one problem-level prompt, creates both members in parallel with `[Committee]` titles, waits without polling because models can reason for 15 to 30 minutes, then passes their arguments to each other until they converge. You get the consensus plus a summary of where they diverged and how it was resolved.
When your agent uses it
- A debugging session keeps looping without progress
- Facing a hard planning problem that benefits from two independent views
- Stepping back to find the root cause before trying another fix
Example prompts
- “Form a committee to work out why the nightly sync keeps failing after three attempted fixes.”
- “I keep going in circles on this schema migration. Get two agents to plan it independently and reconcile.”
- “Convene the committee with my planning and review profiles on the caching redesign.”
Requirements
- Paseo with at least two configured agent profiles
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Write a problem-level prompt
- Create both agents in parallel via Paseo with [Committee] 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
What it can do on your machine
Read from SKILL.md and the folder at commit 6ec6633. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Paseo Committee loads about 496 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 237 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 237 words (~496 tokens).
“Two agents from contrasting profiles, fresh context, planning a solution in parallel.”
- name
- paseo-committee
- user-invocable
- true
Files
Just SKILL.md in skills/paseo-committee of getpaseo/paseo.
Open the folder on GitHubat commit 6ec6633
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in getpaseo/paseo, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Paseo Committee next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Paseo Committee this skillgetpaseo/paseo | 20k | 1 repos | ~496 | Automated safety check: Pass | Custom licence | |
| Launch Delivery PipelineYeachan-Heo/oh-my-claudecode | 40k | — | ~7.3k | Automated safety check: Pass | MIT | |
| Codex with ChatGPT Planning LoopXiaoDuoYa/codex-with-chatgpt | 7.2k | — | ~11k | Automated safety check: Notes | MIT | |
| SPARC Development Methodologyruvnet/ruflo | 74k | 2 repos | ~829 | Automated safety check: Pass | MIT | |
| AutopilotYeachan-Heo/oh-my-claudecode | 40k | — | ~4.4k | Automated safety check: Pass | MIT | |
| Autopilot End-to-End Buildernick-vels/skills | 414 | — | ~2.5k | Automated safety check: Notes | MIT |
Similar skills
Codex with ChatGPT Planning Loop
XiaoDuoYa/codex-with-chatgpt
Uses ChatGPT in the browser as the planning and review brain for a Codex session, with Codex keeping all execution and ChatGPT reading the workspace through a bridge.
SPARC Development Methodology
ruvnet/ruflo
Applies the SPARC method (specification, pseudocode, architecture, refinement, completion) with 17 specialized modes and multi-agent orchestration, from research to deployment.
Autopilot
Yeachan-Heo/oh-my-claudecode
Takes a short product idea through requirements, design, planning, parallel implementation, QA cycles and multi-reviewer validation to produce working code.
Autopilot End-to-End Builder
nick-vels/skills
Builds an app, site, bot or feature from a spoken idea through requirements, spec, tickets, subagent work, review and acceptance, with a live progress dashboard.
PRP Implementation Planner
Wirasm/prp
Turns a PRD, issue or description into an implementation-ready plan grounded in codebase evidence, adding root-cause analysis for bugs and publishing issue plans back to the issue.
More from getpaseo/paseo
Paseo Advisor Second Opinion
getpaseo/paseo
Launches one separate agent through Paseo to give a second opinion on the current task, with a self-contained briefing and no permission to edit files.
Paseo Agent Handoff
getpaseo/paseo
Hands off the current task, including context, decisions and failed attempts, to a fresh agent through Paseo by writing a self-contained briefing prompt and launching that agent.
Paseo Help
getpaseo/paseo
Answers questions about the Paseo app, such as setup, providers, connectivity, updates and logs, by checking the current public docs and working out which daemon is involved.
Paseo Plugin Builder
getpaseo/paseo
Builds, installs and troubleshoots trusted local Paseo plugins, from lifecycle hooks and slash commands to screens, themes and timeline renderers.
Paseo Agent Orchestration Reference
getpaseo/paseo
Reference for managing Paseo's projects, workspaces, workspace scripts and agents through its MCP tools or CLI, across a local or remote daemon.
Related
Categories
Questions about Paseo Committee
What does Paseo Committee do?
Forms a two-agent committee with contrasting profiles to analyze a stuck problem in parallel, reconcile their views and return a consensus plan without editing files. When work is looping or tunnel-visioned, the agent reads the paseo skill, calls `list_profiles` and reads each configured profile's notes before creating anyone. It picks two members: one whose notes suit planning, research or root-cause analysis, and a contrasting high-reasoning profile from another provider family.
When should I use Paseo Committee?
Paseo Committee fits situations like: A debugging session keeps looping without progress; facing a hard planning problem that benefits from two independent views; stepping back to find the root cause before trying another fix.
How do I install Paseo Committee in Claude Code?
Run `npx skills add getpaseo/paseo --skill paseo-committee -a claude-code`. Or copy the skill folder (skills/paseo-committee in getpaseo/paseo) into .claude/skills/paseo-committee in your project. Claude Code loads it when a task matches its description.
How do I install Paseo Committee in Codex?
Run `npx skills add getpaseo/paseo --skill paseo-committee -a codex`. Or copy the skill folder (skills/paseo-committee in getpaseo/paseo) into .agents/skills/paseo-committee in your project. Codex loads it when a task matches its description.
Can I use Paseo Committee in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add getpaseo/paseo --skill paseo-committee -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/paseo-committee, .gemini/skills/paseo-committee, .github/skills/paseo-committee and .opencode/skills/paseo-committee in your project.
What does Paseo Committee need to run?
SKILL.md names no scripts, command-line tools or credentials: Paseo Committee is instructions for the agent only. Our summary lists: Paseo with at least two configured agent profiles.
Does Paseo Committee access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Paseo Committee safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Paseo Committee use?
Paseo Committee has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Paseo Committee use?
About 496 tokens (SKILL.md is roughly 2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Paseo Committee?
Skills that share tags, products or a category with Paseo Committee: Launch Delivery Pipeline (Yeachan-Heo/oh-my-claudecode, 40k stars), Codex with ChatGPT Planning Loop (XiaoDuoYa/codex-with-chatgpt, 7.2k stars), SPARC Development Methodology (ruvnet/ruflo, 74k stars) and Autopilot (Yeachan-Heo/oh-my-claudecode, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Paseo Committee?
getpaseo (a GitHub organization) maintains it in getpaseo/paseo, which has 20,322 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 9, 2026.
Source: getpaseo/paseo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.