pm-analysis

Route product-analysis work to PM subagents and merge their outputs.

3|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/infraspecdev/tesseract --skill pm-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-analysis
Source: https://github.com/infraspecdev/tesseract/tree/main/shield/skills/general/pm-analysis
Command: npx skills add https://github.com/infraspecdev/tesseract --skill pm-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill adds a product-management lens to technical work by routing analysis to the right specialist subagents, so plans and research can be judged for user impact, scope discipline, and business value.

Core Features & Use Cases

  • Mode-aware routing: Chooses research-framing, research-review, plan-review, or standalone analysis based on where it is called from.
  • Parallel PM evaluation: Dispatches PM1-PM10 in parallel for comprehensive coverage of user impact, prioritization, stakeholder communicability, and value alignment.
  • Framing-aware review: Includes PM11 when a framing brief exists so research reviews can check whether the original framing was honored.
  • Use case: Review an RFC or strategy doc when you need a clear product verdict before implementation starts.

Quick Start

Ask the pm-analysis skill to review the attached proposal from a product lens and return guidance on user impact, prioritization, scope, and business value.

Frequently Asked Questions about pm-analysis

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

FAQPage Schema
How do I review an RFC from a product management perspective before implementation?

Review an RFC from a product lens by routing the document to parallel PM subagents that evaluate user impact, prioritization, scope discipline, and business value. This mode-aware dispatch merges specialist outputs into a clear product verdict before engineering starts.

What is the best way to evaluate user impact and scope discipline in a product proposal?

Evaluating user impact and scope discipline in a product proposal requires parallel PM1-PM10 subagent execution. This dispatch mechanism comprehensively covers prioritization, stakeholder communicability, and value alignment, returning merged guidance for stakeholder review.

How do I check if a research review honors the original framing brief?

Checking if a research review honors the original framing brief requires optional PM11 framing coverage. When a framing brief exists, this subagent evaluates whether the original stakeholder alignment and research scope were preserved during analysis.

Can I use product-management analysis for standalone strategy documents without a full research framework?

Product-management analysis supports standalone evaluations for strategy documents, RFCs, and proposals without a full research framework. The mode-aware routing intelligently selects standalone analysis mode to deliver a product verdict independently of research or plan review modes.

Does plan review require dispatching multiple PM subagents in parallel?

Plan review requires parallel PM1-PM10 execution to achieve comprehensive coverage of user impact and stakeholder framing. This parallel dispatch ensures plans are thoroughly judged for scope discipline and business value before receiving a final merged product evaluation.

When should I not use a multi-agent product review for my technical proposal?

Avoid multi-agent product review when a technical proposal only requires a simple engineering check without stakeholder alignment or user impact analysis. This routing mechanism is designed for comprehensive evaluations needing prioritization, scope discipline, and business value judgments.