paseo-committeelisted

# 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-le