plan-validator

Validate code changes against lkup-plan.json policies and output a JSON report.

Updated Feb 10, 2026

Search Tags:#code review #policy compliance #code validation #architecture enforcement #JSON output

Ready to run

npx skills add https://github.com/ammonfife/sakima.co --skill plan-validator-ammonfife

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-validator
Source: https://github.com/ammonfife/sakima.co/tree/main/.claude/skills/plan-validator
Command: npx skills add https://github.com/ammonfife/sakima.co --skill plan-validator-ammonfife

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The Skill ensures that proposed code changes adhere to predefined architecture policies, URL rules, schema constraints, and other guidelines.

Core Features & Use Cases

Policy Enforcement: Validates code changes against a set of predefined policies to ensure compliance.
URL and Schema Validation: Checks URL rules and schema constraints for accuracy and adherence.
Status Transition Validation: Ensures that status transitions of items are performed correctly with proper screenshots and claim checks.
Automated Testing: Produces structured JSON output and fails loudly on violations, serving as a mandatory gate for code changes.

Quick Start

Run the 'plan-validator' skill with the proposed change set to validate it against the 'lkup-plan.json' architecture.

Frequently Asked Questions about plan-validator

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

FAQPage Schema

How do I enforce architecture policy compliance on proposed code changes?▼

To enforce architecture policy compliance on proposed code changes, you validate them against a canonical JSON plan. This process performs pre-flight checks and outputs a structured JSON report detailing violations or a PASS status.

What is code change validation against schema constraints and URL rules?▼

Code change validation against schema constraints and URL rules is an automated pre-flight check that ensures proposed modifications adhere to predefined architectural policies. It produces a structured JSON report of violations or a PASS status.

Can I use a JSON plan to validate status transitions and screenshot proofing?▼

Yes, you can use a canonical JSON plan to validate status transitions and screenshot proofing. The validator performs checks against these rules and fails loudly with a structured JSON report if violations are found.

Does the code validation process output structured JSON reports for CI gates?▼

Yes, the code validation process outputs structured JSON reports for CI gates. It fails loudly on violations and produces a structured JSON report, serving as a mandatory gate for code changes.

What are the limitations of using a JSON plan validator for architecture enforcement?▼

A limitation of using a JSON plan validator for architecture enforcement is that it strictly requires a canonical lkup-plan.json file to function. Without this predefined plan file, the validator cannot perform pre-flight checks or output compliance reports.