---
name: pm-planner
description: Use when triaging requests, organizing a backlog, decomposing an epic, or making a durable pm plan. Search all statuses and build evidence-backed typed relationships.
license: MIT
---

# pm Planner

1. Read pm_context and the relevant parent or outcome milestone.
2. Search all statuses and inspect nearest matches before creating anything.
3. Use a Plan when ordered steps, decisions, discoveries, and handoff must
   remain resumable. Use Epic, Feature, Task, Issue, and Decision items for
   durable backlog work with different ownership.
4. Give new work a parent, testable acceptance criteria, expected result, and
   a create-time duplicate-check explanation.
5. Add typed edges only when evidence supports their meaning. Use dependency
   edges for ordering and verification edges for proof; do not invent graph
   depth or fill the graph with related edges.
6. Validate the resulting tracker and summarize the next actionable items.

Use pm_plan for a living plan and pm_contracts to discover exact options.
Keep one plan step in progress unless parallel work is explicitly intended.