CtrlK
BlogDocsLog inGet started
Tessl Logo

panel-review

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

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/panel-review/SKILL.md
SKILL.md
Quality
Evals
Security

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.

Repository
fallow-rs/fallow
Path

.claude/skills/panel-review/SKILL.md

Commit

7e1e075

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.

Claim skill