Index of every page on this site: llms.txt
All skills
deanpeters avatar

/pm-role-charter

@476ae12
Run it yourself

Write a one-page charter for a PM role: what it owns, decides, influences, and is measured on. Use when expectations clash, scope creeps, or a PM is held accountable for things they can't control.

Use this Skill: https://skilld.dev/gh/deanpeters/product-manager-skills/pm-role-charter

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

examplessample.md

≈609 tokens on demand. Your agent reads this file only when SKILL.md points to it.

PM Role Charter Example: SaaS

Role: Product Manager, Route Optimizer (Fieldlight) Why this example exists: the PM was told they "own revenue" for an add-on but didn't control pricing, packaging, or the sales motion. The charter made the gap visible instead of personal.


**Role:** PM, Route Optimizer · **Reports to:** Director of Product · **Reviewed:** Nov 13 · **Next:** Feb

1. **Outcome:** Dispatchers at mid-size service companies run their day with the optimizer, and enough accounts adopt it to justify the investment.
2. **Scope:** In: Route Optimizer (roadmap, onboarding, proof). Out: base platform, billing engine, pricing model.
3. **Decisions owned:** what the optimizer's roadmap includes; what ships in a release; the onboarding experience; which proof points we publish.
4. **Decisions shared:** price and discount bands (**VP Product** decides; PM drives the analysis); launch go/no-go (**VP Product**); customer-specific commitments (VP Sales inside bands, VP Product outside).
5. **Interfaces:**
| With | PM provides | PM gets |
|---|---|---|
| Engineering | Problem, priority, acceptance | Feasibility, sizing |
| Sales | Narrative, proof, battle cards | Deal feedback, objections |
| Support | Release notes, runbook | Ticket themes |
| Finance | Attach and margin assumptions | Margin floor |
6. **Success measures:**
| Measure | Type | Influence | Target |
|---|---|---|---|
| Trials reaching first optimized route in 7 days | Leading | Onboarding, defaults | `[NEEDS SOURCE]` |
| Seats activated / purchased | Leading | Onboarding, CS enablement | `[NEEDS SOURCE]` |
| Attach rate at 180 days | Lagging | Product + proof (not price, not sales motion) | 15% (business case) |
**Gap:** attach depends on sales motion and pricing, which the PM does not control. Manager to confirm
the attach target is shared with the VP Sales.
7. **Not this role:** project management (delivery lead), quota or pricing decisions (VP Sales / VP Product), customer support (Support lead), release scheduling (engineering manager).

**Confirmed by:** manager ☑ · VP Sales ☑ · engineering manager ☑

What to learn from this

  • The gap is written on the page, so the conversation is about the structure, not the person.
  • The PM drives the pricing analysis but doesn't decide it, which is honest and still useful.
  • "Not this role" names four real tasks, and who owns each.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts7d3 checks · Risk SAFE
  • Gen Agent Trust Hub7d

    The skill provides a structured framework and templates for defining Product Manager role charters. It is a documentation-only skill containing no executable code, shell commands, or network operations.

  • Socket7d

    No alerts

  • Snyk7d

    Risk: LOW · No issues

Signed by skilld at 476ae12. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated last week
argument-hint
[the PM role, the product or area, and where the role feels unclear]
type
component
theme
stakeholder-comms
Other metadata
intent
Make a PM role explicit enough to hold someone accountable and to defend: the outcome the role is responsible for, the decisions it makes versus shares, the interfaces with engineering, design, sales, and support, how success is judged, and what the role is not. Sized so a new PM gets a half page and a senior or multi-product role gets the full charter.
best_for
[
  "Defining a PM role when expectations differ between the PM, their manager, and peers",
  "Onboarding a new PM with a shared understanding of the job",
  "Pushing back on scope creep and on accountability without authority",
  "Setting up product roles in a team that has never had them"
]
scenarios
[
  "I'm accountable for revenue but don't control pricing or sales. How do I frame the role?",
  "Write a charter for a new PM joining our industrial controls team",
  "My manager and engineering director describe my job differently",
  "Our PMs act as project managers. How do we describe the role differently?"
]
estimated_time
30-45 min

README badge

README badge for deanpeters/product-manager-skills/pm-role-charter