gsd-review-backlog

Review backlog items and promote selected entries to active milestones.

1|Updated Aug 17, 2025
One-click install
npx skills add https://github.com/DuySeu/StockMind --skill gsd-review-backlog-duyseu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-review-backlog
Source: https://github.com/DuySeu/StockMind/tree/main/.agent/skills/gsd-review-backlog
Command: npx skills add https://github.com/DuySeu/StockMind --skill gsd-review-backlog-duyseu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Backlog governance is often manual, slow, and error‑prone; this skill standardizes the process to review backlog items and promote selected entries to the active milestone, preserving context and history.

Core Features & Use Cases

  • List backlog items by reading .planning/phases/999* entries and the ROADMAP.md file, showing each item with its description, any accumulated context (CONTEXT.md, RESEARCH.md), and creation date.
  • Promote selected backlog items to the next active milestone by renaming the directory from 999.x-slug to a new milestone number and slug, moving associated artifacts, and updating ROADMAP.md accordingly.
  • Update ROADMAP.md to reflect promoted items, remove backlog markers, and record the promotion rationale via a commit message.

Quick Start

Start by listing backlog items, review their descriptions and context, and promote selected entries to the next milestone using the standard gsd-tools workflow.

Frequently Asked Questions about gsd-review-backlog

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

FAQPage Schema
How do I promote backlog items to active milestones in ROADMAP.md?

Promote backlog items by reading .planning/phases/999* entries and ROADMAP.md, selecting items, renaming directories, moving artifacts, updating ROADMAP.md, and recording a commit message.

What is the best way to convert 999.x backlog directories into active milestones?

Converting 999.x backlog directories involves renaming them to a new milestone number and slug, moving associated artifacts, and updating ROADMAP.md to reflect the promotion while preserving context and history.

Does the backlog promotion workflow preserve accumulated context like RESEARCH.md?

Yes, backlog promotion preserves accumulated context by reading CONTEXT.md and RESEARCH.md files during the listing phase and moving associated artifacts when renaming the 999.x backlog directories to active milestones.

How do I list backlog items with their descriptions and creation dates for review?

List backlog items by reading .planning/phases/999* entries and ROADMAP.md, which shows each item with its description, accumulated context files like CONTEXT.md and RESEARCH.md, and creation date.

Can I use this skill to standardize manual backlog governance across planning directories?

Yes, this skill standardizes backlog governance by enforcing a deterministic workflow with explicit steps for listing, reading ROADMAP.md, presenting options, renaming directories, moving artifacts, and updating ROADMAP.md.

What limitations exist when promoting backlog items to the next milestone sequence?

Promotion is limited to planning directories like .planning and ROADMAP.md across backlog phases, requiring 999.x backlog item formats and deterministic workflow steps to maintain context and history.