openspec-verify-change

Name: openspec-verify-change
Availability: InStock
Author: Emergent

Verify code implementations against openspec artifacts for completeness and correctness.

1|Updated Feb 6, 2026

Search Tags:#quality assurance #code review #implementation #verification #change management #openspec

Ready to run

npx skills add https://github.com/emergent-company/emergent.memory --skill openspec-verify-change-emergent-company

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/emergent-company/emergent.memory/tree/main/.opencode/skills/openspec-verify-change
Command: npx skills add https://github.com/emergent-company/emergent.memory --skill openspec-verify-change-emergent-company

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that code implementations accurately reflect the intended design, tasks, and specifications, preventing drift and ensuring quality before changes are finalized.

Core Features & Use Cases

Completeness Check: Verifies all defined tasks and requirements are addressed.
Correctness Validation: Assesses if the implementation aligns with spec requirements and scenarios.
Coherence Review: Checks adherence to design decisions and code patterns.
Use Case: Before merging a new feature, use this Skill to confirm that all user stories, acceptance criteria, and design documents have been fully and correctly implemented in the codebase.

Quick Start

Use the openspec-verify-change skill to verify the implementation for the change named 'user-authentication-flow'.

Frequently Asked Questions about openspec-verify-change

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

FAQPage Schema

How do I verify code implementation matches design specifications before merging?▼

Verifying code implementation matches design specifications involves parsing change artifacts like tasks and design documents, then cross-referencing them with codebase content to identify any discrepancies or missing requirements.

What is change artifact verification in software engineering?▼

Change artifact verification is the process of assessing whether code implementations precisely match associated specifications, tasks, and design documents to prevent drift and ensure quality before changes are finalized.

How do I check if all acceptance criteria and user stories are implemented correctly?▼

You can check implementation completeness and correctness by parsing defined requirements and cross-referencing them with codebase content to confirm all user stories and acceptance criteria are fully addressed.

Does code review verification work without external dependencies?▼

Yes, code review verification can operate without external dependencies by parsing openspec artifacts internally and cross-referencing the parsed specifications directly with the existing codebase content.

When should I use automated implementation verification for change management?▼

You should use automated implementation verification before merging a new feature to confirm that all design decisions, specifications, and project standards have been fully and correctly implemented in the codebase.

Why does code implementation drift from original specifications during development?▼

Code implementation drifts from original specifications when developers deviate from defined requirements and design decisions, which is why cross-referencing codebase content against change artifacts identifies these discrepancies before finalizing changes.