openspec-verify-change

Validate software implementations against specifications, tasks, and designs.

1|Updated Jul 30, 2023

Search Tags:#code review #implementation #verification #compliance #change management #openspec

Ready to run

npx skills add https://github.com/DanielShuguang/tool-box --skill openspec-verify-change-danielshuguang

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/DanielShuguang/tool-box/tree/main/.trae/skills/openspec-verify-change
Command: npx skills add https://github.com/DanielShuguang/tool-box --skill openspec-verify-change-danielshuguang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec-cn, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that software implementations accurately match the defined specifications, tasks, and designs before archiving, preventing inconsistencies and errors.

Core Features & Use Cases

Integrity Checks: Validates that all tasks are completed and requirements are met.
Consistency Verification: Checks if the implementation adheres to design decisions and coding patterns.
Use Case: Before a code merge or release, use this Skill to automatically verify that the implemented features align with the approved design documents and user stories, flagging any discrepancies.

Quick Start

Use the openspec-verify-change skill to verify the implementation for the change named 'feature-x'.

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 software implementation against change specifications before archiving?▼

To verify implementation against change specifications, you can use this skill to perform integrity, correctness, and consistency checks on code and documentation. It validates that all tasks are completed and requirements are met before code merge or release.

What does change management verification check for in a development workflow?▼

Change management verification checks for completeness, correctness, and consistency in development workflows. It ensures the software implementation accurately matches defined specifications, tasks, and designs, flagging any discrepancies before archiving.

How do I check if my code implementation adheres to design decisions and coding patterns?▼

You check implementation adherence by running consistency verification against your change artifacts. This process validates whether the implemented features align with approved design documents and user stories, preventing inconsistencies and errors.

Do I need the openspec CLI to validate implementation completeness for a specific change?▼

Yes, you need the openspec CLI to validate implementation completeness. The verification process requires the openspec CLI to list, status, and apply changes, and performs integrity checks on code and documentation.

What is the best way to ensure code matches approved design documents before a merge?▼

The best way to ensure code matches approved design documents is to run pre-archival verification. This automatically validates that implemented features align with user stories and design decisions, flagging discrepancies for correction.

Why does implementation verification fail when tasks are not completed?▼

Implementation verification fails when tasks are not completed because the integrity check validates that all requirements are met. The verification process ensures software implementations accurately match defined specifications and tasks before archiving.