committee-plan

Coordinates four AI subagents to draft, compare, and converge on executable plans with verification steps and risk flags.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/Crispy13/copilot-directions --skill committee-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: committee-plan
Source: https://github.com/Crispy13/copilot-directions/tree/main/.github/skills/committee-plan
Command: npx skills add https://github.com/Crispy13/copilot-directions --skill committee-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning complex initiatives often stalls due to conflicting perspectives and unclear sequencing. committee-plan coordinates four AI subagents to draft parallel plans, surface consensus vs. contested steps, and iterate through structured discussion rounds to produce a single executable plan.

Core Features & Use Cases

  • Orchestrates a multi-model planning process using a structured Delphi-like method.
  • Four AI subagents (Opus, Sonnet, Gemini, GPT) draft plans in parallel and then converge on a consensus where possible.
  • Produces a final plan with a fixed output format, explicit verification steps, risk flags, and provenance.
  • Useful for roadmap construction, project scoping under uncertainty, and complex operation planning with dependencies.

Quick Start

Initiate a planning brief to the committee-plan skill to generate an executable plan.

Frequently Asked Questions about committee-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an executable project plan when team members have conflicting perspectives?

To create an executable project plan despite conflicting perspectives, this approach coordinates four AI subagents to draft parallel plans, surface contested steps, and iterate through structured discussion rounds to converge on a single consensus. It applies a structured Delphi-like method to resolve disagreements and produces a final plan with explicit verification steps.

What is multi-model consensus planning and how does it work for complex roadmaps?

Multi-model consensus planning works by orchestrating four AI subagents—Opus, Sonnet, Gemini, and GPT—to draft plans in parallel for complex roadmaps. These models compare their outputs, identify agreements versus contested steps, and iterate through structured discussion rounds to converge on a single executable plan with risk flags and provenance.

Can I use multi-model planning for risk-aware sequencing and dependency management?

Yes, you can use multi-model planning for risk-aware sequencing and dependency management. It is specifically designed for complex projects needing multiple perspectives and explicit verification, such as multi-phase roadmaps. The final output includes explicit risk flags, verification steps, and provenance to ensure practical delivery checks.

What's the best way to draft and compare parallel plans for uncertain project scoping?

The best way to draft and compare parallel plans for uncertain project scoping is initiating a planning brief to a four-model committee. This method grounds the planning in codebase patterns and existing constraints, allowing four AI subagents to draft independently, compare outputs, and converge on an executable plan with a fixed output format.

Do I need to provide codebase patterns and existing constraints before generating a plan?

Yes, you need to provide codebase patterns and existing constraints before generating a plan. The multi-model planning process requires grounding in these practical delivery checks and existing project limitations to ensure the four AI subagents can accurately draft, compare, and converge on a realistic executable plan.

When should I not use a multi-model committee for project planning?

You should not use a multi-model committee for simple project planning tasks that lack complex dependencies, multi-phase roadmaps, or significant uncertainty. If your project does not require multiple perspectives, explicit verification steps, or risk-aware sequencing, the overhead of coordinating four AI subagents to reach consensus is unnecessary.