verify

Validate software implementation against a predefined plan using file and MCP memory checks.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/rodlc/claude-workshop-plugins --skill verify-rodlc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/rodlc/claude-workshop-plugins/tree/main/skills/verify
Command: npx skills add https://github.com/rodlc/claude-workshop-plugins --skill verify-rodlc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that the implemented work aligns with the defined plan, acting as a crucial go/no-go gate before finalizing a session.

Core Features & Use Cases

  • Automated Validation: Checks deliverables against expected outcomes defined in a plan file.
  • Decision Making: Automatically determines if the session can be auto-recap'd, requires plan fixes, or needs manual review.
  • Use Case: After implementing a new feature, run /verify to confirm all required files were created, modified correctly, and MCP memories were updated as specified in the project plan.

Quick Start

Run the verify skill to check the current implementation against the active plan.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I validate code implementation against a project plan?

To validate code implementation against a project plan, use an automated verification process to check deliverables like created and modified files. It automates go/no-go decisions for session wrap-ups by comparing actual files and MCP memories against expected outcomes.

What is automated plan adherence validation in software engineering?

Automated plan adherence validation is the process of checking implemented deliverables against a predefined project plan. It determines whether a development session can be finalized, requires plan corrections, or needs manual review.

How do I check if required files were created during a development session?

To check if required files were created or modified correctly during a session, perform validation using read operations and grep. This confirms that the actual file deliverables match the expected outcomes defined in your project plan.

Can I automate go/no-go decisions for session wrap-ups?

Yes, you can automate go/no-go decisions for session wrap-ups by validating software implementation against a predefined plan. The process identifies failures for plan correction or flags items for manual review before finalizing.

Do I need a plan file path to validate deliverables?

Yes, you need a plan file path provided through context to validate deliverables. The verification process requires this predefined plan context to check created files, modifications, and MCP memories against expected outcomes.