メニュー
Read-only backlog planning for Azure DevOps, GitHub, and Jira. Use to discover, triage, sprint-plan, or resume without mutating a tracker.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/microsoft/hve-core --skill backlog-planコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SOC 職業分類に基づく
SKILL.md を表示中
| name | backlog-plan |
| description | Read-only backlog planning for Azure DevOps, GitHub, and Jira. Use to discover, triage, sprint-plan, or resume without mutating a tracker. |
| license | MIT |
| user-invocable | true |
| argument-hint | [discover|my-work|task-plan|triage|sprint|resume] [scope or query] |
| compatibility | Hosts: vscode, github-coding-agent. Requires read access to the target tracker (Azure DevOps, GitHub, or Jira); for Jira, JIRA_BASE_URL plus JIRA_API_TOKEN or JIRA_PAT. |
| metadata | {"authors":"microsoft/hve-core","spec_version":"1.0.0","last_updated":"2026-08-01"} |
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 skill. It produces planning files that a separate execution pass acts on.
backlog-managementThis 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.
Use this command to plan backlog work on any supported platform:
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.
Run the Platform Resolution section of the backlog-management skill before any planning work. Carry its resolved platform and readiness verdict forward. When resolution is ambiguous, resolve it there rather than assuming a tracker here.
Every mode below is read-only, so a platform inferred from preflight success may proceed without the confirmation a mutating workflow requires.
Classify the request into exactly one mode. When the argument names a mode, use it. Otherwise infer from these signals, and when two modes remain plausible, state both with a brief rationale and ask.
| Mode | Signals | Protocol |
|---|---|---|
discover | discover, find, search, extract, gaps, roadmap, backlog brief, from a document | Discovery workflow in the workflows reference |
my-work | my items, assigned to me, my queue, what am I working on | Stage 1 of the task-planning reference |
task-plan | task planning, prepare for implementation, hand off to research | Stage 2 of the task-planning reference |
triage | triage, classify, categorize, prioritize, duplicates, untriaged | Triage workflow in the workflows reference plus the platform's Triage Delta |
sprint | sprint, iteration, milestone, release, capacity, velocity, coverage | The sprint-planning reference plus the platform's Sprint Planning Delta |
resume | resume, continue, next step, suggest, where was I | Resumption below |
Follow the named protocol. Resolve every command, field name, action verb, and container name through the active platform reference rather than assuming a literal from a template.
When a mode authors or evaluates item content, apply the story-quality reference of the backlog-management skill at the level the item occupies. Recommending an item as ready without checking its completeness dimensions is the most common failure of a planning pass.
Summarize what was produced, name the planning files by path, and state the next action. When the natural next step is applying changes, name backlog-execute and the handoff file it would consume; do not apply them here.
The resume mode reads the durable planning artifacts rather than the conversation, because the conversation may have been summarized or lost.
planning-log.md first to establish the active workflow, planning type, scope, and last completed step.Stop and ask rather than improvising when the logs are missing, when a completed operation has no recorded item key, or when a placeholder cannot be resolved from the rebuilt mapping. An unresolved mapping is a blocker, not a value to guess.
planning-log.md.backlog-management skill does not resolve; the conventions this command depends on are unavailable.This body is deliberately thin. Every protocol lives in the backlog-management skill so that backlog-plan, backlog-execute, and the Backlog Manager agent share one definition rather than three copies. Activate backlog-management by name; when it does not resolve, warn the user that platform resolution, workflow protocols, and per-platform command surfaces are unavailable, and stop rather than improvising them here.
That skill supplies: