verify

Verify built software against acceptance criteria with execution-based evidence.

Updated May 24, 2026
One-click install
npx skills add https://github.com/RCSnyder/lights-out-swe-plugin --skill verify-rcsnyder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/RCSnyder/lights-out-swe-plugin/tree/main/skills/verify
Command: npx skills add https://github.com/RCSnyder/lights-out-swe-plugin --skill verify-rcsnyder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents shipping broken or insecure software by verifying that the build actually satisfies the acceptance criteria, tests, and deployment readiness requirements.

Core Features & Use Cases

  • Acceptance-criteria verification: Reads scope, design, and readiness artifacts and validates each AC with concrete evidence.
  • Test quality auditing: Ensures tests are non-vacuous, meaningfully assert real properties, and preserve AC traceability.
  • Security and deployment checks: Searches for secret patterns and performs baseline security sanity checks while confirming deployment configuration exists and matches the target.
  • Optional performance/load validation: When criteria include latency/throughput requirements, validates behavior under concurrent load.

Quick Start

Ask the agent to run the Verify phase by checking tests, validating every AC-* with recorded command output, and performing the security and deployment readiness checks for your build.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I verify software acceptance criteria before a deployment pipeline promotes my build?

To verify software acceptance criteria, the build is tested and exercised against written specifications, validating each requirement with concrete evidence logs before gated pipeline deployment promotion.

What is acceptance criteria traceability and how does test quality auditing work?

Acceptance criteria traceability links test execution directly to requirements. Test quality auditing ensures tests are non-vacuous, meaningfully assert real properties, and preserve this traceability throughout the build verification process.

How do I run security auditing and deployment readiness checks for a gated pipeline?

Security auditing and deployment readiness checks search for secret patterns, perform baseline security sanity checks, and confirm deployment configuration exists and matches the target environment before pipeline promotion.

Can I validate load testing and concurrency constraints for web APIs and data pipelines?

Yes, you can validate load testing and concurrency constraints for web APIs, UIs, CLI, and data pipelines. When performance criteria exist, behavior is validated under concurrent load to ensure deployment readiness.

Does build verification work for cron-style pipelines and CLI applications?

Build verification works for cron-style pipelines, CLI applications, web APIs, and UIs. It requires skeptical evaluation and execution-based verification to prove correctness, security basics, and deployment readiness before promotion.

What is the best way to prove build correctness without shipping broken or insecure software?

The best way to prove build correctness is through skeptical evaluation, running non-trivial tests, validating every acceptance criterion with recorded command output, and executing security and deployment readiness checks.