# Soloscrum Tracker Linear Query Backlog

> Operation: list backlog Linear Tasks and subtasks ordered by priority. Used when active tracker profile is linear+github.

- Skill: `mew-ton/soloscrum-tracker-linear-query-backlog` (Agent Skill)
- Install (CLI): `npx get-skill add mew-ton/soloscrum-tracker-linear-query-backlog`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mew-ton/soloscrum-tracker-linear-query-backlog/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: mew-ton (https://skillmd.com/u/mew-ton)
- Updated: 2026-11-18
- Page: https://skillmd.com/skills/mew-ton/soloscrum-tracker-linear-query-backlog

---


# soloscrum-tracker-linear-query-backlog

Returns the Linear backlog (items in Backlog or Todo states) ordered by priority. Active when `tracker_profile = linear+github`.

## Inputs

- (none) — defaults to the user's configured team

## Steps

1. Fetch backlog items:
   - Linear MCP — `list_issues` with `filter: { state: { type: { in: ["backlog", "unstarted"] } } }`, ordered by `priority` desc then `createdAt` asc
2. Group by priority bucket: Urgent / High / Medium / Low / No priority

## Output

- Grouped backlog list:
  ```
  Urgent:
    PRJ-123 (SP 3, develop) — Add password reset
  High:
    PRJ-124 (SP 5, design-ui) — Login screen
  ...
  ```

## Notes

- This operation skill is the basis for `/soloscrum:next` and `/soloscrum:status` when in linear+github profile
- "Backlog" excludes In Progress and In Review — those are surfaced by `query-state` instead
- If the user has multiple Linear teams, prompt for which team to query (or read from `.claude/rules/tracker.md`)

