Menü
Show current GitHub Issues backlog — what's in progress, what's next, priorities
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Run a remote Trinity agent task in a sequential, bounded loop — a fixed number of iterations or until a stop signal, with optional response chaining. Fires server-side via run_agent_loop (caller can disconnect), then polls and renders progress. The remote, durable counterpart to Claude Code's local /loop. Add `local` to run the same bounded loop natively in this session instead — inline back-to-back iterations, or a hand-off to the built-in /loop when a cadence is given.
Make any agent a system-aware orchestrator — installs /discover-agents (discover the fleet from live Trinity and/or a repo list into a descriptive fleet/system-map.yaml), /compose-system (turn the map into a Trinity SystemManifest and deploy_system), and /orchestrate (route, fan out, and run ephemeral agents via Trinity MCP). Aligns with Trinity's existing SystemManifest; no parallel standard.
Create a new skill or playbook. Guides through requirements gathering and generates the appropriate template based on complexity.
Create an executive chief of staff agent — asks about your tools, team, and priorities, then scaffolds a Trinity-compatible agent for daily briefings, meeting prep, and decision tracking
Create a personal medical-records agent — bootstraps a profile from your existing health documents, then ingests new files, maintains structured memory, tracks lab trends, prepares doctor visits, and runs an evidence-based nutrition + supplement framework
Create a content writer agent — asks about your brand voice, platforms, and topics, then scaffolds a Trinity-compatible ghostwriter agent that writes in your voice
| name | backlog |
| description | Show current GitHub Issues backlog — what's in progress, what's next, priorities |
| argument-hint | [all|in-progress|blocked] |
| allowed-tools | Bash, Read |
| user-invocable | true |
| metadata | {"version":"1.1","created":"2026-04-14T00:00:00.000Z","author":"Ability.ai","changelog":["1.1: Add error handling and prerequisite checks","1.0: Initial version — priority-ordered view of open GitHub Issues by status and priority"]} |
ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of
metadata.changelogabove — e.g.backlog vX.Y — recent: <summary>. Then proceed.
View the agent's task backlog from GitHub Issues.
| Source | Location | Read | Write | Description |
|---|---|---|---|---|
| GitHub Issues | Current repo | Yes | No | Task backlog |
| GitHub Labels | status:, priority: | Yes | No | Status and priority |
/backlog or /backlog status → Show overview (in-progress + next up)/backlog all → Show all open issues by priority/backlog in-progress → Show only in-progress items/backlog blocked → Show blocked items/backlog p0 or /backlog p1 → Show specific prioritygh auth status 2>&1 | head -3
If not authenticated, tell user to run ! gh auth login.
gh label list --json name --jq '.[].name' | grep -E '^(status:|priority:)' | sort
If missing required labels, offer to create them:
gh label create "status:todo" --color "0E8A16" --description "Ready to work"
gh label create "status:in-progress" --color "FBCA04" --description "Currently working"
gh label create "status:blocked" --color "D93F0B" --description "Waiting on something"
gh label create "status:done" --color "6E5494" --description "Finished"
gh label create "priority:p0" --color "B60205" --description "Do now"
gh label create "priority:p1" --color "D93F0B" --description "Do soon"
gh label create "priority:p2" --color "FBCA04" --description "Do eventually"
For overview (default):
# In-progress
gh issue list --label "status:in-progress" --state open --json number,title,labels,assignees,updatedAt
# Next up (P0 todos)
gh issue list --label "priority:p0" --label "status:todo" --state open --json number,title,labels,assignees
# P1 todos
gh issue list --label "priority:p1" --label "status:todo" --state open --json number,title,labels,assignees --limit 5
For all:
gh issue list --state open --json number,title,labels,assignees,updatedAt --limit 50
For in-progress:
gh issue list --label "status:in-progress" --state open --json number,title,labels,body,assignees,updatedAt
For blocked:
gh issue list --label "status:blocked" --state open --json number,title,labels,body,assignees
Present results in a clear format:
## Backlog Overview
### In Progress (1)
| # | Title | Priority | Updated |
|---|-------|----------|---------|
| 42 | Implement feature X | p1 | 2h ago |
### Next Up — P0 (2)
| # | Title |
|---|-------|
| 45 | Critical bug fix |
| 46 | Urgent deploy |
### Queued — P1 (3)
| # | Title |
|---|-------|
| 48 | Add new endpoint |
| 49 | Refactor auth |
| 50 | Update docs |
**Total open: 12 issues**
View full backlog: [Issues →](https://github.com/owner/repo/issues)
| Error | Action |
|---|---|
| gh not authenticated | Tell user to run ! gh auth login |
| Not in a git repo | Report "Not in a GitHub repository" |
| No labels configured | Offer to create them (show commands) |
| API rate limited | Report error, suggest waiting |