Why does it only report P1 and P2 findings?

The skill focuses on high-impact issues to ensure the review remains actionable and identifies fundamental flaws that could jeopardize the project.

What dimensions does this skill use for evaluation?

The skill evaluates plans based on five weighted dimensions: Completeness (25%), Correctness (25%), Feasibility (20%), Risk (15%), and Clarity (15%).

How do I format the output for a plan review?

The skill automatically generates a verdict, followed by a findings section including the dimension, issue description, and a specific recommendation for a fix.

What do the different verdicts mean?

BLOCK indicates critical P1 flaws that will cause failure, REVISE indicates major P2 issues that need addressing, and APPROVE means the plan is technically sound.

Implementation Plan Reviewer

Name: Implementation Plan Reviewer
Author: tenzir

bytenzir

•

Productivity & Workflow

Evaluates implementation plans using a weighted framework to identify critical flaws and technical risks before development begins.

About

The Implementation Plan Reviewer skill provides a structured methodology for auditing technical proposals and roadmaps. By scoring plans across five essential dimensions—Completeness, Correctness, Feasibility, Risk, and Clarity—it ensures that Claude provides objective, high-stakes feedback. This skill is specifically designed for developers and architects who need to validate complex implementation steps, identify P1/P2 issues early, and receive a clear verdict on whether a project is ready to proceed or requires immediate revision.

Key Features

Severity-based issue reporting focused on P1 and P2 findings
Weighted evaluation framework covering five core technical dimensions
Standardized verdict system (APPROVE, REVISE, or BLOCK)
Risk assessment for security, performance, and scalability
Specific recommendation fields for every identified finding
3 GitHub stars

Use Cases

Validating a complex database migration plan to prevent data loss
Reviewing refactoring strategies to identify potential regressions early
Auditing a technical design document before starting a new microservice

About

Key Features

Severity-based issue reporting focused on P1 and P2 findings
Weighted evaluation framework covering five core technical dimensions
Standardized verdict system (APPROVE, REVISE, or BLOCK)
Risk assessment for security, performance, and scalability
Specific recommendation fields for every identified finding
3 GitHub stars

Use Cases

Validating a complex database migration plan to prevent data loss
Reviewing refactoring strategies to identify potential regressions early
Auditing a technical design document before starting a new microservice