backlog

Analyzes Linear backlog issues, maps dependencies, and proposes a prioritized sprint order.

2|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/Vibecoder79/jarvis --skill backlog-vibecoder79
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backlog
Source: https://github.com/Vibecoder79/jarvis/tree/main/.claude/skills/backlog
Command: npx skills add https://github.com/Vibecoder79/jarvis --skill backlog-vibecoder79

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Flat backlogs sorted only by priority hide critical structure: dependencies between stories, database schema version chains, and issues that look blocked but are actually done. This Skill loads the full backlog from Linear, builds a dependency graph, and proposes a concrete, reasoned priority order so sprint planning is no longer guesswork. ## Core Features & Use Cases - Dependency Graph Analysis: Reads issue descriptions for dependency sections, detects circular dependencies, and flags orphaned references to non-existent issues. - Schema-Chain Check: Scans open issues for DB Schema Impact sections, enforces ordering by target schema version, and reports two stories targeting the same version as a critical blocker. - Context-Aware Prioritization: Loads CLAUDE.md, ARCHITECTURE_DESIGN.md, and SYSTEM_ARCHITECTURE.md plus completed issues from the last 30 days, so stories already shipped are not treated as open blockers. - Use Case: Before sprint planning, ask what to work on next and receive a ranked story list with per-story reasoning, conflict reports, and backlog hygiene suggestions such as issues to close or re-prioritize. ## Quick Start Ask the assistant to run the backlog skill and tell you which story to pick up next based on dependencies and priorities.

Frequently Asked Questions about backlog

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

FAQPage Schema
How do I prioritize a backlog with dependencies between stories?▼

Load all open issues, parse their dependency sections into a graph, then sort by status, blocker impact, priority, dependency depth, and age. This Skill automates that process against a Linear backlog and outputs a ranked list with reasoning per story.

How to detect database schema migration conflicts in sprint planning?▼

Scan open issues for DB Schema Impact sections and build a chain of current to target schema versions. Stories with lower target versions must ship first, and two stories targeting the same version are flagged as a critical blocker requiring a rewrite.

Does this backlog planning skill work with Linear?▼

Yes, it loads open issues and completed issues from the last 30 days via Linear. Completed issues are used to update blocker status, so stories referencing already-done blockers are marked unblocked.

Why does my backlog show stories as blocked when the blocker is done?▼

Issue trackers often leave dependency references stale after a blocker ships. This Skill cross-references completed issues from the last 30 days and CLAUDE.md implementation notes to mark such stories as unblocked and calls this out explicitly.

What are the limitations of automated backlog prioritization?▼

It depends on issues containing structured dependency and schema impact sections; missing or informal descriptions reduce detection accuracy. It also cannot judge business value beyond the priority field, so final calls still need human review.