/safina:backlog
Pull your assigned tickets and set today’s session focus. This is the entry point of every working session — it establishes the ticket context that the rest of the loop depends on.
When to run it
- At the start of every session
- When grooming: creating or updating issues
- Any time you need to check what’s assigned to you
What it does
- Reads your config (
~/.claude/ilmiya-config.json) to determine your tier and identity - Pulls your assigned tickets from the right source
- Shows them as a numbered list with ID, title, priority, and status
- Lets you pick focus, create a new issue, or update an existing one
By developer tier
| Tier 1 (Taha, Adnan) | Tier 2 (everyone else) | |
|---|---|---|
| Ticket source | Linear via Linear MCP | GitHub issues in ilmiya/safina |
| Mark in progress | Linear status update | in-progress label via gh or GitHub MCP |
| Create issue | mcp__claude_ai_Linear__save_issue | gh issue create |
If your required connector isn’t set up, the command tells you: “Connect [service] at claude.ai/settings.”
Session context
When you pick your focus ticket, the command confirms: “Today you’re on [ticket title — TICKET-ID].”
This is the session context. /safina:update requires it. If you try to post an update without running backlog first and knowing your ticket, it stops and sends you back here.
Prerequisite for
/safina:update— won’t post without ticket context
Complementary Claude commands
| Command | Use it when… |
|---|---|
/plan | You want to break a ticket down into an implementation plan before starting |