platform-product-manager

Clarify platform product strategy, architecture, and analytics decisions for enterprise SaaS.

73|6|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/shuangluan/Product-Manager-Platform --skill platform-product-manager-shuangluan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: platform-product-manager
Source: https://github.com/shuangluan/Product-Manager-Platform/tree/main
Command: npx skills add https://github.com/shuangluan/Product-Manager-Platform --skill platform-product-manager-shuangluan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product managers reason through complex platform decisions in B2B and enterprise SaaS, including architecture, permissions, multi-tenancy, APIs, analytics, and launch strategy.

Core Features & Use Cases

  • Platform architecture: Breaks a product into data, logic, API, application, and observability layers so tradeoffs are visible early.
  • PRD writing: Produces structured, testable product specs for features like RBAC, admin workflows, and multi-tenant capabilities.
  • Journey and analytics design: Maps multi-role user journeys, defines event tracking plans, and shapes North Star Metric frameworks for post-launch analysis.
  • Use case: Use it when you need to design a new enterprise platform, scale an existing one, or diagnose retention and adoption problems with structured product thinking.

Quick Start

Ask this skill to design the architecture, PRD, user journeys, and tracking plan for a multi-tenant enterprise SaaS feature.

Frequently Asked Questions about platform-product-manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design multi-tenant architecture for an enterprise SaaS platform?

Multi-tenant enterprise SaaS architecture breaks a product into data, logic, API, application, and observability layers so tradeoffs are visible early. Layered architecture reasoning helps clarify platform decisions and capability mapping for complex B2B products.

What is a noun_verb event schema and when do I need it for SaaS analytics?

A noun_verb event schema structures platform event tracking by pairing entities with actions, which you need when mapping multi-role user journeys and analytics dimensions. It shapes North Star metric frameworks for post-launch validation and adoption analysis.

How do I write a testable PRD for RBAC and admin workflows?

Writing a testable PRD for RBAC and admin workflows requires structured product specs that define permissions, roles, and capability mapping with QA impact analysis. This ensures cross-role journey analysis produces testable requirements for complex enterprise SaaS features.

Can I use this platform strategy approach for zero-to-one SaaS launches and one-to-ten scaling?

Platform strategy applies to both zero-to-one launches and one-to-ten scaling for enterprise SaaS products. It clarifies architecture decisions, API planning, multi-tenant design, and post-launch validation checks needed at each growth stage.

What's the best way to map multi-role user journeys in enterprise SaaS products?

Mapping multi-role user journeys requires analyzing cross-role interactions across layered platform architecture and defining event tracking plans with analytics dimensions. This approach shapes North Star Metric frameworks to diagnose retention and adoption problems.

Why does my enterprise SaaS platform struggle with adoption after launch?

Enterprise SaaS adoption problems often stem from unclear platform architecture, incomplete cross-role journey mapping, or missing event tracking plans with analytics dimensions. Post-launch validation checks and North Star Metric frameworks help diagnose these structured product thinking gaps.