05-verify-tech

Verify technical plans by classifying risks and checking consistency with product plans.

1|Updated May 31, 2026
One-click install
npx skills add https://github.com/joseph-c-mcguire/spec-driven --skill 05-verify-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 05-verify-tech
Source: https://github.com/joseph-c-mcguire/spec-driven/tree/main/.cursor/skills/05-verify-tech
Command: npx skills add https://github.com/joseph-c-mcguire/spec-driven --skill 05-verify-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pypdf, pdfplumber, pdf2image, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the verification of technical plan documents by breaking them down into provable statements, classifying risks, and presenting medium/low confidence statements for review, ensuring technical plan consistency with product requirements.

Core Features & Use Cases

  • Technical Plan Verification: Breaks technical plans into provable statements for verification.
  • Risk Classification: Classifies each statement's risk level.
  • Consistency Checking: Checks for internal and product plan consistency.
  • Interactive Review: Presents medium/low confidence statements for review.
  • Use Case: After completing the technical plan, use this Skill to automatically verify the plan and ensure it aligns with the product requirements.

Quick Start

Use the 05-verify-tech skill to review and verify the technical plan document 'execution-plan.md'.

Frequently Asked Questions about 05-verify-tech

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

FAQPage Schema
How do I automate technical plan verification and risk assessment?

Automate technical plan verification by breaking plans into provable statements, classifying risks, and checking consistency with product requirements. This Skill executes Python scripts to process execution-plan.md and product plan documents, outputting classified risks and consistency reports.

What is the process for breaking technical plans into provable statements?

Breaking technical plans into provable statements involves decomposing execution-plan.md documents into discrete, testable assertions. The Skill then classifies each statement's risk level and flags medium to low confidence items for interactive review.

Do I need PDF processing dependencies to check technical plan consistency?

Yes, consistency checking requires PDF processing dependencies including pypdf, pdfplumber, and pdf2image. These libraries enable the Skill to extract text and data from technical plan and product plan PDF documents for automated verification.

How do I check if my technical plan aligns with product requirements?

Check technical plan alignment by running the consistency checking scripts against product plan documents. The Skill compares provable statements extracted from execution-plan.md against product requirements to identify internal inconsistencies and misalignments.

Can I use Python scripts to classify risks in technical plan documents?

Yes, you can use Python scripts to classify risks in technical plan documents. The Skill executes classification scripts that evaluate each provable statement's risk level, presenting medium and low confidence statements for interactive review.

What are the limitations of automated technical plan verification?

Automated technical plan verification requires properly formatted execution-plan.md and product plan documents to function. While it automates statement classification and consistency checking, medium and low confidence statements still require manual interactive review to validate findings.