council

KvFxKaido's avatarfrom KvFxKaido

Gather design feedback from AI consultants (Gemini and Codex). Use for architecture decisions, design review, or when you want multiple expert perspectives on SENTINEL development. (project)

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 8, 2026
[Architecture Design]

When & Why to Use This Skill

The Council is a sophisticated Claude skill designed to streamline architectural decision-making and technical design reviews by orchestrating feedback from multiple AI consultants, such as Gemini and Codex. It provides a multi-perspective analysis of software projects, balancing high-level conceptual clarity with deep technical implementation focus to ensure robust, scalable, and well-vetted system designs.

Use Cases

  • Architectural Trade-off Analysis: Evaluate competing technical approaches, such as choosing between different database schemas or persistence layers, by gathering diverse expert opinions.
  • Complex Design Reviews: Invoke the council to review intricate system designs that affect multiple subsystems, ensuring consistency and identifying potential integration risks.
  • Implementation Strategy Validation: Use specialized AI consultants to refine implementation details, focusing on code quality, performance optimization, and practical technical constraints.
  • Multi-Perspective Problem Solving: Gain comprehensive insights on difficult development hurdles where both big-picture thinking and granular technical depth are required.
namecouncil
descriptionGather design feedback from AI consultants (Gemini and Codex). Use for architecture decisions, design review, or when you want multiple expert perspectives on SENTINEL development. (project)
allowed-toolsBash, Read, Glob, Grep
user-invocabletrue
proactivetrue

The Council

Invoke external AI consultants for design feedback on SENTINEL.

Consultants

Model Strength Best For
Gemini Big-picture thinking, design patterns Architecture, conceptual clarity
Codex Technical depth, implementation focus Code quality, practical constraints

How to Run

When the user invokes /council, gather context and consult both AIs:

Step 1: Prepare Context

Read the project brief and any relevant files the user mentions:

C:\dev\SENTINEL\SENTINEL_PROJECT_BRIEF.md

Step 2: Consult Gemini

Run non-interactively with the user's question + context:

gemini "You are reviewing SENTINEL, a tactical TTRPG with an AI Game Master.

<context>
[Insert project brief or relevant code]
</context>

<question>
[User's design question]
</question>

Provide focused feedback on design patterns, architecture, or the specific question asked. Be concise."

Step 3: Consult Codex

Run non-interactively:

codex exec "You are reviewing SENTINEL, a tactical TTRPG with an AI Game Master.

<context>
[Insert project brief or relevant code]
</context>

<question>
[User's design question]
</question>

Provide focused feedback on implementation, code quality, or the specific question asked. Be concise."

Step 4: Synthesize

Present both perspectives, noting:

  • Where they agree (strong signal)
  • Where they differ (worth investigating)
  • Actionable recommendations

Example Usage

User: /council Should we use SQLite instead of JSON for campaign persistence?

Then:

  1. Read SENTINEL_PROJECT_BRIEF.md and src/state/schema.py
  2. Ask Gemini about data model evolution and query patterns
  3. Ask Codex about migration complexity and performance
  4. Synthesize into recommendation

Tips

  • Keep prompts focused on one question at a time
  • Include relevant code snippets, not entire files
  • The consultants don't have project context — you must provide it
  • Use when genuinely uncertain, not for validation