sr-get-backlog-specs

To prioritize a GitHub backlog for sprint planning, this Skill reads issues labeled product-driven-backlog, constructs a dependency graph from parsed prerequisites, detects cycles, and computes a safe topological order grouped by area. It then ranks items by persona score and proposes the top 3 for the next sprint.

Handling prerequisites in GitHub issues involves parsing prerequisite metadata to build a dependency graph. This Skill detects cycles, flags blocked or cyclic items with clear indicators in per-area backlog tables, and ensures only safe, unblocked items are proposed for the next sprint.

Persona scoring for ranking backlog items works by extracting persona fit scores from GitHub issue metadata. This Skill uses those extracted scores to rank items within their respective areas after computing a safe topological order from the dependency graph.

Yes, GitHub issues must be labeled product-driven-backlog. This Skill specifically reads issues with that label to extract key metadata including effort estimates, user stories, persona scores, areas, and prerequisites for backlog prioritization.

Yes, you can cache a prioritized backlog snapshot to maintain continuity across runs. This Skill writes a backlog cache containing the extracted metadata and computed priorities to the .claude/backlog-cache.json file after rendering the backlog tables.