pm-reflect

Analyze PM unit structure and generate a reflection report with restructuring recommendations.

3|3|Updated Aug 19, 2024
One-click install
npx skills add https://github.com/AMDResearch/dh_comms --skill pm-reflect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-reflect
Source: https://github.com/AMDResearch/dh_comms/tree/main/.agents/skills/pm-reflect
Command: npx skills add https://github.com/AMDResearch/dh_comms --skill pm-reflect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, repeatable approach to evaluate PM unit granularity, coverage, and load patterns, enabling teams to detect misalignments and inform reorganization.

Core Features & Use Cases

  • Coverage gap analysis across active and recent workflows to surface unrepresented work areas.
  • Granularity and load-frequency assessment to identify split/merge candidates and flag obsolete units.
  • Automated reflection report generation with concrete recommendations for PM unit restructuring.

Use cases include quarterly PM reviews after major project changes and post-initiative assessments to validate PM unit alignment.

Quick Start

Analyze current PM units and workflow states to produce a reflection report that highlights gaps and improvement opportunities.

Frequently Asked Questions about pm-reflect

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

FAQPage Schema
How do I identify coverage gaps and granularity issues in my product management unit structure?

To identify PM unit coverage gaps and granularity issues, you analyze current PM units against active workflows to surface unrepresented work areas and detect misalignments. This process evaluates unit load patterns to flag obsolete units needing archival.

What is the best way to assess PM unit load patterns for split or merge decisions?

Assessing PM unit load-frequency patterns involves analyzing granular workflow data to identify units with disproportionate workloads. This generates concrete recommendations for splitting overloaded units or merging underutilized ones to optimize structure.

When do I need to run a PM unit reflection analysis?

You need a PM unit reflection analysis during quarterly product management reviews or after major project changes and post-initiative assessments. It validates whether your PM unit alignment still matches current workflow demands and coverage requirements.

Can I generate an automated reflection report for PM unit restructuring?

Yes, you can generate an automated reflection report that compiles coverage gaps and load-pattern anomalies into concrete restructuring recommendations. The final output is saved as a markdown file detailing suggested splits, merges, and archival decisions.

What inputs are required to analyze PM unit structure and workflow states?

Analyzing PM unit structure requires access to the PM unit registry, current-state documents, and recent workflow dossiers. These inputs provide the necessary coverage data and load-frequency context to compile the final reflection report.

Does this PM unit analysis approach work for detecting obsolete units in recent workflows?

Yes, this approach detects obsolete PM units by analyzing load-frequency patterns across active and recent workflows. It identifies units with no current workflow representation and recommends them for archival in the generated reflection report.