skills.rest
leonletto
leonlettoCOMMUNITY
Explore all skills by this author →
Website𝕏@leonlettoGitHub

verify-against-plan

Verify plan files and implementation diffs to produce structured findings.

28|5|Updated Feb 3, 2026
Search Tags:#diff#plan#verify#code-review#report#acceptance-criteria#findings
One-click install
npx skills add https://github.com/leonletto/thrum --skill verify-against-plan-leonletto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-against-plan
Source: https://github.com/leonletto/thrum/tree/main/opencode-plugin/assets/skills/verify-against-plan
Command: npx skills add https://github.com/leonletto/thrum --skill verify-against-plan-leonletto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams ensure that code implementations conform to a written plan or design spec by performing a second-pass review that surfaces missing scope, unmet acceptance criteria, and deviations.

Core Features & Use Cases

  • Performs pre-flight checks to verify the plan/spec file exists, is readable, and the implementation scope yields a non-empty diff.
  • Extracts and reports findings in a standardized format with BLOCKING, IMPORTANT, and MINOR severities for plan-reference and implementation-state gaps.
  • Supports structured output that can be ingested by coordinators during dual-review batches and integrated into CI/code-review workflows.

Quick Start

Run the verify-against-plan workflow with a plan file path and an implementation scope to generate a Findings report.

Frequently Asked Questions about verify-against-plan

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

FAQPage Schema
How do I verify code matches a design spec or plan file?▼

To verify code matches a plan, you parse the plan's file structure and acceptance criteria, compare them against the implementation diff, and generate a structured report of deviations and missing scope.

What is a structured findings report for code review?▼

A structured findings report categorizes implementation gaps and plan deviations by severity levels—BLOCKING, IMPORTANT, and MINOR—to help teams prioritize unmet acceptance criteria and code review issues.

Can I integrate plan verification into CI and code-review workflows?▼

Yes, plan verification supports structured output that can be ingested by coordinators during dual-review batches and integrated directly into CI and code-review workflows to automate conformance checks.

How do I check if an implementation diff meets acceptance criteria?▼

You check if an implementation diff meets acceptance criteria by resolving the implementation scope against the plan, parsing the test plan anchors, and surfacing any unmet criteria as structured findings.

Why does plan verification fail when the design spec is empty?▼

Plan verification fails because pre-flight checks confirm the plan or spec file is accessible and non-empty, and the implementation scope resolves to a non-empty diff before parsing anchors to produce findings.

Related Skills

Explore More Software Engineering Skills→
jacob-balslevjacob-balslev
1

with-grounding

Validate v6 codebase-scoped skills for grounding fields and non-empty keywords.

Community
Basic
BoraPerusicBoraPerusic

code-review-excellence

Identify and document prioritized issues in pull requests with severity ratings.

Community
Advanced
nalthoffnalthoff

speckit-analyze

Analyze spec.md, plan.md, and tasks.md for inconsistencies and gaps.

Community
Advanced
xiduzoxiduzo
7

wtf.pr-review

Compare pull request diffs against linked Task specs to identify spec drift.

Community
Advanced