skills.rest
nullmastermind
nullmastermindCOMMUNITY
Explore all skills by this author →
Website𝕏@nullmastermindGitHub

verify

Verify implementation against OpenSpec change artifacts using the osf-verify subagent.

9|9|Updated Mar 24, 2026
Search Tags:#validation#implementation#verify#code-review#change-artifacts#release-readiness#osf-verify
One-click install
npx skills add https://github.com/nullmastermind/viber-router --skill verify-nullmastermind
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/nullmastermind/viber-router/tree/main/.claude/skills/verify
Command: npx skills add https://github.com/nullmastermind/viber-router --skill verify-nullmastermind

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill verifies that an implementation matches the intended change artifacts so teams can confidently archive or release work without hidden gaps or inconsistencies.

Core Features & Use Cases

  • Context-aware verification: Collects the OpenSpec change name if available or accepts a brief summary of the implemented changes and expected behavior.
  • Adaptive input handling: Accepts explicit user arguments, a prior spec reference, or an implementation summary to prepare a verification briefing.
  • Subagent-driven checks: Briefs the user and launches a verification subagent configured with subagent_type osf-verify to run automated validations for release readiness and code-review sign-off.

Quick Start

Verify that the recent implementation matches the change artifacts named "Add user profiles" and report any missing or inconsistent items.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I verify implementation matches change artifacts before release?▼

To verify implementation against change artifacts, provide an OpenSpec change name or implementation summary to launch a subagent that checks delivered work against specifications for release readiness.

What is automated release readiness validation for software specifications?▼

Release readiness validation is the process of confirming an implementation matches change artifacts, ensuring delivered work has no hidden gaps or inconsistencies before archiving or releasing.

Can I verify a bug fix without an OpenSpec change name?▼

Yes, you can verify a bug fix by providing a concise implementation summary of the changes and expected behavior instead of an OpenSpec change name to prepare the verification briefing.

How do I validate feature implementations for code-review sign-off?▼

Validate feature implementations by passing the change name or summary to the verification subagent, which runs automated checks to confirm specifications are met for code-review sign-off.

Does the verification process work with specification workflows?▼

Yes, the verification process works with software development and specification workflows by collecting context from OpenSpec changes or summaries to validate feature implementations and bug-fix confirmations.

What inputs do I need to start implementation verification?▼

Implementation verification requires either an explicit OpenSpec change name, a prior spec reference, or a concise implementation summary to collect context and prepare the verification briefing.

Related Skills

Explore More Software Engineering Skills→
tuliopc23tuliopc23

openspec-ff-change

Automates creation of OpenSpec artifacts for a specified change using CLI scaffolding and dependency ordering.

Community
Advanced
hongquandevhongquandev

openspec-archive-change

Archive completed OpenSpec changes to openspec/changes/archive after deployment.

Community
Advanced
f0rr0f0rr0
94

qualify-oliphaunt-change

Select and execute qualification gates for Oliphaunt changes.

Community
Advanced
LeKayLeKay

story-done

Verify story completion against design documents and update status.

Community
Advanced