start-review

Discover existing plans and validate implementations before handing off to technical-review.

27|1|Updated Nov 23, 2025

Search Tags:#workflow #planning #validation #review #handoff #software

Ready to run

npx skills add https://github.com/leeovery/claude-technical-workflows --skill start-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: start-review
Source: https://github.com/leeovery/claude-technical-workflows/tree/main/skills/start-review
Command: npx skills add https://github.com/leeovery/claude-technical-workflows --skill start-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you start a formal review session by discovering available plans and validating their implementation, ensuring alignment between planned work and delivered code.

Core Features & Use Cases

Discovery-driven review: Locates existing plans and checks that implementations exist before initiating a technical review.
Validation & routing: Verifies the scope and readiness, then routes to the dedicated technical-review skill for execution.
Use Case: A team completes a planning phase and wants a quick, documented validation pass against the plan, before merging.

Quick Start

Use /start-review to begin a review session for the active plan and implementation. The skill will discover plans, verify availability, and hand off to the technical-review skill.

Frequently Asked Questions about start-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I start a formal code review for a completed software plan?▼

A formal code review begins by discovering your project's existing plans, verifying the code implementation is ready, and routing the validated scope to a technical review skill for execution.

What is plan-based code validation and how does it work?▼

Plan-based code validation locates existing software plans and verifies the delivered code against them, ensuring alignment between planned work and implementation before handing off to a technical review.

How do I verify implementation readiness before merging code?▼

You verify implementation readiness by running a discovery-driven review workflow that checks for available project plans and validates that the corresponding code implementations exist before routing to a technical review.

Can I use this code review workflow without a pre-existing plan?▼

This code review workflow requires an existing project plan to discover, as it validates the implementation against the planned scope and verifies readiness before routing to the technical review execution.

Does the review workflow execute the technical validation itself?▼

The review workflow does not execute the technical validation itself; it handles plan discovery and implementation validation, then hands off to a dedicated technical-review skill to execute the formal validation.