opsx-verify

Verify implementation alignment with specs, tasks, and design artifacts.

Updated Jan 20, 2026
One-click install
npx skills add https://github.com/moogah/emacs --skill opsx-verify-moogah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opsx-verify
Source: https://github.com/moogah/emacs/tree/main/.claude/skills/opsx-verify
Command: npx skills add https://github.com/moogah/emacs --skill opsx-verify-moogah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that a change's implementation aligns with its specs, tasks, and design, ensuring completeness and coherence before archiving.

Core Features & Use Cases

  • Validate alignment of implementation with delta specs and change artifacts.
  • Assess task status, spec coverage, and design adherence to produce a structured verification report.
  • Generate actionable guidance (CRITICAL/WARNING/SUGGESTION) for remediation.

Quick Start

Run opsx-verify to validate the current change against its artifacts and generate a verification report.

Frequently Asked Questions about opsx-verify

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

FAQPage Schema
How do I verify that my code implementation matches the project specs and design artifacts?

To verify implementation matches specs and design artifacts, you need a tool that checks task completion, spec coverage, and pattern coherence, then outputs a structured verification report for archiving.

What is the best way to check if delta specs and task status are fully covered before archiving a change?

Checking delta specs and task status before archiving requires validating design adherence and tracing change artifacts against the implementation to produce actionable remediation guidance.

How do I validate task completion and spec coverage for a software change?

Validating task completion and spec coverage involves tracing the implementation against delta specs and change artifacts, testing alignment, and generating a structured verification report with actionable guidance.

Can I generate a code review report that checks design adherence and pattern coherence?

Yes, you can generate a code review report that checks design adherence and pattern coherence by assessing change artifacts, validating spec coverage, and outputting structured remediation guidance.

Why does my implementation verification fail to trace design decisions and change artifacts correctly?

Implementation verification fails to trace design decisions when the change's implementation does not fully align with its specs, tasks, and design artifacts, requiring a structured alignment check.

When do I need to run a structured verification report for software change artifacts?

You need to run a structured verification report for software change artifacts when you must validate task completion, spec coverage, and pattern coherence before archiving a change.