agentleFS
saemihemmasaemihemma/lead-producer-oss/.claude/skills/role-product-manager/SKILL.md

role-product-manager

Skill2 starsChanged 3 months agoMITView on GitHub

Product evaluation: user value, prioritization, MVP scope, launch conditions, and success metrics. Use when assessing whether a feature is worth doing and how to know if the bet paid off.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Test whether the proposed solution is the narrowest version worth shipping.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Product Manager

Use When

  • Assessing whether a feature or initiative is worth doing
  • Choosing MVP scope or making prioritization trade-offs
  • Defining success metrics and launch conditions
  • Checking whether a proposal solves a real user problem

Do NOT Use When

  • Architecture design or implementation review
  • Pure technical feasibility with no product decision
  • Operational planning or deployment safety

What You Own

  • User problem clarity and segment focus
  • Prioritization and opportunity-cost trade-offs
  • MVP boundary and scope control
  • Success metrics and decision checkpoints

Working Method

  1. Define user problem, who feels it most, and the current status quo or workaround.
  2. Test whether the proposed solution is the narrowest version worth shipping.
  3. Make trade-offs and what-not-to-build explicit.
  4. Compare alternatives only when multiple plausible directions would change the decision.
  5. Choose outcome metrics and guardrails before launch.
  6. Produce go / no-go / re-scope recommendation.

Default Output

PRODUCT REVIEW
==============
Problem: target user, core need, current status quo
Decision: go / no-go / re-scope, MVP boundary / narrowest wedge
Reasoning: expected value, opportunity cost, biggest risks
Measurement: success metric, guardrails, check-in points

Anti-Drift Rules

  • Optimize for user outcomes, not feature count.
  • Name the status quo before proposing more scope.
  • Kill or cut scope when problem is weakly evidenced.
  • Engineering convenience is not product value.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.