backlog-auditor

Audits JIRA sprint backlog files to generate Vietnamese progress reports with completion metrics.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/manhthien2005/PM_REVIEW --skill backlog-auditor-manhthien2005
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backlog-auditor
Source: https://github.com/manhthien2005/PM_REVIEW/tree/main/tooling/.windsurf-template/shared/skills/backlog-auditor
Command: npx skills add https://github.com/manhthien2005/PM_REVIEW --skill backlog-auditor-manhthien2005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Project managers lack a quick, consistent way to measure sprint progress across scattered JIRA backlog files, making it hard to spot blocked epics and at-risk stories before deadlines slip. ## Core Features & Use Cases - Automated Progress Tallying: Scans _SPRINT.md and STORIES.md files to count completed vs pending Epics and Acceptance Criteria checkboxes, producing accurate completion percentages. - Risk Detection: Identifies stalled epics, unstarted stories, and potential blocking dependencies between backlog items. - Vietnamese Reporting: Generates a structured Markdown progress report saved to PM_REVIEW/Task/Backlog_Review_{date}.md entirely in Vietnamese. - Use Case: A PM asks for a sprint review before a weekly sync; the skill reads all Sprint folders, computes per-sprint completion rates, and flags EP04-Login as stalled at 3/15 acceptance criteria. ## Quick Start Ask the AI to review the current sprint backlog progress and generate a progress report from the JIRA folder.

Frequently Asked Questions about backlog-auditor

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

FAQPage Schema
How do I check sprint progress from JIRA Markdown files?▼

Run a backlog audit that scans _SPRINT.md files for checked Epic boxes and STORIES.md files for completed Acceptance Criteria checkboxes. The skill tallies these counts and produces a completion percentage per sprint in a Markdown report.

How to identify blocked or at-risk backlog items automatically?▼

The audit flags epics with low Acceptance Criteria completion, stories that have not started, and potential dependency blocks between items. These findings appear in a dedicated risk section of the generated report.

Does the backlog audit modify my JIRA files?▼

No, the audit is strictly read-only for the JIRA directory. It only writes a new report file to the Task output folder and never creates, edits, or deletes any backlog items.

What files are required for a sprint backlog review?▼

The review requires a JIRA folder containing Sprint subfolders with _SPRINT.md files and Epic folders containing STORIES.md files with checkbox-formatted Acceptance Criteria. A MASTER_INDEX.md and JIRA README provide navigation context.

What are the limitations of checkbox-based progress tracking?▼

Checkbox-based tracking only reflects manually updated statuses, so stale or unchecked boxes can skew completion metrics. It cannot verify actual code completion or integrate with live JIRA API data.