This skill should be used when the user asks to "review the plan", "check the execution plan", "validate this plan", "is this plan good", or automatically after the planner agent creates an execution plan. Validates plans for completeness, clarity, measurability, and proper acceptance criteria before execution begins.
Validates execution plans for completeness, measurable criteria, and proper critic assignments before coding begins.
/plugin marketplace add reggiechan74/cc-plugins/plugin install code-coherence@cc-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Review and validate execution plans before code changes begin, ensuring plans have clear acceptance criteria, appropriate critic assignments, and realistic scope.
✓ Scope defined: Files, operations, and boundaries clear ✓ Success criteria present: At least 3 specific, measurable criteria ✓ Critic assignment: Each criterion mapped to responsible critic ✓ Retry budget set: Escalation path defined ✓ Cost estimate included: Token overhead calculated
Acceptance criteria must be:
Domain-specific patterns:
EXECUTION PLAN ✓
Scope: Refactor auth to JWT ✓
Files: src/auth/*.ts ✓
SUCCESS CRITERIA: ✓
✓ All 18 existing tests pass (Code Critic validates)
✓ No OWASP Top 10 violations (Security Critic validates)
✓ Token storage uses httpOnly cookies (Security Critic validates)
✓ Token refresh handles 401 (Code Critic validates)
✓ Coverage maintains 85%+ (Code Critic validates)
Critics: code, security ✓
Budget: 6 iterations ✓
Cost: +40% tokens ($0.15) ✓
EXECUTION PLAN ❌
Scope: Make the code better ❌ TOO VAGUE
Files: Not specified ❌ MISSING
SUCCESS CRITERIA: ❌
- Code should be high quality ❌ NOT MEASURABLE
- No bugs ❌ NOT SPECIFIC
- Fast performance ❌ NO THRESHOLD
Critics: None assigned ❌
Budget: Not set ❌
Required fixes:
Plans automatically reviewed when autoVerify: true in settings.
For manual review, invoke explicitly after planning phase.
references/acceptance-criteria-patterns.md - Domain-specific criteria templatesreferences/plan-examples.md - Good and bad plan examplesCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.