Aa panel

Skill Peeyushmeher/agent-agile/skills/aa-panel

Use when a drafted plan (PROJECT.md, ROADMAP.md, and the current epic's story cards) needs adversarial review before execution starts, or the user invokes /aa-panel.From its SKILL.md

Install

npx -y skills add Peeyushmeher/agent-agile --skill aa-panel

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.6 KB, 637 tokens by cl100k_base, as published. Nobody here has run it

aa-panel

Resolve the Agent-Agile playbook root: use the first of these that exists — (1) ${CLAUDE_PLUGIN_ROOT}/playbooks, (2) ./.claude/agent-agile/playbooks, (3) ./.agents/agent-agile/playbooks, (4) ~/.claude/agent-agile/playbooks, (5) ~/.agents/agent-agile/playbooks, (6) ./playbooks.

Read playbooks/critics.md in full — Panel protocol, Product critic, Spec auditor, Execution auditor, Market critic, Verdict format — and follow it exactly; do not re-derive or improvise the panel's doctrine. The panel gate in Panel protocol applies here: run this skill only for multi-epic projects — a single-epic throwaway skips the panel entirely.

Wiring

Read the draft plan: .planning/PROJECT.md, .planning/ROADMAP.md, the current epic's story cards at .planning/epics/EPIC-NN/stories/S*.md, .planning/epics/EPIC-NN/CONTRACTS.md if it exists, and .planning/RESEARCH.md if it exists (per Panel protocol, the spec auditor alone receives it).
Read .planning/CONFIG.md for the smart_tier and commercial fields.
Spawn aa-critic-product, aa-critic-spec, and aa-critic-execution as parallel fresh subagents, each with the model configured for its tier in .planning/CONFIG.md. If commercial: yes, also spawn aa-critic-market the same way. Give each subagent exactly two inputs: its two sections of playbooks/critics.md verbatim — Panel protocol plus its own critic section (the same pair its agent definition names) — and the full draft plan gathered in step 1; nothing else. They do not see each other's output.
Collect every subagent's Verdict format block.
Fix every BLOCK finding by invoking planner behavior per playbooks/planner.md — spawn a fresh aa-planner subagent with the model configured for the smart tier in .planning/CONFIG.md, or apply the fix inline in the main loop if already holding full planning context; inline is default. Only the critic(s) whose findings forced a structural change get re-run, and only once.
Present the remaining FLAG findings plus the fixed plan to the user; the user's decision is the gate.
If the market critic's verdict is KILL, present its evidence and recommend stopping instead of presenting the plan for approval. If the user agrees to stop, write .planning/epics/EPIC-NN/LEARNINGS.md from playbooks/templates/LEARNINGS.md explaining why, and stop.
Update .planning/STATE.md to record the outcome of the gate.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.