marsai:dev-delivery-verification

Verify requested work is delivered and reachable in the running application.

2|Updated Apr 10, 2026

Search Tags:#integration #requirements #verification #traceability #delivery #gate #dead-code

Ready to run

npx skills add https://github.com/V4-Company/marsai --skill marsai-dev-delivery-verification

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delivery Verification ensures that what was requested is delivered as reachable, integrated code, not just compiled or superficially completed.

Core Features & Use Cases

Ensures delivered code is wired into the application execution path and is actually executable
Generates structured verification reports including Delivery Verification Summary, Requirement Coverage Matrix, Integration Verification, Dead Code Detection, and Verdict
Automates gate-to-gate integrity checks after Gate 0 to flag gaps and guide returns to Gate 0

Quick Start

Run the Delivery Verification step after Gate 0 to confirm all requirements are wired and reachable.

Frequently Asked Questions about marsai:dev-delivery-verification

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

FAQPage Schema

How do I verify that delivered code is actually wired into the application execution path?▼

Delivery verification checks that requested features are integrated and reachable in the running application, not just compiled. It confirms execution path wiring and generates a structured Delivery Verification Summary to flag gaps.

What is dead code detection and how does it relate to requirement traceability?▼

Dead code detection identifies unlinked or unreachable code segments, while requirement traceability maps delivered features to original requests. Together they ensure complete integration wiring and expose leftover or non-executable code in the codebase.

How do I generate a requirement coverage matrix after completing a feature or refactor?▼

Run delivery verification after Gate 0 to automatically produce a Requirement Coverage Matrix. This matrix maps original requirements against delivered code, confirming integration wiring and reporting any missing traceability.

Does delivery verification work for infrastructure and API tasks or only feature development?▼

Delivery verification applies to any task type, including features, refactors, fixes, infrastructure, APIs, and middleware. It enforces complete delivery with integration wiring across all Gate 0 outcomes.

Why does my delivered feature show as dead code in the running application?▼

Delivered code appears as dead code when it is compiled but not wired into the application execution path. Delivery verification detects this by checking integration wiring and confirming the code is actually executable and reachable.

When should I return to Gate 0 during delivery verification?▼

You should return to Gate 0 when delivery verification detects gaps in requirement coverage or integration wiring. The verification verdict provides instructions to return to Gate 0 to fix incomplete or non-reachable deliveries.