agentsclimarketplace
Sign in

Product stakeholders

Skill jpoindexter/product-management-skills/skills/product-stakeholders

Map stakeholders, prepare product decisions, resolve alignment risks, and write evidence-based product updates. Use when ownership is unclear, teams disagree, an executive decision is needed, incentives conflict, or the user must communicate trade-offs, status, risks, and asks.From its SKILL.md

Install
npx -y skills add jpoindexter/product-management-skills --skill product-stakeholders

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 24 days oldThe repository was created 24 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.3 KB, 394 tokens by cl100k_base, as published. Nobody here has run it

Product Stakeholders

Create shared understanding around a product decision without substituting consensus for accountable judgment.

Inputs

  • Decision, owner, deadline, and reversibility
  • Stakeholders, roles, incentives, and authority
  • Evidence, alternatives, constraints, and risks
  • Current disagreements and communication history
  • Required approvals or consultations

Workflow

  1. Define the exact decision and accountable owner.
  2. Map who decides, recommends, contributes evidence, must be consulted, and must be informed.
  3. Identify each stakeholder's goals, constraints, incentives, and likely loss from the decision.
  4. Separate factual disagreement, interpretive disagreement, value conflict, and ownership ambiguity.
  5. Prepare a decision packet: context, evidence, alternatives, trade-offs, recommendation, non-goals, and consequences of delay.
  6. Resolve missing evidence before debating preferences where feasible.
  7. Make the decision at the appropriate level; record dissent and conditions for review.
  8. Communicate what changed, why, who owns next actions, and when the decision will be revisited.

Output contract

Return stakeholder map, decision rights, disagreement diagnosis, evidence gaps, decision packet, communication plan, owner-action table, and review trigger.

Quality gate

  • One person or body owns the decision.
  • Consultation is not confused with veto power.
  • Trade-offs and non-goals are visible.
  • Dissenting evidence is preserved.
  • The update contains a clear ask or next action.

Avoid

  • Seeking universal agreement for a reversible decision
  • Hiding uncertainty to appear confident
  • Using a prioritization score to settle incentive conflicts
  • Escalating before clarifying the decision
  • Broadcasting status without decisions, risks, or asks

Source grounding

Framework-informed operational guidance using product-team accountability from Inspired, organizational outcome thinking from Escaping the Build Trap, and strategy decision discipline from Good Strategy/Bad Strategy.

What ships with it: 1 file

221 B alongside SKILL.md

agents/

Keep looking

Skills are one crate of 326,401. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.