review-code-plan-satisfaction

Review implementation fidelity against PLAN.md and AMENDMENTS.md and emit PS# findings.

2|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/siarhei-belavus/agent-public --skill review-code-plan-satisfaction-siarhei-belavus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-code-plan-satisfaction
Source: https://github.com/siarhei-belavus/agent-public/tree/main/skills/atelier-workflow/review-code-plan-satisfaction
Command: npx skills add https://github.com/siarhei-belavus/agent-public --skill review-code-plan-satisfaction-siarhei-belavus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often drift from the approved plan, skip required amendments, or claim validation that was never actually run. This Skill performs a focused Phase 1 review that verifies whether an implementation matches PLAN.md and AMENDMENTS.md and whether the claimed behavior is genuinely proved. ## Core Features & Use Cases - Plan-Fidelity Review: Compares the exact implementation commit against PLAN.md and AMENDMENTS.md, flagging silent deviations, missing amendments, and unapproved design changes. - Validation Verification: Runs the smallest relevant tests, records what was actually executed, and flags weak tests that would pass even if the bug remained. - Structured Findings Output: Emits severity-ordered PS# findings into PLAN_SATISFACTION_REVIEW.md and updates CODE_REVIEW.md with a compliance verdict and Phase 2 handoff note. - Use Case: After a developer finishes a planned change, run this review to confirm the commit matches the approved plan, catch unauthorized backward-compatibility shims, and produce a compliant/non_compliant verdict before maintainability review begins. ## Quick Start Review the implementation commit against PLAN.md and AMENDMENTS.md in the current task packet and write the PS# findings to PLAN_SATISFACTION_REVIEW.md.

Frequently Asked Questions about review-code-plan-satisfaction

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

FAQPage Schema
How do I review whether code matches an approved plan?▼

Compare the exact implementation commit against PLAN.md and AMENDMENTS.md rather than the desired outcome. Flag silent deviations, missing amendments, and design changes made without approval, then record findings as severity-ordered PS# items.

How to verify claimed test validation actually proves a change?▼

Run the smallest relevant tests yourself and record what was actually executed. Treat a test as a finding if it would still pass when the bug remains, and prefer one strong targeted test over a broad noisy suite.

What should a code review do when the workspace is dirty?▼

Stop and ask which commit is the review target instead of guessing from a floating workspace. If drift exists beyond the named commit, review the named commit and call out the drift explicitly so the lead can re-anchor.

When is unapproved backward-compatibility code a review finding?▼

Unapproved compatibility shims are non-compliant findings, not harmless implementation detail. If the change touches a real external boundary and the packet never resolved whether compatibility was required, the handoff fails pending explicit human clarification.

What are the limitations of a plan-satisfaction review?▼

It deliberately excludes deep maintainability, evolvability, and anti-slop analysis, which belong to a separate Phase 2 review. It only reports actionable findings tied to correctness, compliance, or confidence in the claimed behavior.