skills.rest
artisticmedic
artisticmedicCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

verify

Verify build outcomes by checking existence, wiring, and automated tests.

Updated Apr 11, 2026
Search Tags:#verification#spec compliance#build validation#tests#codebase inspection#evidence reporting#route wiring
One-click install
npx skills add https://github.com/artisticmedic/tim-gsd --skill verify-artisticmedic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/artisticmedic/tim-gsd/tree/main/skills/verify
Command: npx skills add https://github.com/artisticmedic/tim-gsd --skill verify-artisticmedic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It eliminates false confidence by verifying that what your spec claims is implemented—files, wiring, and runtime behavior—matches the actual codebase.

Core Features & Use Cases

  • Goal-backward verification: Works from outcomes (“must-be-true” claims) back to evidence in the repository.
  • Multi-level checks: Confirms artifacts exist, are wired into routes/components/entry points, and work via build/tests and basic runtime checks.
  • Evidence-based reporting: Produces a structured .planning/VERIFICATION.md report and lists failures with targeted fixes.
  • Remediation loop: Offers to apply fixes for failed items and then re-verify.
  • Standalone verification: Can run without a full /build pipeline by verifying user-described truths directly against the codebase.

Quick Start

Use verify to check a finished feature against its spec by running: “/verify .planning/SPEC.md”.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I verify that spec compliance matches the actual codebase after a build?▼

Spec compliance verification confirms that build outcomes defined in a spec actually exist, are wired into the codebase, and work via automated checks. It extracts must-be-true statements and classifies evidence into exists, wired, and works levels.

What is the best way to check if endpoints and routes are properly wired during iterative development?▼

Route wiring validation checks if build artifacts are connected into entry points and components. It applies three-level evidence classification to confirm required artifacts exist, are wired, and work via basic runtime checks and build tests.

How do I generate an evidence report for build validation failures?▼

Build validation generates a structured evidence table report in .planning/VERIFICATION.md. It lists failed items with targeted fixes and offers a remediation loop to apply fixes and re-verify the outcomes automatically.

Can I run standalone codebase inspection without a full build pipeline?▼

Standalone codebase inspection runs without a full build pipeline by verifying user-described truths directly against the repository. It requires spec-driven extraction of must-be-true statements to perform goal-backward verification.

When do I need to use evidence reporting for spec compliance?▼

Evidence reporting is needed when you want to eliminate false confidence that files, wiring, and runtime behavior match your spec. It produces structured documentation proving artifacts exist, are wired, and work as described.

Related Skills

Explore More Software Engineering Skills→
prepforeverythingprepforeverything
2

product-metrics-analysis

Define product outcome metrics with North Star, input, and leaf metrics.

Official
Advanced
mikopbxmikopbx
569

babel-compiler

Transpile ES6+ JavaScript to ES5 via Docker-based Babel compiler.

Official
Advanced
jaypatrickjaypatrick

develop-web-game

Automate HTML/JS web-game development with Playwright test loops.

Community
Intermediate
Chang-Shih-YungChang-Shih-Yung

health

Aggregate type checker, linter, and test results into a 0-10 composite score.

Community
Advanced