backlog-management
Backlog Management
Shared, platform-agnostic conventions for backlog managers across Azure DevOps, GitHub, and Jira. This skill owns the structural core that every platform reuses: how planning files are named and laid out, how planned items are identified, how candidate work is compared to existing work, how autonomy gates mutations, how outbound text is sanitized, and how an interrupted workflow resumes. Each platform contributes only its small delta (the command surface, field vocabulary, reference-ID prefix, and action verbs) through a per-platform reference.
When to Use
Use this skill when running any backlog workflow for a supported platform:
- Discovery — turn user requests, artifacts, or queries into candidate work items.
- Triage — assess existing items, recommend field, label, priority, and status changes, and flag duplicates.
- PRD-to-work-item planning — map a PRD into a validated work-item hierarchy for a separate execution pass.
- Sprint and iteration planning — analyze a delivery window for coverage, capacity, dependencies, and gaps, and recommend grooming candidates.
- Execution — process a reviewed handoff into sequential create, update, transition or move, and comment operations.
Read the platform-agnostic conventions below, then load the reference that matches the active platform for its concrete command surface and vocabulary.