pm-review

Audit decision notes for schema compliance, body quality, and connection integrity.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/LopeWale/amplLABS --skill pm-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-review
Source: https://github.com/LopeWale/amplLABS/tree/main/.claude/skills/pm-review
Command: npx skills add https://github.com/LopeWale/amplLABS --skill pm-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quality notes in decision registers are often incomplete or misaligned with required schema, leading to unreliable inferences. pm-review provides a structured and reasoning audit that checks schema compliance, body quality, connections, and staleness, distinguishing from content audits.

Core Features & Use Cases

  • Schema Compliance: ensure required fields exist and follow defined formats.
  • Body & Reasoning Quality: verify that decision notes include reasoning and avoid unsupported claims.
  • Connection & Staleness Checks: validates proper links to registers and that reviews are timely.
  • Use Case: audit a single decision note or an entire register to surface issues needing correction.

Quick Start

Provide the target decision or register path to initiate the quality review.

Frequently Asked Questions about pm-review

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

FAQPage Schema
How do I audit decision notes for schema compliance and reasoning quality?

Auditing decision notes for schema compliance involves checking required fields like description, type, status, meta_state, last_reviewed, and topics. You can review a single decision note or an entire register to ensure proper connections, freshness, and reasoning integrity.

What fields are required for decision register governance?

Decision register governance requires fields including description, type, status, meta_state, last_reviewed, and topics. Enforcing these fields ensures trustworthy inferences and reliable decision notes within the register.

Can I check an entire decision register for staleness and connection integrity?

Yes, you can audit an entire decision register to validate connection integrity and check staleness. This ensures reviews are timely and links to registers are properly maintained across all entries.

What's the best way to ensure decision notes include reasoning and avoid unsupported claims?

To ensure decision notes include reasoning and avoid unsupported claims, perform a structured body quality audit. This verifies that reasoning is present and unsupported inferences are flagged for correction.

Does pm-review work for both single decision notes and full register audits?

Yes, pm-review supports auditing both per-decision notes and entire registers. Provide the target decision or register path to initiate the quality review and surface schema or reasoning issues needing correction.

Why does my decision review fail schema compliance checks?

Decision reviews fail schema compliance when required fields are missing or misaligned with defined formats. Missing description, type, status, meta_state, last_reviewed, or topics fields will trigger compliance failures during the audit.