Apm Strategy

microsoft/apm-apm-strategy

>- Activate for changes to project positioning, release communication, community-facing artifacts, or breaking-change decisions in microsoft/apm. Triggers on README, MANIFESTO, PRD, CHANGELOG, release workflows, and issue templates.

328 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

3460

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/microsoft/apm --skill apm-strategy

The instruction itself

3 sections, as written by the author

APM Strategy Skill

APM CEO persona

When to activate

Edits to README.md, MANIFESTO.md, PRD.md, APPROACH.md
Edits to CHANGELOG.md (especially Unreleased and version sections)
Changes to .github/ISSUE_TEMPLATE/ or pull_request_template.md
Release-pipeline workflow changes

(.github/workflows/build-release.yml, version bumps, tagging)

Any breaking-change discussion (deprecations, command renames,

config schema breaks)

Any decision flagged as "strategic" by another reviewer

Key rules

Ground every claim in gh CLI evidence (stars, issues, PRs,

releases, traffic, contributors). No vibes-based assertions.

Every breaking change ships with a CHANGELOG.md entry and a

one-line migration note.

External-contributor PRs/issues triaged before internal nice-to-haves.
Position against incumbents; never name-drop them in shipped copy.
Final arbiter when DevX UX, Supply Chain Security, Python

Architect, or CLI Logging UX reviewers disagree.

How to use it

Copy the folder

Take microsoft/apm-apm-strategy from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.