agent-tower-plugin
Multi-agent deliberation for Claude Code - orchestrate AI coding assistants (Claude, Codex, Gemini) for council, debate, and consensus workflows
Best use case
agent-tower-plugin is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Multi-agent deliberation for Claude Code - orchestrate AI coding assistants (Claude, Codex, Gemini) for council, debate, and consensus workflows
Teams using agent-tower-plugin should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
How agent-tower-plugin Compares
| Feature / Agent | agent-tower-plugin | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Multi-agent deliberation for Claude Code - orchestrate AI coding assistants (Claude, Codex, Gemini) for council, debate, and consensus workflows
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# Agent Tower Plugin
Multi-agent deliberation for Claude Code. Orchestrate multiple AI coding assistants (Claude, Codex, Gemini) to get diverse perspectives on tasks.
## Interactive Configuration
Before running any multi-agent workflow, use **AskUserQuestion** to gather configuration preferences from the user. This ensures the user has control over:
- Number of agents/rounds
- Consensus thresholds
- Agent role assignments
- Other mode-specific options
Skip questions for any options the user explicitly provided in their command.
## Available Skills
### `/tower:council`
**Multi-agent council with parallel opinions and synthesis**
First, analyze the user's question and suggest relevant perspectives via AskUserQuestion. Then run multiple agents in parallel with the selected personas. Agents anonymously rank each other's responses, and a chairman synthesizes the final answer.
Best for: Evaluations, strategy decisions, comprehensive analysis, general knowledge questions
### `/tower:debate`
**Adversarial debate with pro/con agents**
Two agents argue opposing positions on a binary decision. A judge evaluates the arguments and declares a winner with scores.
Best for: Binary decisions, trade-off analysis, technology choices
### `/tower:deliberate`
**Producer/reviewer consensus loop**
A producer generates a response, a reviewer provides structured feedback, and they iterate until reaching consensus or hitting max rounds.
Best for: Code review, document refinement, iterative improvement
### `/tower:agents`
**List available agents**
Shows which agent backends (Claude, Codex, Gemini) are currently available.
## Agent Backends
| Agent | CLI | Default Model |
|-------|-----|---------------|
| claude | `claude -p` | opus |
| codex | `codex exec` | default |
| gemini | `gemini` | gemini-3-pro-preview |
## Dynamic Personas
Analyze the user's question and suggest relevant personas. Use technical personas for code/architecture questions, generalist personas for general knowledge questions.
**Technical:** Security Analyst, Systems Architect, Code Quality Reviewer, DevOps Engineer, Data Engineer, Devil's Advocate
**Generalist:** Research Analyst, Local Expert, Critical Thinker, Practical Advisor
**Business:** Business Strategist, Product Manager, Financial Analyst, UX Designer
Custom personas can be passed via `--personas '[{"name":"Expert Name","focus":"focus area"}]'`
## Examples
```
/tower:council "Evaluate this startup idea: AI-powered meal planning"
/tower:debate "Should we use microservices or a monolith?"
/tower:deliberate "Review the security of ~/GH/myproject"
/tower:agents
```Related Skills
laravel-plugin-discovery
Discover and evaluate Laravel packages via LaraPlugins.io MCP. Use when the user wants to find plugins, check package health, or assess Laravel/PHP compatibility.
Teleton Plugin Builder
This skill guides an AI agent through the process of building custom plugins for Teleton, a Telegram AI agent operating on the TON blockchain.
claude-code-plugin-release
Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, and plugin.json, build verification, git tagging, GitHub releases, and changelog generation.
Claude-Mem OpenClaw Plugin — Setup Guide
This guide walks through setting up the claude-mem plugin on an OpenClaw gateway. By the end, your agents will have persistent memory across sessions via system prompt context injection, and optionally a real-time observation feed streaming to a messaging channel.
wordpress-plugin-development
WordPress plugin development workflow covering plugin architecture, hooks, admin interfaces, REST API, security best practices, and WordPress 7.0 features: Real-Time Collaboration, AI Connectors, Abilities API, DataViews, and PHP-only blocks.
typespec-create-api-plugin
Generate a TypeSpec API plugin with REST operations, authentication, and Adaptive Cards for Microsoft 365 Copilot
Plugin Structure
This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices.
Plugin Settings
This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable. Documents the .claude/plugin-name.local.md pattern for storing plugin-specific configuration with YAML frontmatter and markdown content.
plugin-forge
Create and manage Claude Code plugins with proper structure, manifests, and marketplace integration. Use when creating plugins for a marketplace, adding plugin components (commands, agents, hooks), bumping plugin versions, or working with plugin.json/marketplace.json manifests.
create-cowork-plugin
Guide users through creating a new plugin from scratch in a cowork session. Use when users want to create a plugin, build a plugin, make a new plugin, develop a plugin, scaffold a plugin, start a plugin from scratch, or design a plugin. This skill requires Cowork mode with access to the outputs directory for delivering the final .plugin file.
cowork-plugin-customizer
Customize a Claude Code plugin for a specific organization's tools and workflows. Use when: customize plugin, set up plugin, configure plugin, tailor plugin, adjust plugin settings, customize plugin connectors, customize plugin skill, tweak plugin, modify plugin configuration.
plugin-audit
Comprehensive audit pipeline for skills, plugins, agents, and commands. Validates structure, quality, security, marketplace compliance, cross-platform compatibility, and ecosystem integration. Runs all built-in validation tools, invokes domain-appropriate agents for code review, and produces a pass/fail gate report. Usage: /plugin-audit <skill-path>