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.
What this skill does
# 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 in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.