backlog-plan
Backlog Plan
Read-only backlog planning for Azure DevOps, GitHub, and Jira. This command resolves the backing tracker at runtime, selects a planning mode, and executes it through the shared conventions and reference structure of the backlog-management skill. It produces planning files that a separate execution pass acts on.
This command never mutates a tracker. It creates, updates, and reads files under the platform tracking root, and it reads from the tracker. Every create, update, transition, link, close, and comment belongs to backlog-execute.
When to Use
Use this command to plan backlog work on any supported platform:
- Discover candidate work from a user request, a set of documents, or a search.
- Retrieve the work assigned to you and enrich it into an implementation-ready handoff.
- Triage existing items and recommend field, label, priority, or status changes.
- Plan a sprint, iteration, or milestone against coverage, capacity, dependencies, and gaps.
- Resume an interrupted planning workflow from its durable artifacts.
Use backlog-execute instead when the intent is to apply changes to a tracker. Use functional-planner instead when the input is a PRD and the output is a work-item hierarchy.