deliverable-review

Compare production deliverables against design and generate an ISO 25010 / IEEE 1012-aligned conformance report.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/ddaanet/edify-plugin --skill deliverable-review-ddaanet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deliverable-review
Source: https://github.com/ddaanet/edify-plugin/tree/main/skills/deliverable-review
Command: npx skills add https://github.com/ddaanet/edify-plugin --skill deliverable-review-ddaanet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review production artifacts after plan execution to surface conformance gaps and issues, producing an ISO 25010 / IEEE 1012-aligned report for accountability.

Core Features & Use Cases

  • Two-layer review: per-file checks delegated to specialists with an interactive cross-project validation pass.
  • Produces a severity-classified report identifying critical, major, and minor findings grounded in design requirements.
  • Outputs plan-specific reports at plans/<plan>/reports/deliverable-review-<type>.md and supports cross-project traceability.

Quick Start

Run this skill after a plan completes to generate a deliverable-review report for the current plan.

Frequently Asked Questions about deliverable-review

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

FAQPage Schema
How do I review production artifacts for conformance gaps against design specifications?

Deliverable conformance checking compares completed production artifacts against design specifications to surface conformance gaps. It produces a severity-classified report identifying critical, major, and minor findings grounded in design requirements.

How does a two-layer artifact review work for multi-project contexts?

A two-layer artifact review delegates per-file checks to specialists first, then performs an interactive cross-project validation pass. It enforces a four-phase workflow of inventory, gap analysis, per-file review, and interactive cross-project review.

When do I need an ISO 25010 or IEEE 1012-aligned report for deliverable review?

You need an ISO 25010 or IEEE 1012-aligned report when accountability and cross-project traceability are required after plan execution. It classifies findings by severity and outputs plan-specific markdown reports for structured quality assurance.

Can I generate per-file review reports for specific plan executions?

Yes, you can generate per-file review reports for specific plan executions. The review outputs plan-specific reports to plans/<plan>/reports/deliverable-review-<type>.md, supporting cross-project traceability across multiple contexts.

What is the best way to identify critical, major, and minor findings in production artifacts?

The best way to identify critical, major, and minor findings is by performing a structured deliverable review that compares artifacts against design requirements. It produces a severity-classified report grounded in those design requirements.