delivery-inspection

Verify sprint progress, acceptance criteria, and release readiness against backlog and Jira evidence.

Updated Sep 14, 2026
One-click install
npx skills add https://github.com/duchuyn04/resume-analyze --skill delivery-inspection-duchuyn04
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: delivery-inspection
Source: https://github.com/duchuyn04/resume-analyze/tree/main/.agents/skills/delivery-inspection
Command: npx skills add https://github.com/duchuyn04/resume-analyze --skill delivery-inspection-duchuyn04

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams struggle to know the true state of delivery: backlog checkboxes, Jira boards, and roadmap claims often disagree, and features get marked Done without verified acceptance criteria or evidence. This Skill reconciles Product Backlog Markdown, roadmaps, and local/Jira status into an evidence-based progress matrix. ## Core Features & Use Cases - Progress Matrix Verification: Cross-references module catalogues, stories, AC, task records, and evidence to compute per-module status across business, UX, contract, implementation, testing, and release columns. - Done/DoD Gatekeeping: Validates acceptance criteria, two-axis review evidence (standards/spec), and Browser Native UI verification before allowing any Done checkbox or Story Point credit. - Release & Sprint Closeout: Assesses release readiness (migrations, rollback, smoke checks) and guides Sprint Review, Retrospective, and next-sprint activation without unauthorized Jira writes. - Use Case: Ask whether Sprint 3 is ready to release; the Skill reads the backlog and roadmap, flags modules with stale or missing evidence, lists blockers with owners, and reports exactly which AC remain unverified. ## Quick Start Ask the agent to inspect the current sprint progress against the product backlog and roadmap and report which features are verifiably Done with evidence.

Frequently Asked Questions about delivery-inspection

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

FAQPage Schema
How do I verify sprint progress against a product backlog?▼

The Skill reads the product backlog Markdown, roadmap, and module catalogue, then cross-checks each feature's stories, acceptance criteria, task records, and evidence. It reports features Done, Story Points completed, and AC passed separately, flagging anything unverified.

When can a task be marked Done in Jira?▼

A task can only be marked Done after its Definition of Done and acceptance criteria are verified with evidence at the correct integrated revision, including two-axis review for feature or risky work. Merged PRs or passing tests alone are insufficient.

Does it work without a Jira connection?▼

Yes, local mode uses Markdown records and the latest evidence to compile status without requiring Jira. In Jira mode, missing connection or permissions are reported as unverified rather than silently falling back to local data.

Why is browser evidence required before ticking UI tasks Done?▼

UI and HTML/SVG diagram changes require Browser Native verification, including font measurement, overflow checks, and screenshots, because code-level tests cannot confirm visual correctness. Non-UI tasks only need logic, API, or database test evidence.

Can it close a sprint or change Jira statuses automatically?▼

No, starting or closing sprints and writing to Jira require explicit user authorization. The Skill only reflects Done status after confirmation and sufficient evidence, and never modifies external state to make reports look better.

What are the limitations of progress percentage reporting?▼

The Skill does not convert task completion percentages into product completion forecasts or delivery dates without basis. Empty task sets, canceled items, and stale evidence are reported explicitly rather than being smoothed over.