verification-checklist

Generate a prioritized markdown verification checklist from specification documents and code changes.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/yamk12nfu/claude-skills --skill verification-checklist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-checklist
Source: https://github.com/yamk12nfu/claude-skills/tree/main/verification-checklist
Command: npx skills add https://github.com/yamk12nfu/claude-skills --skill verification-checklist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Teams need a reliable way to ensure that AI-generated implementations match the original specifications, identifying missing requirements, concerns, and edge cases before release.

Core Features & Use Cases

  • Specification Input: Accepts spec files from various sources (Markdown, Google Docs, Notion, Figma, etc.).
  • Code Scope Definition: Handles explicit file lists, commit ranges, or branch diffs.
  • Automated Analysis: Detects coverage gaps, potential concerns, and edge cases based on objective observations.
  • Prioritized Checklist: Generates a markdown checklist with risk levels, references to spec and code, and actionable verification steps.
  • Use Case: A product team can quickly produce a verification checklist for a new feature by providing the spec URL and the relevant code diff.

Quick Start

Ask the verification-checklist skill to create a checklist for the spec at https://example.com/spec.md and the code changes in src/.

Frequently Asked Questions about verification-checklist

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

FAQPage Schema
How do I generate a verification checklist from a spec and code changes?

Generate a verification checklist by providing a specification document URL and the relevant code diff or file list. The skill analyzes the inputs to output a markdown checklist with prioritized risk levels and references.

What's the best way to verify AI-generated code matches the original spec?

To verify AI-generated code against a spec, use an automated analysis tool to compare specification documents with codebases, extracting test items, edge cases, and manual verification points.

Can I use commit ranges or branch diffs to define the code scope for test generation?

Yes, you can define the code scope using explicit file lists, commit ranges, or branch diffs. The skill analyzes these code changes against the specification to identify missing requirements.

How does spec-to-code analysis handle edge cases and missing requirements?

Spec-to-code analysis detects coverage gaps, potential concerns, and edge cases based on objective observations. It outputs a markdown checklist with risk levels, references to spec and code, and actionable verification steps.

Does the verification checklist output support manual QA testing points?

Yes, the generated markdown checklist includes manual verification points alongside automated test items. It provides actionable verification steps with prioritized risk levels and references to the specification and code.