council

Give your agent more
perspectives.

Five independent advisors.
One clear recommendation.

Council is a skill that helps you make decisions. Ask a question about your project. Five independent advisors weigh in. The Chairman brings it all together.

Install Council See an example
Three confident robot advisors in blue, each looking from a different perspective.

Works where you work.

Independent minds.
Useful disagreements.

  1. Ask your question

    Bring a decision. Council chooses relevant perspectives, or you name your own.

  2. Convene the council

    Five advisor subagents assess independently in parallel.

  3. Make the call

    The Chairman weighs each perspective. Your agent adds its take and next step.

Architecture Product Naming
Illustrative output

Should we rewrite this service?

Architecture example: five independent perspectives
PerspectiveRecommendationPosition
PerformanceProfile the bottleneck first.Refactor
SecurityMigrate one boundary at a time.Refactor
MaintenanceA clean rewrite could simplify ownership.Rewrite — dissent
CostKeep the parts already earning their keep.Refactor
SimplicityFix the smallest thing that changes the outcome.Refactor

Chairman’s verdict

Refactor first. Revisit a rewrite when the measured constraints justify it.

My take

Start with the slowest path. Set a benchmark before changing the architecture.

Should we launch now or add more features?

Product example: five independent perspectives
PerspectiveRecommendationPosition
User experiencePut the core workflow in real users’ hands.Small beta
EngineeringFix critical bugs. Save the extras for later.Small beta
BrandPolish onboarding before making a first impression.Wait — dissent
GrowthLearn which benefits actually bring people back.Small beta
SupportStart with a group you can help personally.Small beta

Chairman’s verdict

Launch a small, supported beta. Fix onboarding friction before a wider release.

My take

Invite ten people with the problem. Watch them complete the core task before adding features.

Should we choose a descriptive or playful name?

Naming example: five independent perspectives
PerspectiveRecommendationPosition
ClarityMake the product’s purpose easy to understand.Descriptive
BrandA distinctive name gives people something to remember.Playful — dissent
SearchCheck that people can find you by name.Verify first
LanguageChoose something easy to say, spell, and share.Keep it simple
PositioningPair a memorable name with a clear descriptor.Playful + clear

Chairman’s verdict

Choose a memorable name with a plain-language descriptor. Check for conflicts before committing.

My take

Test three names with five likely users. Ask what each does, then which one they remember.

Example only. Your council’s recommendations depend on the question and evidence.

Pull up a chair.

Install the skill. Bring a question. Convene the Council.

Claude Code

/plugin marketplace add mattakins/council
/plugin install council@mattakins

Then ask

/council:council should we rewrite this service?

Codex

codex plugin marketplace add mattakins/council
codex plugin add council@mattakins

Then ask

$council:council should we rewrite this service?

Other agents

npx skills add mattakins/council -g

Then ask

Use the council skill: should we rewrite this service?

Select your agents in the installer. Or follow the standalone install instructions.

Full behavior requires parallel, isolated subagents.

Make it your own.

quick
Skip the Chairman for a faster take.
deep
Research + seven advisors + Chairman.
3
Choose how many advisors join.
"SEO, legal, UX"
Choose the perspectives yourself.
no research
Reason only from the context you provide.
save
Keep the complete result in Markdown.

Options combine. Natural language works too.

Install Council