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-industrial.md

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

PM Role Charter Example: Industrial

Role: Product Manager, NFA-500 controller (Northfield Automation), new to the company Why this example exists: in a matrix organization, plant operations, regional sales, and service all expect something from the PM. The charter defines the interfaces and the escalation.


**Role:** PM, NFA-500 · **Reports to:** Head of Controls Product · **Reviewed:** Nov 13 · **Next:** Feb

1. **Outcome:** Existing NFA-200 sites migrate to the NFA-500 in a shift, not a shutdown, and the launch reaches its business-case win rate through eight partners.
2. **Scope:** In: NFA-500 roadmap, migration path, launch plan, partner enablement content. Out: plant production, regional sales targets, service contracts, certification process.
3. **Decisions owned:** product requirements and trade-offs; the migration path design; launch readiness criteria (drafted by PM); what to publish as proof.
4. **Decisions shared:** launch go/no-go (**COO**); list price and partner margin (**Commercial director**); special engineering commitments (**Engineering director**); NFA-200 end of sale (**GM, Controls**).
5. **Interfaces:**
| With | PM provides | PM gets |
|---|---|---|
| Plant | Forecast, ramp priorities | Capacity, lead times |
| Regional sales | Narrative, battle cards, price file | Deal feedback, objections |
| Service | Migration guide, spares plan input | Field failure data |
| Compliance | Design changes | Certification lead times |
| Partners (via channel manager) | Training content, demo plan | Sell-through, objections |
6. **Success measures:**
| Measure | Type | Influence | Target |
|---|---|---|---|
| Migration quotes issued to NFA-200 sites | Leading | Narrative, partner enablement | `[NEEDS SOURCE]` |
| Units commissioned vs plan | Leading | Readiness, partner training | `[NEEDS SOURCE]` |
| Win rate on migration quotes | Lagging | Product, proof (not price, not coverage) | 35% (business case) |
| Early-life failure rate | Guardrail | Product quality, install guide | Escalate above 2x baseline |
**Gap:** win rate also depends on regional sales coverage, which the PM doesn't control. Head of Controls to confirm with sales leadership.
7. **Not this role:** regional sales management; production scheduling; service contract terms; project management (program office owns).

**Confirmed by:** Head of Controls ☑ · Commercial director ☑ · Plant manager ☐ (to review Dec 2)

What to learn from this

  • One confirmation is still open (plant manager) and the charter says so, instead of claiming agreement.
  • A guardrail sits in the measures, so the PM can't be rewarded for volume that fails in the field.
  • The interfaces table is the real content: it says what the PM gives and gets from each function.

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