sdd-verify

Execute code to verify implementations against specs, design, and tasks.

Updated Jun 22, 2024

Search Tags:#testing #verification #compliance #execution #code #quality-assurance #specs

Ready to run

npx skills add https://github.com/KilloconQ/dotfiles --skill sdd-verify-killoconq

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-verify
Source: https://github.com/KilloconQ/dotfiles/tree/main/opencode/.config/opencode/skills/sdd-verify
Command: npx skills add https://github.com/KilloconQ/dotfiles --skill sdd-verify-killoconq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate that implementations match specs, design, and tasks by executing the code to produce real-world evidence of correctness, rather than relying on static analysis alone.

Core Features & Use Cases

End-to-end verification: execute code to demonstrate completion and behavioral compliance against specs.
Design and task coherence: evaluate alignment with design decisions, specs, and task lists.
Artifact-driven reporting: generate a verification report according to the active artifact_store mode and persistence rules.

Quick Start

Run the verification workflow on a completed or partial change to generate a verifiable report.

Frequently Asked Questions about sdd-verify

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

FAQPage Schema

How do I verify code compliance against formal specs through live execution?▼

To verify code compliance against formal specs, you execute the implementation to collect real-world evidence of correctness rather than relying on static analysis. This process evaluates alignment with design decisions, specs, and task lists to demonstrate behavioral compliance.

What is spec-compliance verification and when do I need live execution checks?▼

Spec-compliance verification is the process of validating that an implementation satisfies specified design and task requirements. You need live execution checks when static analysis is insufficient and you must produce real-world evidence of correctness for formal specs.

How do I generate a verification report for a completed code change?▼

You generate a verification report by executing the code on a completed or partial change and collecting artifact-driven evidence. The system produces a structured verify-report according to the active artifact_store mode and persistence rules.

Does spec-compliance verification work for partial code changes or only completed implementations?▼

Spec-compliance verification works for both partial and completed code changes. You can run the verification workflow on any stage of implementation to evaluate alignment with design decisions, specs, and task lists through live execution and artifact generation.

Why use live execution for spec verification instead of static code analysis?▼

Live execution is used for spec verification to produce real-world evidence of correctness and behavioral compliance. Static analysis alone cannot demonstrate completion or validate that implementations match specs and design decisions through actual runtime behavior.

What do I need to locate before running a spec-compliance verification workflow?▼

Before running spec-compliance verification, you need to locate project dependencies and follow persistence rules. The workflow requires formal specs, design decisions, and task lists to execute the code and generate a structured verify-report under the configured mode.