# Panel Review

Review a Fallow design, plan, workflow, CLI surface, documentation architecture, or...

- Repository: https://github.com/fallow-rs/fallow (5289 stars)
- Category: Design
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add fallow-rs/fallow --skill panel-review -g -a claude-code -y`
Codex: `npx skills add fallow-rs/fallow --skill panel-review -g -a codex -y`
Cursor: `npx skills add fallow-rs/fallow --skill panel-review -g -a cursor -y`
Gemini CLI: `npx skills add fallow-rs/fallow --skill panel-review -g -a gemini-cli -y`

## Description

Review a Fallow design, plan, workflow, CLI surface, documentation architecture, or user experience with representative end-user and domain-expert perspectives before implementation.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Panel review

1. Read the controlling plan or specification first.
2. Build one evidence package from current source, live behavior, and relevant
   public contracts.
3. Select representative users plus specialists for accessibility, security,
   privacy, compatibility, operations, or agent runtimes as applicable.
4. Ask reviewers for concrete blockers, concerns, follow-ups, and no-action
   decisions.
5. Verify load-bearing claims against source before accepting them.
6. Filter the findings first. Drop style preferences and "a different design
   would also work" unless the reviewer shows a concrete problem. Trace a call
   site before you accept a bug claim. Put each dropped finding under No
   action with one reason.
7. Synthesize consensus under:
   - Fix before change
   - Fix now
   - Follow-up
   - No action
8. Record approved decisions in the active `.plans/<task>.md`.

Do not expose private source text or internal review labels in public output.
Panel feedback is evidence, not authority over tested contracts.