gsd-add-backlog

Automate backlog item creation and ROADMAP.md updates with 999.x numbering.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

backlog management for product initiatives is tedious and error-prone; this skill automates creation, organization, and maintenance of backlog items and future-phase roadmaps to save time and reduce manual errors.

Core Features & Use Cases

  • Automates backlog item generation, phase directory creation, and ROADMAP.md updates.
  • Supports adding backlog items with 999.x numbering and automatically creates corresponding directories under .planning/phases.
  • Use case: a product manager describes a new idea and the tool adds it to the backlog with a generated slug and phase placeholder.

Quick Start

Describe your backlog idea and run the gsd-add-backlog workflow to add it to the backlog.

Frequently Asked Questions about gsd-add-backlog

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

FAQPage Schema
How do I automate backlog creation and phase planning for product development?

Backlog creation and phase planning can be automated by generating backlog items with 999.x numbering, creating phase directories under .planning/phases, and updating ROADMAP.md automatically based on your described idea.

What is the best way to add a new product initiative to a structured backlog?

Adding a product initiative to a structured backlog is best handled by generating a slug, assigning a 999.x backlog number, and creating a corresponding phase placeholder directory to persist planning artifacts.

Does automated roadmap generation work with existing phase directories?

Automated roadmap generation works with structured product development workflows by creating phase directories under .planning/phases and persisting updates directly into the ROADMAP.md file.

How do I update ROADMAP.md when adding new backlog items?

Updating ROADMAP.md when adding backlog items happens automatically: the workflow generates the entry, assigns 999.x numbering, creates the phase directory, and writes the updates to the roadmap file.

Can I use this to organize future phase roadmaps without manual numbering?

Yes, you can organize future phase roadmaps without manual numbering because the workflow automatically applies 999.x backlog numbering and generates phase placeholders during the creation process.

Do I need any dependencies to automate backlog item generation?

No dependencies are required to automate backlog item generation; the workflow independently handles 999.x numbering, phase directory creation, and ROADMAP.md updates within your repository.