product-playbook 1.0.8 → 1.0.10

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.
@@ -6,8 +6,8 @@
6
6
  "plugins": [
7
7
  {
8
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.6",
9
+ "description": "MUST use when user wants to plan or strategize a product/feature. 22 PM frameworks, 6 modes, multi-language, from idea to dev handoff",
10
+ "version": "1.0.10",
11
11
  "source": "./."
12
12
  }
13
13
  ]
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "product-playbook",
3
- "description": "World-class product planning AI skill 22 PM frameworks, 6 modes, multi-language, from idea to dev handoff",
4
- "version": "1.0.6",
3
+ "description": "MUST use when user wants to plan or strategize a product/feature. 22 PM frameworks, 6 modes, multi-language, from idea to dev handoff",
4
+ "version": "1.0.10",
5
5
  "author": {
6
6
  "name": "Charles Chen"
7
7
  },
package/SKILL.md CHANGED
@@ -1,18 +1,9 @@
1
1
  ---
2
2
  name: product-playbook
3
3
  description: |
4
- World-class product planning framework with 22 PM frameworks (JTBD, PR-FAQ, North Star, OST, Working Backwards, DHM, etc.) from Teresa Torres, Shreyas Doshi, Marty Cagan, Gibson Biddle, April Dunford.
5
-
6
- MUST trigger this skill when the user wants to think about WHAT to build or WHY, not HOW to code it:
7
- - Planning, scoping, or defining a new feature — even without the word "product" (e.g., "plan a new feature", "scope a feature", "I want to add a feature")
8
- - Any vague idea or early-stage thinking, even without the word "product"
9
- - Side project with product intent: understanding pain points, validating demand, or planning before coding
10
- - Product strategy questions: PMF, retention, onboarding optimization, positioning, competitive analysis, target audience, user churn, North Star Metric, Sean Ellis Score
11
- - Framework requests: JTBD, OST, Working Backwards, PR-FAQ, Persona, User Journey Map
12
- - Product revision, redesign, or revamp of product direction
13
- - Planning a new product line, roadmap rethink, or go-to-market strategy
14
- - Supports any language: Chinese, English, Japanese, Korean, Spanish, and more
15
-
4
+ MUST use when user wants to plan, design, or strategize a product or feature including "plan a feature", "add a new feature", "product planning", "I want to plan". This is the correct skill for product/feature PLANNING (not brainstorming for implementation). Integrates 22 PM frameworks (JTBD, PR-FAQ, North Star, etc.) for 0-to-1 through scale-up.
5
+ ALSO trigger when: user wants to scope/define a feature, create Persona/JTBD/Journey Map, mentions "PMF"/"MVP"/"North Star"/"product strategy", requests a specific framework (OST, Working Backwards, etc.), or vaguely says "I have a product idea" / "I want to build something".
6
+ Trigger by semantic intent regardless of language e.g. "規劃新功能", "新機能を企画したい", "quiero planificar una función nueva".
16
7
  DO NOT trigger for: writing code, debugging, SQL/API/CSS optimization, sprint planning, DB schema design, CI/CD, or technical implementation tasks.
17
8
  ---
18
9
 
package/i18n/en/SKILL.md CHANGED
@@ -1,18 +1,9 @@
1
1
  ---
2
2
  name: product-playbook
3
3
  description: |
