deep-execution

Featured

Executes agent-enhanced council queries as one Workflow of parallel Claude analyst agents that each query a provider, evaluate response quality, ask follow-up questions, and return a schema-enforced analysis with confidence ratings and blind spot analysis. Invoked when the --agents flag is used or when complex architectural decisions are detected.

AI & Automation 791 stars 96 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 92/100

Stars 20%
97
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Agent-Enhanced Council Execution Run one Workflow of parallel Claude analyst agents for deeper analysis. Each analyst queries its provider, evaluates response quality, can ask follow-up questions, and returns a structured analysis that the workflow enforces against the schema. ## Step 1: Resolve Providers and Write the Questions One shell call resolves what the workflow needs — each provider's model, its role, and the question file it will send — with the same helpers the standard flow uses. Paste the final question into the heredoc verbatim: the quoted marker means the shell does NOT interpret quotes, backticks or `$()` in it. The question is emitted once; each provider's role-injected variant is built in shell, not pasted again. ```bash source "${CLAUDE_PLUGIN_ROOT}/scripts/lib/providers.sh" source "${CLAUDE_PLUGIN_ROOT}/scripts/lib/roles.sh" PROVIDERS=(<the selected providers, space separated>) ROLES="<the --roles value, or empty>" RUN=$(date +%s) # names this run's files; Step 6 reuses it Q="$PWD/.claude/council-cache/.agents-$RUN" mkdir -p "$PWD/.claude/council-cache" # Self-ignoring, as cache.sh and run-council.sh keep it: these files carry the # question and any --file contents, and must never land in a commit. [[ -f "$PWD/.claude/council-cache/.gitignore" ]] || printf '*\n' > "$PWD/.claude/council-cache/.gitignore" cat > "$Q.txt" <<'COUNCIL_Q_EOF' <the question, verbatim> COUNCIL_Q_EOF # --file / auto-context: append the context ...

Details

Author
hex
Repository
hex/claude-council
Created
9 months ago
Last Updated
yesterday
Language
Shell
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

council-execution

Executes council queries by running the query pipeline across selected AI providers (Gemini, OpenAI, Grok, Perplexity), displaying formatted responses verbatim, and generating a synthesis of consensus, divergence, and recommendations. Invoked by the ask command during standard (non-agent) council queries.

791 Updated yesterday
hex
AI & Automation Featured

local-council-execution

Runs a local council when no external AI providers are configured. Spawns N independent Claude subagents (one per role, blind to each other) that each answer the question from a single assigned lens, then synthesizes their perspectives. Invoked by the ask command via --local, or when the user accepts the local-council offer after no providers are found. This is a same-model (Claude-only) panel, not a cross-vendor council.

791 Updated yesterday
hex
AI & Automation Listed

council

Put a decision to four models across three vendors, have them rank each other blind, then synthesise. Use in plan mode before committing to an approach; before an architecture, schema, security or concurrency decision that is expensive to reverse; when a review is uncertain or two reviewers disagree; before verifying that a design actually holds; and when about to ship something whose failure mode is data loss, a breach, or a production outage. Do NOT use for questions with a knowable answer — read the code, run the test, grep. Costs 10–30 minutes.

0 Updated 3 weeks ago
developerjillur