verify

Audit code changes against SSpec tests and architecture documentation for production readiness.

1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/ormastes/simple --skill verify-ormastes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/ormastes/simple/tree/main/.agents/skills/verify
Command: npx skills add https://github.com/ormastes/simple --skill verify-ormastes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Production readiness verification automates auditing SSpec tests, implementation completeness, and architecture/design doc freshness to ensure releases are robust and well-documented.

Core Features & Use Cases

  • Audits code changes against SSpec tests to ensure all assertions have real checks and no placeholder stubs
  • Verifies requirement coverage, NFR targets, and currency of architecture/design documentation across modules
  • Use Case: Before release, run the verification to confirm readiness, traceability, and documentation accuracy

Quick Start

Run verify on the current changes to perform production readiness checks.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I verify production readiness before a release?

Production readiness verification audits code changes against SSpec tests to ensure all assertions have real checks, confirms requirement coverage, validates NFR targets, and checks architecture documentation freshness. Run automated verification on current changes to confirm traceability and documentation accuracy before release.

What is production readiness verification in software engineering?

Production readiness verification is an automated audit that evaluates code changes against SSpec tests, implementation completeness, and architecture documentation. It ensures every requirement is tested, non-functional requirements are met, and design docs are current before a robust and well-documented release.

How do I check requirement traceability and test coverage across modules?

Check requirement traceability and test coverage by auditing feature changes across modules to verify each requirement (REQ) is tested and NFR targets are met. Automated verification enforces traceability and surfaces failures for remediation before release.

Does automated production readiness verification detect placeholder test stubs?

Yes, production readiness verification detects placeholder test stubs by auditing SSpec tests to ensure all assertions have real checks. It audits code changes to verify implementation completeness and surfaces failures for remediation before release.

How do I ensure architecture documentation is current before deployment?

Ensure architecture documentation is current by running automated production readiness verification. It audits code changes to verify architecture and design doc freshness across modules, enforcing traceability and surfacing failures for remediation before release.

What happens when production readiness verification finds a failure?

When production readiness verification finds a failure, it surfaces the failure for remediation before release. The automated audit identifies missing SSpec test coverage, unmet NFR targets, or outdated architecture docs to ensure robust and well-documented releases.