---
name: list-issues
description: >-
  Show the open issues and epics on the turbine GitLab roadmap so you can pick
  something and start work. Use whenever the user asks what to work on, what's
  open, what's left, what's in the backlog, what issues/epics/tickets exist,
  what's in a milestone (e.g. "what's in v0.8"), what bugs are open, who's got
  what, or says "list issues", "show epics", "what's next", "what should I
  start", "show the board" — even if they don't say GitLab. Reads
  turbine-platform/turbine (issues) and the turbine-platform group (epics).
---

# List issues / epics

One read-only command that prints the open epics and open issues, grouped by
milestone (nearest due date first) so the top of the list is what to start now.

```bash
python3 .claude/skills/list-issues/scripts/list_work.py
```

Run it and show the output as-is — it's already formatted to be scannable. Don't
re-fetch or reformat by hand; the script is the source of truth.

## Filters

Pass plain flags when the user narrows the ask:

- `--milestone v0.8` — only that milestone (use for "what's in v0.8")
- `--bugs` — only `type::bug` issues (use for "what bugs are open")
- `--mine` — only issues assigned to the current user
- `--epics` / `--issues` — show just one of the two sections

```bash
python3 .claude/skills/list-issues/scripts/list_work.py --milestone v0.8 --bugs
```

## After listing

When the user picks one (e.g. "let's do #7"), read it in full so work can start:

```bash
glab api "projects/20196/issues/7" \
  | python3 -c "import sys,json;d=json.load(sys.stdin);print(d['title']);print();print(d['description'])"
```

The numbers shown are issue `iid`s — open one at
`https://enx.gitlab.schubergphilis.com/1000078-app-keten-shared/applications/turbine-platform/turbine/-/work_items/<iid>`.

## Notes

- `glab` is on PATH with the corporate-proxy wrapper already handled — no prefix,
  no env vars. If it ever errors with a connection failure, the SOCKS tunnel on
  `127.0.0.1:1080` is down (same one glab/snowflake use); that's transport, not a
  query problem.
- Project id `20196` (turbine-platform/turbine), group id `1254326`
  (turbine-platform). These are stable; the script holds them.
