phased-review

Validate technical implementation plans against codebase patterns and architectural invariants.

1|Updated Apr 9, 2026

Search Tags:#architecture #quality assurance #code review #refactoring #verification #technical planning

Ready to run

npx skills add https://github.com/hadi-technology/phased-workflow --skill phased-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: phased-review
Source: https://github.com/hadi-technology/phased-workflow/tree/main/skills/phased-review
Command: npx skills add https://github.com/hadi-technology/phased-workflow --skill phased-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents implementation drift and architectural errors by rigorously verifying proposed technical plans against the actual state of the codebase before any code is written.

Core Features & Use Cases

Evidence-Based Review: Validates plan claims against live source code, including numeric constants, type constraints, and interface contracts.
Risk-Scaled Analysis: Employs specialized lenses (verifier, adversary, domain) to identify blast radius, security vulnerabilities, and logic gaps.
Use Case: Use this before starting a complex refactor to ensure the plan's assumptions about existing patterns, dependencies, and test coverage are accurate, preventing costly mid-implementation re-planning.

Quick Start

Trigger the phased review process by asking the assistant to review the implementation plan located at the specified file path.

Frequently Asked Questions about phased-review

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

FAQPage Schema

How do I verify an implementation plan against an existing codebase?▼

To verify an implementation plan against an existing codebase, cross-reference proposed changes with live source code patterns, type definitions, and architectural invariants. This validation process ensures plan readiness and identifies blast radius before execution.

What is codebase architecture validation and when do I need it?▼

Codebase architecture validation is the process of rigorously checking proposed technical plans against actual source code. You need it before starting complex refactoring to prevent implementation drift and ensure assumptions about dependencies and test coverage are accurate.

Can I check interface contracts and type definitions before refactoring code?▼

Yes, you can check interface contracts and type definitions before refactoring by performing deep source code analysis. This verifies numeric constants and security-sensitive logic, ensuring proposed changes comply with strict Definition of Done requirements.

What is the best way to identify blast radius for a technical plan?▼

The best way to identify blast radius for a technical plan is employing risk-scaled analysis with specialized lenses like adversary and domain verification. This exposes security vulnerabilities and logic gaps by validating claims against live source code.

Why does implementation drift occur and how can multiple review rounds prevent it?▼

Implementation drift occurs when technical plan assumptions about existing patterns are inaccurate. Multiple review rounds prevent it by continuously enforcing strict DoD compliance and cross-referencing proposed changes across specialized verification lenses before execution.