gsd-review-backlog

Review backlog phase directories and update planning records for 999.x items.

264|11|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/coco-research/coco --skill gsd-review-backlog-coco-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-review-backlog
Source: https://github.com/coco-research/coco/tree/main/systems/gsd/skills/gsd-review-backlog
Command: npx skills add https://github.com/coco-research/coco --skill gsd-review-backlog-coco-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams clean up long-running planning backlogs by reviewing dormant 999.x phase items, deciding which ones should move into active work, and removing entries that are no longer useful.

Core Features & Use Cases

  • Backlog Review: Lists all backlog phases and surfaces their descriptions, context files, and creation details for human decision-making.
  • Promote or Remove Items: Renames promoted phases into the active sequence, updates roadmap references, and deletes stale entries when needed.
  • Keep Planning State Consistent: Rewrites the roadmap and commits the result so milestone tracking stays aligned with the actual directory structure.
  • Use Case: A project lead can run this Skill to convert promising research ideas from backlog status into scheduled delivery work without manually hunting through planning files.

Quick Start

Use this skill to review the backlog phases in the repository, then tell me which items you want promoted, kept, or removed.

Frequently Asked Questions about gsd-review-backlog

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

FAQPage Schema
How do I clean up dormant backlog phases in a repository?

Cleaning up dormant backlog phases involves reviewing 999.x directory items, promoting useful ones into the active sequence, and deleting stale entries to keep the repository planning state consistent.

How do I promote backlog items into an active roadmap?

Promoting backlog items into an active roadmap requires renaming 999.x phase directories into the scheduled delivery sequence and rewriting roadmap references to preserve milestone tracking consistency.

What is the best way to manage stale planning artifacts during repository maintenance?

Managing stale planning artifacts during repository maintenance involves triaging phase directories, removing obsolete entries, updating roadmap references, and committing the final directory structure to maintain alignment.

Does reviewing backlog phases require manual confirmation before removing items?

Yes, reviewing backlog phases requires explicit user confirmation for decisions to promote, retain, or remove items before executing filesystem operations and committing the updated planning records.

Can I use this workflow to update roadmap entries without breaking milestone tracking?

Updating roadmap entries through this workflow rewrites planning records and commits the result, ensuring the active directory structure stays aligned with milestone tracking without breaking consistency.

What limitations exist when triaging 999.x phase directories for active work?

Triaging 999.x phase directories requires read-write filesystem access and operates within repository maintenance workflows, meaning it cannot process phases lacking directory structures or roadmap references.