council

Evaluate architectural decisions from four perspectives into a decision matrix.

161|21|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/softspark/ai-toolkit --skill council-softspark
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: council
Source: https://github.com/softspark/ai-toolkit/tree/main/app/skills/council
Command: npx skills add https://github.com/softspark/ai-toolkit --skill council-softspark

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Help teams make structured, evidence-backed decisions by evaluating a proposal from four distinct perspectives and producing a weighted recommendation, reducing bias and overlooked risks during architectural or product trade-offs.

Core Features & Use Cases

  • Parse and Clarify: Extracts the proposal, alternatives (or infers status quo), and relevant context from the user's prompt and asks one clarifying question if needed.
  • Codebase-grounded Analysis: Scans the repository for tech stack, related code, configs, and dependencies to ground each perspective in real evidence.
  • Parallel Sub-agents & Synthesis: Orchestrates four parallel sub-agents (Advocate, Critic, Pragmatist, User-Proxy), collects 200–400 word evidence-focused responses, and synthesizes them into a decision matrix and a clear recommendation.
  • Governance & Safety: Enforces that sub-agents run via the Agent tool and that the skill itself remains read-only and analytic.

Quick Start

Ask the assistant to evaluate your proposal by saying: /council Should we migrate the payments module to a microservices architecture given our current monolith and CI/CD pipeline?

Frequently Asked Questions about council

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

FAQPage Schema
How do I evaluate architectural trade-offs in a codebase before making a decision?

To evaluate architectural trade-offs, you can use a multi-perspective analysis approach where four sub-agents review codebase evidence and synthesize a weighted decision matrix to produce a conditional recommendation.

What is multi-perspective decision analysis for software architecture?

Multi-perspective decision analysis evaluates proposals from Advocate, Critic, Pragmatist, and User-Proxy viewpoints to reduce bias and overlooked risks during complex architectural or product trade-offs.

How do I analyze deployment strategy options using codebase context?

Analyzing deployment strategy options requires scanning your repository for related code and configs, then running parallel evidence-focused evaluations to compare trade-offs and generate a structured recommendation.

Can I use this to compare libraries for an existing software project?

Yes, you can compare libraries by asking the skill to evaluate your proposal; it will infer the status quo from your codebase and ask one clarifying question if needed before generating the decision matrix.

What are the limitations of automated codebase evaluation for product decisions?

The automated codebase evaluation remains strictly read-only and analytic, meaning it cannot modify your repository or execute changes, and relies entirely on the context provided in your prompt and codebase.

When do I need a decision matrix for UX or product trade-offs?

You need a decision matrix for UX or product trade-offs when choosing between multiple options where codebase context and trade-offs matter, ensuring evidence-backed choices over subjective preference.