Verified:GitHub

deliverable-review

Evaluate delivered artifacts against the brief with severity tiers and disposition rules.

Updated Aug 23, 2026

Search Tags:#quality-assurance #quality-gates #deliverable-review #pattern-completeness #disposition-framework #review-output

Ready to run

npx skills add https://github.com/Kiwi-Home/ai-workflow --skill deliverable-review-kiwi-home

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deliverable-review
Source: https://github.com/Kiwi-Home/ai-workflow/tree/main/plugins/structured-workflows/skills/deliverable-review
Command: npx skills add https://github.com/Kiwi-Home/ai-workflow --skill deliverable-review-kiwi-home

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill encodes a formal, repeatable protocol to evaluate delivered artifacts against the original brief, identify gaps, assign severity, and decide whether shipping is blocked.

Core Features & Use Cases

Severity-guided findings with MUST FIX, FIX NOW, and CREATE ISSUE
Four universal review categories (Requirements, Integrity, Standards, Quality) and a cross-system disposition framework
Clear, traceable output including evidence, scope, and actionability for consolidated follow-ups

Quick Start

Run a comprehensive deliverable-review on the latest PR diffs to classify findings and drive a decision to ship or fix.

Frequently Asked Questions about deliverable-review

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

FAQPage Schema

How do I evaluate delivered artifacts against a brief to prevent gaps before shipping?▼

Deliverable review applies a formal protocol to evaluate delivered artifacts against the original brief, identifying gaps and assigning severity tiers to prevent shipping incomplete work.

What is the three-layer disposition framework for quality gate findings?▼

The three-layer disposition framework classifies quality gate findings into MUST FIX, FIX NOW, and CREATE ISSUE severity tiers, providing structured actionability for consolidated follow-ups.

How do I classify review findings across requirements, integrity, standards, and quality categories?▼

You can classify review findings across four universal categories—Requirements, Integrity, Standards, and Quality—using severity-guided rules to drive a structured ship or fix decision.

Can I use this deliverable review protocol on PR diffs to decide whether to ship or fix?▼

Yes, you can run a comprehensive deliverable review on PR diffs to classify findings, apply cross-domain traceability, and drive a formal decision to ship or fix.

What's the best way to enforce pattern-completeness during a post-execution review?▼

The best way to enforce pattern-completeness is applying structured review categories and cross-system disposition rules during post-execution reviews to satisfy formal traceability requirements.

Why does my deliverable review lack traceable evidence for consolidated follow-ups?▼

Your deliverable review lacks traceable evidence because it needs a formal output structure that includes evidence, scope, and actionability with cross-domain traceability for consolidated follow-ups.