backlog-refinement

Audits and refines GitHub issues against codebase reality for adversarial backlog grooming.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/jacobmiller22/chrishop --skill backlog-refinement-jacobmiller22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backlog-refinement
Source: https://github.com/jacobmiller22/chrishop/tree/main/.agents/skills/backlog-refinement
Command: npx skills add https://github.com/jacobmiller22/chrishop --skill backlog-refinement-jacobmiller22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a project backlog accurate is hard: completed stories may lack tests, open issues may miss priorities or dependencies, and milestones can drift from the actual architecture. This Skill provides a structured protocol for adversarial backlog grooming that verifies issues against the real codebase and files new stories for discovered gaps. ## Core Features & Use Cases - Codebase Ground-Truth Verification: Compares open and closed GitHub issues against actual code in apps, packages, migrations, and integration tests to confirm claimed work truly exists. - Adversarial Gap Detection: Systematically hunts for failure modes such as webhook replay attacks, missing DB transactions, race conditions during drops, and secrets leakage. - Story Refinement & Creation: Enriches issues with file paths, acceptance criteria, dependency links, and mandatory priority labels, and files new issues via the GitHub CLI. - Roadmap Auditing: Runs automated audits that flag legacy architecture keywords in milestones, verify deliverables on disk, and enforce priority-label compliance. - Use Case: Before a sprint planning session, run the refinement workflow to verify recently closed stories, detect unblocked shovel-ready issues, and produce a grooming report with escalated decisions. ## Quick Start Ask the AI to run an adversarial backlog refinement pass over the repository's open GitHub issues and produce a grooming report with refined stories and gaps.

Frequently Asked Questions about backlog-refinement

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

FAQPage Schema
How do I run an adversarial backlog refinement on GitHub issues?

Inventory open and closed issues with the GitHub CLI, verify closed stories against actual code in the repository, then refine or create issues with priority labels, dependencies, and acceptance criteria. Finish by running the roadmap audit command and compiling a grooming report.

How to verify completed GitHub issues against actual code?

List recently closed issues with gh issue list, then inspect the corresponding directories such as apps, packages, and migrations to confirm the implementation exists with tests and error handling. The audit:backlog command also cross-references closed issues with deliverables on disk.

What does the roadmap audit check for?

The audit flags legacy architecture keywords like docker or postgres in milestone descriptions, verifies every issue has an assigned milestone and priority label, detects blocked versus shovel-ready issues via the dependency graph, and confirms closed stories have files on disk.

Can this backlog grooming workflow run on a schedule?

The legacy launchd background daemon was decommissioned, so refinement now runs purely on-demand. You trigger it manually via pnpm run audit:roadmap, pnpm run audit:backlog, or through the project-management skill.

What labels are required when creating refined stories?

Every story must carry an explicit priority label such as priority:critical, high, medium, or low, plus standard labels like epic:phase-X, type:feature or type:infra, and a size label. Issues without priority labels cannot be dispatched.