4
- World-class product planning framework with 22 PM frameworks (JTBD, PR-FAQ, North Star, OST, Working Backwards, DHM, etc.) from Teresa Torres, Shreyas Doshi, Marty Cagan, Gibson Biddle, April Dunford.
5
-
6
- MUST trigger this skill when the user wants to think about WHAT to build or WHY, not HOW to code it:
7
- - Planning, scoping, or defining a new feature — even without the word "product" (e.g., "plan a new feature", "scope a feature", "I want to add a feature")
8
- - Any vague idea or early-stage thinking, even without the word "product"
9
- - Side project with product intent: understanding pain points, validating demand, or planning before coding
10
- - Product strategy questions: PMF, retention, onboarding optimization, positioning, competitive analysis, target audience, user churn, North Star Metric, Sean Ellis Score
11
- - Framework requests: JTBD, OST, Working Backwards, PR-FAQ, Persona, User Journey Map
12
- - Product revision, redesign, or revamp of product direction
13
- - Planning a new product line, roadmap rethink, or go-to-market strategy
14
- - Supports any language: Chinese, English, Japanese, Korean, Spanish, and more
15
-
4
+ MUST use when user wants to plan, design, or strategize a product or feature including "plan a feature", "add a new feature", "product planning", "I want to plan". This is the correct skill for product/feature PLANNING (not brainstorming for implementation). Integrates 22 PM frameworks (JTBD, PR-FAQ, North Star, etc.) for 0-to-1 through scale-up.
5
+ ALSO trigger when: user wants to scope/define a feature, create Persona/JTBD/Journey Map, mentions "PMF"/"MVP"/"North Star"/"product strategy", requests a specific framework (OST, Working Backwards, etc.), or vaguely says "I have a product idea" / "I want to build something".
6
+ Trigger by semantic intent regardless of language e.g. "規劃新功能", "新機能を企画したい", "quiero planificar una función nueva".
16
7
  DO NOT trigger for: writing code, debugging, SQL/API/CSS optimization, sprint planning, DB schema design, CI/CD, or technical implementation tasks.
17
8
  ---
18
9
 
package/i18n/es/SKILL.md CHANGED
@@ -1,18 +1,9 @@
1
1
  ---
2
2
  name: product-playbook
3
3
  description: |
4
- World-class product planning framework with 22 PM frameworks (JTBD, PR-FAQ, North Star, OST, Working Backwards, DHM, etc.) from Teresa Torres, Shreyas Doshi, Marty Cagan, Gibson Biddle, April Dunford.
5
-
6
- MUST trigger this skill when the user wants to think about WHAT to build or WHY, not HOW to code it:
7
- - Planning, scoping, or defining a new feature — even without the word "product" (e.g., "plan a new feature", "scope a feature", "I want to add a feature")
8
- - Any vague idea or early-stage thinking, even without the word "product"
9
- - Side project with product intent: understanding pain points, validating demand, or planning before coding
10
- - Product strategy questions: PMF, retention, onboarding optimization, positioning, competitive analysis, target audience, user churn, North Star Metric, Sean Ellis Score
11
- - Framework requests: JTBD, OST, Working Backwards, PR-FAQ, Persona, User Journey Map
12
- - Product revision, redesign, or revamp of product direction
13
- - Planning a new product line, roadmap rethink, or go-to-market strategy
14
- - Supports any language: Chinese, English, Japanese, Korean, Spanish, and more
15
-
4
+ MUST use when user wants to plan, design, or strategize a product or feature including "plan a feature", "add a new feature", "product planning", "I want to plan". This is the correct skill for product/feature PLANNING (not brainstorming for implementation). Integrates 22 PM frameworks (JTBD, PR-FAQ, North Star, etc.) for 0-to-1 through scale-up.
5
+ ALSO trigger when: user wants to scope/define a feature, create Persona/JTBD/Journey Map, mentions "PMF"/"MVP"/"North Star"/"product strategy", requests a specific framework (OST, Working Backwards, etc.), or vaguely says "I have a product idea" / "I want to build something".
6
+ Trigger by semantic intent regardless of language e.g. "規劃新功能", "新機能を企画したい", "quiero planificar una función nueva".
16
7
  DO NOT trigger for: writing code, debugging, SQL/API/CSS optimization, sprint planning, DB schema design, CI/CD, or technical implementation tasks.
17
8
  ---
18
9
 
package/i18n/ja/SKILL.md CHANGED
@@ -1,18 +1,9 @@
1
1
  ---
2
2
  name: product-playbook
3
3
  description: |
