Skip to content

MVPavan/via / .claude/skills/model-council

model-council

Verified

Use only for an explicitly requested council of named models or agents with a judge. Ordinary review and brainstorming do not need a council.

Model Council

Run the same task through user-selected independent members, then a selected judge. Preserve every member's full report and the judge's consolidation.

Resolve members and judge from this request or its existing explicit selections; ask only for missing choices or unreachable members. Inspect current runtime configuration and the available permitted dispatch interfaces. Do not infer cross-provider access from a model name, put effort only in prose when a runtime control exists, or silently substitute a member. Follow shared delegation policy. For Codex members from Claude Code, call the Codex CLI directly (codex exec), never the retired codex-adapter plugin; see AGENTS.md §Running Codex.

  1. Write one common brief: question, relevant source pointers, constraints, acceptance and report format. Use a neutral brief without preferred conclusions.
  2. Give each member that brief independently. Parallelism is useful but optional; isolation means members do not see one another's answers. Save full attributed reports under the supplied run directory or scratchpad/council/<topic>/.
  3. Give a fresh judge the brief and all attributed reports. Request a synthesis of agreement, disputes, evidence, best-supported conclusion and uncovered gaps. Majority agreement is not proof; the judge may favor a supported minority view.
  4. Deliver a concise consolidation, member-position summaries and paths to every full report. Include full text inline when requested, rather than discarding it.

Record actual model identities where the runtime provides evidence. A failed member gets bounded safe recovery; report any missing member and whether the judge saw an incomplete council. Never backfill a member with your own answer. A council-only request does not authorize implementing its recommendations.

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 467kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 319kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 319kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 319kUpdated Claude CodeCodexVerifiedInstall