Backlog Execute

Mutating backlog execution for Azure DevOps, GitHub, and Jira. This command resolves the backing tracker at runtime and applies changes through the shared conventions and reference structure of the backlog-management skill.

Every operation this command runs is externally visible. The five safety protocols below are not optional refinements; they are the reason a single command can be trusted with write access to three trackers.

When to Use

• Create a single work item through guided field collection.
• Process a reviewed handoff file into sequential create, update, link, transition, close, and comment operations.
• Resume an interrupted execution without duplicating completed work.

Use backlog-plan instead for discovery, triage, sprint planning, or any read-only analysis. A handoff file is normally produced there and reviewed by a human before it reaches this command.

Direct Invocation

This command is user-invocable. When a user runs it directly, build the missing context collaboratively rather than demanding a fully formed request. The bar for entry is low; the bar for mutating is not.

Infer what can be inferred safely, from the live conversation, an item key or URL the user names, the tracking root already present under .copilot-tracking/, the repository remote, and which platform credentials and tools are actually available. Confirm an inference before acting on it. Ask only for what is missing and mutation-critical, one focused question at a time rather than as an intake form.