pm-approve

Approve product lifecycle artifacts by computing content hashes and tracking stage state.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/pingmepi/pm-os --skill pm-approve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-approve
Source: https://github.com/pingmepi/pm-os/tree/main/skills/pm-approve
Command: npx skills add https://github.com/pingmepi/pm-os --skill pm-approve

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the problem of tracking product development lifecycle state by ensuring that every artifact transition is explicitly approved, versioned, and validated against previous drafts.

Core Features & Use Cases

  • State Management: Updates the project state and computes content hashes to ensure the source of truth remains consistent.
  • Drift Detection: Estimates semantic distance between generated drafts and current artifacts to distinguish between cosmetic and meaningful changes.
  • Use Case: After a PM reviews a generated PRD draft, this skill is used to formally approve the document, record the approval in the project state, and cascade staleness to downstream dependencies.

Quick Start

Use the pm-approve skill to approve the product brief stage by running the command with the stage identifier as an argument.

Frequently Asked Questions about pm-approve

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

FAQPage Schema
How do I formally approve product development lifecycle artifacts in Markdown?

To approve product documentation, you run a Python 3 script that computes content hashes and records the stage state. This formalizes the approval process for Markdown-based artifacts and prevents upstream drift.

What is stage state management for product documentation?

Stage state management tracks product documents by computing content hashes and recording explicit approvals. It ensures the source of truth remains consistent and cascades staleness to downstream dependencies when changes occur.

How do I detect semantic drift in generated PRD drafts?

To detect semantic drift in PRD drafts, the approval script estimates the semantic distance between generated drafts and current artifacts. This distinguishes between cosmetic modifications and meaningful changes during the definition phase.

Do I need Python to manage product lifecycle approvals?

Yes, you need Python 3 installed to execute the approval script and update local project metadata. The script relies on Python to compute content hashes and manage the formal state of product documentation.

What's the best way to prevent upstream drift in product definition?

The best way to prevent upstream drift is to compute content hashes and validate generated drafts against previous versions before approval. This ensures every artifact transition is explicitly versioned and validated.

How do I cascade staleness to downstream dependencies after approving a PRD?

To cascade staleness to downstream dependencies, you approve the PRD stage using the script. Updating the project state records the approval and automatically marks dependent downstream artifacts as stale.