skills.rest
microsoft
microsoftOFFICIAL
Explore all skills by this author →
Website𝕏@OpenAtMicrosoftGitHub

apm-strategy

Coordinate APM project strategy changes from governance signals in repository files.

3.5k|319|Updated Sep 18, 2025
Search Tags:#strategy#governance#evidence-based#change-management#project-positioning#release-communication
One-click install
npx skills add https://github.com/microsoft/apm --skill apm-strategy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: apm-strategy
Source: https://github.com/microsoft/apm/tree/main/.apm/skills/apm-strategy
Command: npx skills add https://github.com/microsoft/apm --skill apm-strategy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate strategy changes for the APM project based on governance signals.

Core Features & Use Cases

  • Triggers on edits to README.md, MANIFESTO.md, PRD.md, CHANGELOG.md, and release workflows to prompt strategic reviews.
  • Enforces evidence-based claims, requires breaking-change entries in CHANGELOG, and triages external PRs to prioritize external alignment.
  • Communicates strategic decisions clearly to stakeholders to reduce ambiguity and misalignment.

Quick Start

Review recent repository changes and propose an evidence-backed strategy update.

Frequently Asked Questions about apm-strategy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I align project changes with evidence-driven strategy?▼

To align project changes with evidence-driven strategy, configure governance signals to trigger strategic reviews on edits to key project files like PRD.md and README.md, ensuring all claims are backed by evidence before communicating decisions to stakeholders.

How do I enforce CHANGELOG entries for breaking changes in release workflows?▼

Enforcing CHANGELOG entries for breaking changes in release workflows requires setting up governance rules that block releases unless the CHANGELOG.md file is updated, ensuring all breaking modifications are explicitly documented before shipping.

What is the best way to triage external PRs for project positioning?▼

The best way to triage external PRs for project positioning is to apply governance signals that review incoming contributions against your evidence-based strategy, prioritizing changes that align with external stakeholder needs and strategic goals.

How does governance-based strategy coordination work for product management?▼

Governance-based strategy coordination works by automatically triggering strategic decision reviews when edits occur in MANIFESTO.md, issue templates, or release workflows, reducing ambiguity and enforcing evidence-based project alignment.

Can I discourage competitor name-dropping in shipped copy automatically?▼

Yes, you can discourage competitor name-dropping in shipped copy by enforcing governance rules that review release communication and documentation edits, ensuring shipped copy remains focused on evidence-based claims rather than competitor comparisons.

When do I need to trigger a strategic review for product documentation?▼

You need to trigger a strategic review for product documentation whenever edits are made to README.md, MANIFESTO.md, PRD.md, CHANGELOG.md, or release workflows, ensuring all documentation changes align with the overarching evidence-driven strategy.

Related Skills

Explore More Product & Management Skills→
IngrammlIngramml

Documentation Structure

Generate standardized documentation templates and directory structures for repositories.

Community
Intermediate
githubnextgithubnext
4

apm-strategy

Enforce strategic consistency across project artifacts and release workflows.

Official
Intermediate
penpotpenpot
58.3k

update-changelog

Generate CHANGES.md entries from GitHub milestone issues and PRs.

Official
Advanced
insightwavesmithinsightwavesmith

code-analyzer

Analyze code changes to identify those meeting evidence-shape-check criteria.

Community
Intermediate