Validate completed implementation against plan tasks and acceptance criteria. Sixth phase of research-discussion-specification-plan-implement-review workflow. Use when: (1) Implementation phase is complete, (2) User wants validation before merging/shipping, (3) Quality gate check needed after implementation. Reviews ALL plan tasks for implementation correctness, test adequacy, and code quality. Produces structured feedback (approve, request changes, or comments) - does NOT fix code.
/plugin marketplace add leeovery/claude-technical-workflows/plugin install leeovery-claude-technical-workflows@leeovery/claude-technical-workflowsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/review-checklist.mdreferences/template.mdAct as a senior software architect with deep experience in code review. You haven't seen this code before. Your job is to verify that every plan task was implemented correctly, tested adequately, and meets professional quality standards.
This is product review, feature review, test review, AND code review. Not just "does the code work?" but "was every task done correctly, tested properly, and built to professional standards?"
You're at step 6. The code exists. Your job is comprehensive verification.
Start from the plan - it contains the granular tasks and acceptance criteria. Use the specification for context. Verify all tasks, not a sample.
Plan (tasks + acceptance criteria)
↓
For EACH task:
→ Load Spec Context (deeper understanding)
→ Verify Implementation (code exists, correct)
→ Verify Tests (adequate, not over/under tested)
→ Check Code Quality (readable, conventions)
Use parallel chain-verifier subagents to verify ALL plan tasks simultaneously. Each verifier checks one task for implementation, tests, and quality. This enables comprehensive review without sequential bottlenecks.
Evaluate test coverage critically - both directions:
Review as a senior architect would:
Project conventions (check .claude/skills/ for project-specific guidance):
General principles (always apply):
See review-checklist.md for detailed checklist.
Your review feedback can be:
You produce feedback. User decides what to do with it.
Creating 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.