4
- World-class product planning framework with 22 PM frameworks (JTBD, PR-FAQ, North Star, OST, Working Backwards, DHM, etc.) from Teresa Torres, Shreyas Doshi, Marty Cagan, Gibson Biddle, April Dunford.
5
-
6
- MUST trigger this skill when the user wants to think about WHAT to build or WHY, not HOW to code it:
7
- - Planning, scoping, or defining a new feature — even without the word "product" (e.g., "plan a new feature", "scope a feature", "I want to add a feature")
8
- - Any vague idea or early-stage thinking, even without the word "product"
9
- - Side project with product intent: understanding pain points, validating demand, or planning before coding
10
- - Product strategy questions: PMF, retention, onboarding optimization, positioning, competitive analysis, target audience, user churn, North Star Metric, Sean Ellis Score
11
- - Framework requests: JTBD, OST, Working Backwards, PR-FAQ, Persona, User Journey Map
12
- - Product revision, redesign, or revamp of product direction
13
- - Planning a new product line, roadmap rethink, or go-to-market strategy
14
- - Supports any language: Chinese, English, Japanese, Korean, Spanish, and more
15
-
4
+ MUST use when user wants to plan, design, or strategize a product or feature including "plan a feature", "add a new feature", "product planning", "I want to plan". This is the correct skill for product/feature PLANNING (not brainstorming for implementation). Integrates 22 PM frameworks (JTBD, PR-FAQ, North Star, etc.) for 0-to-1 through scale-up.
5
+ ALSO trigger when: user wants to scope/define a feature, create Persona/JTBD/Journey Map, mentions "PMF"/"MVP"/"North Star"/"product strategy", requests a specific framework (OST, Working Backwards, etc.), or vaguely says "I have a product idea" / "I want to build something".
6
+ Trigger by semantic intent regardless of language e.g. "規劃新功能", "新機能を企画したい", "quiero planificar una función nueva".
16
7
  DO NOT trigger for: writing code, debugging, SQL/API/CSS optimization, sprint planning, DB schema design, CI/CD, or technical implementation tasks.
17
8
  ---
18
9
 
package/i18n/ko/SKILL.md CHANGED
@@ -1,18 +1,9 @@
1
1
  ---
2
2
  name: product-playbook
3
3
  description: |
4
- World-class product planning framework with 22 PM frameworks (JTBD, PR-FAQ, North Star, OST, Working Backwards, DHM, etc.) from Teresa Torres, Shreyas Doshi, Marty Cagan, Gibson Biddle, April Dunford.
5
-
6
- MUST trigger this skill when the user wants to think about WHAT to build or WHY, not HOW to code it:
7
- - Planning, scoping, or defining a new feature — even without the word "product" (e.g., "plan a new feature", "scope a feature", "I want to add a feature")
8
- - Any vague idea or early-stage thinking, even without the word "product"
9
- - Side project with product intent: understanding pain points, validating demand, or planning before coding
10
- - Product strategy questions: PMF, retention, onboarding optimization, positioning, competitive analysis, target audience, user churn, North Star Metric, Sean Ellis Score
11
- - Framework requests: JTBD, OST, Working Backwards, PR-FAQ, Persona, User Journey Map
12
- - Product revision, redesign, or revamp of product direction
13
- - Planning a new product line, roadmap rethink, or go-to-market strategy
14
- - Supports any language: Chinese, English, Japanese, Korean, Spanish, and more
15
-
4
+ MUST use when user wants to plan, design, or strategize a product or feature including "plan a feature", "add a new feature", "product planning", "I want to plan". This is the correct skill for product/feature PLANNING (not brainstorming for implementation). Integrates 22 PM frameworks (JTBD, PR-FAQ, North Star, etc.) for 0-to-1 through scale-up.
5
+ ALSO trigger when: user wants to scope/define a feature, create Persona/JTBD/Journey Map, mentions "PMF"/"MVP"/"North Star"/"product strategy", requests a specific framework (OST, Working Backwards, etc.), or vaguely says "I have a product idea" / "I want to build something".
6
+ Trigger by semantic intent regardless of language e.g. "規劃新功能", "新機能を企画したい", "quiero planificar una función nueva".
16
7
  DO NOT trigger for: writing code, debugging, SQL/API/CSS optimization, sprint planning, DB schema design, CI/CD, or technical implementation tasks.
17
8
  ---
18
9
 
@@ -1,18 +1,9 @@
1
1
  ---
2
2
  name: product-playbook
3
3
  description: |
