backlog-ops

Synchronize roadmap and backlog documents across task hierarchies.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/GrinRus/ai_driven_dev_v2 --skill backlog-ops-grinrus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backlog-ops
Source: https://github.com/GrinRus/ai_driven_dev_v2/tree/main/.agents/skills/backlog-ops
Command: npx skills add https://github.com/GrinRus/ai_driven_dev_v2 --skill backlog-ops-grinrus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams frequently face misalignment between high-level roadmap goals and actionable backlog tasks, leading to duplicated work, missed dependencies, and unclear priorities during software delivery. This Skill eliminates that friction by enforcing strict synchronization rules and validation checks between planning documents.

Core Features & Use Cases

  • Task Lifecycle Management: Select, split, create, promote, and close local tasks while maintaining the canonical wave -> epic -> slice -> local task hierarchy.
  • Document Synchronization: Ensures all changes to roadmap.md are reflected in backlog.md with no orphaned task IDs or misaligned priorities.
  • Quality Validation: Enforces strict quality bars for local tasks to ensure every task is reviewable, has a single clear output, and explicit dependencies before work begins.
  • Use Case: A product manager can use this Skill to decompose a large epic into small, verifiable local tasks, promote the next actionable task to the backlog queue, and track cross-wave dependencies without manual cross-checking of multiple planning files.

Quick Start

Use the backlog-ops skill to decompose the current active slice into individual reviewable local tasks and sync all changes to both the roadmap and backlog documents.

Frequently Asked Questions about backlog-ops

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

FAQPage Schema
How do I keep my product roadmap and backlog tasks synchronized without manual cross-checking?

To keep your product roadmap and backlog synchronized without manual cross-checking, enforce strict document synchronization rules. This eliminates misaligned priorities by ensuring all roadmap changes reflect in the backlog with no orphaned task IDs.

What is the best way to decompose a large epic into reviewable local tasks?

Decomposing a large epic into reviewable local tasks requires enforcing strict quality validation bars. Every local task must be reviewable, produce a single clear output, and list explicit dependencies before any development work actually begins.

How does dependency tracking work across wave and epic hierarchies in backlog planning?

Dependency tracking across wave and epic hierarchies works by maintaining a canonical wave, epic, slice, and local task structure. This canonical hierarchy allows you to track cross-wave dependencies automatically as tasks are promoted to the backlog queue.

Can I use this approach to manage task promotion rules for my backlog queue?

You can manage task promotion rules for your backlog queue by enforcing validation checks during task lifecycle management. This ensures only qualified local tasks are promoted from an active slice into the actionable backlog queue.

Why does my backlog planning have orphaned task IDs and misaligned priorities?

Your backlog planning has orphaned task IDs and misaligned priorities due to a lack of strict synchronization between your roadmap and backlog documents. Enforcing document structure validation eliminates this friction and prevents duplicated work.