← ClaudeAtlas

roadmaplisted

Use when working the Shkills roadmap — picking up the next ticket, starting the next roadmap item, asking what to work on next, or finishing and closing out a roadmap ticket. Triggers on "next roadmap ticket", "work the roadmap", "what's next", "pick up the next item".
ydbondt/shkills · ★ 0 · Web & Frontend · score 62
Install: claude install-skill ydbondt/shkills
# Working the Shkills roadmap The roadmap is GitHub project [ydbondt/projects/4](https://github.com/users/ydbondt/projects/4). Tickets are issues in `ydbondt/shkills`. Work them **one at a time, in board order, top to bottom**. Statuses: `Proposed` → `Planned` → `In Progress` → `Done`. Only `Planned` tickets are yours to start. `Proposed` has not been agreed yet — leave it alone. ## Before you touch anything: two things that bite **Board order is the priority decision — do not re-litigate it.** The top `Planned` row is the next ticket, full stop. Do not sort by issue number, age or label. `gh project item-list` returns board order, not issue order (issue #2 currently sorts above #1); trust it. **Finishing a ticket ships it.** Every push to `main` builds and rolls out to the homelab cluster, and the Deployment uses `Recreate`, so the rollout is a short outage. Run the checks before you push, not after. See the `shkills-operations` skill if the rollout misbehaves. ## 1. Reconcile before picking Never start a second ticket while one is `In Progress`. ```bash gh project item-list 4 --owner ydbondt --format json \ -q '.items[] | select(.status=="In Progress") | {id, number: .content.number, title}' ``` Anything returned? Resume it instead of starting something new — check for a local branch `issue-<n>-*` and pick up where the last run stopped. Only when this returns nothing do you move on. ## 2. Pick the top Planned ticket ```bash gh project item-list 4 --owner ydbond