4
- World-class product planning framework with 22 PM frameworks (JTBD, PR-FAQ, North Star, OST, Working Backwards, DHM, etc.) from Teresa Torres, Shreyas Doshi, Marty Cagan, Gibson Biddle, April Dunford.
5
-
6
- MUST trigger this skill when the user wants to think about WHAT to build or WHY, not HOW to code it:
7
- - Planning, scoping, or defining a new feature — even without the word "product" (e.g., "plan a new feature", "scope a feature", "I want to add a feature")
8
- - Any vague idea or early-stage thinking, even without the word "product"
9
- - Side project with product intent: understanding pain points, validating demand, or planning before coding
10
- - Product strategy questions: PMF, retention, onboarding optimization, positioning, competitive analysis, target audience, user churn, North Star Metric, Sean Ellis Score
11
- - Framework requests: JTBD, OST, Working Backwards, PR-FAQ, Persona, User Journey Map
12
- - Product revision, redesign, or revamp of product direction
13
- - Planning a new product line, roadmap rethink, or go-to-market strategy
14
- - Supports any language: Chinese, English, Japanese, Korean, Spanish, and more
15
-
4
+ MUST use when user wants to plan, design, or strategize a product or feature including "plan a feature", "add a new feature", "product planning", "I want to plan". This is the correct skill for product/feature PLANNING (not brainstorming for implementation). Integrates 22 PM frameworks (JTBD, PR-FAQ, North Star, etc.) for 0-to-1 through scale-up.
5
+ ALSO trigger when: user wants to scope/define a feature, create Persona/JTBD/Journey Map, mentions "PMF"/"MVP"/"North Star"/"product strategy", requests a specific framework (OST, Working Backwards, etc.), or vaguely says "I have a product idea" / "I want to build something".
6
+ Trigger by semantic intent regardless of language e.g. "規劃新功能", "新機能を企画したい", "quiero planificar una función nueva".
16
7
  DO NOT trigger for: writing code, debugging, SQL/API/CSS optimization, sprint planning, DB schema design, CI/CD, or technical implementation tasks.
17
8
  ---
18
9
 
@@ -1,18 +1,9 @@
1
1
  ---
2
2
  name: product-playbook
3
3
  description: |
4
- World-class product planning framework with 22 PM frameworks (JTBD, PR-FAQ, North Star, OST, Working Backwards, DHM, etc.) from Teresa Torres, Shreyas Doshi, Marty Cagan, Gibson Biddle, April Dunford.
5
-
6
- MUST trigger this skill when the user wants to think about WHAT to build or WHY, not HOW to code it:
7
- - Planning, scoping, or defining a new feature — even without the word "product" (e.g., "plan a new feature", "scope a feature", "I want to add a feature")
8
- - Any vague idea or early-stage thinking, even without the word "product"
9
- - Side project with product intent: understanding pain points, validating demand, or planning before coding
10
- - Product strategy questions: PMF, retention, onboarding optimization, positioning, competitive analysis, target audience, user churn, North Star Metric, Sean Ellis Score
11
- - Framework requests: JTBD, OST, Working Backwards, PR-FAQ, Persona, User Journey Map
12
- - Product revision, redesign, or revamp of product direction
13
- - Planning a new product line, roadmap rethink, or go-to-market strategy
14
- - Supports any language: Chinese, English, Japanese, Korean, Spanish, and more
15
-
4
+ MUST use when user wants to plan, design, or strategize a product or feature including "plan a feature", "add a new feature", "product planning", "I want to plan". This is the correct skill for product/feature PLANNING (not brainstorming for implementation). Integrates 22 PM frameworks (JTBD, PR-FAQ, North Star, etc.) for 0-to-1 through scale-up.
5
+ ALSO trigger when: user wants to scope/define a feature, create Persona/JTBD/Journey Map, mentions "PMF"/"MVP"/"North Star"/"product strategy", requests a specific framework (OST, Working Backwards, etc.), or vaguely says "I have a product idea" / "I want to build something".
6
+ Trigger by semantic intent regardless of language e.g. "規劃新功能", "新機能を企画したい", "quiero planificar una función nueva".
16
7
  DO NOT trigger for: writing code, debugging, SQL/API/CSS optimization, sprint planning, DB schema design, CI/CD, or technical implementation tasks.
17
8
  ---
18
9
 
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "product-playbook",
3
- "version": "1.0.8",
4
- "description": "World-class product planning AI skill for Claude Code 22 PM frameworks, 6 modes, from idea to dev handoff",
3
+ "version": "1.0.10",
4
+ "description": "MUST use when user wants to plan or strategize a product/feature. 22 PM frameworks, 6 modes, from idea to dev handoff",
5
5
  "bin": {
6
6
  "product-playbook": "./install.sh"
7
7
  },