pm-skills-mcp 2.5.2 → 2.8.0

package/README.md

@@ -119,7 +119,7 @@ PM-Skills MCP is built on [pm-skills](https://github.com/product-on-purpose/pm-s
 **Not sure which to use?** See the [Comparison](#comparison) section below.
 <!-- ========== END ENHANCED ========== -->
 
-**_One connection. 25 skills. Any MCP client._**
+**_One connection. 27 skills. Any MCP client._**
 
 ### Why MCP?
 
@@ -486,9 +486,9 @@ See the [pm-skills authoring guide](https://github.com/product-on-purpose/pm-ski
 ├─────────────────────────────────────────────────────────────┤
 │                                                             │
 │   ┌─────────────┐   ┌─────────────┐   ┌─────────────┐       │
-│   │   38 Tools  │   │  Resources  │   │  3 Prompts  │       │
+│   │   40 Tools  │   │  Resources  │   │  3 Prompts  │       │
 │   │             │   │             │   │             │       │
-│   │ • 25 skills │   │ • templates │   │ • kickoff   │       │
+│   │ • 27 skills │   │ • templates │   │ • kickoff   │       │
 │   │ • 5 flows   │   │ • examples  │   │ • lean      │       │
 │   │ • 8 utils   │   │ • skills    │   │ • quick-prd │       │
 │   │             │   │             │   │             │       │
@@ -496,7 +496,7 @@ See the [pm-skills authoring guide](https://github.com/product-on-purpose/pm-ski
 │                                                             │
 │   ┌─────────────────────────────────────────────────────┐   │
 │   │              Embedded PM-Skills Library             │   │
-│   │     25 skills × (SKILL.md + TEMPLATE + EXAMPLE)     │   │
+│   │     27 skills × (SKILL.md + TEMPLATE + EXAMPLE)     │   │
 │   └─────────────────────────────────────────────────────┘   │
 │                                                             │
 └─────────────────────────────────────────────────────────────┘
@@ -509,7 +509,7 @@ See the [pm-skills authoring guide](https://github.com/product-on-purpose/pm-ski
 
 ### Tools
 
-PM-Skills MCP wraps each skill from [pm-skills](https://github.com/product-on-purpose/pm-skills) as an MCP tool. The **25 skill tools** (like `pm_prd`, `pm_hypothesis`) generate PM artifacts, while **5 workflow tools** and **8 utility tools** help you orchestrate and validate skill usage. See the [Comparison](#comparison) section for when to use MCP tools vs file-based slash commands.
+PM-Skills MCP wraps each skill from [pm-skills](https://github.com/product-on-purpose/pm-skills) as an MCP tool. The **27 skill tools** (like `pm_prd`, `pm_hypothesis`, `pm_acceptance_criteria`, `pm_pm_skill_builder`) generate PM artifacts, while **5 workflow tools** and **8 utility tools** help you orchestrate and validate skill usage. See the [Comparison](#comparison) section for when to use MCP tools vs file-based slash commands.
 
 Every skill tool accepts these parameters:
 
@@ -694,7 +694,7 @@ npm install -g pm-skills-mcp
 **Install a pinned release:**
 
 ```bash
-npm install -g pm-skills-mcp@2.5.2
+npm install -g pm-skills-mcp@2.7.0
 ```
 
 [![npm version](https://img.shields.io/npm/v/pm-skills-mcp?style=for-the-badge&label=npm)](https://www.npmjs.com/package/pm-skills-mcp)
@@ -703,15 +703,7 @@ npm install -g pm-skills-mcp@2.5.2
 From `v2.4.0` onward, `pm-skills-mcp` directly tracks `pm-skills` release versions.
 Pinned source compatibility metadata is declared in `pm-skills-source.json` for each release.
 
-Latest release notes:
-- [`docs/releases/Release_v2.5.2.md`](docs/releases/Release_v2.5.2.md)
-- [`docs/releases/Release_v2.5.1.md`](docs/releases/Release_v2.5.1.md)
-- [`docs/releases/Release_v2.5.0.md`](docs/releases/Release_v2.5.0.md)
-- [`docs/releases/Release_v2.4.3.md`](docs/releases/Release_v2.4.3.md)
-- [`docs/releases/Release_v2.4.2.md`](docs/releases/Release_v2.4.2.md)
-- [`docs/releases/Release_v2.4.1.md`](docs/releases/Release_v2.4.1.md)
-- [`docs/releases/Release_v2.4.0.md`](docs/releases/Release_v2.4.0.md)
-- Published release tag: [`v2.5.2`](https://github.com/product-on-purpose/pm-skills-mcp/releases/tag/v2.5.2)
+Latest: [`docs/releases/Release_v2.7.0.md`](docs/releases/Release_v2.7.0.md) | [Previous release details](#previous-release-details) | [Full changelog](#changelog)
 
 ### Project Structure
 See [docs/reference/project-structure.md](docs/reference/project-structure.md) for detailed descriptions.
@@ -724,7 +716,7 @@ pm-skills-mcp/
 │   ├── config.ts             # Configuration management
 │   ├── cache.ts              # Skill caching layer
 │   ├── skills/               # Skill loader and parser
-│   ├── tools/                # MCP tool handlers (38 tools)
+│   ├── tools/                # MCP tool handlers (40 tools)
 │   ├── resources/            # MCP resource handlers (skills/templates/examples + optional personas)
 │   ├── prompts/              # MCP prompt definitions (3 prompts)
 │   ├── workflows/            # Workflow bundle logic
@@ -733,7 +725,7 @@ pm-skills-mcp/
 │   ├── deliver-prd/          # Example: phase-prefixed skill directories
 │   ├── define-hypothesis/    # Each skill has SKILL.md + references/
 │   ├── discover-interview-synthesis/
-│   └── ...                   # 25 skills total
+│   └── ...                   # 27 skills total
 ├── docs/                     # Documentation
 │   ├── getting-started.md    # Complete setup and first-use guide
 │   ├── integration-guide.md  # Client-specific configuration
@@ -758,31 +750,67 @@ pm-skills-mcp/
 
 
 
+### Previous Release Details
+
+<a id="previous-release-details"></a>
+
+<details>
+<summary>v2.6.0 - Maintenance: pm-skills v2.6.0 version parity</summary>
+
+- Version and source-pin metadata aligned with `pm-skills v2.6.0`.
+- No MCP tool/resource/prompt behavior changes.
+- Release note: [`docs/releases/Release_v2.6.0.md`](docs/releases/Release_v2.6.0.md).
+
+</details>
+<details>
+<summary>v2.5.x - Persona tool support + taxonomy contract updates</summary>
+
+**v2.5.2** — Public release-doc readability cleanup.
+**v2.5.1** — Canonical `AGENTS/claude` continuity path.
+**v2.5.0** — Persona skill tool (`pm_persona`), two-axis classification model (`phase` + `classification`), embed validation hardening. Tool count: 38.
+- Release notes: [`Release_v2.5.0.md`](docs/releases/Release_v2.5.0.md) through [`Release_v2.5.2.md`](docs/releases/Release_v2.5.2.md).
+
+</details>
+<details>
+<summary>v2.4.x - Direct version tracking with pm-skills</summary>
+
+**v2.4.3** — Release metadata/link alignment patch.
+**v2.4.2** — Governance + structure-doc alignment.
+**v2.4.1** — Version/pin parity patch.
+**v2.4.0** — Adopted direct version tracking with `pm-skills`. Added `pm-skills-source.json` for reproducible embeds. Resource URI contract tests. Tool count: 36.
+- Release notes: [`Release_v2.4.0.md`](docs/releases/Release_v2.4.0.md) through [`Release_v2.4.3.md`](docs/releases/Release_v2.4.3.md).
+
+</details>
+<details>
+<summary>v2.1.0 and earlier</summary>
+
+**v2.1.0** — Flat skill structure alignment with pm-skills v2.x. Resource URIs flattened.
+**v1.1.0** — Comprehensive documentation suite, platform compatibility.
+**v1.0.0** — First stable release: 36 tools, caching, community governance.
+**v0.1.x** — Initial implementation: MCP server, CI/CD, npm packaging.
+- See [CHANGELOG.md](CHANGELOG.md) for full detail.
+
+</details>
+
 ### Changelog
 
 See [CHANGELOG.md](CHANGELOG.md) for full version history.
 
 | Version   | Date       | Highlights                                                    |
 | --------- | ---------- | ------------------------------------------------------------- |
-| **2.5.2** | 2026-03-04 | Public release-doc readability cleanup + 2.5.2 source-pin/runtime parity |
-| **2.5.1** | 2026-03-04 | Canonical `AGENTS/claude` continuity path + 2.5.1 source-pin/runtime parity |
-| **2.5.0** | 2026-03-02 | Persona tool support + taxonomy contract updates + 2.5.0 pin alignment |
-| **2.4.3** | 2026-02-16 | Patch release to include post-`v2.4.2` documentation/release-link updates |
-| **2.4.2** | 2026-02-16 | Governance + structure-doc alignment with pm-skills `v2.4.2` |
-| **2.4.1** | 2026-02-16 | Patch version/pin parity with pm-skills `v2.4.1` |
-| **2.4.0** | 2026-02-16 | Direct version tracking with pm-skills + pinned source metadata |
-| **2.1.0** | 2026-01-27 | Flat skill structure alignment with pm-skills v2.x            |
-| **1.1.0** | 2026-01-21 | Comprehensive documentation suite, platform compatibility     |
-| **1.0.0** | 2026-01-21 | First stable release baseline with MCP tooling, resources, and caching |
-| **0.1.2** | 2026-01-20 | CI/CD infrastructure, branch migration to main                |
-| **0.1.1** | 2026-01-20 | GitHub Actions CI/CD, ESLint + Prettier, npm package setup    |
-| **0.1.0** | 2026-01-20 | Initial implementation baseline for PM-skills MCP integration  |
+| **2.7.0** | 2026-03-22 | 2 new skill tools (`pm_acceptance_criteria`, `pm_pm_skill_builder`), 27 skills, 40 tools |
+| **2.6.0** | 2026-03-04 | Maintenance: pm-skills v2.6.0 version/source-pin parity |
+| **2.5.0** | 2026-03-02 | Persona tool + taxonomy contract updates + embed hardening |
+| **2.4.0** | 2026-02-16 | Direct version tracking + pinned source metadata |
+| **2.1.0** | 2026-01-27 | Flat skill structure alignment with pm-skills v2.x |
+| **1.0.0** | 2026-01-21 | First stable release: 36 tools, caching, governance |
+| **0.1.0** | 2026-01-20 | Initial MCP server implementation |
 
 ### Roadmap
 
 See the [open issues](https://github.com/product-on-purpose/pm-skills-mcp/issues) for planned features.
 
-- [x] Core MCP server with all 25 PM skills
+- [x] Core MCP server with all 27 PM skills
 - [x] Workflow bundle tools
 - [x] MCP resources for direct skill access
 - [x] MCP prompts for guided workflows

package/dist/config.d.ts

@@ -11,8 +11,8 @@ export declare function loadConfig(): ServerConfig;
  */
 export declare const SERVER_INFO: {
     readonly name: "pm-skills-mcp";
-    readonly version: "2.5.2";
-    readonly description: "MCP server exposing 25 product management skills as tools";
+    readonly version: "2.7.0";
+    readonly description: "MCP server exposing 27 product management skills as tools";
 };
 /**
  * Tool naming configuration

package/dist/config.js

@@ -81,8 +81,8 @@ export function loadConfig() {
  */
 export const SERVER_INFO = {
     name: 'pm-skills-mcp',
-    version: '2.5.2',
-    description: 'MCP server exposing 25 product management skills as tools',
+    version: '2.7.0',
+    description: 'MCP server exposing 27 product management skills as tools',
 };
 /**
  * Tool naming configuration

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pm-skills-mcp",
-  "version": "2.5.2",
+  "version": "2.8.0",
   "description": "MCP server exposing product management skills as tools, resources, and workflows",
   "main": "dist/index.js",
   "type": "module",

package/pm-skills-source.json

@@ -1,8 +1,8 @@
 {
   "pmSkillsRepository": "product-on-purpose/pm-skills",
-  "pmSkillsRef": "v2.5.2",
-  "pmSkillsVersion": "2.5.2",
-  "outputContractVersion": "2.5.2",
-  "configContractVersion": "2.5.2",
-  "updated": "2026-03-04"
+  "pmSkillsRef": "v2.8.0",
+  "pmSkillsVersion": "2.8.0",
+  "outputContractVersion": "2.8.0",
+  "configContractVersion": "2.8.0",
+  "updated": "2026-04-03"
 }

package/skills/define-hypothesis/SKILL.md

@@ -1,4 +1,3 @@
-<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
 ---
 name: define-hypothesis
 description: Defines a testable hypothesis with clear success metrics and validation approach. Use when forming assumptions to test, designing experiments, or aligning team on what success looks like.
@@ -11,6 +10,7 @@ metadata:
   frameworks: [triple-diamond, lean-startup, design-thinking]
   author: product-on-purpose
 ---
+<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
 # Hypothesis
 
 A hypothesis is a testable prediction about how a change will affect user behavior or business outcomes. It transforms assumptions into explicit statements that can be validated or invalidated through experimentation. Well-formed hypotheses prevent teams from building features based on untested beliefs and create shared understanding of what success looks like.

package/skills/define-jtbd-canvas/SKILL.md

@@ -1,4 +1,3 @@
-<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
 ---
 name: define-jtbd-canvas
 description: Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job. Use when deeply understanding customer motivations, designing for jobs, or reframing product positioning.
@@ -11,6 +10,7 @@ metadata:
   frameworks: [triple-diamond, lean-startup, design-thinking]
   author: product-on-purpose
 ---
+<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
 # Jobs to be Done Canvas
 
 A Jobs to be Done (JTBD) canvas captures the complete picture of why customers "hire" products to make progress in their lives. Based on Clayton Christensen's framework, JTBD goes beyond features and demographics to understand the underlying motivations—functional, emotional, and social—that drive customer behavior.

package/skills/define-opportunity-tree/SKILL.md

@@ -1,4 +1,3 @@
-<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
 ---
 name: define-opportunity-tree
 description: Creates an opportunity solution tree mapping desired outcomes to opportunities and potential solutions. Use for outcome-driven product discovery, prioritization, or communicating product strategy.
@@ -11,6 +10,7 @@ metadata:
   frameworks: [triple-diamond, lean-startup, design-thinking]
   author: product-on-purpose
 ---
+<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
 # Opportunity Solution Tree
 
 An Opportunity Solution Tree (OST) is a visual framework for product discovery that connects business outcomes to customer opportunities and potential solutions. Developed by Teresa Torres, it prevents the common trap of jumping straight to solutions by ensuring every feature idea traces back to a customer need and measurable outcome.

package/skills/define-problem-statement/SKILL.md

@@ -1,4 +1,3 @@
-<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
 ---
 name: define-problem-statement
 description: Creates a clear problem framing document with user impact, business context, and success criteria. Use when starting a new initiative, realigning a drifted project, or communicating up to leadership.
@@ -11,6 +10,7 @@ metadata:
   frameworks: [triple-diamond, lean-startup, design-thinking]
   author: product-on-purpose
 ---
+<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
 # Problem Statement
 
 A problem statement is a concise document that frames the problem you're solving, articulates the impact on users and the business, and defines clear success criteria. It serves as the foundation for all subsequent product work by ensuring alignment on *what* problem to solve before jumping to *how* to solve it.

package/skills/deliver-acceptance-criteria/SKILL.md

@@ -0,0 +1,73 @@
+---
+name: deliver-acceptance-criteria
+description: Generates structured Given/When/Then acceptance criteria for a user story or feature slice. Use when translating product requirements into testable scenarios that cover the happy path, edge cases, error states, and non-functional expectations for engineering handoff and QA.
+phase: deliver
+version: "1.0.0"
+updated: 2026-03-22
+license: Apache-2.0
+metadata:
+  category: specification
+  frameworks: [triple-diamond, lean-startup, design-thinking]
+  author: product-on-purpose
+---
+<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
+# Acceptance Criteria
+
+Acceptance criteria define the observable behavior that must be true for a story or feature to be considered done. This skill turns feature context into concise, testable Given/When/Then scenarios that engineers and QA can verify without guessing intent.
+
+## When to Use
+
+- After a user story, PRD section, or feature slice is defined
+- When a team needs clear pass/fail conditions for implementation
+- When writing QA-ready criteria for sprint planning or handoff
+- When a story has edge cases, error paths, or non-functional expectations that should be explicit
+
+## Instructions
+
+When asked to create acceptance criteria, follow these steps:
+
+1. **Confirm the story or feature scope**
+   Identify the exact slice of work. If the scope is unclear, ask for the user story, PRD section, or feature description before drafting criteria.
+
+2. **Separate the happy path from exceptions**
+   Start with the primary success flow, then add edge cases and error states that are likely or costly if missed.
+
+3. **Write each criterion as an observable scenario**
+   Use Given/When/Then language only. Keep each criterion independently testable and avoid implementation details.
+
+4. **Cover recovery and failure behavior**
+   Describe what the user sees or can do when validation fails, a dependency is unavailable, or a save action cannot complete.
+
+5. **Include non-functional expectations**
+   Add criteria for performance, accessibility, security, reliability, or auditability when they matter to the story.
+
+6. **Avoid duplication and overlap**
+   Each criterion should test one outcome. If two criteria describe the same behavior, merge or split them until the intent is clear.
+
+7. **Review for testability**
+   Ensure a reviewer can pass or fail each criterion without interpretation. If a statement is subjective, rewrite it into a measurable outcome.
+
+## Output Contract
+
+Use `references/TEMPLATE.md` as the output format. A complete response should:
+
+- Restate the feature or story context
+- Group criteria into happy path, edge cases, error states, and non-functional criteria
+- Use explicit Given/When/Then statements for each criterion
+- Note assumptions or open questions when context is incomplete
+
+## Quality Checklist
+
+Before finalizing, verify:
+
+- [ ] The criteria map to a specific story or feature slice
+- [ ] The happy path is covered first
+- [ ] Edge cases are explicit, not implied
+- [ ] Error states include user-visible recovery behavior
+- [ ] Non-functional criteria are included when relevant
+- [ ] Each criterion is testable and has one clear outcome
+- [ ] No implementation details leak into the acceptance criteria
+
+## Examples
+
+See `references/EXAMPLE.md` for a completed example based on a realistic e-commerce checkout flow.

package/skills/deliver-acceptance-criteria/references/EXAMPLE.md

@@ -0,0 +1,92 @@
+---
+artifact: acceptance-criteria
+version: "1.0"
+created: 2026-03-22
+status: complete
+context: Acceptance criteria for a guest checkout flow in an e-commerce storefront
+---
+
+# Acceptance Criteria: Guest Checkout
+
+This example describes the acceptance criteria for a guest checkout flow that lets shoppers buy items without creating an account.
+
+## Story Context
+
+The checkout experience must let a shopper complete an order as a guest, enter shipping and payment details, and receive a confirmation after payment succeeds. The criteria below focus on the behavior a reviewer can observe in the UI and system responses.
+
+## Happy Path
+
+### AC-1: Guest Checkout Form Loads
+
+**Given** I have items in my cart and I am not signed in
+
+**When** I open the checkout page
+
+**Then** I can enter shipping information, delivery method, and payment details without being prompted to create an account
+
+### AC-2: Order Completes Successfully
+
+**Given** I have entered valid shipping and payment details
+
+**When** I submit the order
+
+**Then** I see an order confirmation page with an order number and estimated delivery date
+
+## Edge Cases
+
+### AC-3: Promo Code Can Be Applied
+
+**Given** I am on checkout and my cart qualifies for a discount
+
+**When** I enter a valid promo code and apply it
+
+**Then** the order summary updates to show the discount before I submit payment
+
+### AC-4: Shipping Address Validation Supports International Formats
+
+**Given** I enter a shipping address for a supported non-US destination
+
+**When** I continue to the next step
+
+**Then** the form accepts the address if it matches the country-specific validation rules
+
+## Error States
+
+### AC-5: Invalid Card Is Rejected
+
+**Given** I have entered shipping information but the payment card is invalid
+
+**When** I attempt to place the order
+
+**Then** I see a clear inline error message and the order is not created
+
+### AC-6: Inventory Changes During Checkout
+
+**Given** an item in my cart becomes out of stock before I submit payment
+
+**When** I place the order
+
+**Then** I am shown which item failed, my cart remains available, and I can remove the item or choose a different variant
+
+## Non-Functional Criteria
+
+### AC-7: Checkout Responds Within the Performance Budget
+
+**Given** I submit a valid order during normal operating conditions
+
+**When** the checkout request is processed
+
+**Then** the confirmation response is returned within 3 seconds for at least 95 percent of requests
+
+### AC-8: Checkout Errors Are Accessible
+
+**Given** a validation or payment error occurs
+
+**When** the error message is shown
+
+**Then** the message is announced by screen readers and the field with the error receives focus when applicable
+
+## Notes
+
+- Payment processor and inventory service availability are external dependencies.
+- Fraud review and manual review flows are out of scope for this example.

package/skills/deliver-acceptance-criteria/references/TEMPLATE.md

@@ -0,0 +1,75 @@
+---
+artifact: acceptance-criteria
+version: "1.0"
+created: <YYYY-MM-DD>
+status: draft
+---
+
+# Acceptance Criteria: [Feature or Story Title]
+
+## Story Context
+
+<!-- Briefly restate the story, feature slice, or PRD section this criteria set supports. -->
+
+[Describe the user need, scope boundary, and any assumptions that matter for testing.]
+
+## Happy Path
+
+<!-- Capture the primary success flow first. Each criterion should be independently testable. -->
+
+### AC-1: [Happy Path Title]
+
+**Given** [initial context or precondition]
+
+**When** [user action or trigger]
+
+**Then** [expected observable outcome]
+
+### AC-2: [Happy Path Title]
+
+**Given** [initial context or precondition]
+
+**When** [user action or trigger]
+
+**Then** [expected observable outcome]
+
+## Edge Cases
+
+<!-- Document boundary conditions and alternate inputs that should still behave correctly. -->
+
+### AC-3: [Edge Case Title]
+
+**Given** [boundary condition or alternate state]
+
+**When** [user action or trigger]
+
+**Then** [expected observable outcome]
+
+## Error States
+
+<!-- Describe failures, validation issues, and dependency problems with recovery behavior. -->
+
+### AC-4: [Error State Title]
+
+**Given** [failure condition]
+
+**When** [user action or trigger]
+
+**Then** [expected observable outcome and recovery path]
+
+## Non-Functional Criteria
+
+<!-- Capture performance, accessibility, security, reliability, or audit requirements. -->
+
+### AC-5: [Non-Functional Title]
+
+**Given** [relevant system or user context]
+
+**When** [measurement or action]
+
+**Then** [expected measurable constraint or guarantee]
+
+## Notes
+
+- [Assumption or dependency]
+- [Open question if the source story is incomplete]

package/skills/deliver-edge-cases/SKILL.md

@@ -1,4 +1,3 @@
-<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
 ---
 name: deliver-edge-cases
 description: Documents edge cases, error states, boundary conditions, and recovery paths for a feature. Use during specification to ensure comprehensive coverage, or during QA planning to identify test scenarios.
@@ -11,6 +10,7 @@ metadata:
   frameworks: [triple-diamond, lean-startup, design-thinking]
   author: product-on-purpose
 ---
+<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
 # Edge Cases
 
 An edge cases document systematically catalogs the unusual, boundary, and error scenarios for a feature. While happy-path flows are typically well-specified, edge cases often get discovered in production — causing bugs, poor user experience, and support burden. Documenting edge cases upfront ensures engineering handles them intentionally and QA knows what to test.

package/skills/deliver-launch-checklist/SKILL.md

@@ -1,4 +1,3 @@
-<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
 ---
 name: deliver-launch-checklist
 description: Creates a comprehensive pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness. Use before releasing features, products, or major updates to ensure nothing is missed.
@@ -11,6 +10,7 @@ metadata:
   frameworks: [triple-diamond, lean-startup, design-thinking]
   author: product-on-purpose
 ---
+<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
 # Launch Checklist
 
 A launch checklist is a comprehensive verification document that ensures all functions are ready before releasing a feature or product. It coordinates across engineering, QA, design, marketing, support, legal, and operations to prevent launch-day surprises. Good launch checklists surface blockers early and create shared accountability for launch readiness.

package/skills/deliver-prd/SKILL.md

@@ -1,4 +1,3 @@
-<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
 ---
 name: deliver-prd
 description: Creates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured. Use when specifying features, epics, or product initiatives for engineering handoff.
@@ -11,6 +10,7 @@ metadata:
   frameworks: [triple-diamond, lean-startup, design-thinking]
   author: product-on-purpose
 ---
+<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
 # Product Requirements Document (PRD)
 
 A Product Requirements Document is the primary specification artifact that communicates what to build and why. It bridges the gap between problem understanding and engineering implementation by providing clear requirements, success criteria, and scope boundaries. A good PRD enables engineering to build the right thing while maintaining flexibility on implementation details.

package/skills/deliver-release-notes/SKILL.md

@@ -1,4 +1,3 @@
-<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
 ---
 name: deliver-release-notes
 description: Creates user-facing release notes that communicate new features, improvements, and fixes in clear, benefit-focused language. Use when shipping updates to communicate changes to users, customers, or stakeholders.
@@ -11,6 +10,7 @@ metadata:
   frameworks: [triple-diamond, lean-startup, design-thinking]
   author: product-on-purpose
 ---
+<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
 # Release Notes
 
 Release notes communicate product changes to users in a way that highlights value and builds excitement. Unlike changelogs (which document what changed technically), release notes translate changes into user benefits. Good release notes help users discover new capabilities, understand improvements, and trust that issues are being addressed.

package/skills/deliver-user-stories/SKILL.md

@@ -1,4 +1,3 @@
-<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
 ---
 name: deliver-user-stories
 description: Generates user stories with clear acceptance criteria from product requirements or feature descriptions. Use when breaking down features for sprint planning, writing tickets, or communicating requirements to engineering.
@@ -11,6 +10,7 @@ metadata:
   frameworks: [triple-diamond, lean-startup, design-thinking]
   author: product-on-purpose
 ---
+<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
 # User Stories
 
 User stories are concise descriptions of functionality from the user's perspective. They capture who needs something, what they need, and why — without prescribing how to build it. Good user stories enable teams to break large features into estimable, deliverable increments while maintaining focus on user value.

package/skills/develop-adr/SKILL.md

@@ -1,4 +1,3 @@
-<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
 ---
 name: develop-adr
 description: Creates an Architecture Decision Record following the Nygard format to document significant technical decisions, their context, and consequences. Use when making technical choices that affect system architecture, technology selection, or development patterns.
@@ -11,6 +10,7 @@ metadata:
   frameworks: [triple-diamond, lean-startup, design-thinking]
   author: product-on-purpose
 ---
+<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
 # Architecture Decision Record (ADR)
 
 An Architecture Decision Record documents a significant technical decision along with its context and consequences. ADRs capture the "why" behind architectural choices so future team members understand the reasoning — especially important when they question why something was done a particular way. This skill follows Michael Nygard's lightweight ADR format.

package/skills/develop-design-rationale/SKILL.md

@@ -1,4 +1,3 @@
-<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
 ---
 name: develop-design-rationale
 description: Documents the reasoning behind design decisions including alternatives considered, trade-offs evaluated, and principles applied. Use when making significant UX decisions, aligning with stakeholders on design direction, or preserving design context for future reference.
@@ -11,6 +10,7 @@ metadata:
   frameworks: [triple-diamond, lean-startup, design-thinking]
   author: product-on-purpose
 ---
+<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
 # Design Rationale
 
 A design rationale document captures the "why" behind design decisions—the context, constraints, alternatives considered, and reasoning that led to a particular solution. While designs themselves show what was built, rationale documents preserve institutional knowledge about why it was built that way.

package/skills/develop-solution-brief/SKILL.md

@@ -1,4 +1,3 @@
-<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
 ---
 name: develop-solution-brief
 description: Creates a concise one-page solution overview that communicates the proposed approach, key decisions, and trade-offs. Use when pitching solutions to stakeholders, aligning teams on approach, or documenting solution intent before detailed specification.
@@ -11,6 +10,7 @@ metadata:
   frameworks: [triple-diamond, lean-startup, design-thinking]
   author: product-on-purpose
 ---
+<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
 # Solution Brief
 
 A solution brief is a concise, one-page document that communicates the proposed solution to a problem. It serves as the bridge between problem understanding and detailed specification, providing enough context for stakeholders to align on the approach without getting lost in implementation details. The one-page constraint forces clarity and prioritization.

package/skills/develop-spike-summary/SKILL.md

@@ -1,4 +1,3 @@
-<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
 ---
 name: develop-spike-summary
 description: Documents the results of a time-boxed technical or design exploration (spike). Use after completing a spike to capture learnings, findings, and recommendations for the team.
@@ -11,6 +10,7 @@ metadata:
   frameworks: [triple-diamond, lean-startup, design-thinking]
   author: product-on-purpose
 ---
+<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
 # Spike Summary
 
 A spike summary documents the results of a time-boxed exploration — a focused investigation to reduce uncertainty before committing to implementation. Spikes answer specific questions like "Can we integrate with this API?" or "Is this technology viable for our use case?" The summary captures findings so the team can make informed decisions without the spike participants needing to repeat explanations.

package/skills/discover-competitive-analysis/SKILL.md

@@ -1,4 +1,3 @@
-<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
 ---
 name: discover-competitive-analysis
 description: Creates a structured competitive analysis comparing features, positioning, and strategy across competitors. Use when entering a market, planning differentiation, or understanding the competitive landscape.
@@ -11,6 +10,7 @@ metadata:
   frameworks: [triple-diamond, lean-startup, design-thinking]
   author: product-on-purpose
 ---
+<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
 # Competitive Analysis
 
 A competitive analysis provides structured insight into the competitive landscape, helping product teams understand where they stand relative to alternatives and identify opportunities for differentiation. Rather than exhaustively cataloging every competitor, an effective analysis focuses on actionable insights that inform product strategy.