speckit-verify

Detect constitution violations in specs, plans, or code and report PASS/FAIL with fixes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifying that specs, plans, and implementations comply with the project constitution to prevent quality gate violations and rework.

Core Features & Use Cases

  • Extract and apply constitution rules to current work artifacts (specs, plans, code).
  • Produce a structured compliance report with PASS/FAIL status and actionable fixes.
  • Integrate with the Speckit pipeline: run before PR merge and surface compliance outcomes.

Quick Start

Invoke speckit-verify with the relevant artifact to trigger the compliance check.

Frequently Asked Questions about speckit-verify

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

FAQPage Schema
How do I check if my code and specs comply with project constitution rules?

Constitution compliance checks involve extracting project rules and evaluating them against your specs, plans, or code. This process identifies violations and produces a structured report with a PASS or FAIL status and actionable fixes to prevent quality gate violations.

How do I automate constitution checks before a PR merge?

You can automate constitution checks before a PR merge by integrating a verification pipeline that determines the target from PR context. It evaluates artifacts against rules and surfaces the compliance outcome directly in the pipeline status to block non-compliant merges.

What is a constitution violation in software specifications and code?

A constitution violation in software specifications and code occurs when an artifact deviates from established project rules. Detecting these violations involves analyzing specs, plans, or code against the constitution to identify security, integrity, or quality compliance issues before pipeline integration.

How do I detect security or integrity concerns in prompts and code?

Detecting security or integrity concerns in prompts and code requires analyzing the artifacts for potential data exposure or compliance issues. The process evaluates the content against project rules and integrates findings into a structured compliance report with pipeline status.

Does pipeline compliance verification work without external dependencies?

Yes, pipeline compliance verification can work without external dependencies. The verification logic determines the target from user input or PR context, applies the constitution rules, and returns a structured compliance report with recommended fixes independently.

What is the best way to report compliance failures in a software pipeline?

The best way to report compliance failures in a software pipeline is to generate a structured compliance report. This report should include a clear PASS or FAIL status, specific constitution violations found, and recommended fixes to integrate with the pipeline status.