Panel Review
Review a Fallow design, plan, workflow, CLI surface, documentation architecture, or...
Install
npx skills add fallow-rs/fallow --skill panel-review -g -a claude-code -y- Repository
- fallow-rs/fallow5.3k
- Category
- Design
- Updated
- 3d ago
- License
- MIT
- Context cost
- Lightabout 259 tokens
- Runs scripts
- No, instructions only
What it does
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
- Read the controlling plan or specification first.
- Build one evidence package from current source, live behavior, and relevant public contracts.
- Select representative users plus specialists for accessibility, security, privacy, compatibility, operations, or agent runtimes as applicable.
- Ask reviewers for concrete blockers, concerns, follow-ups, and no-action decisions.
- Verify load-bearing claims against source before accepting them.
- 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.
- Synthesize consensus under:
- Fix before change
- Fix now
- Follow-up
- No action
- 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.
