pm-agent-doctrine

Enforces corpus-grounding, human decision gates, and compare-don't-replace synthesis across PM agent outputs.

3|2|Updated Aug 24, 2026
One-click install
npx skills add https://github.com/hero-engine/hero --skill pm-agent-doctrine-hero-engine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-agent-doctrine
Source: https://github.com/hero-engine/hero/tree/main/domains/pm/skills/pm-agent-doctrine
Command: npx skills add https://github.com/hero-engine/hero --skill pm-agent-doctrine-hero-engine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated product management work is often distrusted because it produces confident, evidence-free claims, silently makes prioritization decisions, and replaces the PM's judgment with unverifiable synthesis. This Skill defines three shared doctrines that keep every PM agent's output grounded, gated, and reviewable. ## Core Features & Use Cases - Corpus-grounding contract: Requires every load-bearing claim to cite the team's own evidence (intake items, support tickets, analytics, interview notes) or be explicitly flagged as an untested assumption, with fabrication treated as a cardinal sin. - Decision gates: Ensures prioritization, strategy, roadmap state, and triage outcomes are emitted as marked, reversible, explainable proposals that a human accepts, never auto-applied decisions. - Compare-don't-replace synthesis: Structures research synthesis as a traceable second opinion with outliers and disconfirming signal surfaced, inviting the PM's own read instead of foreclosing it. - Use Case: When asked whether to prioritize a bulk-import feature, the agent cites the six intake items and 22 support tickets behind the demand, shows its RICE math with confidence gaps, and proposes a ranking the human can accept or override. ## Quick Start Load the pm-agent-doctrine skill before any PM authoring or review pass and check each output against the grounded, gated, and compared quick-check questions.

Frequently Asked Questions about pm-agent-doctrine

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

FAQPage Schema
How do I make AI-generated PRDs more trustworthy?▼

Require every load-bearing claim to cite a corpus source such as intake items, support tickets, or analytics, or be explicitly flagged as an untested assumption. This doctrine forbids confident free-association and fabricated quotes, which are the main reasons AI PM output is distrusted.

How should AI agents handle product prioritization decisions?▼

Agents should compute scores and show the math, but leave the final call to a human. Each suggestion must be marked as a proposal, reversible, explainable with visible inputs, and attributable to a person who accepts it.

What is compare-don't-replace synthesis in product research?▼

It means the agent's synthesis is presented alongside the PM's own reading for reconciliation, not as a replacement. Every theme links back to verbatim evidence, outliers and disconfirming signal are surfaced, and the synthesis stays proposed until the human reconciles it.

When should this doctrine be loaded in a PM workflow?▼

Load it at the start of any authoring pass such as initiatives, PRDs, stories, intake triage, or roadmap curation, and at the start of any review or critic pass. It applies whenever an agent is about to state a fact, produce a ranking, or synthesize research.

What are the limitations of AI product management agents?▼

Agents cannot occupy the accountable decision seat and must not auto-reorder roadmaps, flip initiative states, or tune scoring inputs to steer outcomes. Ungrounded claims must be flagged as evidence gaps rather than softened into vagueness.