technical-review

Verify plan task implementation, tests, and quality against acceptance criteria.

27|1|Updated Nov 23, 2025

Search Tags:#code quality #pull request #specification #acceptance criteria #review #quality gate #plan verification

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Technical Review skill provides a rigorous evaluation of implemented work against the original plan, acceptance criteria, and quality standards, helping ensure code changes are sound and production-ready before merging.

Core Features & Use Cases

Comprehensive plan verification: checks every plan task, acceptance criterion, and associated tests for completeness.
Structured feedback: outputs clear guidance such as approve, request changes, or comments with rationale.
Standalone or sequential use: can review finished implementations or be invoked as a contract entry to validate work against a plan.

Quick Start

Provide the latest plan and, if available, the specification to the review skill and trigger a task-based assessment to generate actionable feedback.

Frequently Asked Questions about technical-review

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

FAQPage Schema

How do I verify implementation against acceptance criteria before a pull request?▼

To verify implementation against acceptance criteria before a pull request, you trigger a task-based assessment using the latest plan and optional specification to generate actionable, structured feedback.

What is the best way to check if every plan task is implemented and tested correctly?▼

Checking if every plan task is implemented and tested correctly requires a comprehensive plan verification process that evaluates implementation scope, tests, and code quality to produce structured approve or request changes guidance.

Does technical review work without a full specification document?▼

Technical review does work without a full specification document, as it primarily relies on the latest plan to verify implementation scope and code quality, using the optional specification to enhance the assessment.

Can I use plan verification as a standalone contract entry to validate finished work?▼

You can use plan verification as a standalone contract entry to validate finished work, or sequentially after implementation, to rigorously assess code changes against defined plans and quality standards.

What kind of structured feedback should I expect from a quality gate review?▼

From a quality gate review, you should expect structured feedback such as clear guidance to approve, request changes, or provide comments with rationale based on the evaluation of acceptance criteria and code quality.

When should I not use automated code quality assessment for merging?▼

You should not use automated code quality assessment when a defined plan or task list is absent, because the review mechanism relies on comparing implemented work against original plan tasks and acceptance criteria to generate feedback.