gsd-review-backlog
Manages the transition of backlog tasks to active phases with artifact cleanup.
Install
mkdir -p .claude/skills/gsd-review-backlog && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10282" && unzip -o skill.zip -d .claude/skills/gsd-review-backlog && rm skill.zipInstalls to .claude/skills/gsd-review-backlog
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Review and promote backlog items to active milestoneKey capabilities
- →List backlog items
- →Promote items to active milestone
- →Remove stale backlog entries
- →Update ROADMAP.md
How it works
It scans the backlog directory, presents items for user action, and automates the renaming and movement of phase artifacts.
Inputs & outputs
When to use gsd-review-backlog
- →Promote backlog to active
- →Review pending tasks
- →Cleanup stale roadmap entries
About this skill
-
List backlog items:
ls -d .planning/phases/999* 2>/dev/null || echo "No backlog items found" -
Read ROADMAP.md and extract all 999.x phase entries:
cat .planning/ROADMAP.mdShow each backlog item with its description, any accumulated context (CONTEXT.md, RESEARCH.md), and creation date.
-
Present the list to the user via AskUserQuestion:
- For each backlog item, show: phase number, description, accumulated artifacts
- Options per item: Promote (move to active), Keep (leave in backlog), Remove (delete)
-
For items to PROMOTE:
- Find the next sequential phase number in the active milestone
- Rename the directory from
999.x-slugto{new_num}-slug:NEW_NUM=$(gsd-tools query phase.add "${DESCRIPTION}" --raw) - Move accumulated artifacts to the new phase directory
- Update ROADMAP.md: move the entry from
## Backlogsection to the active phase list - Remove
(BACKLOG)marker - Add appropriate
**Depends on:**field
-
For items to REMOVE:
- Delete the phase directory
- Remove the entry from ROADMAP.md
## Backlogsection
-
Commit changes:
gsd-tools query commit "docs: review backlog — promoted N, removed M" --files .planning/ROADMAP.md -
Report summary:
## 📋 Backlog Review Complete Promoted: {list of promoted items with new phase numbers} Kept: {list of items remaining in backlog} Removed: {list of deleted items}
When not to use it
- →Projects without a .planning/phases directory
- →Repositories lacking a ROADMAP.md file
Prerequisites
Limitations
- →Limited to 999.x phase naming
How it compares
It automates the manual roadmap update and directory renaming process using gsd-tools.
Compared to similar skills
gsd-review-backlog side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| gsd-review-backlog (this skill) | 0 | 2mo | Review | Beginner |
| trello | 41 | 2mo | Review | Beginner |
| executing-plans | 6 | 3mo | No flags | Intermediate |
| github-project-management | 4 | 6mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by pjmagee
View all by pjmagee →You might also like
trello
openclaw
Manage Trello boards, lists, and cards via the Trello REST API.
executing-plans
obra
Use when you have a written implementation plan to execute in a separate session with review checkpoints
github-project-management
ruvnet
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
project-clickup
incidentfox
ClickUp project management integration for incident tracking and task management
coo-advisor
alirezarezvani
Operations leadership for scaling companies. Process design, OKR execution, operational cadence, and scaling playbooks. Use when designing operations, setting up OKRs, building processes, scaling teams, analyzing bottlenecks, planning operational cadence, or when user mentions COO, operations, process improvement, OKRs, scaling, operational efficiency, or execution.
tlc-spec-driven
tech-leads-club
Project and feature planning with 4 phases - Specify, Design, Tasks, Implement+Validate. Creates atomic tasks with verification criteria and maintains persistent memory across sessions. Stack-agnostic. Use when: (1) Starting new projects (initialize vision, goals, roadmap), (2) Working with existing codebases (map stack, architecture, conventions), (3) Planning features (requirements, design, task breakdown), (4) Implementing with verification, (5) Tracking decisions/blockers across sessions, (6) Pausing/resuming work. Triggers on "initialize project", "map codebase", "specify feature", "design", "tasks", "implement", "pause work", "resume work".