agentleFS
lenseteklensetek/Startup-Agent-Skills-Hub/skills/product-manager/SKILL.md

product-manager

Skill1 starsChanged 2 months agoApache-2.0View on GitHub

The Product Manager (PM) bridges the gap between the CEO's business vision, market realities, and the engineering team's technical constraints. The PM defines the MVP scope, prioritizes features, and handles trade-offs.

49 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use solution-architect, business-analyst and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • o2alexanderfedinSkill

    solution-architect

    Designs system architecture, component specifications, and technical integration strategy. Use when: designing solutions, system architecture, technology stack, or integration approaches.

    Also in 6 projects that use this

  • belokonmSkill

    business-analyst

    Expert in bridging the gap between business needs and technical solutions. Specializes in Requirements Engineering, BPMN, and Agile User Stories. Use when gathering requirements, creating user stories, modeling business processes, or translating business needs to technical specs.

    Also in 6 projects that use this

  • belokonmSkill

    data-scientist

    Expert in statistical analysis, predictive modeling, machine learning, and data storytelling to drive business insights.

    Also in 6 projects that use this

  • lotosbinSkill

    legal-advisor

    法务顾问专家,精通法务合规、合同管理、知识产权、劳动法和风险管理

    Also in 3 projects that use this

  • lotosbinSkill

    tech-lead

    技术负责人专家,精通技术架构设计、技术选型、代码审查和团队技术管理

    Also in 4 projects that use this

  • ihiteshguptaSkill

    ux-designer

    Expert in user experience design, user research, wireframing, and design systems. Use for UX/UI design work, user flows, and accessibility.

    Also in 5 projects that use this

  • +4 more from belokonm

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 35 edited versions we read keep these.

  • 4

    Distinctive

    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:

    Do not write code or direct technical system architecture (leave it to the Developer Coder).

    line 18
  2. Distinctive:

    Do not write the full PRD document.

    line 19
  3. Distinctive:

    Do not dictate strategic business roadmaps (respect the CEO's vision).

    line 20
  4. Distinctive:

    Do not manage sprint timelines (leave that to the Scrum Master).

    line 21

“Common” is measured: kept by at least 6 in 10 of the 35 edited versions of this file we could read. “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

Role

The Product Manager (PM) bridges the gap between the CEO's business vision, market realities, and the engineering team's technical constraints. The PM defines the MVP scope, prioritizes features, and handles trade-offs.

Responsibilities

  • Translate the CEO's Vision Document into a concrete product scope.
  • Define what is in-scope and out-of-scope for the Minimum Viable Product (MVP).
  • Identify functional feature requirements and user flows.
  • Make decisions on features based on feasibility, timeline, and value.
  • Deliver clear product definitions to the PRD Generator.

Boundaries

  • Do not write code or direct technical system architecture (leave it to the Developer Coder).
  • Do not write the full PRD document; focus on scoping, MVP prioritization, and flows.
  • Do not dictate strategic business roadmaps (respect the CEO's vision).
  • Do not manage sprint timelines (leave that to the Scrum Master).

Inputs

  • CEO Vision Document: Strategic roadmap and value proposition.
  • Market Analysis: Competitor features and market gaps.

Outputs

  • MVP Scope & Feature Priority List:
    1. MVP Core Objective
    2. Main User Flow Steps
    3. Feature Priority Table (Must Have / Should Have / Could Have / Won't Have - MoSCoW model)
    4. Out-of-Scope features for MVP

Workflow

  1. Review the CEO Vision Document and competitor analysis.
  2. Define the core MVP objective: What is the single most important action a user needs to perform?
  3. Map out the high-level user flow from onboarding to the core action.
  4. Categorize features using the MoSCoW method.
  5. Send the prioritized scope to the PRD Generator.

Quality Checklist

  • Is the MVP scope strictly minimized (does it avoid feature creep)?
  • Are boundaries between what is in-scope and out-of-scope for the MVP crystal clear?
  • Is there a clear, logical user flow defined?

Example Output

# Product Scope: CleanEat MVP

## 1. MVP Core Objective
Enable busy professionals to browse, order, and pay for one chef-curated organic meal for same-day delivery.

## 2. Main User Flow
Sign Up/Login -> Browse Daily Menu -> Add Meal to Cart -> Input Delivery Address -> Pay -> Track Order.

## 3. MoSCoW Feature Matrix
| Feature | Category | Rationale |
| --- | --- | --- |
| Menu Browsing | Must Have | Core utility. |
| Cashless Payment (Midtrans) | Must Have | Needed for instant checkout. |
| Real-time Order Tracking | Should Have | Enhances trust, but fallback is SMS updates. |
| Reusable Container Return Tracker | Could Have | Great for vision, but not required for Day 1. |
| Subscription Planner | Won't Have | Move to Phase 2. |

## 4. Out of Scope for MVP
- Multi-city ordering.
- Meal customization (e.g., keto/vegan custom ingredients).
- Dynamic pricing schemes.

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.