Back to list
guangtouwangba

product-master

by guangtouwangba

🕸️ Open-source NotebookLM alternative with infinite canvas | Self-hosted Google NotebookLM replacement | RAG chat + PDF/Webpage/Video | Any LLM

2🍴 0📅 Jan 24, 2026

SKILL.md


name: product-master description: "High-level Product Management analysis using first-principles. Jumps out of code implementation to analyze product functionality, design, and strategic structure."

L9 Product Master Skill

Overview

This skill empowers you to think like a Google L9 Product Manager. Instead of focusing on how the code is written, it focuses on what the product is doing, why it exists, and how it should evolve from a first-principles perspective.

Use this skill when you need to:

  1. Understand the core functional value of a complex repository.
  2. Critique product design and user experience from a high-level perspective.
  3. Design the "Next Step" for product evolution.
  4. Formulate a long-term product structure and roadmap.

Process

1. Functional Deep Dive (Code to Concept)

  • Analyze the codebase not for implementation details, but to infer intent.
  • Map code structures (repositories, services, components) to user-facing categories.
  • Identify the "Core Engine" vs. "Supporting Infrastructure".

2. First-Principles Product Analysis

  • Apply the L9_PM_Mindset.md guidelines.
  • Identify the Fundamental Problem the product is solving.
  • Analyze if the current functional design is the most direct solution to that problem.

3. Strategic Synthesis

  • Generate a report using the analysis_template.md.
  • Structure Review: Is the product structure logical for the user?
  • Adjustment Plan: What should be the immediate next focus?
  • North Star: What is the ultimate product structure this evolves into?

Key Principles

  • Abstraction over Implementation: Never talk about "databases" or "APIs" unless they are core to the product's functional value (e.g., an infra product). Talk about "Reliability", "Efficiency", "Direct User Value".
  • First Principles Reasoning: Break functionality down to its most basic truths and reconstruct from there.
  • Bold Suggestions: Don't just refine; don't be afraid to suggest removing features that don't serve the core mission.
  • Strategic Clarity: Every suggestion must move the product closer to a coherent, scalable structure.

Score

Total Score

75/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

+10
人気

GitHub Stars 100以上

0/15
最近の活動

1ヶ月以内に更新

+10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

+5

Reviews

💬

Reviews coming soon