sdd-verify

Validate code implementations against specifications and design documents through static analysis and test execution.

Updated May 14, 2025
One-click install
npx skills add https://github.com/Mikisbell/freecloud --skill sdd-verify-mikisbell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-verify
Source: https://github.com/Mikisbell/freecloud/tree/main/.agents/skills/sdd-verify
Command: npx skills add https://github.com/Mikisbell/freecloud --skill sdd-verify-mikisbell

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill acts as a quality gate, ensuring that code implementations precisely match specifications, design documents, and assigned tasks, preventing the introduction of bugs and regressions.

Core Features & Use Cases

  • Completeness Check: Verifies all tasks associated with a change are completed.
  • Correctness Validation: Statically analyzes code against spec requirements and scenarios.
  • Design Coherence: Ensures implementation aligns with architectural design decisions.
  • Test Execution: Runs automated tests and build processes to confirm functionality and stability.
  • Behavioral Validation: Cross-references spec scenarios with actual test results for compliance.
  • Use Case: After a developer completes a new feature, this Skill is triggered to automatically confirm that all requirements are met, tests pass, and the code adheres to the approved design before it's merged.

Quick Start

Use the sdd-verify skill to verify the completed code changes against the project specifications.

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 implementations against project specifications?

Verifying code against specifications requires static analysis and dynamic test execution to validate behavioral compliance. This process cross-references test results with defined scenarios to ensure implementations match design documents and tasks.

What is the best way to validate code compliance with design documents before a merge?

Validating design coherence before a merge involves checking completeness and running automated build processes. This ensures the implementation aligns with architectural decisions and confirms all tasks associated with the change are completed.

How does automated behavioral validation cross-reference scenarios with test results?

Behavioral validation cross-references spec scenarios with actual test results by executing tests and comparing outputs. It statically analyzes code against requirements to confirm behavioral compliance and handles artifact persistence in configured modes.

Can I configure artifact persistence modes like engram or openspec for verification tasks?

Artifact persistence can be configured in modes like engram, openspec, or hybrid during verification. These modes determine how validation results and compliance artifacts are stored after tests execute and cross-reference scenarios.

Does static analysis alone confirm code correctness for specification requirements?

Static analysis alone does not confirm full correctness; it must be paired with test execution. Correctness validation requires both statically analyzing code against spec requirements and running dynamic tests to verify functionality and stability.