product-playbook 1.0.3 → 1.0.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude-plugin/marketplace.json +14 -0
- package/.claude-plugin/plugin.json +1 -1
- package/README.es.md +5 -5
- package/README.ja.md +5 -5
- package/README.ko.md +5 -5
- package/README.md +4 -4
- package/README.zh-CN.md +4 -4
- package/README.zh-TW.md +4 -4
- package/commands/product-build.md +8 -8
- package/commands/product-dev.md +16 -16
- package/commands/product-feature.md +8 -8
- package/commands/product-full.md +8 -8
- package/commands/product-prd.md +9 -9
- package/commands/product-quick.md +8 -8
- package/commands/product-report.md +7 -7
- package/commands/product-revision.md +8 -8
- package/package.json +1 -1
|
@@ -0,0 +1,14 @@
|
|
|
1
|
+
{
|
|
2
|
+
"name": "product-playbook",
|
|
3
|
+
"owner": {
|
|
4
|
+
"name": "Charles Chen"
|
|
5
|
+
},
|
|
6
|
+
"plugins": [
|
|
7
|
+
{
|
|
8
|
+
"name": "product-playbook",
|
|
9
|
+
"description": "World-class product planning AI skill — 22 PM frameworks, 6 modes, multi-language, from idea to dev handoff",
|
|
10
|
+
"version": "1.0.4",
|
|
11
|
+
"source": "./."
|
|
12
|
+
}
|
|
13
|
+
]
|
|
14
|
+
}
|
package/README.es.md
CHANGED
|
@@ -54,18 +54,18 @@ Quiero construir un producto
|
|
|
54
54
|
3. Sube toda la carpeta `product-playbook/`
|
|
55
55
|
4. Di "Quiero construir un producto" en una conversación para activar el skill
|
|
56
56
|
|
|
57
|
-
### Opción 2: Claude Code Plugin
|
|
57
|
+
### Opción 2: Claude Code Plugin
|
|
58
58
|
|
|
59
59
|
En Claude Code, ejecuta:
|
|
60
60
|
|
|
61
61
|
```
|
|
62
|
-
/
|
|
63
|
-
/install product-playbook
|
|
62
|
+
/plugin marketplace add kaminoikari/product-playbook
|
|
63
|
+
/plugin install product-playbook@kaminoikari-product-playbook
|
|
64
64
|
```
|
|
65
65
|
|
|
66
|
-
> El primer comando
|
|
66
|
+
> El primer comando añade el marketplace (solo una vez). El segundo instala el plugin.
|
|
67
67
|
|
|
68
|
-
### Opción 3: Skill de Claude Code
|
|
68
|
+
### Opción 3: Skill de Claude Code (Recomendado)
|
|
69
69
|
|
|
70
70
|
> 💡 Para actualizar: simplemente vuelve a ejecutar el comando de instalación para sobrescribir con la última versión.
|
|
71
71
|
|
package/README.ja.md
CHANGED
|
@@ -54,18 +54,18 @@ The Product Playbookは、ゼロから一まで体系的にプロダクト企画
|
|
|
54
54
|
3. `product-playbook/`フォルダ全体をアップロード
|
|
55
55
|
4. 会話で「プロダクトを作りたい」と言ってスキルをトリガー
|
|
56
56
|
|
|
57
|
-
### 方法2:Claude Code Plugin
|
|
57
|
+
### 方法2:Claude Code Plugin
|
|
58
58
|
|
|
59
59
|
Claude Code で以下を実行:
|
|
60
60
|
|
|
61
61
|
```
|
|
62
|
-
/
|
|
63
|
-
/install product-playbook
|
|
62
|
+
/plugin marketplace add kaminoikari/product-playbook
|
|
63
|
+
/plugin install product-playbook@kaminoikari-product-playbook
|
|
64
64
|
```
|
|
65
65
|
|
|
66
|
-
>
|
|
66
|
+
> 最初のコマンドで marketplace を追加(初回のみ)、2番目で plugin をインストールします。
|
|
67
67
|
|
|
68
|
-
### オプション3:Claude Code
|
|
68
|
+
### オプション3:Claude Codeスキル(推奨)
|
|
69
69
|
|
|
70
70
|
> 💡 更新するには:インストールコマンドを再実行するだけで最新バージョンに上書きされます。
|
|
71
71
|
|
package/README.ko.md
CHANGED
|
@@ -54,18 +54,18 @@ The Product Playbook은 제로부터 원까지 제품 기획 전 과정을 체
|
|
|
54
54
|
3. `product-playbook/` 전체 폴더 업로드
|
|
55
55
|
4. 대화에서 "제품을 만들고 싶어요"라고 말하면 스킬이 트리거됩니다
|
|
56
56
|
|
|
57
|
-
### 옵션 2: Claude Code Plugin
|
|
57
|
+
### 옵션 2: Claude Code Plugin
|
|
58
58
|
|
|
59
59
|
Claude Code에서 실행:
|
|
60
60
|
|
|
61
61
|
```
|
|
62
|
-
/
|
|
63
|
-
/install product-playbook
|
|
62
|
+
/plugin marketplace add kaminoikari/product-playbook
|
|
63
|
+
/plugin install product-playbook@kaminoikari-product-playbook
|
|
64
64
|
```
|
|
65
65
|
|
|
66
|
-
> 첫 번째 명령어로
|
|
66
|
+
> 첫 번째 명령어로 marketplace를 추가하고(최초 1회), 두 번째로 plugin을 설치합니다.
|
|
67
67
|
|
|
68
|
-
### 옵션 3: Claude Code 스킬
|
|
68
|
+
### 옵션 3: Claude Code 스킬 (권장)
|
|
69
69
|
|
|
70
70
|
> 💡 업데이트하려면: 설치 명령을 다시 실행하면 최신 버전으로 덮어쓰기됩니다.
|
|
71
71
|
|
package/README.md
CHANGED
|
@@ -54,18 +54,18 @@ I want to build a product
|
|
|
54
54
|
3. Upload the entire `product-playbook/` folder
|
|
55
55
|
4. Say "I want to build a product" in a conversation to trigger the skill
|
|
56
56
|
|
|
57
|
-
### Option 2: Claude Code Plugin
|
|
57
|
+
### Option 2: Claude Code Plugin
|
|
58
58
|
|
|
59
59
|
In Claude Code, run:
|
|
60
60
|
|
|
61
61
|
```
|
|
62
|
-
/
|
|
63
|
-
/install product-playbook
|
|
62
|
+
/plugin marketplace add kaminoikari/product-playbook
|
|
63
|
+
/plugin install product-playbook@kaminoikari-product-playbook
|
|
64
64
|
```
|
|
65
65
|
|
|
66
66
|
> The first command adds the marketplace (one-time setup). The second installs the plugin.
|
|
67
67
|
|
|
68
|
-
### Option 3: Claude Code Skill
|
|
68
|
+
### Option 3: Claude Code Skill (Recommended)
|
|
69
69
|
|
|
70
70
|
> 💡 To update: simply re-run the install command to overwrite with the latest version.
|
|
71
71
|
|
package/README.zh-CN.md
CHANGED
|
@@ -54,18 +54,18 @@ The Product Playbook 是一个 **Claude AI Skill**,能够系统性地引导你
|
|
|
54
54
|
3. 上传整个 `product-playbook/` 数据夹
|
|
55
55
|
4. 在对话中说「我想做一个产品」即可触发
|
|
56
56
|
|
|
57
|
-
### 方法二:Claude Code Plugin
|
|
57
|
+
### 方法二:Claude Code Plugin
|
|
58
58
|
|
|
59
59
|
在 Claude Code 中执行:
|
|
60
60
|
|
|
61
61
|
```
|
|
62
|
-
/
|
|
63
|
-
/install product-playbook
|
|
62
|
+
/plugin marketplace add kaminoikari/product-playbook
|
|
63
|
+
/plugin install product-playbook@kaminoikari-product-playbook
|
|
64
64
|
```
|
|
65
65
|
|
|
66
66
|
> 第一行命令添加 marketplace(只需执行一次),第二行安装 plugin。
|
|
67
67
|
|
|
68
|
-
### 方法三:Claude Code Skill
|
|
68
|
+
### 方法三:Claude Code Skill(推荐)
|
|
69
69
|
|
|
70
70
|
> 💡 更新方式:重新执行安装指令即可覆盖更新。
|
|
71
71
|
|
package/README.zh-TW.md
CHANGED
|
@@ -54,18 +54,18 @@ The Product Playbook 是一個 **Claude AI Skill**,能夠系統性地引導你
|
|
|
54
54
|
3. 上傳整個 `product-playbook/` 資料夾
|
|
55
55
|
4. 在對話中說「我想做一個產品」即可觸發
|
|
56
56
|
|
|
57
|
-
### 方法二:Claude Code Plugin
|
|
57
|
+
### 方法二:Claude Code Plugin
|
|
58
58
|
|
|
59
59
|
在 Claude Code 中執行:
|
|
60
60
|
|
|
61
61
|
```
|
|
62
|
-
/
|
|
63
|
-
/install product-playbook
|
|
62
|
+
/plugin marketplace add kaminoikari/product-playbook
|
|
63
|
+
/plugin install product-playbook@kaminoikari-product-playbook
|
|
64
64
|
```
|
|
65
65
|
|
|
66
66
|
> 第一行指令新增 marketplace(只需執行一次),第二行安裝 plugin。
|
|
67
67
|
|
|
68
|
-
### 方法三:Claude Code Skill
|
|
68
|
+
### 方法三:Claude Code Skill(推薦)
|
|
69
69
|
|
|
70
70
|
> 💡 更新方式:重新執行安裝指令即可覆蓋更新。
|
|
71
71
|
|
|
@@ -1,13 +1,13 @@
|
|
|
1
1
|
---
|
|
2
|
-
description:
|
|
3
|
-
argument-hint:
|
|
2
|
+
description: Build Mode — Problem is known, skip Discovery, go straight to solution design and MVP planning
|
|
3
|
+
argument-hint: <problem description>
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
6
|
+
Invoke the product-playbook skill.
|
|
7
|
+
Then read references/rules-build.md for the step sequence.
|
|
8
|
+
When executing each step, load the corresponding reference files as indicated in rules-build.md.
|
|
9
9
|
|
|
10
|
-
|
|
11
|
-
|
|
10
|
+
Execution mode: ⚡ Build Mode
|
|
11
|
+
Problem description: $ARGUMENTS
|
|
12
12
|
|
|
13
|
-
|
|
13
|
+
Follow the step sequence in rules-build.md (S1 → S7). Remind the user of the risks of skipping user research. Display a progress indicator at each step.
|
package/commands/product-dev.md
CHANGED
|
@@ -1,21 +1,21 @@
|
|
|
1
1
|
---
|
|
2
|
-
description:
|
|
2
|
+
description: Generate Dev Handoff Package — Produces CLAUDE.md + TASKS.md + TICKETS.md + ARCHITECTURE.md + setup.sh, ready to start development in Claude Code
|
|
3
3
|
---
|
|
4
4
|
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
1. `references/07a-handoff-core.md
|
|
8
|
-
2. `references/07b-tasks-tickets.md
|
|
9
|
-
3. `references/07c-architecture-setup.md
|
|
5
|
+
Invoke the product-playbook skill.
|
|
6
|
+
Then read the following reference files in order:
|
|
7
|
+
1. `references/07a-handoff-core.md` (CLAUDE.md template + tech stack confirmation)
|
|
8
|
+
2. `references/07b-tasks-tickets.md` (TASKS.md + TICKETS.md templates)
|
|
9
|
+
3. `references/07c-architecture-setup.md` (ARCHITECTURE.md + setup.sh + user guidance)
|
|
10
10
|
|
|
11
|
-
|
|
12
|
-
1.
|
|
13
|
-
2.
|
|
14
|
-
3.
|
|
15
|
-
4.
|
|
16
|
-
5.
|
|
17
|
-
6.
|
|
18
|
-
7.
|
|
19
|
-
8.
|
|
11
|
+
Based on the product planning content completed in the current conversation, generate the full dev handoff package:
|
|
12
|
+
1. Confirm the tech stack (if not specified by the user, recommend one based on product characteristics)
|
|
13
|
+
2. Generate CLAUDE.md (Claude Code project memory)
|
|
14
|
+
3. Generate TASKS.md (feature breakdown + phased releases + acceptance criteria)
|
|
15
|
+
4. Generate TICKETS.md (ticket list)
|
|
16
|
+
5. Generate docs/ARCHITECTURE.md (directory structure + DB Schema + API Endpoints)
|
|
17
|
+
6. Generate docs/PRD.md + docs/PRODUCT-SPEC.md
|
|
18
|
+
7. Generate scripts/setup.sh (one-click initialization)
|
|
19
|
+
8. Display Claude Code transition guide
|
|
20
20
|
|
|
21
|
-
|
|
21
|
+
If no product planning content exists in the conversation, prompt the user to run a product planning flow first.
|
|
@@ -1,13 +1,13 @@
|
|
|
1
1
|
---
|
|
2
|
-
description:
|
|
3
|
-
argument-hint:
|
|
2
|
+
description: Feature Extension Mode — Add a single feature to an existing product in 4 streamlined steps
|
|
3
|
+
argument-hint: <feature description>
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
6
|
+
Invoke the product-playbook skill.
|
|
7
|
+
Then read references/rules-build.md and jump directly to the "🔧 Feature Extension Quick Path" section.
|
|
8
|
+
When executing each step, load the corresponding reference files as indicated.
|
|
9
9
|
|
|
10
|
-
|
|
11
|
-
|
|
10
|
+
Execution mode: 🔧 Feature Extension Mode
|
|
11
|
+
Feature description: $ARGUMENTS
|
|
12
12
|
|
|
13
|
-
|
|
13
|
+
Follow the Feature Extension step sequence (S1 → S4). Load product context first per rules-context.md. Display a progress indicator at each step.
|
package/commands/product-full.md
CHANGED
|
@@ -1,13 +1,13 @@
|
|
|
1
1
|
---
|
|
2
|
-
description:
|
|
3
|
-
argument-hint:
|
|
2
|
+
description: Full Mode Product Planning — Run through all 20 steps across every framework, producing deliverable planning documents
|
|
3
|
+
argument-hint: <product description>
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
6
|
+
Invoke the product-playbook skill.
|
|
7
|
+
Then read references/rules-full.md for the step sequence.
|
|
8
|
+
When executing each step, load the corresponding reference files as indicated in rules-full.md.
|
|
9
9
|
|
|
10
|
-
|
|
11
|
-
|
|
10
|
+
Execution mode: Full Mode
|
|
11
|
+
Product description: $ARGUMENTS
|
|
12
12
|
|
|
13
|
-
|
|
13
|
+
Follow the step sequence in rules-full.md (S1 → S20). First confirm the product type (B2B/B2C) and target audience, then begin the first step. Display a progress indicator at each step.
|
package/commands/product-prd.md
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
---
|
|
2
|
-
description:
|
|
2
|
+
description: Generate PRD Engineering Package — Integrates PR-FAQ + MVP + User Story + Pre-mortem, including flowcharts, DB Schema, and UI Wireframes
|
|
3
3
|
---
|
|
4
4
|
|
|
5
|
-
|
|
6
|
-
|
|
5
|
+
Invoke the product-playbook skill.
|
|
6
|
+
Then read references/04b-solutions.md (contains PRD template + flowchart/DB Schema/UI Wireframe specs).
|
|
7
7
|
|
|
8
|
-
|
|
9
|
-
1. PRD
|
|
10
|
-
2.
|
|
11
|
-
3. DB Schema
|
|
12
|
-
4. UI Wireframe
|
|
8
|
+
Based on the product planning content completed in the current conversation, generate the full PRD engineering package:
|
|
9
|
+
1. PRD document (background & goals + feature scope + User Stories + feature specs + technical considerations + risks + milestones)
|
|
10
|
+
2. Flowchart (Mermaid flowchart)
|
|
11
|
+
3. DB Schema (Mermaid erDiagram)
|
|
12
|
+
4. UI Wireframe (HTML low-fidelity wireframe)
|
|
13
13
|
|
|
14
|
-
|
|
14
|
+
If no product planning content exists in the conversation, prompt the user to run a product planning flow first.
|
|
@@ -1,13 +1,13 @@
|
|
|
1
1
|
---
|
|
2
|
-
description:
|
|
3
|
-
argument-hint:
|
|
2
|
+
description: Quick Mode Product Planning — Run through JTBD → PR-FAQ → North Star in under 30 minutes, producing a one-page direction summary
|
|
3
|
+
argument-hint: <product description>
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
6
|
+
Invoke the product-playbook skill.
|
|
7
|
+
Then read references/rules-quick.md for the step sequence.
|
|
8
|
+
When executing each step, load the corresponding reference files as indicated in rules-quick.md.
|
|
9
9
|
|
|
10
|
-
|
|
11
|
-
|
|
10
|
+
Execution mode: Quick Mode
|
|
11
|
+
Product description: $ARGUMENTS
|
|
12
12
|
|
|
13
|
-
|
|
13
|
+
Start immediately without confirming the mode. Follow the step sequence in rules-quick.md (S1 → S2 → S3), displaying a progress indicator at each step.
|
|
@@ -1,12 +1,12 @@
|
|
|
1
1
|
---
|
|
2
|
-
description:
|
|
2
|
+
description: Generate HTML Planning Report — Compile all product planning content into a single offline-readable HTML report
|
|
3
3
|
---
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
Invoke the product-playbook skill. Then read references/06-html-report.md.
|
|
6
6
|
|
|
7
|
-
|
|
8
|
-
-
|
|
9
|
-
-
|
|
10
|
-
-
|
|
7
|
+
Based on the product planning content completed in the current conversation, generate a full HTML planning report following the design specs in 06-html-report.md:
|
|
8
|
+
- Single HTML file (CSS + JS inline, Google Fonts CDN loading Noto Sans TC)
|
|
9
|
+
- Dynamically render completed stages; skip any stages not yet completed
|
|
10
|
+
- Include sticky table-of-contents navigation, card-based layout, and interactive effects
|
|
11
11
|
|
|
12
|
-
|
|
12
|
+
If no product planning content exists in the conversation, prompt the user to run a product planning flow first.
|
|
@@ -1,13 +1,13 @@
|
|
|
1
1
|
---
|
|
2
|
-
description:
|
|
3
|
-
argument-hint:
|
|
2
|
+
description: Revision Mode Product Planning — Optimize and iterate on an existing product, leveraging user data and feature foundations
|
|
3
|
+
argument-hint: <product name and revision goals>
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
6
|
+
Invoke the product-playbook skill.
|
|
7
|
+
Then read references/rules-revision.md for the step sequence.
|
|
8
|
+
When executing each step, load the corresponding reference files as indicated in rules-revision.md.
|
|
9
9
|
|
|
10
|
-
|
|
11
|
-
|
|
10
|
+
Execution mode: Revision Mode
|
|
11
|
+
Product description: $ARGUMENTS
|
|
12
12
|
|
|
13
|
-
|
|
13
|
+
Follow the step sequence in rules-revision.md (S1 → S12). S1 will proactively ask about existing product metrics (DAU/MAU, retention rate, key user feedback, etc.). Display a progress indicator at each step.
|
package/package.json
CHANGED