APM Strategy
Review project positioning, release strategy, and breaking changes for APM.
Installation
- Make sure Claude is on your device and in your terminal.
Skills load from
~/.claude/skills/when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then runclaudein any terminal to verify.One-time setupnpm i -g @anthropic-ai/claude-codeAlready have it? Skip ahead.
- Paste into Claude Code or into your terminal.
This copies the whole skill folder into
~/.claude/skills/apm-strategy-microsoft/— the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.Faster alternative (instruction-only skills)
Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.
Quick install (SKILL.md only)Sign up to copy - Restart Claude Code.
Quit and reopen Claude Code (or any other agent that loads from
~/.claude/skills/). New skills are picked up on startup. - Just ask Claude.
Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.
Prefer to read the source first? Open on GitHub.
When Claude uses it
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.
What this skill does
APM Strategy Skill
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/orpull_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
ghCLI evidence (stars, issues, PRs, releases, traffic, contributors). No vibes-based assertions. - Every breaking change ships with a
CHANGELOG.mdentry 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.
Related skills
App Store Listing Audit
coreyhaines31
Analyze your app listing against best practices and get a prioritized optimization plan.
Co-Marketing Partnerships
coreyhaines31
Find ideal partners and plan joint marketing campaigns with other companies.
Cold Email Writer
coreyhaines31
Write B2B cold emails and follow-up sequences designed to get replies.
Community-Led Growth
coreyhaines31
Build and grow online communities to drive product adoption and customer loyalty.