Stats
Actions
Tags
From reviewer
Review a spec, proposal, or design before implementation to catch gaps, risks, and ambiguities. Scans codebase for context before review. Supports iterative review+fix with --fix flag and parallel multi-angle review. Use when you want to validate specs before coding.
How this skill is triggered — by the user, by Claude, or both
Slash command
/reviewer:specThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Review feature specifications, proposals, designs, or task lists before implementation starts.
Review feature specifications, proposals, designs, or task lists before implementation starts.
Provide the paths to spec files or folders to review:
$spec docs/plans/auth-flow/
$spec proposal.md spec.md tasks.md
With iterative auto-fix:
$spec docs/plans/auth-flow/ --fix
$spec docs/plan/ --fix -n 5 --fix-all
$spec docs/plan/ --fix --parallel "scope,tasks"
Skip codebase exploration:
$spec docs/plan/ --no-explore
If no paths are given, ask which files to review.
--no-explore)--fix)Before either dispatch, the code-explorer agent scans the codebase for relevant context based on spec content. Pass --no-explore to skip this step.
Without --fix: use the companion spec-reviewer.md in this directory as the agent prompt.
With --fix: dispatch reviewer:spec-fix-orchestrator with parameters (paths, max_iterations, parallel, angles, fix_all, codebase_context, review-angles template content).
The agent will cd to the git root automatically. Provide it with:
npx claudepluginhub shdennlin/agent-plugins --plugin reviewerReviews specs, PRDs, requirements, and design docs for unrelated features, oversized scope, contradictions, feasibility issues, scope imbalance, omissions, ambiguity, security concerns, and git repo conflicts.
Reviews technical specifications using expert personas to identify gaps, risks, and missing considerations. Verifies claims against repositories, discusses resolutions, and applies updates.
Reviews spec.md files for completeness, clarity, implementability, testability, and structure. Identifies ambiguities, gaps, and missing sections before implementation.