ring:dev-delivery-verification

Name: ring:dev-delivery-verification
Availability: InStock
Author: LucasMalessa

Verify delivered code implements original requirements and reports dead code.

Updated Mar 21, 2026

Search Tags:#devops #integration-testing #gate #code-validation #requirements-traceability #delivery-verification

Ready to run

npx skills add https://github.com/LucasMalessa/TheRing --skill ring-dev-delivery-verification

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ring:dev-delivery-verification
Source: https://github.com/LucasMalessa/TheRing/tree/main/dev-team/skills/dev-delivery-verification
Command: npx skills add https://github.com/LucasMalessa/TheRing --skill ring-dev-delivery-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delivery verification ensures that what was requested is actually delivered as reachable, integrated code. It distinguishes between created artifacts and what actually runs in the application, preventing dead or unconnected work. It applies to all task types: features, refactors, infrastructure, APIs, and integrations.

Core Features & Use Cases

End-to-end verification across features, refactors, and infrastructure
Dead code detection and requirement coverage reporting
Generation of a Delivery Verification Summary and a detailed integration report

Quick Start

Run the Delivery Verification Gate after implementing a task to generate a verification report.

Frequently Asked Questions about ring:dev-delivery-verification

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

FAQPage Schema

How do I verify delivered code matches all original requirements?▼

Delivery verification confirms that delivered code implements all original requirements by ensuring every requirement is wired into the execution path and reachable at runtime, preventing dead or unconnected artifacts.

What is delivery verification in software engineering?▼

Delivery verification distinguishes between created artifacts and what actually runs in the application, validating that code for features, refactors, or infrastructure matches the original task requirements at runtime.

How do I detect dead code and integration gaps after a task?▼

Run a delivery verification gate after implementing a task to detect dead code and integration gaps, producing a detailed integration report that maps requirement coverage and runtime reachability across the execution path.

Can I use delivery verification for infrastructure and API refactoring tasks?▼

Yes, delivery verification applies end-to-end across features, refactors, infrastructure, APIs, and integrations to validate runtime delivery and ensure all requirements are present and reachable.

What's the best way to check if requirements traceability is maintained at runtime?▼

The best approach is running a delivery verification gate that traces requirements through the execution path, confirming each requirement is present, integrated, and reachable while reporting on delivery status and gaps.