Critique SPEC.md, PLAN.md, and source files with persona-based lenses.
npx skills add https://github.com/smp4/claude-skills --skill review-smp4
Please help me install this Agent Skill. Skill: review Source: https://github.com/smp4/claude-skills/tree/main/dot_claude/skills/review Command: npx skills add https://github.com/smp4/claude-skills --skill review-smp4
This Skill ensures that SPEC.md, PLAN.md, and source files receive objective persona-driven critiques that overcome confirmation bias and clarify actionable next steps.
Invoke the review skill with /review dev-docs/auth/PLAN.md --lens farley to get a verification-focused critique.
High-intent search queries and answers about installing and using this skill.
To run a persona-based code review, invoke the review skill targeting a directory containing SPEC.md and PLAN.md to surface alignment issues and domain language drift. This applies specific persona lenses like Beck or Farley to frame actionable findings.
Persona lens heuristic validation is a critique mechanism that checks SPEC.md files for missing acceptance criteria and misaligned domain vocabulary. It proposes lenses lazily and mandates specific personas like Farley for code to ensure verification and safety.
To check SPEC.md and PLAN.md alignment, run a review on the feature directory after generating your plan and tasks. This process validates requirement structures and flags mis-traced requirements to catch issues before implementation or release.
The review skill works with both planning documents and source code files. It delivers persona-driven critiques for SPEC.md, PLAN.md, and implementation files, mandating the Farley persona specifically for code to highlight verification concerns.
Yes, you can target a specific persona lens when reviewing a PLAN.md file by passing the lens argument. Invoking the review skill with a specific lens like Farley ensures the critique focuses heavily on verification, simplicity, and safety concerns.
The best way to overcome confirmation bias during plan reviews is applying objective persona-driven critiques. By using distinct personas such as Beck, Farley, and Feathers, the review process surfaces simplicity and verification issues that clarify actionable next steps.
datamonsterrGenerate Mermaid component, system design, and architecture diagrams from Speck Kit planning artifacts.
cagdotinInterview users to resolve plan ambiguities against repository language and documented decisions, updating CONTEXT.md, CONTEXT-MAP.md, and ADRs inline.
MRenAIAgentGenerate design artifacts and roadmaps from feature specs.
ddobrinIdentify ambiguity and unverifiable acceptance criteria in software specifications via remote skeptic reviews.
