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.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

APM Strategy Skill

Name: apm-strategy
Rating: 76 (1 reviews)
Author: microsoft

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.

Repository: microsoft/apm
Path: .agents/skills/apm-strategy/SKILL.md
Commit: 634f7b6

Last updated: 8 days ago
First committed: about 2 months ago

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.