sdd-verify

Verify change implementations against specs, design, and tasks.

3|Updated Apr 5, 2023

Search Tags:#design #testing #quality #tasks #verify #code-review #specs

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that a given change meets the defined specs, design, and tasks by cross-checking artifacts and ensuring completeness.

Core Features & Use Cases

Automated completeness checks against specs, design, and tasks.
Traceability of changes from proposal to implementation with a structured verification report.
Use Case: You just submitted a change; run this Skill to generate a verification brief and highlight gaps.

Quick Start

Provide the change artifacts (proposal, design, and tasks) to trigger a verification pass and produce a structured 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 implementations against design specs and tasks?▼

To verify code implementations against design specs, you provide the change artifacts, design documents, and task lists to trigger a verification pass that cross-checks completeness and generates a structured report.

What is the best way to check if a completed software change meets the original specs?▼

The best way to check if a completed software change meets original specs is to run an automated completeness verification pass that cross-checks the artifacts and produces a structured verification brief highlighting any gaps.

Can I use automated verification for partially completed changes in orchestrator-led workflows?▼

Yes, you can apply automated verification to partially completed changes in orchestrator-led workflows to check correctness, coherence, and testing coverage against provided artifacts and generate a structured report.

How does traceability work when validating software changes from proposal to implementation?▼

Traceability when validating software changes works by cross-checking the proposal, design, and task artifacts against the actual implementation to ensure completeness and coherence, outputting a structured verification report.

What do I need to provide to generate a software verification brief for my project?▼

You need to provide the change artifacts, specifically the proposal, design, and tasks, to trigger the verification pass and produce a structured report highlighting gaps in the implementation.

When should I run a verification pass against specs and design in my software project?▼

You should run a verification pass against specs and design immediately after submitting a change or completing a task in your software project to ensure the implementation meets defined requirements and has adequate testing coverage.