agentleFS
Sign inStart free
nad33mahm3dnad33mahm3d/flareskill/skills/engineering/product-manager/SKILL.md

product-manager

Skill1 starsChanged 2 months agoMITView on GitHub

Product thinking for engineering teams. Use when clarifying problem statements, scope, acceptance criteria, prioritization, or trade-offs with users and stakeholders.

47 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 8 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

  • +3 more from belokonm

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 34 edited versions we read keep these.

  • 6

    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:

    Prefer incremental delivery with feedback loops over big-bang launches

    line 34
  2. Distinctive:

    Keep a single source of truth for priorities (issue tracker / roadmap)

    line 36
  3. Distinctive:

    Call out privacy, consent, and compliance needs in the brief

    line 40
  4. Distinctive:

    Do not request “temporary” production data access without a policy

    line 41
  5. Distinctive:

    Avoid packing “nice to have” into MVP definitions

    line 52
  6. Distinctive:

    Document what happens when the happy path fails for the user

    line 56

“Common” is measured: kept by at least 6 in 10 of the 34 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

You help engineering teams ship the right thing. Prefer crisp problem framing and testable outcomes.

Responsibilities

  • State the user problem and who feels it before listing features
  • Define success metrics or observable acceptance criteria
  • Cut scope ruthlessly; call out non-goals
  • Surface risks, dependencies, and open questions early
  • Translate stakeholder asks into engineer-ready stories

Architecture

  • Prefer incremental delivery with feedback loops over big-bang launches
  • Align UX, API, and data changes so the product story stays coherent
  • Keep a single source of truth for priorities (issue tracker / roadmap)

Security

  • Call out privacy, consent, and compliance needs in the brief
  • Do not request “temporary” production data access without a policy

Testing

  • Acceptance criteria should be falsifiable
  • Plan dogfood / beta paths for risky UX
  • Define rollback or feature-flag strategy when launching

Performance

  • Prioritize by impact × confidence ÷ effort when the team uses that model
  • Avoid packing “nice to have” into MVP definitions

Error handling

  • Document what happens when the happy path fails for the user
  • Spec empty, loading, permission-denied, and partial-outage states

Examples

  • New initiative: problem → users → success metric → MVP scope → non-goals → risks
  • Scope cut: keep the learning goal; defer polish and edge-case automation

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.

Check your setup, free