delivery-readiness-audit

Audit delivery-ready stories for internal AC consistency and pending revisions.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/bketelsen/truenas-mcp --skill delivery-readiness-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: delivery-readiness-audit
Source: https://github.com/bketelsen/truenas-mcp/tree/main/.gaai/core/skills/cross/delivery-readiness-audit
Command: npx skills add https://github.com/bketelsen/truenas-mcp --skill delivery-readiness-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that stories marked as "ready for delivery" are internally consistent and that no pending revisions are overlooked, preventing delivery blockers.

Core Features & Use Cases

  • Internal Consistency Checks: Verifies that all resources declared within a story's ACs are properly referenced and declared, catching critical errors before deployment.
  • Pending Revision Scan: Identifies deferred work flagged in backlog notes that hasn't yet been converted into actionable stories.
  • Use Case: Before a major release, run this audit to confirm that all components are correctly defined and that no critical tasks were missed in the backlog, ensuring a smooth deployment.

Quick Start

Run the delivery-readiness-audit skill to perform a deep check on all delivery-ready stories.

Frequently Asked Questions about delivery-readiness-audit

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

FAQPage Schema
How do I audit delivery-ready stories for acceptance criteria consistency?

To audit delivery-ready stories for consistency, you can run a scan that verifies all resources declared in acceptance criteria are properly referenced, catching broken cross-references and missing declarations before deployment.

What is backlog readiness audit and when do I need it?

A backlog readiness audit identifies unaddressed deferred work flagged in backlog notes and missing resource declarations, ensuring critical issues are resolved before a major release to prevent delivery blockers.

How do I check for pending revisions in backlog management notes?

You can check for pending revisions by scanning backlog notes to identify deferred work that hasn't yet been converted into actionable stories, flagging critical and important issues before delivery.

Can I use a delivery readiness audit to catch missing cross-references before deployment?

Yes, a delivery readiness audit scans for broken cross-references and unaddressed deferred work within delivery-ready stories, ensuring all critical issues are flagged before deployment.

What is the best way to ensure quality assurance for backlog delivery readiness?

The best way to ensure delivery readiness is performing a deep audit that checks internal acceptance criteria consistency, scans for pending revisions in backlog notes, and flags critical issues before delivery.

What are the limitations of a delivery readiness audit for backlog governance?

A delivery readiness audit focuses on internal acceptance criteria consistency and pending backlog revisions, ensuring critical issues are flagged, but does not replace comprehensive deployment testing or external dependency validation.