sdd-verify

Validate Data Manager investigation reports for completeness and code evidence.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/PixelDroid19/Data-Management-Analyst --skill sdd-verify-pixeldroid19
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-verify
Source: https://github.com/PixelDroid19/Data-Management-Analyst/tree/main/skills/sdd-verify
Command: npx skills add https://github.com/PixelDroid19/Data-Management-Analyst --skill sdd-verify-pixeldroid19

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Ensures that Data Manager (DM) investigations are thorough, evidence-based, and meet the repository's standards before proceeding to documentation.

Core Features & Use Cases

  • Quality Gate: Acts as a crucial checkpoint to verify the completeness and accuracy of traced flows.
  • Evidence Validation: Confirms that all claims are backed by code evidence, not assumptions.
  • Use Case: After an AI agent has traced a complex data flow, this Skill reviews the findings to ensure all steps, service calls, and data mappings are correctly identified and supported by the codebase, preventing the generation of inaccurate documentation.

Quick Start

Validate the completed investigation report for completeness and evidence quality.

Frequently Asked Questions about sdd-verify

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

FAQPage Schema
How do I validate the evidence quality of a data flow investigation report?

Validate investigation report evidence quality by checking that all traced flows, service call chains, and parameter mappings are supported by code evidence and meet repository standards.

What is trace completeness verification for Data Manager investigations?

Trace completeness verification ensures all steps, service calls, and data mappings in a Data Manager investigation are correctly identified and backed by the codebase, preventing inaccurate documentation.

How do I check internal consistency in a DM investigation against repository standards?

Check internal consistency by analyzing traced flows and parameter mappings within the investigation report, ensuring all claims adhere to OpenSpec and output contracts for verification.

When do I need to verify code evidence for traced flows before generating documentation?

Verify code evidence for traced flows after completing a complex data flow investigation and before proceeding to documentation, acting as a quality gate to prevent assumptions.

Does the investigation validation process require adherence to OpenSpec output contracts?

Yes, the investigation validation process requires strict adherence to OpenSpec and output contracts to verify the completeness and internal consistency of the Data Manager report.

What are the limitations of validating investigation reports without code evidence?

Validating without code evidence means claims are based on assumptions, which risks generating inaccurate documentation and fails the quality gate for repository standards.