gsd-review-backlog

Review backlog items and update ROADMAP.md for promotions or removals.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/hadpadrahul/school-erp --skill gsd-review-backlog-hadpadrahul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-review-backlog
Source: https://github.com/hadpadrahul/school-erp/tree/main/.codex/skills/gsd-review-backlog
Command: npx skills add https://github.com/hadpadrahul/school-erp --skill gsd-review-backlog-hadpadrahul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Backlog governance can be time-consuming and error-prone when promotions to milestones and removals require manual coordination across ROADMAP.md and phase directories.

Core Features & Use Cases

  • Automates backlog review by inspecting backlog items, describing context, and presenting promotion/removal options.
  • Handles bulk decisions and updates ROADMAP.md and directory structure accordingly.

Quick Start

Identify backlog items, review their context, and promote or remove items to update ROADMAP.md and move artifacts to the new phase directories.

Frequently Asked Questions about gsd-review-backlog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate moving software backlog items to active milestones?

You can automate moving software backlog items to active milestones by inspecting items, reviewing their context, and executing bulk promotion or removal decisions. This process automatically renames directories, moves artifacts, and updates your ROADMAP.md file.

What is the best way to clean up stale entries in a project backlog?

The best way to clean up stale entries in a project backlog is to review their context and dates, then remove outdated items. This automatically handles directory renaming, artifact removal, and ROADMAP.md updates to keep your roadmap current.

How does backlog governance work with ROADMAP.md and phase directories?

Backlog governance with ROADMAP.md and phase directories works by reading the roadmap to surface item context and dates, then coordinating bulk decisions. Promoting or removing items automatically moves artifacts and commits changes to maintain directory structure.

Can I use this backlog review workflow for directories named 999.x?

Yes, you can use this backlog review workflow specifically for directories named 999.x. It reads these backlog directories alongside ROADMAP.md to surface descriptions and dates, enabling targeted promotion to active milestones or removal of stale entries.

How do I update ROADMAP.md when promoting backlog items to milestones?

To update ROADMAP.md when promoting backlog items to milestones, you review the item context and select promotion. The workflow automatically updates the ROADMAP.md file, moves artifacts to new phase directories, and commits the changes end-to-end.

What are the limitations of automating backlog governance across phase directories?

The main limitation of automating backlog governance is that it specifically targets backlog directories named 999.x and relies on a ROADMAP.md file to surface item context. Directory structures and roadmap files outside this convention are not automatically managed.