Mohamed Boudra
90feb8050c
Skills installed via Paseo desktop never updated after first run, so users were stuck on already-fixed skill content. On every launch, if the paseo base skill is present in `~/.agents/skills/`, sync each bundled skill (incl. `references/`) into agents, claude (via symlink/ junction), and codex — overwriting only files whose content differs. Files on disk that are not in the bundle are left alone; deprecation goes through tombstones (e.g. `paseo-orchestrate` redirects to `paseo-epic`). Also refreshes the bundled skill set: drops `paseo-chat`, adds `paseo-advisor` and `paseo-epic`, and turns `paseo-orchestrate` into a tombstone redirecting to `paseo-epic`. Adds a desktop test job to CI on Ubuntu and Windows so the junction/symlink path is exercised on both platforms.
3.0 KiB
name, description, user-invocable
| name | description | user-invocable |
|---|---|---|
| paseo-committee | 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. | true |
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. Contrast is the point of a committee, so pick across providers deliberately rather than using whatever the default category would resolve to.
Composition
Two members with different reasoning styles:
- Claude Opus with extended thinking on
- Codex GPT-5.4 with thinking on
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: "use think-harder — 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 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.
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.