backlog-management

backlog-management is a skill for Claude Code from microsoft/hve-core. It costs 49 tokens per session (5,149 once invoked), scanned C, original, MIT.

A shared set of rules for managing work items in Azure DevOps, GitHub, and Jira. It covers how to find, compare, organize, sanitize, and safely change planned work.

In plain words
What is it for?
Use it to discover requests, triage existing items, turn product requirements into work-item plans, plan sprints, compare possible duplicates, and prepare or resume tracker updates.
Why use it?
Backlog work can become duplicated, inconsistently formatted, or changed without the right level of approval. These conventions make planning and execution more consistent across trackers.

Skill for Claude Code ✓ vendor

Written for Claude Code: user-invocable in frontmatter.

Good fit Use it to discover requests, triage existing items, turn product requirements into work-item plans, plan sprints, compare possible duplicates, and prepare or resume tracker updates.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/microsoft/hve-core/backlog-management
About the project

HVE Core is a collection of agents, prompts, coding instructions, and skills for building repeatable software-development workflows with GitHub Copilot. It is intended for individuals and teams that want structured AI-assisted research, planning, implementation, and review, while the catalogue entries provide many of its reusable workflow components.

microsoft/hve-core · 1,606 stars · on GitHub

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add microsoft/hve-core --skill backlog-management
Clone the repo
git clone --depth 1 https://github.com/microsoft/hve-core

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for backlog-management

README.md
[![agentmods](https://agentmods.dev/badge/skills/microsoft/hve-core/backlog-management/github.svg)](https://agentmods.dev/skills/microsoft/hve-core/backlog-management)
Your own site
<a href="https://agentmods.dev/skills/microsoft/hve-core/backlog-management"><img src="https://agentmods.dev/badge/skills/microsoft/hve-core/backlog-management/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for backlog-management

Your own site · 80×15
<a href="https://agentmods.dev/skills/microsoft/hve-core/backlog-management"><img src="https://agentmods.dev/badge/skills/microsoft/hve-core/backlog-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,149 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 15 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high YARA Match · line 3
    YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).
    Fix: Remove offensive tool references and exploit code. Legitimate agent skills should not contain penetration testing tools, exploit frameworks, or reconnaissance utilities.
  • high Prompt Injection · line 135
    Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
    Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
  • high Prompt Injection · line 142
    Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
    Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
  • high Privilege Escalation · line 265
    Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
    Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
  • medium Memory Poisoning · line 72
    Skill attempts to fill the context window with filler content, displacing legitimate instructions and safety constraints. This can degrade agent performance or bypass safety boundaries.
    Fix: Implement context-window management that detects and rejects padding or stuffing attempts. Prioritize system instructions over user-injected content.
  • medium Prompt Injection · line 72
    Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
    Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
  • medium Prompt Injection · line 74
    Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
    Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
  • medium Prompt Injection · line 75
    Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
    Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
  • medium Excessive Agency · line 82
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
  • medium Excessive Agency · line 194
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
  • medium Prompt Injection · line 192
    Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
    Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
  • medium Prompt Injection · line 194
    Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
    Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
  • medium Excessive Agency · line 195
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
  • medium Prompt Injection · line 196
    Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
    Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
  • medium Prompt Injection · line 269
    Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
    Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00049 $0.05149
Opus 5.5 $0.00020 $0.02060
Sonnet 5.5 $0.00010 $0.01030
Haiku 4.5 $0.00005 $0.00515

Measured 1mo ago against content hash 3c54f76417c1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

backlog-management scanned grade C with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Hidden instructionshighPrompt injection

Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.

<!-- markdown-table-prettify-ignore-start -->
.github/skills/project-planning/backlog-management/SKILL.md · 338 lines

How it starts

The opening of the file, as written. The whole thing — 338 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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.

How This Skill Is Organized

  • This file — the platform-agnostic core: platform resolution, planning-file lifecycle, directory conventions, planning-type enum, scope normalization, reference-ID scheme, similarity assessment, autonomy tiers, content sanitization, state persistence, and human review triggers.
  • references/workflows.md — the platform-agnostic workflow protocols (discovery, triage, execution), the platform binding resolution table, the operation contract, dry-run and error handling, and the shared planning-file templates.
  • references/story-quality.md — work-item quality at epic, feature, user story, and task level: title and description conventions, acceptance criteria, definition of done, scope and sizing signals, evidence sourcing, completeness dimensions, and the authoring and refinement coaching loop.
  • references/sprint-planning.md — the platform-agnostic sprint and iteration planning protocol: container binding, coverage and capacity analysis, gap and dependency detection, grooming recommendations, and the sprint-plan template.
  • references/task-planning.md — assigned-work retrieval and enrichment: identity-scoped retrieval, repository-context gathering, discussion integration, and the implementation handoff record.
  • references/ado.md — Azure DevOps platform delta: MCP ADO command surface, namespaced field vocabulary, the WI reference prefix, action verbs, PRD hierarchy (Epic → Feature → User Story), relationship semantics, and work-item tracking paths.
  • references/ado-pull-request.md — Azure DevOps pull request creation: work item discovery and linking, reviewer identification from git history, the seven-phase creation protocol, and its planning-file formats.
  • references/ado-build-info.md — Azure DevOps build and pipeline information: pipeline tool surface, build location by PR, build ID, or branch, log extraction, and summarization rules.
  • references/github.md — GitHub platform delta: MCP GitHub command surface, supported operations, field vocabulary and field matrix, search syntax, issue body and type strategy, label taxonomy, milestone protocol, the IS reference prefix, action verbs, community-communication guardrails, PRD sub-issue hierarchy, and issue tracking paths.
  • references/jira.md — Jira platform delta: command surface (delegated to the jira skill), field vocabulary, the JI reference prefix, action verbs, PRD hierarchy and field-mapping rules, triage and update decisions, and Jira tracking paths.

Read the full file on GitHub · 338 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago Changed · +15 tokens per session 3c54f76417c1
  2. 2mo ago Changed 4803a12b8adf
  3. 2mo ago First seen · 338 lines · 34 tokens per session scan C db85335cb0c4

Subscribe to this mod's changes

backlog-management is a skill published in the GitHub repository microsoft/hve-core (1,606 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 5,149 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

backlog-management compared with skills from other repositories

backlog-management next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
backlog-managementmicrosoft/hve-coreSkill1.6ktodayMITC49Claude Code
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79kyesterdayMITA200Claude Code, Codex
playwright-climicrosoft/playwrightSkill100kyesterdayApache-2.0A19Claude Code
browser-automationopenclaw/openclawSkill394ktodayMITA36Claude Code
systematic-debuggingobra/superpowersSkill314k4d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code