sdd-verify

Verify software implementations against specs, designs, and tasks with execution-based evidence.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/tiagofur/kakoclaw --skill sdd-verify-tiagofur
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-verify
Source: https://github.com/tiagofur/kakoclaw/tree/main/.claude/skills/sdd-verify
Command: npx skills add https://github.com/tiagofur/kakoclaw --skill sdd-verify-tiagofur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate that software implementations align with the defined specs, design, and tasks by executing verification workflows and collecting real evidence.

Core Features & Use Cases

  • End-to-end verification combining static analysis with runtime execution to prove compliance.
  • Supports delta specs, design validation, and task traceability for audit-ready changes.
  • Generates structured verification reports suitable for reviews, audits, and compliance workflows.

Quick Start

Run the verification workflow on the provided change and generate a verify 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 software implementations against design specs and tasks?

End-to-end verification proves compliance by combining static analysis with runtime execution to validate code against design specs and tasks. It collects real execution evidence to confirm implementations match the defined requirements.

Can I use runtime execution evidence for audit-ready software changes?

Yes, you can generate audit-ready software changes by capturing runtime execution evidence and applying task traceability. This produces a formal verify-report that satisfies compliance and review workflow requirements.

What is task traceability in software design validation?

Task traceability in design validation ensures every software change maps directly to a defined task or spec. It enables audit-ready verification by proving implementation compliance through collected runtime execution evidence rather than static review alone.

How do I generate a formal verify-report for compliance workflows?

You generate a formal verify-report by running the verification workflow on your provided software change. The resulting report combines static analysis with runtime execution evidence to document spec compliance for reviews and audits.

Does design validation require runtime execution or is static analysis enough?

Design validation requires runtime execution because static analysis alone cannot fully prove implementation compliance. Combining both methods produces the real execution evidence needed for task-traceable verification and audit-ready reports.

When do I need delta specs for software verification?

You need delta specs for software verification when validating incremental changes rather than the entire system. This targeted approach applies task traceability and runtime execution evidence to prove compliance for specific audit-ready modifications.