A set of rules for managing GitHub issues, which are tracked tasks or bug reports, using a project's backlog conventions.

Creating and filing issues, sorting untriaged work, reviewing backlog priorities, and checking whether open issues are still valid.

It prevents inconsistent labels, milestones, priorities, and triage decisions when deciding what work should be done next.

How joshsmithxrm/power-platform-developer-suite configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to joshsmithxrm/power-platform-developer-suite. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/joshsmithxrm/power-platform-developer-suite/main/.claude/skills/backlog/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/joshsmithxrm/power-platform-developer-suite

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/joshsmithxrm/power-platform-developer-suite/backlog/github.svg)](https://agentmods.dev/skills/joshsmithxrm/power-platform-developer-suite/backlog)

Your own site

<a href="https://agentmods.dev/skills/joshsmithxrm/power-platform-developer-suite/backlog"><img src="https://agentmods.dev/badge/skills/joshsmithxrm/power-platform-developer-suite/backlog/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/joshsmithxrm/power-platform-developer-suite/backlog"><img src="https://agentmods.dev/badge/skills/joshsmithxrm/power-platform-developer-suite/backlog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 660 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00039	$0.00660
Opus 5.5	$0.00016	$0.00264
Sonnet 5.5	$0.00008	$0.00132
Haiku 4.5	$0.00004	$0.00066

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

Security

Grade A, and why

backlog scanned grade A with 0 findings 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/backlog/SKILL.md · 78 lines

How it starts

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

Backlog

Manage GitHub issues using the label taxonomy, milestone conventions, and triage rules defined in docs/BACKLOG.md.

When to Use

"Create an issue for X"
"File a bug for X"
"Triage the backlog"
"Groom issues"
"What should we work on next?"
"Review backlog priorities"
After completing work that reveals follow-up issues

Reference

Read docs/BACKLOG.md at the start of every backlog operation - it is the source of truth for labels, milestones, and rules. Read REFERENCE.md §1 "Label taxonomy" before classifying any issue.

Process

1. Parse Arguments

/backlog create <description> - create a new issue
/backlog triage - triage untriaged inbox
/backlog review - review backlog for promotion
/backlog validate - verify open issues are still valid
/backlog (no args) - show backlog summary

2. Read Rules

cat docs/BACKLOG.md

3. Execute Operation

Create Issue

Determine type: label (bug/enhancement/docs/performance/refactor)
Determine area: label (auth/cli/data/extension/plugins/tui)
Ask user for milestone or default to none
Check if an epic: label applies
Ask user for priority: label if not obvious
Create:

gh issue create --title "<title>" --body "<body>" --label "type:<type>,area:<area>" --milestone "<milestone>"

If no milestone, add status:backlog. Every issue must have at minimum one type: + one area: + either a milestone or status: label.

Triage Inbox

gh issue list --state open --limit 200 --json number,title,labels,milestone --jq '[.[] | select(.milestone == null) | select(.labels | map(.name) | any(startswith("status:")) | not)]'

Read REFERENCE.md §2 "Mandatory verification" for the per-issue checklist before presenting any issue to the user. Read REFERENCE.md §3 "Triage decision rules" for the categorization heuristic.

Review Backlog

Surface ready-to-promote issues from status:backlog based on completion criteria + dependency satisfaction. See REFERENCE.md §4 "Promotion rules".

Read the full file on GitHub · 78 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

REFERENCE.md 3.8 KB

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.

1mo ago First seen · 78 lines · 39 tokens per session scan A 18a1c094abbc

Subscribe to this mod's changes

backlog is a skill published in the GitHub repository joshsmithxrm/power-platform-developer-suite (7 stars, last pushed 4d ago), licensed MIT. It adds 39 tokens to every session and 660 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Project management cli dataverse dotnet dynamics365 mcp power-platform

dynamics365-expert

Expert in Dynamics 365 platform, model-driven apps, canvas apps, Power Automate flows, Dataverse, plugins, and custom workflows. Use when the user mentions Microsoft platforms, ERP, CRM, business apps, the Power Platform, or Dataverse, or when the task involves Dynamics 365 Applications, Dataverse Platform…

personamanagmentlayer/pcl · 80 tokens

quality

Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.

google-gemini/gemini-cli · 24 tokens

follow-up-after-call

Use after a completed customer, prospect, partner, or important internal sales call, discovery session, demo, or conversation, including when the user supplies or uploads a transcript, notes, recording summary, or other grounded evidence. Advise on, assess, qualify, recap, and produce seller-ready follow-up actions…

XiaomiMiMo/MiMo-Code · 69 tokens

power-platform-developer-suite: Skill for Claude Code