add-delivery-validation

Validate feature delivery against requirements and acceptance criteria in about.md and plan.md.

8|2|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/brabos-ai/code-addiction --skill add-delivery-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-delivery-validation
Source: https://github.com/brabos-ai/code-addiction/tree/main/framwork/.codeadd/skills/add-delivery-validation
Command: npx skills add https://github.com/brabos-ai/code-addiction --skill add-delivery-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that delivered features fully meet all defined product requirements and acceptance criteria, preventing incomplete or non-compliant releases.

Core Features & Use Cases

  • Requirement Verification: Checks if all functional requirements (RF) and business rules (RN) are implemented.
  • Prerequisite Analysis: Identifies and validates necessary dependencies and pre-existing conditions for a feature to function correctly.
  • Use Case: Before merging a new feature, use this Skill to confirm that all user stories and acceptance criteria outlined in the about.md file have been successfully implemented and tested.

Quick Start

Validate the delivery of the current feature against its requirements.

Frequently Asked Questions about add-delivery-validation

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

FAQPage Schema
How do I validate feature delivery against product requirements before merging?

Feature delivery validation checks if 100% of functional requirements, business rules, and acceptance criteria are implemented. It analyzes about.md and plan.md files to ensure complete prerequisite existence and passing validation gates before finalization.

What is product requirement verification for feature finalization?

Product requirement verification is a validation gate process that confirms delivered features fully meet defined acceptance criteria. It prevents incomplete or non-compliant releases by analyzing functional requirements and business rules outlined in about.md and plan.md.

How to check if acceptance criteria are met before a feature release?

Checking acceptance criteria involves analyzing about.md and plan.md to verify all user stories and functional requirements are successfully implemented. This validation gate confirms prerequisite existence and passing criteria before merging.

Does this validation process work with standard markdown documentation files?

Yes, the validation process requires analysis of about.md and plan.md markdown files. These files must contain functional requirements, business rules, and acceptance criteria for the feature being validated before finalization.

Why should I use automated requirement verification instead of manual review?

Automated requirement verification ensures 100% implementation coverage of functional requirements and business rules, preventing incomplete releases. It systematically validates prerequisite existence and acceptance criteria that manual review might miss before merging.

When do I need to run feature delivery validation in the product workflow?

Feature delivery validation is needed at product validation gates before feature finalization and merging. It ensures all functional requirements, business rules, and acceptance criteria from about.md and plan.md are fully implemented.