request-council-review

Runs parallel read-only reviews of planning docs by Claude, Codex, and Grok, then merges and resolves findings.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/mistakenot/skills --skill request-council-review-mistakenot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: request-council-review
Source: https://github.com/mistakenot/skills/tree/main/plugins/planning-workflow/skills/request-council-review
Command: npx skills add https://github.com/mistakenot/skills --skill request-council-review-mistakenot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Getting a single AI agent to review task planning documents can miss issues, but running multiple reviewers in parallel risks conflicting edits and duplicate comments in the same files. This Skill coordinates three independent reviewers without any of them touching the docs, then de-duplicates and merges their findings into one clean set of comment threads. ## Core Features & Use Cases - Parallel Multi-Agent Review: Launches Claude Code, Codex, and Grok as concurrent read-only reviewers over the planning docs in docs/tasks/, so wall-clock time equals the slowest single reviewer. - Deterministic De-duplication: The coordinator is the single writer; it pools structured JSON findings, merges duplicates across reviewers, keeps the highest priority, and tags each thread with reviewer attribution (e.g. [council: claude, codex]). - Markdown and HTML Comment Threads: Appends append-only comment threads in either markdown comment syntax or <pd-thread> elements, then hands off to resolve-comments and verifies author replies. - Use Case: Before executing task 042, run a council review so three independent agents verify acceptance criteria, file paths, and test coverage against the actual codebase, with consensus signaling which issues are real. ## Quick Start Ask the agent to run a council review on task 042 so Claude, Codex, and Grok review the planning docs in parallel and the merged comments get resolved.

Frequently Asked Questions about request-council-review

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

FAQPage Schema
How do I run a multi-agent review of planning documents?▼

Provide the numeric task ID and repository root, and the Skill launches Claude Code, Codex, and Grok in parallel as read-only reviewers. Each emits a structured findings block, which the coordinator de-duplicates and merges into comment threads before resolving them.

How do I get Claude, Codex, and Grok to review the same docs without conflicts?▼

Make all three reviewers read-only so none of them edits the files: Claude uses --permission-mode plan, Codex uses --sandbox read-only, and Grok is constrained by the prompt. A single coordinator then writes all merged comments, eliminating races and duplicate threads.

When should I use council review instead of a single-agent review?▼

Use council review when you want multiple independent reviewers before execution, since consensus across reviewers is a strong signal an issue is real. For a single-agent review, use the dedicated request-claude-review, request-codex-review, or request-grok-review skills instead.

What happens if one of the reviewers fails or times out?▼

A reviewer that errors or produces no findings block does not abort the run; the coordinator proceeds with whoever succeeded and notes the gap. Only if all three reviewers fail does the council stop, inspect the logs, and report the failure without writing placeholder threads.

Does the council review support HTML planning documents?▼

Yes, it supports both markdown and HTML planning docs. Markdown files get append-only comment blocks, while HTML files get <pd-thread> elements anchored to element ids, with priority and status attributes matching the review format conventions.