From rpi
Validates implementation plans against requirements and design docs by mapping acceptance criteria coverage, checking architectural alignment, and flagging ambiguities or gaps. Use after plan creation.
npx claudepluginhub crouton-labs/crouton-kit --plugin rpiThis skill is limited to using the following tools:
**Input:** `$ARGUMENTS`
Implements Playwright E2E testing patterns: Page Object Model, test organization, configuration, reporters, artifacts, and CI/CD integration for stable suites.
Guides Next.js 16+ Turbopack for faster dev via incremental bundling, FS caching, and HMR; covers webpack comparison, bundle analysis, and production builds.
Discovers and evaluates Laravel packages via LaraPlugins.io MCP. Searches by keyword/feature, filters by health score, Laravel/PHP compatibility; fetches details, metrics, and version history.
Input: $ARGUMENTS
Parse input to extract requirements path, design path, and plan path. Expected format: {requirements-path} {design-path} {plan-path} or topic name (resolve from .claude/specs/{topic}/ and .claude/plans/).
Spawn a Task agent to review:
Task tool parameters:
subagent_type: general-purpose
model: sonnet
description: Review plan against requirements and design
prompt: |
Review plan against requirements and design.
Paths from input: $ARGUMENTS
- Requirements: `.claude/specs/{topic}/requirements.md`
- Design: `.claude/specs/{topic}/design.md`
- Plan: `.claude/plans/*.plan.md`
## Process
1. Read all three documents (requirements first, then design, then plan)
2. Extract every acceptance criterion from requirements
3. Extract every architectural decision from design
4. Map each acceptance criterion to plan coverage: covered, partial, or missing
5. Verify plan implements the design's architecture (not an alternative approach)
6. Check plan quality
**Threshold: Only flag issues that would block implementation or cause genuine confusion.**
### Quality Checks
- Ambiguous language → only if implementation would stall or go wrong
- Deferred decisions → only if missing info needed to start work
- Conditional branches → only if unresolved decisions (valid branching is fine)
- Unexplored complexity → only if it hides surprising work
- Design divergence → plan contradicts design's architecture without justification
## Output
If all covered and no issues: `PASS`
If issues exist:
1. Missing: [acceptance criterion from requirements not in plan]
2. Design mismatch: [plan diverges from design without justification]
3. Ambiguous: [unclear section that needs resolution]
Report the agent's findings to the user.