validate-implementation

Inspect git diffs and codebase to validate implementation against the plan.

Updated Feb 7, 2026
One-click install
npx skills add https://github.com/loagma/LoagmaPMS --skill validate-implementation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-implementation
Source: https://github.com/loagma/LoagmaPMS/tree/main/.claude/skills/validate-implementation
Command: npx skills add https://github.com/loagma/LoagmaPMS --skill validate-implementation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate that implemented code and systems align with the plan by comparing diffs, staged changes, and the live codebase to prevent drift between proposal and delivery.

Core Features & Use Cases

  • Check git diffs of current changes and staged changes to verify what was implemented.
  • Inspect the actual codebase to confirm implementation accuracy beyond version control.
  • Update the plan document with completion status, identify gaps, and ensure all plan requirements are met.
  • Perform production-like testing guidelines, including sanitizing data and checking for dead-code and wiring gaps.

Quick Start

Review the plan, compare it to the codebase, and update the plan with statuses and fixes.

Frequently Asked Questions about validate-implementation

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

FAQPage Schema
How do I verify implemented code aligns with the original plan?

Verify code alignment by inspecting git diffs and staged changes against the plan. This process confirms implemented features match requirements, updates the plan with completion status, and identifies any gaps between proposal and delivery.

What's the best way to check git diffs for plan alignment?

Check git diffs by comparing current changes and staged changes against the plan requirements. This reveals implementation accuracy, detects drift between proposal and delivery, and highlights dead-code or wiring gaps needing fixes.

Can I update a plan document with completion status after reviewing code?

Yes, update the plan document with completion status after reviewing the codebase. This ensures all plan requirements are met, identifies gaps requiring fixes, and documents verification results for future reference.

How do I generate real-world tests using sanitized production data?

Generate real-world tests by applying production-like testing guidelines that sanitize production data. This validates implemented features end-to-end while protecting sensitive information during the testing process.

Does code validation include dead-code and wiring checks?

Yes, code validation includes dead-code and wiring checks to prevent drift. Inspecting the actual codebase beyond version control confirms implementation accuracy and identifies unused components or missing connections.

Why does my implemented code drift from the original plan?

Code drifts from the plan when implementation diverges from requirements without tracking. Comparing git diffs and staged changes against the plan document identifies these gaps, allowing you to fix discrepancies and update completion status.