Product Manager Platform banner
shuangluan shuangluan

Product Manager Platform

Development community

Description

Claude skill for platform product management challenges in B2B or enterprise SaaS contexts.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

Platform Product Manager Skill

A Claude skill for platform product management in B2B and Enterprise SaaS contexts. Invoke it to get structured, opinionated help with architecture design, PRD writing, user journey mapping, event tracking, and go-to-market strategy — across every stage of a platform's lifecycle.


When to use this skill

This skill activates when you're working on:

  • Platform architecture — structuring capabilities across layers (Data, Business Logic, API, Application, Observability), multi-tenancy design, RBAC and permission systems
  • PRDs and product specs — writing requirements for platform features like permissions, multi-tenancy, APIs, or admin workflows
  • User journey maps — mapping flows for multi-role platforms (admins, members, guests, developers) and the handoffs between them
  • Zero-to-one strategy — designing a new platform from scratch, scoping an MVP, deciding what to build first
  • One-to-ten scaling — identifying leverage points as the platform grows, deepening the data model, building out the API layer
  • Event tracking and analytics — designing event schemas, decomposing a North Star Metric, defining analytics dimensions, validating post-launch data
  • Post-launch validation — sanity-checking tracking data, designing user satisfaction surveys, setting up feedback loops

It also triggers when you describe a multi-tenant, multi-role, or layered product problem — even if you don't use the word "platform."


What the skill produces

Deliverable Format
Architecture overview Five-layer model + capability map
PRD Structured template with QA & Testing Impact section
User journey map Stage-by-stage table (actor → action → system response → data)
Interaction flow Numbered step notation with branching
Event tracking plan Table: Event / Trigger / Properties / Questions answered
NSM framework Acquisition → Activation → Retention → Expansion decomposition t