backlog

Sprint backlog prioritization builds a dependency graph from Linear issues, ordering stories by completion state, blockers, priority, dependency depth, and age to output an actionable sequence. It loads open and recently completed issues to map dependencies accurately.

DB schema-chain conflict checking detects critical structural issues during sprint planning, such as two stories targeting the same database schema version. It validates schema version chains and reports ordering rules to prevent migration conflicts.

Backlog hygiene analysis flags cycles, orphaned references, and outdated items in your Linear backlog. It evaluates issue relationships to recommend cleanup actions and ensure dependency integrity across projects.

Dependency-aware sprint planning works by loading your repository architecture context alongside Linear backlog data. It uses this combined context to detect inter-story dependencies and schema version conflicts across projects.

Ordering Linear stories with inter-story dependencies requires evaluating completion state, blockers, priority, and dependency depth. This approach generates a prioritized list with explicit reasoning and hygiene recommendations.