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.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Two agents from contrasting profiles, fresh context, planning a solution in parallel.
User's additional context: $ARGUMENTS
Read the paseo skill. Call list_profiles before choosing committee members. Do not create committee agents until you have read the configured profiles and their notes.
Contrast is the point of a committee, so pick profiles from different provider families when possible. Materialize each profile into create_agent.
Two members with different reasoning styles, selected from configured Agent profiles:
If the user names profiles, use those. If fewer than two suitable profiles are configured, use Paseo's provider discovery fallback for the missing member and tell the user. Override the selection only when the user explicitly asks for different members.
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 finish notification. Do not poll, send hurry-ups, or interrupt. Models can reason for 15–30 minutes. You can go idle and Paseo will notify you.
[Committee] <task> titles and the same promptShare the consensus with the user. Summarize where the agents diverged and how they resolved it.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Quick-save the last assistant response as a verbatim note in the 2ndBrain Obsidian vault (~/2ndBrain/quick-notes/<year>/). Use when the user asks to quick-save/save the last response to 2ndBrain, or invokes $2ndbrain or /skill:2ndbrain.
The English summary is being prepared. Showing the original description.
Write commit messages under the agent-commits convention - a Conventional Commits fork with no chore catch-all, intent-only type tokens, facts in trailers, and legally-grounded AI provenance (Assisted-by, never Co-authored-by). Use when composing a commit in a repo whose commitlint.config.js extends agent-commits, when deciding between feat/fix/refactor/perf, or when recording AI participation.
The English summary is being prepared. Showing the original description.
Coordinate multi-agent work through durable artifacts in git instead of chat. Use this whenever a task involves sending a message to another agent, agent mailboxes or handoffs, claiming work from a shared queue, notifying another agent or crew (OpenClaw, Grok Bot, Claude Code, Codex, Gas Town/Gas City workers) that work is ready, or whenever the user mentions the artifact bus, message bus, agent mail, beads mail, doorbells, or pings between agents — even if they don't say "bus" explicitly.
The English summary is being prepared. Showing the original description.
Use aven to find tasks, update status, and leave durable handoff context.
The English summary is being prepared. Showing the original description.
Plan, order and deliver a batch of backlog items (e.g. every High item) in a Conventional Docs repo, one decision, branch, worktree, draft PR, review and merge per item. Use when asked to work through the backlog, implement all items of a priority, or sequence several backlog items end to end.
The English summary is being prepared. Showing the original description.
Codex workflow tips from Boris Cherny and the Codex team. Use when setting up Codex or optimizing workflows: parallel sessions, worktrees, plan mode, AGENTS.md, skills, subagents, hooks, MCP, permissions, and sandboxing.
The English summary is being prepared. Showing the original description.