panel-review

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

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. Synthesize consensus under:
   • Fix before change
   • Fix now
   • Follow-up
   • No action
7. 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.