docs: sync counts and regenerate pages for product team expansion
Update all documentation to reflect 177 skills, 254 tools, 357 references, 16 agents, and 17 commands. Add 4 new skill pages, 1 agent page, and 2 command pages to MkDocs site. Sync Codex (156) and Gemini (218) indexes. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Reza Rezvani
32
docs/agents/cs-product-analyst.md
Normal file
32
docs/agents/cs-product-analyst.md
Normal file
@@ -0,0 +1,32 @@
|
||||
---
|
||||
title: "Product Analyst Agent"
|
||||
description: "Product Analyst Agent - Claude Code agent for Product."
|
||||
---
|
||||
|
||||
# Product Analyst Agent
|
||||
|
||||
<div class="page-meta" markdown>
|
||||
<span class="meta-badge">:material-robot: Agent</span>
|
||||
<span class="meta-badge">:material-lightbulb-outline: Product</span>
|
||||
<span class="meta-badge">:material-github: <a href="https://github.com/alirezarezvani/claude-skills/tree/main/agents/product/cs-product-analyst.md">Source</a></span>
|
||||
</div>
|
||||
|
||||
|
||||
## Skill Links
|
||||
- `../../product-team/product-analytics/SKILL.md`
|
||||
- `../../product-team/experiment-designer/SKILL.md`
|
||||
|
||||
## Primary Workflows
|
||||
1. Metric framework and KPI definition
|
||||
2. Dashboard design and cohort/retention analysis
|
||||
3. Experiment design with hypothesis + sample sizing
|
||||
4. Result interpretation and decision recommendations
|
||||
|
||||
## Tooling
|
||||
- `../../product-team/product-analytics/scripts/metrics_calculator.py`
|
||||
- `../../product-team/experiment-designer/scripts/sample_size_calculator.py`
|
||||
|
||||
## Usage Notes
|
||||
- Define decision metrics before analysis to avoid post-hoc bias.
|
||||
- Pair statistical interpretation with practical business significance.
|
||||
- Use guardrail metrics to prevent local optimization mistakes.
|
||||
@@ -1,13 +1,13 @@
|
||||
---
|
||||
title: "Agents"
|
||||
description: "All 15 Claude Code agents — multi-skill orchestrators across domains."
|
||||
description: "All 16 Claude Code agents — multi-skill orchestrators across domains."
|
||||
---
|
||||
|
||||
<div class="domain-header" markdown>
|
||||
|
||||
# :material-robot: Agents
|
||||
|
||||
<p class="domain-count">15 agents that orchestrate skills across domains</p>
|
||||
<p class="domain-count">16 agents that orchestrate skills across domains</p>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -73,6 +73,12 @@ description: "All 15 Claude Code agents — multi-skill orchestrators across dom
|
||||
|
||||
Product
|
||||
|
||||
- :material-lightbulb-outline:{ .lg .middle } **[Product Analyst Agent](cs-product-analyst.md)**
|
||||
|
||||
---
|
||||
|
||||
Product
|
||||
|
||||
- :material-lightbulb-outline:{ .lg .middle } **[Product Manager Agent](cs-product-manager.md)**
|
||||
|
||||
---
|
||||
|
||||
@@ -1,13 +1,13 @@
|
||||
---
|
||||
title: "Commands"
|
||||
description: "All 15 slash commands for quick access to common operations."
|
||||
description: "All 17 slash commands for quick access to common operations."
|
||||
---
|
||||
|
||||
<div class="domain-header" markdown>
|
||||
|
||||
# :material-console: Slash Commands
|
||||
|
||||
<p class="domain-count">15 commands for quick access to common operations</p>
|
||||
<p class="domain-count">17 commands for quick access to common operations</p>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -55,6 +55,12 @@ description: "All 15 slash commands for quick access to common operations."
|
||||
|
||||
Detect project stack and generate CI/CD pipeline configurations for GitHub Actions or GitLab CI.
|
||||
|
||||
- :material-console:{ .lg .middle } **[`/prd`](prd.md)**
|
||||
|
||||
---
|
||||
|
||||
Generate a concise product requirements document for a feature, initiative, or problem statement.
|
||||
|
||||
- :material-console:{ .lg .middle } **[`/project-health`](project-health.md)**
|
||||
|
||||
---
|
||||
@@ -85,6 +91,12 @@ description: "All 15 slash commands for quick access to common operations."
|
||||
|
||||
Score sprint health across delivery, quality, and team metrics with velocity trend analysis.
|
||||
|
||||
- :material-console:{ .lg .middle } **[`/sprint-plan`](sprint-plan.md)**
|
||||
|
||||
---
|
||||
|
||||
Create a sprint plan with prioritized stories and capacity guardrails.
|
||||
|
||||
- :material-console:{ .lg .middle } **[`/tdd`](tdd.md)**
|
||||
|
||||
---
|
||||
|
||||
31
docs/commands/prd.md
Normal file
31
docs/commands/prd.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
title: "/prd"
|
||||
description: "/prd — Claude Code slash command."
|
||||
---
|
||||
|
||||
# /prd
|
||||
|
||||
<div class="page-meta" markdown>
|
||||
<span class="meta-badge">:material-console: Slash Command</span>
|
||||
<span class="meta-badge">:material-github: <a href="https://github.com/alirezarezvani/claude-skills/tree/main/commands/prd.md">Source</a></span>
|
||||
</div>
|
||||
|
||||
|
||||
Generate a concise product requirements document for a feature, initiative, or problem statement.
|
||||
|
||||
## Usage
|
||||
|
||||
```bash
|
||||
/prd <feature-or-problem>
|
||||
```
|
||||
|
||||
## Output Structure
|
||||
|
||||
- Problem statement
|
||||
- Goals and non-goals
|
||||
- User stories and acceptance criteria
|
||||
- Metrics and success thresholds
|
||||
- Scope and timeline assumptions
|
||||
|
||||
## Skill Reference
|
||||
- `product-team/product-manager-toolkit/SKILL.md`
|
||||
31
docs/commands/sprint-plan.md
Normal file
31
docs/commands/sprint-plan.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
title: "/sprint-plan"
|
||||
description: "/sprint-plan — Claude Code slash command."
|
||||
---
|
||||
|
||||
# /sprint-plan
|
||||
|
||||
<div class="page-meta" markdown>
|
||||
<span class="meta-badge">:material-console: Slash Command</span>
|
||||
<span class="meta-badge">:material-github: <a href="https://github.com/alirezarezvani/claude-skills/tree/main/commands/sprint-plan.md">Source</a></span>
|
||||
</div>
|
||||
|
||||
|
||||
Create a sprint plan with prioritized stories and capacity guardrails.
|
||||
|
||||
## Usage
|
||||
|
||||
```bash
|
||||
/sprint-plan <goal> [capacity]
|
||||
```
|
||||
|
||||
## Output Structure
|
||||
|
||||
- Sprint goal
|
||||
- Committed scope
|
||||
- Stretch scope
|
||||
- Risks and dependencies
|
||||
- Story-level acceptance criteria checks
|
||||
|
||||
## Skill Reference
|
||||
- `product-team/agile-product-owner/SKILL.md`
|
||||
@@ -72,7 +72,7 @@ Choose your platform and follow the steps:
|
||||
|--------|----------------|--------|
|
||||
| **Engineering Core** | `/plugin install engineering-skills@claude-code-skills` | 24 |
|
||||
| **Engineering POWERFUL** | `/plugin install engineering-advanced-skills@claude-code-skills` | 25 |
|
||||
| **Product** | `/plugin install product-skills@claude-code-skills` | 8 |
|
||||
| **Product** | `/plugin install product-skills@claude-code-skills` | 12 |
|
||||
| **Marketing** | `/plugin install marketing-skills@claude-code-skills` | 43 |
|
||||
| **Regulatory & Quality** | `/plugin install ra-qm-skills@claude-code-skills` | 12 |
|
||||
| **Project Management** | `/plugin install pm-skills@claude-code-skills` | 6 |
|
||||
@@ -112,7 +112,7 @@ AI-augmented development. Optimize for SEO.
|
||||
|
||||
## Python Tools
|
||||
|
||||
All 250 tools use the standard library only — zero pip installs, all verified.
|
||||
All 254 tools use the standard library only — zero pip installs, all verified.
|
||||
|
||||
```bash
|
||||
# Security audit a skill before installing
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Claude Code Skills & Plugins
|
||||
description: "173 production-ready skills, 19 plugins, 15 agents, and 15 commands for Claude Code, OpenAI Codex, Gemini CLI, and OpenClaw."
|
||||
description: "177 production-ready skills, 19 plugins, 16 agents, and 17 commands for Claude Code, OpenAI Codex, Gemini CLI, and OpenClaw."
|
||||
hide:
|
||||
- toc
|
||||
- edit
|
||||
@@ -14,7 +14,7 @@ hide:
|
||||
|
||||
# Claude Code Skills
|
||||
|
||||
173 production-ready skills that transform AI coding agents into specialized professionals.
|
||||
177 production-ready skills that transform AI coding agents into specialized professionals.
|
||||
{ .hero-subtitle }
|
||||
|
||||
**Claude Code** | **OpenAI Codex** | **Gemini CLI** | **OpenClaw**
|
||||
@@ -27,19 +27,19 @@ hide:
|
||||
|
||||
<div class="grid cards" markdown>
|
||||
|
||||
- :material-counter:{ .lg .middle } **173**
|
||||
- :material-counter:{ .lg .middle } **177**
|
||||
|
||||
---
|
||||
|
||||
Production-ready skills
|
||||
|
||||
- :material-language-python:{ .lg .middle } **250**
|
||||
- :material-language-python:{ .lg .middle } **254**
|
||||
|
||||
---
|
||||
|
||||
Python CLI tools (stdlib-only, all verified)
|
||||
|
||||
- :material-robot:{ .lg .middle } **15**
|
||||
- :material-robot:{ .lg .middle } **16**
|
||||
|
||||
---
|
||||
|
||||
@@ -51,7 +51,7 @@ hide:
|
||||
|
||||
[Installable plugins](plugins/)
|
||||
|
||||
- :material-console:{ .lg .middle } **15**
|
||||
- :material-console:{ .lg .middle } **17**
|
||||
|
||||
---
|
||||
|
||||
@@ -85,9 +85,9 @@ hide:
|
||||
|
||||
---
|
||||
|
||||
Product manager, agile PO, strategist, UX researcher, UI design system, landing pages (TSX + Tailwind), SaaS scaffolder
|
||||
Product manager, agile PO, strategist, UX researcher, UI design system, landing pages, SaaS scaffolder, analytics, experiment designer, discovery, roadmap communicator
|
||||
|
||||
[:octicons-arrow-right-24: 8 skills](skills/product-team/)
|
||||
[:octicons-arrow-right-24: 12 skills](skills/product-team/)
|
||||
|
||||
- :material-bullhorn:{ .lg .middle } **Marketing**
|
||||
|
||||
|
||||
@@ -31,7 +31,7 @@ description: "19 installable plugins for Claude Code, Codex CLI, Gemini CLI, and
|
||||
|
||||
Engineering, Marketing, Product, C-Level, PM, RA/QM, Business, Finance
|
||||
|
||||
- :material-toolbox-outline:{ .lg .middle } **173 Skills**
|
||||
- :material-toolbox-outline:{ .lg .middle } **177 Skills**
|
||||
|
||||
---
|
||||
|
||||
@@ -99,7 +99,7 @@ graph TB
|
||||
B3["marketing-skills<br/>43 skills"]
|
||||
B4["c-level-skills<br/>28 skills"]
|
||||
B5["ra-qm-skills<br/>12 skills"]
|
||||
B6["product-skills<br/>8 skills"]
|
||||
B6["product-skills<br/>12 skills"]
|
||||
B7["pm-skills<br/>6 skills"]
|
||||
B8["business-growth-skills<br/>4 skills"]
|
||||
B9["finance-skills<br/>2 skills"]
|
||||
@@ -203,10 +203,10 @@ ISO 13485 QMS, MDR 2017/745, FDA 510(k)/PMA, GDPR/DSGVO, ISO 27001 ISMS, CAPA ma
|
||||
| | |
|
||||
|---|---|
|
||||
| **Plugin** | `product-skills` |
|
||||
| **Skills** | 8 |
|
||||
| **Skills** | 12 |
|
||||
| **Install** | `claude /plugin install product-skills` |
|
||||
|
||||
Product manager toolkit (RICE, PRDs), agile product owner, product strategist, UX researcher, UI design system, competitive teardown, landing page generator, SaaS scaffolder. 9 Python tools.
|
||||
Product manager toolkit (RICE, PRDs), agile product owner, product strategist, UX researcher, UI design system, competitive teardown, landing page generator, SaaS scaffolder, product analytics, experiment designer, product discovery, roadmap communicator. 13 Python tools.
|
||||
|
||||
[:octicons-arrow-right-24: Browse skills](../skills/product-team/index.md)
|
||||
|
||||
@@ -431,7 +431,7 @@ domain-name/
|
||||
| `engineering-advanced-skills` | Bundle | 25 | Development | agent, rag, database, ci-cd, mcp |
|
||||
| `engineering-skills` | Bundle | 24 | Development | architecture, devops, ai, ml |
|
||||
| `ra-qm-skills` | Bundle | 12 | Compliance | iso-13485, mdr, fda, gdpr |
|
||||
| `product-skills` | Bundle | 8 | Product | pm, agile, ux, saas |
|
||||
| `product-skills` | Bundle | 12 | Product | pm, agile, ux, saas, analytics, experimentation, discovery, roadmap |
|
||||
| `pm-skills` | Bundle | 6 | PM | scrum, jira, confluence |
|
||||
| `business-growth-skills` | Bundle | 4 | Business | sales, revenue, customer-success |
|
||||
| `finance-skills` | Bundle | 2 | Finance | dcf, valuation, saas-metrics |
|
||||
|
||||
115
docs/skills/product-team/experiment-designer.md
Normal file
115
docs/skills/product-team/experiment-designer.md
Normal file
@@ -0,0 +1,115 @@
|
||||
---
|
||||
title: "Experiment Designer"
|
||||
description: "Experiment Designer - Claude Code skill from the Product domain."
|
||||
---
|
||||
|
||||
# Experiment Designer
|
||||
|
||||
<div class="page-meta" markdown>
|
||||
<span class="meta-badge">:material-lightbulb-outline: Product</span>
|
||||
<span class="meta-badge">:material-identifier: `experiment-designer`</span>
|
||||
<span class="meta-badge">:material-github: <a href="https://github.com/alirezarezvani/claude-skills/tree/main/product-team/experiment-designer/SKILL.md">Source</a></span>
|
||||
</div>
|
||||
|
||||
<div class="install-banner" markdown>
|
||||
<span class="install-label">Install:</span> <code>claude /plugin install product-skills</code>
|
||||
</div>
|
||||
|
||||
|
||||
Design, prioritize, and evaluate product experiments with clear hypotheses and defensible decisions.
|
||||
|
||||
## When To Use
|
||||
|
||||
Use this skill for:
|
||||
- A/B and multivariate experiment planning
|
||||
- Hypothesis writing and success criteria definition
|
||||
- Sample size and minimum detectable effect planning
|
||||
- Experiment prioritization with ICE scoring
|
||||
- Reading statistical output for product decisions
|
||||
|
||||
## Core Workflow
|
||||
|
||||
1. Write hypothesis in If/Then/Because format
|
||||
- If we change `[intervention]`
|
||||
- Then `[metric]` will change by `[expected direction/magnitude]`
|
||||
- Because `[behavioral mechanism]`
|
||||
|
||||
2. Define metrics before running test
|
||||
- Primary metric: single decision metric
|
||||
- Guardrail metrics: quality/risk protection
|
||||
- Secondary metrics: diagnostics only
|
||||
|
||||
3. Estimate sample size
|
||||
- Baseline conversion or baseline mean
|
||||
- Minimum detectable effect (MDE)
|
||||
- Significance level (alpha) and power
|
||||
|
||||
Use:
|
||||
```bash
|
||||
python3 scripts/sample_size_calculator.py --baseline-rate 0.12 --mde 0.02 --mde-type absolute
|
||||
```
|
||||
|
||||
4. Prioritize experiments with ICE
|
||||
- Impact: potential upside
|
||||
- Confidence: evidence quality
|
||||
- Ease: cost/speed/complexity
|
||||
|
||||
ICE Score = (Impact * Confidence * Ease) / 10
|
||||
|
||||
5. Launch with stopping rules
|
||||
- Decide fixed sample size or fixed duration in advance
|
||||
- Avoid repeated peeking without proper method
|
||||
- Monitor guardrails continuously
|
||||
|
||||
6. Interpret results
|
||||
- Statistical significance is not business significance
|
||||
- Compare point estimate + confidence interval to decision threshold
|
||||
- Investigate novelty effects and segment heterogeneity
|
||||
|
||||
## Hypothesis Quality Checklist
|
||||
|
||||
- [ ] Contains explicit intervention and audience
|
||||
- [ ] Specifies measurable metric change
|
||||
- [ ] States plausible causal reason
|
||||
- [ ] Includes expected minimum effect
|
||||
- [ ] Defines failure condition
|
||||
|
||||
## Common Experiment Pitfalls
|
||||
|
||||
- Underpowered tests leading to false negatives
|
||||
- Running too many simultaneous changes without isolation
|
||||
- Changing targeting or implementation mid-test
|
||||
- Stopping early on random spikes
|
||||
- Ignoring sample ratio mismatch and instrumentation drift
|
||||
- Declaring success from p-value without effect-size context
|
||||
|
||||
## Statistical Interpretation Guardrails
|
||||
|
||||
- p-value < alpha indicates evidence against null, not guaranteed truth.
|
||||
- Confidence interval crossing zero/no-effect means uncertain directional claim.
|
||||
- Wide intervals imply low precision even when significant.
|
||||
- Use practical significance thresholds tied to business impact.
|
||||
|
||||
See:
|
||||
- `references/experiment-playbook.md`
|
||||
- `references/statistics-reference.md`
|
||||
|
||||
## Tooling
|
||||
|
||||
### `scripts/sample_size_calculator.py`
|
||||
|
||||
Computes required sample size (per variant and total) from:
|
||||
- baseline rate
|
||||
- MDE (absolute or relative)
|
||||
- significance level (alpha)
|
||||
- statistical power
|
||||
|
||||
Example:
|
||||
```bash
|
||||
python3 scripts/sample_size_calculator.py \
|
||||
--baseline-rate 0.10 \
|
||||
--mde 0.015 \
|
||||
--mde-type absolute \
|
||||
--alpha 0.05 \
|
||||
--power 0.8
|
||||
```
|
||||
@@ -1,13 +1,13 @@
|
||||
---
|
||||
title: "Product Skills"
|
||||
description: "All 9 Product skills for Claude Code, Codex CLI, Gemini CLI, and OpenClaw."
|
||||
description: "All 13 Product skills for Claude Code, Codex CLI, Gemini CLI, and OpenClaw."
|
||||
---
|
||||
|
||||
<div class="domain-header" markdown>
|
||||
|
||||
# :material-lightbulb-outline: Product
|
||||
|
||||
<p class="domain-count">9 skills in this domain</p>
|
||||
<p class="domain-count">13 skills in this domain</p>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -29,12 +29,30 @@ description: "All 9 Product skills for Claude Code, Codex CLI, Gemini CLI, and O
|
||||
|
||||
Tier: POWERFUL
|
||||
|
||||
- **[Experiment Designer](experiment-designer.md)**
|
||||
|
||||
---
|
||||
|
||||
Design, prioritize, and evaluate product experiments with clear hypotheses and defensible decisions.
|
||||
|
||||
- **[Landing Page Generator](landing-page-generator.md)**
|
||||
|
||||
---
|
||||
|
||||
Generate high-converting landing pages from a product description. Output complete Next.js/React components with mult...
|
||||
|
||||
- **[Product Analytics](product-analytics.md)**
|
||||
|
||||
---
|
||||
|
||||
Define, track, and interpret product metrics across discovery, growth, and mature product stages.
|
||||
|
||||
- **[Product Discovery](product-discovery.md)**
|
||||
|
||||
---
|
||||
|
||||
Run structured discovery to identify high-value opportunities and de-risk product bets.
|
||||
|
||||
- **[Product Manager Toolkit](product-manager-toolkit.md)**
|
||||
|
||||
---
|
||||
@@ -53,6 +71,12 @@ description: "All 9 Product skills for Claude Code, Codex CLI, Gemini CLI, and O
|
||||
|
||||
8 production-ready product skills covering product management, UX/UI design, and SaaS development.
|
||||
|
||||
- **[Roadmap Communicator](roadmap-communicator.md)**
|
||||
|
||||
---
|
||||
|
||||
Create clear roadmap communication artifacts for internal and external stakeholders.
|
||||
|
||||
- **[SaaS Scaffolder](saas-scaffolder.md)**
|
||||
|
||||
---
|
||||
|
||||
118
docs/skills/product-team/product-analytics.md
Normal file
118
docs/skills/product-team/product-analytics.md
Normal file
@@ -0,0 +1,118 @@
|
||||
---
|
||||
title: "Product Analytics"
|
||||
description: "Product Analytics - Claude Code skill from the Product domain."
|
||||
---
|
||||
|
||||
# Product Analytics
|
||||
|
||||
<div class="page-meta" markdown>
|
||||
<span class="meta-badge">:material-lightbulb-outline: Product</span>
|
||||
<span class="meta-badge">:material-identifier: `product-analytics`</span>
|
||||
<span class="meta-badge">:material-github: <a href="https://github.com/alirezarezvani/claude-skills/tree/main/product-team/product-analytics/SKILL.md">Source</a></span>
|
||||
</div>
|
||||
|
||||
<div class="install-banner" markdown>
|
||||
<span class="install-label">Install:</span> <code>claude /plugin install product-skills</code>
|
||||
</div>
|
||||
|
||||
|
||||
Define, track, and interpret product metrics across discovery, growth, and mature product stages.
|
||||
|
||||
## When To Use
|
||||
|
||||
Use this skill for:
|
||||
- Metric framework selection (AARRR, North Star, HEART)
|
||||
- KPI definition by product stage (pre-PMF, growth, mature)
|
||||
- Dashboard design and metric hierarchy
|
||||
- Cohort and retention analysis
|
||||
- Feature adoption and funnel interpretation
|
||||
|
||||
## Workflow
|
||||
|
||||
1. Select metric framework
|
||||
- AARRR for growth loops and funnel visibility
|
||||
- North Star for cross-functional strategic alignment
|
||||
- HEART for UX quality and user experience measurement
|
||||
|
||||
2. Define stage-appropriate KPIs
|
||||
- Pre-PMF: activation, early retention, qualitative success
|
||||
- Growth: acquisition efficiency, expansion, conversion velocity
|
||||
- Mature: retention depth, revenue quality, operational efficiency
|
||||
|
||||
3. Design dashboard layers
|
||||
- Executive layer: 5-7 directional metrics
|
||||
- Product health layer: acquisition, activation, retention, engagement
|
||||
- Feature layer: adoption, depth, repeat usage, outcome correlation
|
||||
|
||||
4. Run cohort + retention analysis
|
||||
- Segment by signup cohort or feature exposure cohort
|
||||
- Compare retention curves, not single-point snapshots
|
||||
- Identify inflection points around onboarding and first value moment
|
||||
|
||||
5. Interpret and act
|
||||
- Connect metric movement to product changes and release timeline
|
||||
- Distinguish signal from noise using period-over-period context
|
||||
- Propose one clear product action per major metric risk/opportunity
|
||||
|
||||
## KPI Guidance By Stage
|
||||
|
||||
### Pre-PMF
|
||||
- Activation rate
|
||||
- Week-1 retention
|
||||
- Time-to-first-value
|
||||
- Problem-solution fit interview score
|
||||
|
||||
### Growth
|
||||
- Funnel conversion by stage
|
||||
- Monthly retained users
|
||||
- Feature adoption among new cohorts
|
||||
- Expansion / upsell proxy metrics
|
||||
|
||||
### Mature
|
||||
- Net revenue retention aligned product metrics
|
||||
- Power-user share and depth of use
|
||||
- Churn risk indicators by segment
|
||||
- Reliability and support-deflection product metrics
|
||||
|
||||
## Dashboard Design Principles
|
||||
|
||||
- Show trends, not isolated point estimates.
|
||||
- Keep one owner per KPI.
|
||||
- Pair each KPI with target, threshold, and decision rule.
|
||||
- Use cohort and segment filters by default.
|
||||
- Prefer comparable time windows (weekly vs weekly, monthly vs monthly).
|
||||
|
||||
See:
|
||||
- `references/metrics-frameworks.md`
|
||||
- `references/dashboard-templates.md`
|
||||
|
||||
## Cohort Analysis Method
|
||||
|
||||
1. Define cohort anchor event (signup, activation, first purchase).
|
||||
2. Define retained behavior (active day, key action, repeat session).
|
||||
3. Build retention matrix by cohort week/month and age period.
|
||||
4. Compare curve shape across cohorts.
|
||||
5. Flag early drop points and investigate journey friction.
|
||||
|
||||
## Retention Curve Interpretation
|
||||
|
||||
- Sharp early drop, low plateau: onboarding mismatch or weak initial value.
|
||||
- Moderate drop, stable plateau: healthy core audience with predictable churn.
|
||||
- Flattening at low level: product used occasionally, revisit value metric.
|
||||
- Improving newer cohorts: onboarding or positioning improvements are working.
|
||||
|
||||
## Tooling
|
||||
|
||||
### `scripts/metrics_calculator.py`
|
||||
|
||||
CLI utility for:
|
||||
- Retention rate calculations by cohort age
|
||||
- Cohort table generation
|
||||
- Basic funnel conversion analysis
|
||||
|
||||
Examples:
|
||||
```bash
|
||||
python3 scripts/metrics_calculator.py retention events.csv
|
||||
python3 scripts/metrics_calculator.py cohort events.csv --cohort-grain month
|
||||
python3 scripts/metrics_calculator.py funnel funnel.csv --stages visit,signup,activate,pay
|
||||
```
|
||||
125
docs/skills/product-team/product-discovery.md
Normal file
125
docs/skills/product-team/product-discovery.md
Normal file
@@ -0,0 +1,125 @@
|
||||
---
|
||||
title: "Product Discovery"
|
||||
description: "Product Discovery - Claude Code skill from the Product domain."
|
||||
---
|
||||
|
||||
# Product Discovery
|
||||
|
||||
<div class="page-meta" markdown>
|
||||
<span class="meta-badge">:material-lightbulb-outline: Product</span>
|
||||
<span class="meta-badge">:material-identifier: `product-discovery`</span>
|
||||
<span class="meta-badge">:material-github: <a href="https://github.com/alirezarezvani/claude-skills/tree/main/product-team/product-discovery/SKILL.md">Source</a></span>
|
||||
</div>
|
||||
|
||||
<div class="install-banner" markdown>
|
||||
<span class="install-label">Install:</span> <code>claude /plugin install product-skills</code>
|
||||
</div>
|
||||
|
||||
|
||||
Run structured discovery to identify high-value opportunities and de-risk product bets.
|
||||
|
||||
## When To Use
|
||||
|
||||
Use this skill for:
|
||||
- Opportunity Solution Tree facilitation
|
||||
- Assumption mapping and test planning
|
||||
- Problem validation interviews and evidence synthesis
|
||||
- Solution validation with prototypes/experiments
|
||||
- Discovery sprint planning and outputs
|
||||
|
||||
## Core Discovery Workflow
|
||||
|
||||
1. Define desired outcome
|
||||
- Set one measurable outcome to improve.
|
||||
- Establish baseline and target horizon.
|
||||
|
||||
2. Build Opportunity Solution Tree (OST)
|
||||
- Outcome -> opportunities -> solution ideas -> experiments
|
||||
- Keep opportunities grounded in user evidence, not internal opinions.
|
||||
|
||||
3. Map assumptions
|
||||
- Identify desirability, viability, feasibility, and usability assumptions.
|
||||
- Score assumptions by risk and certainty.
|
||||
|
||||
Use:
|
||||
```bash
|
||||
python3 scripts/assumption_mapper.py assumptions.csv
|
||||
```
|
||||
|
||||
4. Validate the problem
|
||||
- Conduct interviews and behavior analysis.
|
||||
- Confirm frequency, severity, and willingness to solve.
|
||||
- Reject weak opportunities early.
|
||||
|
||||
5. Validate the solution
|
||||
- Prototype before building.
|
||||
- Run concept, usability, and value tests.
|
||||
- Measure behavior, not only stated preference.
|
||||
|
||||
6. Plan discovery sprint
|
||||
- 1-2 week cycle with explicit hypotheses
|
||||
- Daily evidence reviews
|
||||
- End with decision: proceed, pivot, or stop
|
||||
|
||||
## Opportunity Solution Tree (Teresa Torres)
|
||||
|
||||
Structure:
|
||||
- Outcome: metric you want to move
|
||||
- Opportunities: unmet customer needs/pains
|
||||
- Solutions: candidate interventions
|
||||
- Experiments: fastest learning actions
|
||||
|
||||
Quality checks:
|
||||
- At least 3 distinct opportunities before converging.
|
||||
- At least 2 experiments per top opportunity.
|
||||
- Tie every branch to evidence source.
|
||||
|
||||
## Assumption Mapping
|
||||
|
||||
Assumption categories:
|
||||
- Desirability: users want this
|
||||
- Viability: business value exists
|
||||
- Feasibility: team can build/operate it
|
||||
- Usability: users can successfully use it
|
||||
|
||||
Prioritization rule:
|
||||
- High risk + low certainty assumptions are tested first.
|
||||
|
||||
## Problem Validation Techniques
|
||||
|
||||
- Problem interviews focused on current behavior
|
||||
- Journey friction mapping
|
||||
- Support ticket and sales-call synthesis
|
||||
- Behavioral analytics triangulation
|
||||
|
||||
Evidence threshold examples:
|
||||
- Same pain repeated across multiple target users
|
||||
- Observable workaround behavior
|
||||
- Measurable cost of current pain
|
||||
|
||||
## Solution Validation Techniques
|
||||
|
||||
- Concept tests (value proposition comprehension)
|
||||
- Prototype usability tests (task success/time-to-complete)
|
||||
- Fake door or concierge tests (demand signal)
|
||||
- Limited beta cohorts (retention/activation signals)
|
||||
|
||||
## Discovery Sprint Planning
|
||||
|
||||
Suggested 10-day structure:
|
||||
- Day 1-2: Outcome + opportunity framing
|
||||
- Day 3-4: Assumption mapping + test design
|
||||
- Day 5-7: Problem and solution tests
|
||||
- Day 8-9: Evidence synthesis + decision options
|
||||
- Day 10: Stakeholder decision review
|
||||
|
||||
## Tooling
|
||||
|
||||
### `scripts/assumption_mapper.py`
|
||||
|
||||
CLI utility that:
|
||||
- reads assumptions from CSV or inline input
|
||||
- scores risk/certainty priority
|
||||
- emits prioritized test plan with suggested test types
|
||||
|
||||
See `references/discovery-frameworks.md` for framework details.
|
||||
103
docs/skills/product-team/roadmap-communicator.md
Normal file
103
docs/skills/product-team/roadmap-communicator.md
Normal file
@@ -0,0 +1,103 @@
|
||||
---
|
||||
title: "Roadmap Communicator"
|
||||
description: "Roadmap Communicator - Claude Code skill from the Product domain."
|
||||
---
|
||||
|
||||
# Roadmap Communicator
|
||||
|
||||
<div class="page-meta" markdown>
|
||||
<span class="meta-badge">:material-lightbulb-outline: Product</span>
|
||||
<span class="meta-badge">:material-identifier: `roadmap-communicator`</span>
|
||||
<span class="meta-badge">:material-github: <a href="https://github.com/alirezarezvani/claude-skills/tree/main/product-team/roadmap-communicator/SKILL.md">Source</a></span>
|
||||
</div>
|
||||
|
||||
<div class="install-banner" markdown>
|
||||
<span class="install-label">Install:</span> <code>claude /plugin install product-skills</code>
|
||||
</div>
|
||||
|
||||
|
||||
Create clear roadmap communication artifacts for internal and external stakeholders.
|
||||
|
||||
## When To Use
|
||||
|
||||
Use this skill for:
|
||||
- Building roadmap presentations in different formats
|
||||
- Writing stakeholder updates (board, engineering, customers)
|
||||
- Producing release notes (user-facing and internal)
|
||||
- Generating changelogs from git history
|
||||
- Structuring feature announcements
|
||||
|
||||
## Roadmap Formats
|
||||
|
||||
1. Now / Next / Later
|
||||
- Best for uncertainty and strategic flexibility.
|
||||
- Communicate direction without false precision.
|
||||
|
||||
2. Timeline roadmap
|
||||
- Best for fixed-date commitments and launch coordination.
|
||||
- Requires active risk and dependency management.
|
||||
|
||||
3. Theme-based roadmap
|
||||
- Best for outcome-led planning and cross-team alignment.
|
||||
- Groups initiatives by problem space or strategic objective.
|
||||
|
||||
See `references/roadmap-templates.md` for templates.
|
||||
|
||||
## Stakeholder Update Patterns
|
||||
|
||||
### Board / Executive
|
||||
- Outcome and risk oriented
|
||||
- Focus on progress against strategic goals
|
||||
- Highlight trade-offs and required decisions
|
||||
|
||||
### Engineering
|
||||
- Scope, dependencies, and sequencing clarity
|
||||
- Status, blockers, and resourcing implications
|
||||
|
||||
### Customers
|
||||
- Value narrative and timing window
|
||||
- What is available now vs upcoming
|
||||
- Clear expectation setting
|
||||
|
||||
See `references/communication-templates.md` for reusable templates.
|
||||
|
||||
## Release Notes Guidance
|
||||
|
||||
### User-Facing Release Notes
|
||||
- Lead with user value, not internal implementation details.
|
||||
- Group by workflows or user jobs.
|
||||
- Include migration/behavior changes explicitly.
|
||||
|
||||
### Internal Release Notes
|
||||
- Include technical details, operational impact, and known issues.
|
||||
- Capture rollout plan, rollback criteria, and monitoring notes.
|
||||
|
||||
## Changelog Generation
|
||||
|
||||
Use:
|
||||
```bash
|
||||
python3 scripts/changelog_generator.py --from v1.0.0 --to HEAD
|
||||
```
|
||||
|
||||
Features:
|
||||
- Reads git log range
|
||||
- Parses conventional commit prefixes
|
||||
- Groups entries by type (`feat`, `fix`, `chore`, etc.)
|
||||
- Outputs markdown or plain text
|
||||
|
||||
## Feature Announcement Framework
|
||||
|
||||
1. Problem context
|
||||
2. What changed
|
||||
3. Why it matters
|
||||
4. Who benefits most
|
||||
5. How to get started
|
||||
6. Call to action and feedback channel
|
||||
|
||||
## Communication Quality Checklist
|
||||
|
||||
- [ ] Audience-specific framing is explicit.
|
||||
- [ ] Outcomes and trade-offs are clear.
|
||||
- [ ] Terminology is consistent across artifacts.
|
||||
- [ ] Risks and dependencies are not hidden.
|
||||
- [ ] Next actions and owners are specified.
|
||||
Reference in New Issue
Block a user