What kind of feedback does the skill provide?

If issues are found, it provides a numbered list identifying missing requirements, ambiguous phrasing, or unexplored complexities that need resolution.

How does this skill compare specs and plans?

It parses your .spec.md and .plan.md files to systematically map behavioral requirements to specific plan sections, checking for full coverage and consistency.

Why does it flag words like 'possibly' or 'might'?

To ensure implementation plans are concrete and deterministic. Eliminating 'might' or 'possibly' prevents bugs caused by unaddressed edge cases or undecided logic.

Can I use this for non-markdown files?

The skill is specifically designed to work with standard .claude/specs/*.spec.md and .claude/plans/*.plan.md file structures used in Claude Code workflows.

Review Plan Validator

Name: Review Plan Validator
Author: CaptainCrouton89

byCaptainCrouton89

•

Productivity & Workflow

Validates implementation plans against technical specifications to ensure complete requirement coverage and eliminate ambiguity.

About

The Review Plan skill automates the critical step of cross-referencing implementation plans with technical specifications. By systematically parsing requirements, acceptance criteria, and constraints from spec files, it identifies missing features, ambiguous language, or deferred decisions in your plan. This ensures that before a single line of code is written, the implementation strategy is solid, complete, and aligned with project goals, significantly reducing the risk of rework or missed edge cases.

Key Features

24 GitHub stars
Standardized PASS/FAIL output with actionable, numbered feedback
Identification of missing acceptance criteria and constraints
Automated requirement mapping between specs and implementation plans
Detection of ambiguous language and non-committal phrasing
Enforcement of concrete decision-making by flagging TBDs or deferred tasks

Use Cases

Pre-implementation verification to ensure all spec requirements are addressed
Identifying 'plan drift' where implementation steps deviate from initial specifications
Quality assurance for complex coding tasks involving multiple behavioral dependencies

About

Key Features

24 GitHub stars
Standardized PASS/FAIL output with actionable, numbered feedback
Identification of missing acceptance criteria and constraints
Automated requirement mapping between specs and implementation plans
Detection of ambiguous language and non-committal phrasing
Enforcement of concrete decision-making by flagging TBDs or deferred tasks

Use Cases

Pre-implementation verification to ensure all spec requirements are addressed
Identifying 'plan drift' where implementation steps deviate from initial specifications
Quality assurance for complex coding tasks involving multiple behavioral dependencies