Menu
Groom the backlog — tag untagged issues with skill:* labels, verify priorities, surface stale in-progress work
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | groom |
| description | Groom the backlog — tag untagged issues with skill:* labels, verify priorities, surface stale in-progress work |
| allowed-tools | Bash, Read |
| user-invocable | true |
| metadata | {"version":"1.0","created":"2026-04-28T00:00:00.000Z","author":"Ability.ai","changelog":["1.0: Initial version — tags untagged issues with skill:* labels, verifies priorities, and surfaces stale in-progress work"]} |
ℹ️ 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.groom vX.Y — recent: <summary>. Then proceed.
Audit the open issue backlog for this agent. Tags issues with the skill they affect, surfaces missing priorities, and flags stale in-progress work. This is the agent-dev equivalent of backlog grooming — but the "areas" are skills, not features.
| Source | Location | Read | Write | Description |
|---|---|---|---|---|
| GitHub Issues | Current repo | Yes | Yes | Backlog issues |
| GitHub Labels | skill:, status:, priority:* | Yes | Yes | Apply missing labels |
| Agent Skills | .claude/skills/ | Yes | No | Available skills to tag against |
ls .claude/skills/
Build a list of skill names from the directory. These become the valid skill:* label values.
Also check if skill:* labels already exist in the repo:
gh label list --json name --jq '.[].name' | grep '^skill:'
Create any missing skill labels (one per skill directory):
gh label create "skill:$SKILL_NAME" --color "0075CA" --description "Issues affecting the $SKILL_NAME skill" 2>/dev/null || true
gh issue list --state open --json number,title,body,labels --limit 100
For each issue that has NO skill:* label:
Tagging options per issue:
.claude/skills/ → apply skill:<name>Apply the label:
gh issue edit $NUMBER --add-label "skill:$SKILL_NAME"
For each open issue without a priority:* label:
List them grouped:
### Issues missing priority labels (3)
| # | Title | Status |
|---|-------|--------|
| 12 | Fix claim flow | todo |
Offer to set priorities in batch: "Assign priorities? (p0/p1/p2 for each, or skip)"
gh issue edit $NUMBER --add-label "priority:$PRIORITY"
gh issue list --label "status:in-progress" --state open --json number,title,updatedAt
For any in-progress issue not updated in the last 48 hours, flag it:
### Stale in-progress (1)
| # | Title | Last updated |
|---|-------|-------------|
| 7 | Update autoplan flow | 3 days ago |
Offer to move stale issues back to status:todo or add a check-in comment.
## Groom Complete
- Tagged: X issues with skill labels
- Prioritized: Y issues
- Stale flagged: Z in-progress issues
Run `/roadmap` to see the skill-grouped view, or `/claim` to start the next issue.
| Error | Action |
|---|---|
No .claude/skills/ directory | Warn: "No skills found. Is this an agent repo?" |
| gh not authenticated | Tell user to run ! gh auth login |
| No open issues | Report "Backlog is empty — nothing to groom" |
| Label creation fails | Note and continue |
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