apm-strategy

Enforce strategic consistency across project artifacts and release workflows.

4|1|Updated May 7, 2026

Search Tags:#release management #project management #decision support #APM #strategic alignment

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: apm-strategy
Source: https://github.com/githubnext/apm/tree/main/.apm/skills/apm-strategy
Command: npx skills add https://github.com/githubnext/apm --skill apm-strategy-githubnext

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining strategic consistency across various project artifacts and decisions in the APM ecosystem.

Core Features & Use Cases

Project Positioning: Aligns README, MANIFESTO, and PRD with strategic direction.
Release Communication: Manages CHANGELOG entries and release workflows.
Community Artifacts: Keeps issue templates and workflow scripts in sync with strategic goals.
Breaking Change Management: Ensures breaking changes are communicated and documented properly.
Decision Arbitration: Serves as a final arbiter for conflicting decisions among key stakeholders.

Quick Start

Activate the apm-strategy skill after making changes to project positioning documents to ensure alignment with strategic objectives.

Frequently Asked Questions about apm-strategy

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

FAQPage Schema

How do I maintain strategic alignment across project positioning documents like README and PRD?▼

To maintain strategic alignment, this Skill evaluates your README, MANIFESTO, and PRD against strategic direction, triggering checks whenever these project positioning documents are modified to ensure consistency.

What is the best way to manage release communication and breaking changes in project management?▼

Managing release communication is handled by validating CHANGELOG entries and release workflows, ensuring breaking changes are properly documented and communicated to maintain strategic project consistency.

How do I arbitrate conflicting decisions among key stakeholders during release management?▼

To arbitrate conflicting decisions, this Skill serves as a final arbiter, enforcing rules based on gh CLI evidence and triage processes to resolve stakeholder disputes over breaking changes.

Does this Skill require specific dependencies to manage community-facing artifacts?▼

No external dependencies are required to manage community-facing artifacts; it relies on internal scripts to keep issue templates and workflow scripts in sync with your strategic goals.

When should I trigger strategic alignment checks for external contributions?▼

You should trigger strategic alignment checks when processing external contributions, using triage processes and gh CLI evidence to ensure community artifacts and breaking-change decisions remain strategically consistent.