Alireza Rezvani
GitHub
@@ -4,11 +4,11 @@
|
||||
"name": "Alireza Rezvani",
|
||||
"url": "https://alirezarezvani.com"
|
||||
},
|
||||
"description": "173 production-ready skill packages for Claude AI across 9 domains: marketing (43), engineering (24+25), C-level advisory (28), regulatory/QMS (12), product (8), project management (6), business growth (4), and finance (2). Includes 250 Python tools, 347 reference documents, 15 agents, and 15 slash commands.",
|
||||
"description": "177 production-ready skill packages for Claude AI across 9 domains: marketing (43), engineering (24+25), C-level advisory (28), regulatory/QMS (12), product (12), project management (6), business growth (4), and finance (2). Includes 254 Python tools, 357 reference documents, 16 agents, and 17 slash commands.",
|
||||
"homepage": "https://github.com/alirezarezvani/claude-skills",
|
||||
"repository": "https://github.com/alirezarezvani/claude-skills",
|
||||
"metadata": {
|
||||
"description": "173 production-ready skill packages across 9 domains with 250 Python tools, 347 reference documents, 15 agents, and 15 slash commands. Compatible with Claude Code, Codex CLI, Gemini CLI, and OpenClaw.",
|
||||
"description": "177 production-ready skill packages across 9 domains with 254 Python tools, 357 reference documents, 16 agents, and 17 slash commands. Compatible with Claude Code, Codex CLI, Gemini CLI, and OpenClaw.",
|
||||
"version": "2.1.2"
|
||||
},
|
||||
"plugins": [
|
||||
@@ -129,7 +129,7 @@
|
||||
{
|
||||
"name": "product-skills",
|
||||
"source": "./product-team",
|
||||
"description": "8 product skills with 9 Python tools: product manager toolkit (RICE, PRDs), agile product owner, product strategist, UX researcher designer, UI design system, competitive teardown, landing page generator, SaaS scaffolder.",
|
||||
"description": "12 product skills with 13 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.",
|
||||
"version": "2.1.2",
|
||||
"author": {
|
||||
"name": "Alireza Rezvani"
|
||||
@@ -142,7 +142,11 @@
|
||||
"design-system",
|
||||
"competitive-analysis",
|
||||
"landing-page",
|
||||
"saas"
|
||||
"saas",
|
||||
"analytics",
|
||||
"experimentation",
|
||||
"discovery",
|
||||
"roadmap"
|
||||
],
|
||||
"category": "product"
|
||||
},
|
||||
|
||||
@@ -3,7 +3,7 @@
|
||||
"name": "claude-code-skills",
|
||||
"description": "Production-ready skill packages for AI agents - Marketing, Engineering, Product, C-Level, PM, and RA/QM",
|
||||
"repository": "https://github.com/alirezarezvani/claude-skills",
|
||||
"total_skills": 152,
|
||||
"total_skills": 156,
|
||||
"skills": [
|
||||
{
|
||||
"name": "contract-and-proposal-writer",
|
||||
@@ -773,12 +773,30 @@
|
||||
"category": "product",
|
||||
"description": "Analyzes competitor products and companies by synthesizing data from pricing pages, app store reviews, job postings, SEO signals, and social media into structured competitive intelligence. Produces feature comparison matrices scored across 12 dimensions, SWOT analyses, positioning maps, UX audits, pricing model breakdowns, action item roadmaps, and stakeholder presentation templates. Use when conducting competitor analysis, comparing products against competitors, researching the competitive landscape, building battle cards for sales, preparing for a product strategy or roadmap session, responding to a competitor's new feature or pricing change, or performing a quarterly competitive review."
|
||||
},
|
||||
{
|
||||
"name": "experiment-designer",
|
||||
"source": "../../product-team/experiment-designer",
|
||||
"category": "product",
|
||||
"description": "Use when planning product experiments, writing testable hypotheses, estimating sample size, prioritizing tests, or interpreting A/B outcomes with practical statistical rigor."
|
||||
},
|
||||
{
|
||||
"name": "landing-page-generator",
|
||||
"source": "../../product-team/landing-page-generator",
|
||||
"category": "product",
|
||||
"description": "Generates high-converting landing pages as complete Next.js/React (TSX) components with Tailwind CSS. Creates hero sections, feature grids, pricing tables, FAQ accordions, testimonial blocks, and CTA sections using proven copy frameworks (PAS, AIDA, BAB). Outputs SEO meta tags, structured data, and performance-optimised code targeting Core Web Vitals (LCP < 1s, CLS < 0.1). Use when the user asks to create a landing page, marketing page, homepage, single-page site, lead capture page, campaign page, promo page, or conversion-optimised web page \u2014 or when they want to A/B test landing page variants or replace a static page with one designed to convert."
|
||||
},
|
||||
{
|
||||
"name": "product-analytics",
|
||||
"source": "../../product-team/product-analytics",
|
||||
"category": "product",
|
||||
"description": "Use when defining product KPIs, building metric dashboards, running cohort or retention analysis, or interpreting feature adoption trends across product stages."
|
||||
},
|
||||
{
|
||||
"name": "product-discovery",
|
||||
"source": "../../product-team/product-discovery",
|
||||
"category": "product",
|
||||
"description": "Use when validating product opportunities, mapping assumptions, planning discovery sprints, or testing problem-solution fit before committing delivery resources."
|
||||
},
|
||||
{
|
||||
"name": "product-manager-toolkit",
|
||||
"source": "../../product-team/product-manager-toolkit",
|
||||
@@ -791,6 +809,12 @@
|
||||
"category": "product",
|
||||
"description": "Strategic product leadership toolkit for Head of Product covering OKR cascade generation, quarterly planning, competitive landscape analysis, product vision documents, and team scaling proposals. Use when creating quarterly OKR documents, defining product goals or KPIs, building product roadmaps, running competitive analysis, drafting team structure or hiring plans, aligning product strategy across engineering and design, or generating cascaded goal hierarchies from company to team level."
|
||||
},
|
||||
{
|
||||
"name": "roadmap-communicator",
|
||||
"source": "../../product-team/roadmap-communicator",
|
||||
"category": "product",
|
||||
"description": "Use when preparing roadmap narratives, release notes, changelogs, or stakeholder updates tailored for executives, engineering teams, and customers."
|
||||
},
|
||||
{
|
||||
"name": "saas-scaffolder",
|
||||
"source": "../../product-team/saas-scaffolder",
|
||||
@@ -950,7 +974,7 @@
|
||||
"description": "Marketing, content, and demand generation skills"
|
||||
},
|
||||
"product": {
|
||||
"count": 8,
|
||||
"count": 12,
|
||||
"source": "../../product-team",
|
||||
"description": "Product management and design skills"
|
||||
},
|
||||
|
||||
1
.codex/skills/experiment-designer
Symbolic link
1
.codex/skills/experiment-designer
Symbolic link
@@ -0,0 +1 @@
|
||||
../../product-team/experiment-designer
|
||||
1
.codex/skills/product-analytics
Symbolic link
1
.codex/skills/product-analytics
Symbolic link
@@ -0,0 +1 @@
|
||||
../../product-team/product-analytics
|
||||
1
.codex/skills/product-discovery
Symbolic link
1
.codex/skills/product-discovery
Symbolic link
@@ -0,0 +1 @@
|
||||
../../product-team/product-discovery
|
||||
1
.codex/skills/roadmap-communicator
Symbolic link
1
.codex/skills/roadmap-communicator
Symbolic link
@@ -0,0 +1 @@
|
||||
../../product-team/roadmap-communicator
|
||||
@@ -1,7 +1,7 @@
|
||||
{
|
||||
"version": "1.0.0",
|
||||
"name": "gemini-cli-skills",
|
||||
"total_skills": 211,
|
||||
"total_skills": 218,
|
||||
"skills": [
|
||||
{
|
||||
"name": "cs-agile-product-owner",
|
||||
@@ -43,6 +43,11 @@
|
||||
"category": "agent",
|
||||
"description": "Growth Strategist agent for revenue operations, sales engineering, customer success, and business development. Orchestrates business-growth skills. Spawn when users need pipeline analysis, churn prevention, expansion scoring, sales demos, or proposal writing."
|
||||
},
|
||||
{
|
||||
"name": "cs-product-analyst",
|
||||
"category": "agent",
|
||||
"description": "Product analytics agent for KPI definition, dashboard setup, experiment design, and test result interpretation."
|
||||
},
|
||||
{
|
||||
"name": "cs-product-manager",
|
||||
"category": "agent",
|
||||
@@ -308,6 +313,11 @@
|
||||
"category": "command",
|
||||
"description": "Detect stack and generate CI/CD pipeline configs. Usage: /pipeline <detect|generate> [options]"
|
||||
},
|
||||
{
|
||||
"name": "prd",
|
||||
"category": "command",
|
||||
"description": "Quick PRD generation command. Usage: /prd <feature-or-problem>"
|
||||
},
|
||||
{
|
||||
"name": "project-health",
|
||||
"category": "command",
|
||||
@@ -333,6 +343,11 @@
|
||||
"category": "command",
|
||||
"description": "Sprint health scoring and velocity analysis for agile teams. Usage: /sprint-health <analyze|velocity> [options]"
|
||||
},
|
||||
{
|
||||
"name": "sprint-plan",
|
||||
"category": "command",
|
||||
"description": "Sprint planning shortcut. Usage: /sprint-plan <goal> [capacity]"
|
||||
},
|
||||
{
|
||||
"name": "tdd",
|
||||
"category": "command",
|
||||
@@ -923,11 +938,26 @@
|
||||
"category": "product",
|
||||
"description": "Analyzes competitor products and companies by synthesizing data from pricing pages, app store reviews, job postings, SEO signals, and social media into structured competitive intelligence. Produces feature comparison matrices scored across 12 dimensions, SWOT analyses, positioning maps, UX audits, pricing model breakdowns, action item roadmaps, and stakeholder presentation templates. Use when conducting competitor analysis, comparing products against competitors, researching the competitive landscape, building battle cards for sales, preparing for a product strategy or roadmap session, responding to a competitor's new feature or pricing change, or performing a quarterly competitive review."
|
||||
},
|
||||
{
|
||||
"name": "experiment-designer",
|
||||
"category": "product",
|
||||
"description": "Use when planning product experiments, writing testable hypotheses, estimating sample size, prioritizing tests, or interpreting A/B outcomes with practical statistical rigor."
|
||||
},
|
||||
{
|
||||
"name": "landing-page-generator",
|
||||
"category": "product",
|
||||
"description": "Generates high-converting landing pages as complete Next.js/React (TSX) components with Tailwind CSS. Creates hero sections, feature grids, pricing tables, FAQ accordions, testimonial blocks, and CTA sections using proven copy frameworks (PAS, AIDA, BAB). Outputs SEO meta tags, structured data, and performance-optimised code targeting Core Web Vitals (LCP < 1s, CLS < 0.1). Use when the user asks to create a landing page, marketing page, homepage, single-page site, lead capture page, campaign page, promo page, or conversion-optimised web page \u2014 or when they want to A/B test landing page variants or replace a static page with one designed to convert."
|
||||
},
|
||||
{
|
||||
"name": "product-analytics",
|
||||
"category": "product",
|
||||
"description": "Use when defining product KPIs, building metric dashboards, running cohort or retention analysis, or interpreting feature adoption trends across product stages."
|
||||
},
|
||||
{
|
||||
"name": "product-discovery",
|
||||
"category": "product",
|
||||
"description": "Use when validating product opportunities, mapping assumptions, planning discovery sprints, or testing problem-solution fit before committing delivery resources."
|
||||
},
|
||||
{
|
||||
"name": "product-manager-toolkit",
|
||||
"category": "product",
|
||||
@@ -943,6 +973,11 @@
|
||||
"category": "product",
|
||||
"description": "8 production-ready product skills: product manager toolkit with RICE prioritization, agile product owner, product strategist with OKR cascades, UX researcher, UI design system, competitive teardown, landing page generator, and SaaS scaffolder. Python tools included (all stdlib-only). Works with Claude Code, Codex CLI, and OpenClaw."
|
||||
},
|
||||
{
|
||||
"name": "roadmap-communicator",
|
||||
"category": "product",
|
||||
"description": "Use when preparing roadmap narratives, release notes, changelogs, or stakeholder updates tailored for executives, engineering teams, and customers."
|
||||
},
|
||||
{
|
||||
"name": "saas-scaffolder",
|
||||
"category": "product",
|
||||
@@ -1061,7 +1096,7 @@
|
||||
],
|
||||
"categories": {
|
||||
"agent": {
|
||||
"count": 15,
|
||||
"count": 16,
|
||||
"description": "Agent resources"
|
||||
},
|
||||
"business-growth": {
|
||||
@@ -1073,7 +1108,7 @@
|
||||
"description": "C-level resources"
|
||||
},
|
||||
"command": {
|
||||
"count": 15,
|
||||
"count": 17,
|
||||
"description": "Command resources"
|
||||
},
|
||||
"engineering": {
|
||||
@@ -1093,7 +1128,7 @@
|
||||
"description": "Marketing resources"
|
||||
},
|
||||
"product": {
|
||||
"count": 9,
|
||||
"count": 13,
|
||||
"description": "Product resources"
|
||||
},
|
||||
"project-management": {
|
||||
|
||||
1
.gemini/skills/cs-product-analyst/SKILL.md
Symbolic link
1
.gemini/skills/cs-product-analyst/SKILL.md
Symbolic link
@@ -0,0 +1 @@
|
||||
../../../agents/product/cs-product-analyst.md
|
||||
1
.gemini/skills/experiment-designer/SKILL.md
Symbolic link
1
.gemini/skills/experiment-designer/SKILL.md
Symbolic link
@@ -0,0 +1 @@
|
||||
../../../product-team/experiment-designer/SKILL.md
|
||||
1
.gemini/skills/prd/SKILL.md
Symbolic link
1
.gemini/skills/prd/SKILL.md
Symbolic link
@@ -0,0 +1 @@
|
||||
../../../commands/prd.md
|
||||
1
.gemini/skills/product-analytics/SKILL.md
Symbolic link
1
.gemini/skills/product-analytics/SKILL.md
Symbolic link
@@ -0,0 +1 @@
|
||||
../../../product-team/product-analytics/SKILL.md
|
||||
1
.gemini/skills/product-discovery/SKILL.md
Symbolic link
1
.gemini/skills/product-discovery/SKILL.md
Symbolic link
@@ -0,0 +1 @@
|
||||
../../../product-team/product-discovery/SKILL.md
|
||||
1
.gemini/skills/roadmap-communicator/SKILL.md
Symbolic link
1
.gemini/skills/roadmap-communicator/SKILL.md
Symbolic link
@@ -0,0 +1 @@
|
||||
../../../product-team/roadmap-communicator/SKILL.md
|
||||
1
.gemini/skills/sprint-plan/SKILL.md
Symbolic link
1
.gemini/skills/sprint-plan/SKILL.md
Symbolic link
@@ -0,0 +1 @@
|
||||
../../../commands/sprint-plan.md
|
||||
12
CLAUDE.md
12
CLAUDE.md
@@ -6,7 +6,7 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
|
||||
|
||||
This is a **comprehensive skills library** for Claude AI and Claude Code - reusable, production-ready skill packages that bundle domain expertise, best practices, analysis tools, and strategic frameworks. The repository provides modular skills that teams can download and use directly in their workflows.
|
||||
|
||||
**Current Scope:** 173 production-ready skills across 9 domains with 250 Python automation tools, 347 reference guides, 15 agents, and 15 slash commands.
|
||||
**Current Scope:** 177 production-ready skills across 9 domains with 254 Python automation tools, 357 reference guides, 16 agents, and 17 slash commands.
|
||||
|
||||
**Key Distinction**: This is NOT a traditional application. It's a library of skill packages meant to be extracted and deployed by users into their own Claude workflows.
|
||||
|
||||
@@ -37,10 +37,10 @@ This repository uses **modular documentation**. For domain-specific guidance, se
|
||||
claude-code-skills/
|
||||
├── .claude-plugin/ # Plugin registry (marketplace.json)
|
||||
├── agents/ # 15 cs-* prefixed agents across all domains
|
||||
├── commands/ # 15 slash commands (changelog, tdd, saas-health, workspace, etc.)
|
||||
├── commands/ # 17 slash commands (changelog, tdd, saas-health, workspace, prd, sprint-plan, etc.)
|
||||
├── engineering-team/ # 24 core engineering skills + Playwright Pro + Self-Improving Agent
|
||||
├── engineering/ # 25 POWERFUL-tier advanced skills
|
||||
├── product-team/ # 8 product skills + Python tools
|
||||
├── product-team/ # 12 product skills + Python tools
|
||||
├── marketing-skill/ # 43 marketing skills (7 pods) + Python tools
|
||||
├── c-level-advisor/ # 28 C-level advisory skills (10 roles + orchestration)
|
||||
├── project-management/ # 6 PM skills + Atlassian MCP
|
||||
@@ -148,9 +148,9 @@ See [standards/git/git-workflow-standards.md](standards/git/git-workflow-standar
|
||||
|
||||
## Roadmap
|
||||
|
||||
**Phase 1-2 Complete:** 173 production-ready skills deployed across 9 domains
|
||||
**Phase 1-2 Complete:** 177 production-ready skills deployed across 9 domains
|
||||
- Engineering Core (24), Engineering POWERFUL (25), Product (8), Marketing (43), PM (6), C-Level (28), RA/QM (12), Business & Growth (4), Finance (2)
|
||||
- 250 Python automation tools, 347 reference guides, 15 agents, 15 commands
|
||||
- 254 Python automation tools, 357 reference guides, 16 agents, 17 commands
|
||||
- Complete enterprise coverage from engineering through regulatory compliance, sales, customer success, and finance
|
||||
- MkDocs Material docs site with 210+ indexed pages for SEO
|
||||
|
||||
@@ -203,4 +203,4 @@ This repository publishes skills to **ClawHub** (clawhub.com) as the distributio
|
||||
|
||||
**Last Updated:** March 11, 2026
|
||||
**Version:** v2.1.2
|
||||
**Status:** 173 skills deployed across 9 domains, 19 marketplace plugins, docs site live
|
||||
**Status:** 177 skills deployed across 9 domains, 19 marketplace plugins, docs site live
|
||||
|
||||
18
README.md
18
README.md
@@ -1,11 +1,11 @@
|
||||
# Claude Code Skills & Plugins
|
||||
|
||||
**173 production-ready skills and plugins for Claude Code, OpenAI Codex, Gemini CLI, and OpenClaw** — reusable expertise bundles that transform AI coding agents into specialized professionals across engineering, product, marketing, compliance, and more.
|
||||
**177 production-ready skills and plugins for Claude Code, OpenAI Codex, Gemini CLI, and OpenClaw** — reusable expertise bundles that transform AI coding agents into specialized professionals across engineering, product, marketing, compliance, and more.
|
||||
|
||||
[](https://opensource.org/licenses/MIT)
|
||||
[](#skills-overview)
|
||||
[](#agents)
|
||||
[](#commands)
|
||||
[](#skills-overview)
|
||||
[](#agents)
|
||||
[](#commands)
|
||||
[](https://github.com/alirezarezvani/claude-skills/stargazers)
|
||||
[](https://getskillcheck.com)
|
||||
|
||||
@@ -17,7 +17,7 @@
|
||||
|
||||
Skills are modular instruction packages (plugins) that give AI coding agents domain expertise they don't have out of the box. Each skill includes a `SKILL.md` (instructions + workflows), Python CLI tools, and reference documentation — everything the agent needs to perform like a specialist.
|
||||
|
||||
**One repo, four platforms:** Works natively as Claude Code plugins, OpenAI Codex CLI and agents, Gemini CLI skills, and OpenClaw skills. All 250 Python tools are stdlib-only and verified working.
|
||||
**One repo, four platforms:** Works natively as Claude Code plugins, OpenAI Codex CLI and agents, Gemini CLI skills, and OpenClaw skills. All 254 Python tools are stdlib-only and verified working.
|
||||
|
||||
---
|
||||
|
||||
@@ -46,7 +46,7 @@ cd claude-skills
|
||||
# Install by domain
|
||||
/plugin install engineering-skills@claude-code-skills # 24 core engineering
|
||||
/plugin install engineering-advanced-skills@claude-code-skills # 25 POWERFUL-tier
|
||||
/plugin install product-skills@claude-code-skills # 8 product skills
|
||||
/plugin install product-skills@claude-code-skills # 12 product skills
|
||||
/plugin install marketing-skills@claude-code-skills # 43 marketing skills
|
||||
/plugin install ra-qm-skills@claude-code-skills # 12 regulatory/quality
|
||||
/plugin install pm-skills@claude-code-skills # 6 project management
|
||||
@@ -85,7 +85,7 @@ git clone https://github.com/alirezarezvani/claude-skills.git
|
||||
|
||||
## Skills Overview
|
||||
|
||||
**173 skills across 9 domains:**
|
||||
**177 skills across 9 domains:**
|
||||
|
||||
| Domain | Skills | Highlights | Details |
|
||||
|--------|--------|------------|---------|
|
||||
@@ -93,7 +93,7 @@ git clone https://github.com/alirezarezvani/claude-skills.git
|
||||
| **🎭 Playwright Pro** | 9+3 | Test generation, flaky fix, Cypress/Selenium migration, TestRail, BrowserStack, 55 templates | [engineering-team/playwright-pro](engineering-team/playwright-pro/) |
|
||||
| **🧠 Self-Improving Agent** | 5+2 | Auto-memory curation, pattern promotion, skill extraction, memory health | [engineering-team/self-improving-agent](engineering-team/self-improving-agent/) |
|
||||
| **⚡ Engineering — POWERFUL** | 25 | Agent designer, RAG architect, database designer, CI/CD builder, security auditor, MCP builder | [engineering/](engineering/) |
|
||||
| **🎯 Product** | 8 | Product manager, agile PO, strategist, UX researcher, UI design, landing pages (TSX + Tailwind), SaaS scaffolder | [product-team/](product-team/) |
|
||||
| **🎯 Product** | 12 | Product manager, agile PO, strategist, UX researcher, UI design, landing pages, SaaS scaffolder, analytics, experiment designer, discovery, roadmap communicator | [product-team/](product-team/) |
|
||||
| **📣 Marketing** | 43 | 7 pods: Content (8), SEO (5), CRO (6), Channels (6), Growth (4), Intelligence (4), Sales (2) + context foundation + orchestration router. 32 Python tools. | [marketing-skill/](marketing-skill/) |
|
||||
| **📋 Project Management** | 6 | Senior PM, scrum master, Jira, Confluence, Atlassian admin, templates | [project-management/](project-management/) |
|
||||
| **🏥 Regulatory & QM** | 12 | ISO 13485, MDR 2017/745, FDA, ISO 27001, GDPR, CAPA, risk management | [ra-qm-team/](ra-qm-team/) |
|
||||
@@ -189,7 +189,7 @@ for MDR Annex II compliance gaps.
|
||||
|
||||
## Python Analysis Tools
|
||||
|
||||
250 CLI tools ship with the skills (all verified, stdlib-only):
|
||||
254 CLI tools ship with the skills (all verified, stdlib-only):
|
||||
|
||||
```bash
|
||||
# SaaS health check
|
||||
|
||||
@@ -6,7 +6,7 @@ This guide provides comprehensive instructions for creating **cs-* prefixed agen
|
||||
|
||||
### What are cs-* Agents?
|
||||
|
||||
**cs-* agents** are specialized Claude Code agents that orchestrate the 173 existing skills. Each agent:
|
||||
**cs-* agents** are specialized Claude Code agents that orchestrate the 177 existing skills. Each agent:
|
||||
- References skills via relative paths (`../../marketing-skill/`)
|
||||
- Executes Python automation tools from skill packages
|
||||
- Follows established workflows and templates
|
||||
@@ -24,7 +24,7 @@ When skills are published to **ClawHub** (clawhub.com):
|
||||
|
||||
### Production Agents
|
||||
|
||||
**15 Agents Currently Available**:
|
||||
**16 Agents Currently Available**:
|
||||
|
||||
| Agent | Domain | Description |
|
||||
|-------|--------|-------------|
|
||||
@@ -36,6 +36,7 @@ When skills are published to **ClawHub** (clawhub.com):
|
||||
| [cs-product-strategist](product/cs-product-strategist.md) | Product | Product strategy, OKR cascades, market positioning |
|
||||
| [cs-agile-product-owner](product/cs-agile-product-owner.md) | Product | Agile product ownership and backlog management |
|
||||
| [cs-ux-researcher](product/cs-ux-researcher.md) | Product | UX research, usability testing, design insights |
|
||||
| [cs-product-analyst](product/cs-product-analyst.md) | Product | Product analytics, KPI design, experiment design |
|
||||
| [cs-engineering-lead](engineering-team/cs-engineering-lead.md) | Engineering | Engineering team coordination and incident management |
|
||||
| [cs-workspace-admin](engineering-team/cs-workspace-admin.md) | Engineering | Google Workspace administration via gws CLI |
|
||||
| [cs-senior-engineer](engineering/cs-senior-engineer.md) | Engineering | Architecture decisions, code review, CI/CD setup |
|
||||
@@ -375,5 +376,5 @@ After creating an agent:
|
||||
---
|
||||
|
||||
**Last Updated:** March 11, 2026
|
||||
**Current:** 15 agents across 8 domains
|
||||
**Current:** 16 agents across 8 domains
|
||||
**Related:** See [main CLAUDE.md](../CLAUDE.md) for repository overview
|
||||
|
||||
31
agents/product/cs-product-analyst.md
Normal file
31
agents/product/cs-product-analyst.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
name: cs-product-analyst
|
||||
description: Product analytics agent for KPI definition, dashboard setup, experiment design, and test result interpretation.
|
||||
skills:
|
||||
- product-team/product-analytics
|
||||
- product-team/experiment-designer
|
||||
domain: product
|
||||
model: sonnet
|
||||
tools: [Read, Write, Bash, Grep, Glob]
|
||||
---
|
||||
|
||||
# Product Analyst Agent
|
||||
|
||||
## 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.
|
||||
25
commands/prd.md
Normal file
25
commands/prd.md
Normal file
@@ -0,0 +1,25 @@
|
||||
---
|
||||
name: prd
|
||||
description: Quick PRD generation command. Usage: /prd <feature-or-problem>
|
||||
---
|
||||
|
||||
# /prd
|
||||
|
||||
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`
|
||||
25
commands/sprint-plan.md
Normal file
25
commands/sprint-plan.md
Normal file
@@ -0,0 +1,25 @@
|
||||
---
|
||||
name: sprint-plan
|
||||
description: Sprint planning shortcut. Usage: /sprint-plan <goal> [capacity]
|
||||
---
|
||||
|
||||
# /sprint-plan
|
||||
|
||||
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`
|
||||
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.
|
||||
@@ -1,6 +1,6 @@
|
||||
site_name: Claude Code Skills & Plugins
|
||||
site_url: https://alirezarezvani.github.io/claude-skills/
|
||||
site_description: "173 production-ready skills, 15 agents, and 15 commands for Claude Code, OpenAI Codex, Gemini CLI, and OpenClaw. Reusable expertise for engineering, product, marketing, compliance, and more."
|
||||
site_description: "177 production-ready skills, 16 agents, and 17 commands for Claude Code, OpenAI Codex, Gemini CLI, and OpenClaw. Reusable expertise for engineering, product, marketing, compliance, and more."
|
||||
site_author: Alireza Rezvani
|
||||
repo_url: https://github.com/alirezarezvani/claude-skills
|
||||
repo_name: alirezarezvani/claude-skills
|
||||
@@ -190,9 +190,13 @@ nav:
|
||||
- Overview: skills/product-team/index.md
|
||||
- "Agile Product Owner": skills/product-team/agile-product-owner.md
|
||||
- "Competitive Teardown": skills/product-team/competitive-teardown.md
|
||||
- "Experiment Designer": skills/product-team/experiment-designer.md
|
||||
- "Landing Page Generator": skills/product-team/landing-page-generator.md
|
||||
- "Product Analytics": skills/product-team/product-analytics.md
|
||||
- "Product Discovery": skills/product-team/product-discovery.md
|
||||
- "Product Manager Toolkit": skills/product-team/product-manager-toolkit.md
|
||||
- "Product Strategist": skills/product-team/product-strategist.md
|
||||
- "Roadmap Communicator": skills/product-team/roadmap-communicator.md
|
||||
- "SaaS Scaffolder": skills/product-team/saas-scaffolder.md
|
||||
- "UI Design System": skills/product-team/ui-design-system.md
|
||||
- "UX Researcher & Designer": skills/product-team/ux-researcher-designer.md
|
||||
@@ -325,6 +329,7 @@ nav:
|
||||
- "CS Growth Strategist": agents/cs-growth-strategist.md
|
||||
- "CS Product Manager": agents/cs-product-manager.md
|
||||
- "CS Workspace Admin": agents/cs-workspace-admin.md
|
||||
- "CS Product Analyst": agents/cs-product-analyst.md
|
||||
- "CS Product Strategist": agents/cs-product-strategist.md
|
||||
- "CS Project Manager": agents/cs-project-manager.md
|
||||
- "CS Quality & Regulatory": agents/cs-quality-regulatory.md
|
||||
@@ -338,11 +343,13 @@ nav:
|
||||
- "/okr": commands/okr.md
|
||||
- "/persona": commands/persona.md
|
||||
- "/pipeline": commands/pipeline.md
|
||||
- "/prd": commands/prd.md
|
||||
- "/project-health": commands/project-health.md
|
||||
- "/retro": commands/retro.md
|
||||
- "/rice": commands/rice.md
|
||||
- "/saas-health": commands/saas-health.md
|
||||
- "/sprint-health": commands/sprint-health.md
|
||||
- "/sprint-plan": commands/sprint-plan.md
|
||||
- "/tdd": commands/tdd.md
|
||||
- "/tech-debt": commands/tech-debt.md
|
||||
- "/user-story": commands/user-story.md
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
{
|
||||
"name": "product-skills",
|
||||
"description": "8 product skills: product manager toolkit (RICE, PRDs), agile product owner, product strategist, UX researcher designer, UI design system, competitive teardown, landing page generator, and SaaS scaffolder",
|
||||
"description": "12 production-ready product skills: 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, and roadmap communicator",
|
||||
"version": "2.1.2",
|
||||
"author": {
|
||||
"name": "Alireza Rezvani",
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# Product Team Skills - Claude Code Guidance
|
||||
|
||||
This guide covers the 8 production-ready product management skills and their Python automation tools.
|
||||
This guide covers the 12 production-ready product management skills and their Python automation tools.
|
||||
|
||||
## Product Skills Overview
|
||||
|
||||
@@ -13,12 +13,16 @@ This guide covers the 8 production-ready product management skills and their Pyt
|
||||
6. **competitive-teardown/** - Competitive matrix building, gap analysis (1 tool)
|
||||
7. **landing-page-generator/** - Landing page scaffolding (1 tool)
|
||||
8. **saas-scaffolder/** - SaaS project bootstrapping (1 tool)
|
||||
9. **product-analytics/** - KPI design, retention/cohort/funnel analysis (1 tool)
|
||||
10. **experiment-designer/** - Experiment design and sample size planning (1 tool)
|
||||
11. **product-discovery/** - Discovery frameworks and assumption mapping (1 tool)
|
||||
12. **roadmap-communicator/** - Roadmap communication and changelog generation (1 tool)
|
||||
|
||||
**Total Tools:** 9 Python automation tools
|
||||
**Total Tools:** 13 Python automation tools
|
||||
|
||||
**Agents:** 4 (cs-product-manager, cs-agile-product-owner, cs-product-strategist, cs-ux-researcher)
|
||||
**Agents:** 5 (cs-product-manager, cs-agile-product-owner, cs-product-strategist, cs-ux-researcher, cs-product-analyst)
|
||||
|
||||
**Slash Commands:** 5 (/rice, /okr, /persona, /user-story, /competitive-matrix)
|
||||
**Slash Commands:** 7 (/rice, /okr, /persona, /user-story, /competitive-matrix, /prd, /sprint-plan)
|
||||
|
||||
## Python Automation Tools
|
||||
|
||||
@@ -95,14 +99,6 @@ python agile-product-owner/scripts/user_story_generator.py
|
||||
python agile-product-owner/scripts/user_story_generator.py sprint 30
|
||||
```
|
||||
|
||||
**Output Format:**
|
||||
```
|
||||
US-001: As a user, I want to...
|
||||
Priority: High | Points: 5
|
||||
Acceptance Criteria:
|
||||
- Given... When... Then...
|
||||
```
|
||||
|
||||
### 4. OKR Cascade Generator (`product-strategist/scripts/okr_cascade_generator.py`)
|
||||
|
||||
**Purpose:** Automated OKR hierarchy (company → product → team)
|
||||
@@ -126,18 +122,9 @@ python product-strategist/scripts/okr_cascade_generator.py retention
|
||||
|
||||
**Purpose:** Data-driven persona creation from user research
|
||||
|
||||
**Features:**
|
||||
- Demographic and psychographic profiling
|
||||
- Goals, pain points, and behavior patterns
|
||||
- User journey mapping integration
|
||||
- Empathy map generation
|
||||
|
||||
**Usage:**
|
||||
```bash
|
||||
# Interactive persona creation
|
||||
python ux-researcher-designer/scripts/persona_generator.py
|
||||
|
||||
# JSON export
|
||||
python ux-researcher-designer/scripts/persona_generator.py --output json
|
||||
```
|
||||
|
||||
@@ -145,22 +132,10 @@ python ux-researcher-designer/scripts/persona_generator.py --output json
|
||||
|
||||
**Purpose:** Complete design token system from brand color
|
||||
|
||||
**Features:**
|
||||
- Color palette generation (primary, secondary, neutrals)
|
||||
- Typography scale (font sizes, line heights, weights)
|
||||
- Spacing system (4px/8px grid)
|
||||
- Shadow and elevation tokens
|
||||
- Export formats: CSS, JSON, SCSS
|
||||
|
||||
**Usage:**
|
||||
```bash
|
||||
# Generate design tokens
|
||||
python ui-design-system/scripts/design_token_generator.py "#0066CC" modern css
|
||||
|
||||
# SCSS output
|
||||
python ui-design-system/scripts/design_token_generator.py "#0066CC" modern scss
|
||||
|
||||
# JSON for Figma integration
|
||||
python ui-design-system/scripts/design_token_generator.py "#0066CC" modern json
|
||||
```
|
||||
|
||||
@@ -182,47 +157,11 @@ python competitive-teardown/scripts/competitive_matrix_builder.py competitors.js
|
||||
- 4 design styles: `dark-saas`, `clean-minimal`, `bold-startup`, `enterprise`
|
||||
- 7 section generators: nav, hero, features, testimonials, pricing, CTA, footer
|
||||
- Copy frameworks: PAS, AIDA, BAB
|
||||
- SEO metadata export
|
||||
- HTML output preserved via `--format html`
|
||||
|
||||
**Usage:**
|
||||
```bash
|
||||
# TSX output (default) with design style
|
||||
python landing-page-generator/scripts/landing_page_scaffolder.py config.json --format tsx
|
||||
|
||||
# HTML output
|
||||
python landing-page-generator/scripts/landing_page_scaffolder.py config.json --format html
|
||||
|
||||
# JSON manifest (dry run)
|
||||
python landing-page-generator/scripts/landing_page_scaffolder.py config.json --format json
|
||||
```
|
||||
|
||||
**Config JSON format:**
|
||||
```json
|
||||
{
|
||||
"product_name": "Acme",
|
||||
"tagline": "Ship faster. Break less.",
|
||||
"design_style": "dark-saas",
|
||||
"copy_framework": "PAS",
|
||||
"sections": ["nav", "hero", "features", "pricing", "cta", "footer"],
|
||||
"features": [
|
||||
{"title": "Fast deploys", "description": "Zero-downtime deployments"}
|
||||
],
|
||||
"pricing": [
|
||||
{"name": "Free", "price": "$0/mo", "features": ["5 projects"]},
|
||||
{"name": "Pro", "price": "$29/mo", "features": ["Unlimited"], "highlighted": true}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
**Brand Voice Integration:** Before generating copy, run the brand voice analyzer to establish tone and formality:
|
||||
```bash
|
||||
# 1. Analyze existing brand content to establish voice profile
|
||||
python ../marketing-skill/content-production/scripts/brand_voice_analyzer.py brand_samples.txt --format json > voice_profile.json
|
||||
|
||||
# 2. Use the voice profile (formality, tone, perspective) to guide copy framework selection
|
||||
# 3. Generate landing page with matching style
|
||||
python landing-page-generator/scripts/landing_page_scaffolder.py config.json --format tsx
|
||||
```
|
||||
|
||||
### 9. Project Bootstrapper (`saas-scaffolder/scripts/project_bootstrapper.py`)
|
||||
@@ -234,102 +173,123 @@ python landing-page-generator/scripts/landing_page_scaffolder.py config.json --f
|
||||
python saas-scaffolder/scripts/project_bootstrapper.py project_config.json
|
||||
```
|
||||
|
||||
### 10. Metrics Calculator (`product-analytics/scripts/metrics_calculator.py`)
|
||||
|
||||
**Purpose:** Product analytics — retention, cohort, and funnel analysis
|
||||
|
||||
**Features:**
|
||||
- Retention curve analysis from event data
|
||||
- Funnel conversion tracking with stage-by-stage drop-off
|
||||
- Cohort grouping and comparison
|
||||
|
||||
**Usage:**
|
||||
```bash
|
||||
# Retention analysis
|
||||
python product-analytics/scripts/metrics_calculator.py retention events.csv
|
||||
|
||||
# Funnel analysis
|
||||
python product-analytics/scripts/metrics_calculator.py funnel funnel.csv --stages visit,signup,activate,pay
|
||||
|
||||
# KPI summary
|
||||
python product-analytics/scripts/metrics_calculator.py kpi metrics.csv --json
|
||||
```
|
||||
|
||||
### 11. Sample Size Calculator (`experiment-designer/scripts/sample_size_calculator.py`)
|
||||
|
||||
**Purpose:** Statistical sample size planning for A/B tests and experiments
|
||||
|
||||
**Features:**
|
||||
- Minimum detectable effect (MDE) calculation
|
||||
- Absolute and relative effect size modes
|
||||
- Power analysis with configurable alpha/beta
|
||||
|
||||
**Usage:**
|
||||
```bash
|
||||
# Absolute MDE
|
||||
python experiment-designer/scripts/sample_size_calculator.py --baseline-rate 0.12 --mde 0.02 --mde-type absolute
|
||||
|
||||
# Relative MDE
|
||||
python experiment-designer/scripts/sample_size_calculator.py --baseline-rate 0.12 --mde 0.15 --mde-type relative
|
||||
|
||||
# Custom power/significance
|
||||
python experiment-designer/scripts/sample_size_calculator.py --baseline-rate 0.12 --mde 0.02 --alpha 0.01 --power 0.9
|
||||
```
|
||||
|
||||
### 12. Assumption Mapper (`product-discovery/scripts/assumption_mapper.py`)
|
||||
|
||||
**Purpose:** Map and prioritize product assumptions for discovery validation
|
||||
|
||||
**Features:**
|
||||
- Risk × uncertainty scoring for prioritization
|
||||
- CSV input with structured assumption fields
|
||||
- Categorization by assumption type (desirability, viability, feasibility, usability)
|
||||
|
||||
**Usage:**
|
||||
```bash
|
||||
python product-discovery/scripts/assumption_mapper.py assumptions.csv
|
||||
python product-discovery/scripts/assumption_mapper.py assumptions.csv --json
|
||||
```
|
||||
|
||||
### 13. Changelog Generator (`roadmap-communicator/scripts/changelog_generator.py`)
|
||||
|
||||
**Purpose:** Generate structured changelogs from git commit history
|
||||
|
||||
**Note:** Requires `git` on PATH — must be run inside a git repository.
|
||||
|
||||
**Usage:**
|
||||
```bash
|
||||
python roadmap-communicator/scripts/changelog_generator.py --from v1.0.0 --to HEAD
|
||||
python roadmap-communicator/scripts/changelog_generator.py --from v1.0.0 --to v2.0.0 --json
|
||||
```
|
||||
|
||||
## Product Workflows
|
||||
|
||||
### Workflow 1: Feature Prioritization
|
||||
### Workflow 1: Feature Prioritization to Sprint Execution
|
||||
|
||||
```bash
|
||||
# 1. Collect feature requests
|
||||
cat feature-requests.csv
|
||||
|
||||
# 2. Run RICE prioritization
|
||||
python product-manager-toolkit/scripts/rice_prioritizer.py features.csv --capacity 30
|
||||
|
||||
# 3. Generate quarterly roadmap
|
||||
|
||||
# 4. Create user stories for top priorities
|
||||
python agile-product-owner/scripts/user_story_generator.py sprint 30
|
||||
```
|
||||
|
||||
### Workflow 2: User Research to Product
|
||||
### Workflow 2: Strategy to Team-Level OKRs
|
||||
|
||||
```bash
|
||||
# 1. Conduct user interviews
|
||||
|
||||
# 2. Analyze transcripts
|
||||
python product-manager-toolkit/scripts/customer_interview_analyzer.py interview-001.txt
|
||||
|
||||
# 3. Generate personas
|
||||
python ux-researcher-designer/scripts/persona_generator.py
|
||||
|
||||
# 4. Create OKRs based on insights
|
||||
python product-strategist/scripts/okr_cascade_generator.py growth
|
||||
python product-strategist/scripts/okr_cascade_generator.py growth --json > okrs.json
|
||||
```
|
||||
|
||||
### Workflow 3: Sprint Planning
|
||||
### Workflow 3: Research to Persona Artifacts
|
||||
|
||||
```bash
|
||||
# 1. Set sprint capacity (story points)
|
||||
CAPACITY=30
|
||||
|
||||
# 2. Generate user stories
|
||||
python agile-product-owner/scripts/user_story_generator.py sprint $CAPACITY
|
||||
|
||||
# 3. Export to Jira (via JSON)
|
||||
python product-manager-toolkit/scripts/rice_prioritizer.py features.csv --output json > priorities.json
|
||||
python ux-researcher-designer/scripts/persona_generator.py json > personas.json
|
||||
```
|
||||
|
||||
### Workflow 4: Brand-Aligned Landing Page
|
||||
|
||||
This workflow connects the marketing brand voice skill with the landing page generator to ensure copy consistency.
|
||||
|
||||
```bash
|
||||
# 1. Analyze existing brand content for voice profile
|
||||
python ../marketing-skill/content-production/scripts/brand_voice_analyzer.py website_copy.txt --format json > voice.json
|
||||
# Output: formality (formal/casual), tone (professional/friendly), perspective (authoritative/conversational)
|
||||
|
||||
# 2. Map voice profile to design style + copy framework:
|
||||
# - formal + professional → enterprise style, AIDA framework
|
||||
# - casual + friendly → bold-startup style, BAB framework
|
||||
# - professional + authoritative → dark-saas style, PAS framework
|
||||
# - casual + conversational → clean-minimal style, BAB framework
|
||||
|
||||
# 3. Generate design tokens for brand consistency
|
||||
python ui-design-system/scripts/design_token_generator.py "#0066CC" modern css
|
||||
|
||||
# 4. Generate the landing page
|
||||
python landing-page-generator/scripts/landing_page_scaffolder.py config.json --format tsx
|
||||
|
||||
# 5. Run competitive teardown to refine positioning
|
||||
python competitive-teardown/scripts/competitive_matrix_builder.py competitors.json
|
||||
```
|
||||
|
||||
## Integration Patterns
|
||||
|
||||
### Jira Integration
|
||||
|
||||
All tools support JSON output for Jira import:
|
||||
### Workflow 5: Product Analytics and Experimentation
|
||||
|
||||
```bash
|
||||
# Export prioritized features
|
||||
python product-manager-toolkit/scripts/rice_prioritizer.py features.csv --output json > jira-import.json
|
||||
python product-analytics/scripts/metrics_calculator.py retention events.csv
|
||||
python product-analytics/scripts/metrics_calculator.py funnel funnel.csv --stages visit,signup,activate,pay
|
||||
python experiment-designer/scripts/sample_size_calculator.py --baseline-rate 0.12 --mde 0.02 --mde-type absolute
|
||||
```
|
||||
|
||||
### Figma Integration
|
||||
|
||||
Design tokens export for Figma plugins:
|
||||
### Workflow 6: Discovery and Opportunity Validation
|
||||
|
||||
```bash
|
||||
# Generate tokens
|
||||
python ui-design-system/scripts/design_token_generator.py "#0066CC" modern json > design-tokens.json
|
||||
python product-discovery/scripts/assumption_mapper.py assumptions.csv
|
||||
```
|
||||
|
||||
### Confluence Documentation
|
||||
|
||||
Use persona generator output for user documentation:
|
||||
### Workflow 7: Roadmap and Release Communication
|
||||
|
||||
```bash
|
||||
python ux-researcher-designer/scripts/persona_generator.py --output json > personas.json
|
||||
python roadmap-communicator/scripts/changelog_generator.py --from v1.0.0 --to HEAD
|
||||
```
|
||||
|
||||
## Quality Standards
|
||||
@@ -341,20 +301,6 @@ python ux-researcher-designer/scripts/persona_generator.py --output json > perso
|
||||
- Standard library only (minimal dependencies)
|
||||
- Actionable recommendations
|
||||
|
||||
## Cross-Domain Integration
|
||||
|
||||
### Brand Voice → Landing Page
|
||||
|
||||
The landing page generator integrates with the marketing brand voice analyzer (`marketing-skill/content-production/scripts/brand_voice_analyzer.py`) to ensure copy on generated pages matches the brand's established voice. The analyzer outputs formality, tone, and perspective dimensions which map to design style and copy framework choices. See Workflow 4 above.
|
||||
|
||||
### Design Tokens → Landing Page
|
||||
|
||||
Design tokens from `ui-design-system/scripts/design_token_generator.py` can be generated alongside landing pages to ensure consistent color, typography, and spacing across the product.
|
||||
|
||||
### Competitive Teardown → Landing Page
|
||||
|
||||
Competitive positioning from `competitive-teardown/scripts/competitive_matrix_builder.py` informs landing page messaging — use SWOT analysis to identify differentiation points and translate them into hero copy and feature sections.
|
||||
|
||||
## Additional Resources
|
||||
|
||||
- **Main Documentation:** `../CLAUDE.md`
|
||||
@@ -362,7 +308,7 @@ Competitive positioning from `competitive-teardown/scripts/competitive_matrix_bu
|
||||
|
||||
---
|
||||
|
||||
**Last Updated:** March 10, 2026
|
||||
**Skills Deployed:** 8/8 product skills production-ready
|
||||
**Total Tools:** 9 Python automation tools
|
||||
**Agents:** 4 | **Commands:** 5
|
||||
**Last Updated:** March 11, 2026
|
||||
**Skills Deployed:** 12/12 product skills production-ready
|
||||
**Total Tools:** 13 Python automation tools
|
||||
**Agents:** 5 | **Commands:** 7
|
||||
|
||||
Binary file not shown.
@@ -0,0 +1,107 @@
|
||||
# Competitive Analysis Frameworks
|
||||
|
||||
This reference provides practical frameworks for evaluating competitors and positioning decisions.
|
||||
|
||||
## Porter's Five Forces
|
||||
|
||||
Assess the competitive intensity of your market:
|
||||
|
||||
1. Threat of new entrants
|
||||
- Barriers to entry (capital, regulation, network effects)
|
||||
- Speed of competitor replication
|
||||
|
||||
2. Bargaining power of suppliers
|
||||
- Dependency on core infrastructure vendors
|
||||
- Concentration of key technical providers
|
||||
|
||||
3. Bargaining power of buyers
|
||||
- Customer switching costs
|
||||
- Procurement complexity and contract leverage
|
||||
|
||||
4. Threat of substitutes
|
||||
- Adjacent alternatives solving the same job
|
||||
- DIY and internal build options
|
||||
|
||||
5. Rivalry among existing competitors
|
||||
- Number and similarity of competitors
|
||||
- Price competition and differentiation pressure
|
||||
|
||||
### Five Forces Template
|
||||
|
||||
| Force | Current Pressure (Low/Med/High) | Evidence | Strategic Response |
|
||||
|---|---|---|---|
|
||||
| New Entrants | | | |
|
||||
| Supplier Power | | | |
|
||||
| Buyer Power | | | |
|
||||
| Substitutes | | | |
|
||||
| Rivalry | | | |
|
||||
|
||||
## SWOT Analysis
|
||||
|
||||
Use SWOT to map internal and external context quickly.
|
||||
|
||||
### SWOT Template
|
||||
|
||||
| Strengths (Internal) | Weaknesses (Internal) |
|
||||
|---|---|
|
||||
| What we do better than alternatives | Where competitors outperform us |
|
||||
| Unique capabilities or assets | Known product or go-to-market gaps |
|
||||
|
||||
| Opportunities (External) | Threats (External) |
|
||||
|---|---|
|
||||
| Market trends we can exploit | Competitor moves or macro risks |
|
||||
| Unserved segments and use cases | Regulatory, platform, or pricing pressure |
|
||||
|
||||
### SWOT Quality Checklist
|
||||
|
||||
- Base every point on evidence, not assumptions.
|
||||
- Separate observations from conclusions.
|
||||
- Prioritize top 3 items per quadrant.
|
||||
|
||||
## Feature Comparison Matrix
|
||||
|
||||
Compare products on meaningful buying criteria, not vanity features.
|
||||
|
||||
### Feature Matrix Template
|
||||
|
||||
| Dimension | Weight | Your Product | Competitor A | Competitor B | Notes |
|
||||
|---|---:|---:|---:|---:|---|
|
||||
| Core workflow coverage | 25% | | | | |
|
||||
| Ease of implementation | 15% | | | | |
|
||||
| Performance / reliability | 15% | | | | |
|
||||
| Integrations / ecosystem | 15% | | | | |
|
||||
| Security / compliance | 15% | | | | |
|
||||
| Pricing / TCO | 15% | | | | |
|
||||
|
||||
Scoring scale recommendation: 1-5 (weak to strong).
|
||||
|
||||
## Competitive Positioning Map
|
||||
|
||||
Create a 2-axis map showing market whitespace and crowding.
|
||||
|
||||
### Positioning Map Steps
|
||||
|
||||
1. Select two high-signal dimensions customers care about.
|
||||
2. Place each competitor based on evidence (pricing pages, reviews, demos).
|
||||
3. Mark clusters where products are undifferentiated.
|
||||
4. Identify white space where demand exists but options are weak.
|
||||
|
||||
Example axes:
|
||||
- X-axis: Ease of use
|
||||
- Y-axis: Enterprise readiness
|
||||
|
||||
## Blue Ocean Strategy Canvas
|
||||
|
||||
Use a strategy canvas to decide where to raise, reduce, eliminate, or create factors.
|
||||
|
||||
### ERRC Grid (Eliminate-Reduce-Raise-Create)
|
||||
|
||||
| Eliminate | Reduce | Raise | Create |
|
||||
|---|---|---|---|
|
||||
| Commodity table-stakes not valued by target users | Costly features with weak adoption | Differentiators tied to target job-to-be-done | New value dimensions competitors ignore |
|
||||
|
||||
### Strategy Canvas Checklist
|
||||
|
||||
- Compare value curves between your product and top competitors.
|
||||
- Ensure target segment is explicit.
|
||||
- Tie every strategic choice to measurable outcome.
|
||||
@@ -1,242 +0,0 @@
|
||||
# 🎯 Complete Product Team Skills Suite - All 5 Roles
|
||||
|
||||
## ✅ All Skills Successfully Created and Packaged!
|
||||
|
||||
You now have **5 specialized skills** for your **5 product team roles**, each with production-ready automation tools.
|
||||
|
||||
---
|
||||
|
||||
## 📦 Delivered Skills Package
|
||||
|
||||
### 1. product-strategist.zip - Head of Product
|
||||
**Strategic Planning & Vision**
|
||||
- **OKR Cascade Generator**: Automatically aligns company → product → team goals
|
||||
- **Alignment Scoring**: Measures vertical and horizontal OKR alignment
|
||||
- **Strategy Templates**: Growth, retention, revenue, innovation strategies
|
||||
- **Team Scaling Tools**: Organizational design frameworks
|
||||
|
||||
**Key Capability**: Run `okr_cascade_generator.py growth` to generate complete OKR hierarchy with 85%+ alignment score
|
||||
|
||||
---
|
||||
|
||||
### 2. product-manager-toolkit.zip - Senior Product Manager
|
||||
**Feature Development & Discovery**
|
||||
- **RICE Prioritizer**: Automated scoring with roadmap generation
|
||||
- **Customer Interview Analyzer**: AI-powered insight extraction
|
||||
- **PRD Templates**: 4 formats for different feature types
|
||||
- **Portfolio Analysis**: Quick wins vs big bets identification
|
||||
|
||||
**Key Capability**: Run `rice_prioritizer.py` to prioritize entire backlog in seconds
|
||||
|
||||
---
|
||||
|
||||
### 3. agile-product-owner.zip - Senior Product Owner
|
||||
**Sprint Execution & Backlog Management**
|
||||
- **User Story Generator**: INVEST-compliant stories with acceptance criteria
|
||||
- **Sprint Planner**: Capacity-based sprint planning
|
||||
- **Epic Breakdown**: Automatic story generation from epics
|
||||
- **Velocity Tracker**: Sprint metrics and burndown
|
||||
|
||||
**Key Capability**: Run `user_story_generator.py sprint 30` to plan complete sprint
|
||||
|
||||
---
|
||||
|
||||
### 4. ux-researcher-designer.zip - Senior UX Designer/Researcher
|
||||
**User Research & Experience Design**
|
||||
- **Persona Generator**: Data-driven personas from user research
|
||||
- **Journey Mapper**: Customer journey visualization
|
||||
- **Research Synthesizer**: Pattern identification from interviews
|
||||
- **Usability Framework**: Testing protocols and heuristics
|
||||
|
||||
**Key Capability**: Run `persona_generator.py` to create research-backed personas
|
||||
|
||||
---
|
||||
|
||||
### 5. ui-design-system.zip - Senior UI Designer
|
||||
**Visual Design & Systems**
|
||||
- **Design Token Generator**: Complete token system from brand color
|
||||
- **Component Architecture**: Atomic design implementation
|
||||
- **Responsive Calculator**: Breakpoint and grid systems
|
||||
- **Export Formats**: JSON, CSS, SCSS outputs
|
||||
|
||||
**Key Capability**: Run `design_token_generator.py #0066CC modern css` for complete design system
|
||||
|
||||
---
|
||||
|
||||
## 🔄 How The Skills Work Together
|
||||
|
||||
```
|
||||
Strategic Level (Head of Product)
|
||||
↓ OKRs & Vision
|
||||
Product Management (Senior PM)
|
||||
↓ Prioritized Features & PRDs
|
||||
Design (UX/UI)
|
||||
↓ Validated Designs & Systems
|
||||
Execution (Product Owner)
|
||||
↓ User Stories & Sprints
|
||||
Development Team
|
||||
= Shipped Features
|
||||
```
|
||||
|
||||
## 📊 Impact Metrics by Role
|
||||
|
||||
### Head of Product
|
||||
- **Strategic Alignment**: +85% improvement
|
||||
- **Planning Time**: -70% reduction
|
||||
- **Goal Clarity**: +90% improvement
|
||||
|
||||
### Senior Product Manager
|
||||
- **Prioritization Speed**: -50% time
|
||||
- **Feature Success Rate**: +35% improvement
|
||||
- **PRD Quality**: +40% consistency
|
||||
|
||||
### Senior Product Owner
|
||||
- **Story Quality**: +60% INVEST compliance
|
||||
- **Sprint Planning**: -40% time
|
||||
- **Velocity Predictability**: +30% accuracy
|
||||
|
||||
### Senior UX Designer/Researcher
|
||||
- **Research Synthesis**: -80% time
|
||||
- **Persona Accuracy**: +45% data-driven
|
||||
- **Design Validation**: +50% confidence
|
||||
|
||||
### Senior UI Designer
|
||||
- **Design Consistency**: 95% compliance
|
||||
- **Token Generation**: -90% time
|
||||
- **Handoff Quality**: +60% clarity
|
||||
|
||||
## 🚀 Quick Start Guide
|
||||
|
||||
### Step 1: Download All Skills
|
||||
- [product-strategist.zip](computer:///mnt/user-data/outputs/product-strategist.zip)
|
||||
- [product-manager-toolkit.zip](computer:///mnt/user-data/outputs/product-manager-toolkit.zip)
|
||||
- [agile-product-owner.zip](computer:///mnt/user-data/outputs/agile-product-owner.zip)
|
||||
- [ux-researcher-designer.zip](computer:///mnt/user-data/outputs/ux-researcher-designer.zip)
|
||||
- [ui-design-system.zip](computer:///mnt/user-data/outputs/ui-design-system.zip)
|
||||
|
||||
### Step 2: Test Each Skill
|
||||
```bash
|
||||
# Head of Product
|
||||
python okr_cascade_generator.py growth
|
||||
|
||||
# Product Manager
|
||||
python rice_prioritizer.py
|
||||
python customer_interview_analyzer.py sample.txt
|
||||
|
||||
# Product Owner
|
||||
python user_story_generator.py
|
||||
python user_story_generator.py sprint 30
|
||||
|
||||
# UX Designer
|
||||
python persona_generator.py
|
||||
|
||||
# UI Designer
|
||||
python design_token_generator.py #0066CC modern json
|
||||
```
|
||||
|
||||
### Step 3: Integrate with Workflow
|
||||
1. Upload to Claude for AI-enhanced usage
|
||||
2. Integrate scripts with existing tools
|
||||
3. Customize templates for your context
|
||||
4. Train team on new capabilities
|
||||
|
||||
## 🎓 Training Plan by Role
|
||||
|
||||
### Week 1: Strategic Layer
|
||||
- Head of Product: OKR workshop (2 hours)
|
||||
- Practice cascade generation
|
||||
- Align with company strategy
|
||||
|
||||
### Week 2: Product Management
|
||||
- PMs: Prioritization training (2 hours)
|
||||
- Interview analysis practice
|
||||
- PRD standardization
|
||||
|
||||
### Week 3: Design Layer
|
||||
- UX: Persona workshop (2 hours)
|
||||
- UI: Design system training (2 hours)
|
||||
- Establish design language
|
||||
|
||||
### Week 4: Execution Layer
|
||||
- Product Owners: Story writing (2 hours)
|
||||
- Sprint planning optimization
|
||||
- Velocity tracking setup
|
||||
|
||||
## 💰 Total ROI Calculation
|
||||
|
||||
### Combined Time Savings (Monthly)
|
||||
- Strategic Planning: 40 hours
|
||||
- Product Management: 60 hours
|
||||
- Design Process: 50 hours
|
||||
- Sprint Execution: 30 hours
|
||||
- **Total: 180 hours/month saved**
|
||||
|
||||
### Quality Improvements
|
||||
- Feature Success: +35%
|
||||
- Design Consistency: +95%
|
||||
- Sprint Predictability: +30%
|
||||
- Team Alignment: +85%
|
||||
|
||||
### Financial Impact
|
||||
- Time Value: $18,000/month (@ $100/hour)
|
||||
- Quality Value: $25,000/month (reduced rework)
|
||||
- Speed Value: $30,000/month (faster delivery)
|
||||
- **Total: $73,000/month value**
|
||||
|
||||
### Payback Period: < 3 days
|
||||
|
||||
## 🔧 Technical Requirements
|
||||
|
||||
### Minimum Setup
|
||||
- Python 3.7+
|
||||
- No additional libraries required for most scripts
|
||||
- CSV support for data import/export
|
||||
|
||||
### Recommended Integrations
|
||||
- Jira (via CSV export)
|
||||
- Figma (manual token import)
|
||||
- Confluence (markdown support)
|
||||
- Google Sheets (CSV compatibility)
|
||||
|
||||
## 📈 Success Metrics to Track
|
||||
|
||||
### Leading Indicators (Week 1-2)
|
||||
- Scripts run per day
|
||||
- Time saved per task
|
||||
- Adoption rate by role
|
||||
|
||||
### Lagging Indicators (Month 1-3)
|
||||
- Feature delivery speed
|
||||
- Quality metrics
|
||||
- Team satisfaction
|
||||
- Customer NPS improvement
|
||||
|
||||
## 🏆 Expected Outcomes
|
||||
|
||||
### 30 Days
|
||||
- All roles using core scripts
|
||||
- 50% time reduction achieved
|
||||
- Standardized workflows established
|
||||
|
||||
### 60 Days
|
||||
- Full skill integration
|
||||
- Cross-functional alignment improved
|
||||
- Measurable quality gains
|
||||
|
||||
### 90 Days
|
||||
- Cultural transformation
|
||||
- Data-driven decisions norm
|
||||
- Predictable delivery achieved
|
||||
|
||||
---
|
||||
|
||||
## 🎯 Your Next Action
|
||||
|
||||
1. **Download all 5 skills** using the links above
|
||||
2. **Run one script** from each skill to see immediate value
|
||||
3. **Share with your team** for feedback
|
||||
4. **Schedule training** for each role
|
||||
|
||||
**You now have a complete, integrated product development system that will transform how your team builds products!**
|
||||
|
||||
Each skill enhances the others, creating a compound effect that will revolutionize your product organization's efficiency, quality, and impact.
|
||||
104
product-team/experiment-designer/SKILL.md
Normal file
104
product-team/experiment-designer/SKILL.md
Normal file
@@ -0,0 +1,104 @@
|
||||
---
|
||||
name: experiment-designer
|
||||
description: Use when planning product experiments, writing testable hypotheses, estimating sample size, prioritizing tests, or interpreting A/B outcomes with practical statistical rigor.
|
||||
---
|
||||
|
||||
# Experiment Designer
|
||||
|
||||
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
|
||||
```
|
||||
@@ -0,0 +1,70 @@
|
||||
# Experiment Playbook
|
||||
|
||||
## Experiment Types
|
||||
|
||||
### A/B Test
|
||||
- Compare one control versus one variant.
|
||||
- Best for high-confidence directional decisions.
|
||||
|
||||
### Multivariate Test
|
||||
- Test combinations of multiple factors.
|
||||
- Useful for interaction effects, requires larger traffic.
|
||||
|
||||
### Holdout Test
|
||||
- Keep a percentage unexposed to intervention.
|
||||
- Useful for measuring incremental lift over broader changes.
|
||||
|
||||
## Metric Design
|
||||
|
||||
### Primary Metric
|
||||
- One metric that decides ship/no-ship.
|
||||
- Must align with user value and business objective.
|
||||
|
||||
### Guardrail Metrics
|
||||
- Prevent local optimization damage.
|
||||
- Examples: error rate, latency, churn proxy, support contacts.
|
||||
|
||||
### Diagnostic Metrics
|
||||
- Explain why change happened.
|
||||
- Do not use as decision gate unless pre-specified.
|
||||
|
||||
## Stopping Rules
|
||||
|
||||
Define before launch:
|
||||
- Fixed sample size per group
|
||||
- Minimum run duration (to capture weekday/weekend behavior)
|
||||
- Guardrail breach thresholds (pause criteria)
|
||||
|
||||
Avoid:
|
||||
- Continuous peeking with fixed-horizon inference
|
||||
- Changing success metric mid-test
|
||||
- Retroactive segmentation without correction
|
||||
|
||||
## Novelty and Primacy Effects
|
||||
|
||||
- Novelty effect: short-term spike due to newness, not durable value.
|
||||
- Primacy effect: early exposure creates bias in user behavior.
|
||||
|
||||
Mitigation:
|
||||
- Run long enough for behavior stabilization.
|
||||
- Check returning users and delayed cohorts separately.
|
||||
- Re-run key tests when stakes are high.
|
||||
|
||||
## Pre-Launch Checklist
|
||||
|
||||
- [ ] Hypothesis complete (If/Then/Because)
|
||||
- [ ] Metric definitions frozen
|
||||
- [ ] Instrumentation validated
|
||||
- [ ] Randomization and assignment verified
|
||||
- [ ] Sample size and duration approved
|
||||
- [ ] Rollback plan documented
|
||||
|
||||
## Post-Test Readout Template
|
||||
|
||||
1. Hypothesis and scope
|
||||
2. Experiment setup and quality checks
|
||||
3. Primary metric effect size + confidence interval
|
||||
4. Guardrail status
|
||||
5. Segment-level observations (pre-registered only)
|
||||
6. Decision: ship, iterate, or reject
|
||||
7. Follow-up experiments
|
||||
@@ -0,0 +1,56 @@
|
||||
# Statistics Reference for Product Managers
|
||||
|
||||
## p-value
|
||||
|
||||
The p-value is the probability of observing data at least as extreme as yours if there were no true effect.
|
||||
|
||||
- Small p-value means data is less consistent with "no effect".
|
||||
- It does not tell you the probability that the variant is best.
|
||||
|
||||
## Confidence Interval (CI)
|
||||
|
||||
A CI gives a plausible range for the true effect size.
|
||||
|
||||
- Narrow interval: more precise estimate.
|
||||
- Wide interval: uncertain estimate.
|
||||
- If CI includes zero (or no-effect), directional confidence is weak.
|
||||
|
||||
## Minimum Detectable Effect (MDE)
|
||||
|
||||
The smallest effect worth detecting.
|
||||
|
||||
- Set MDE by business value threshold, not wishful optimism.
|
||||
- Smaller MDE requires larger sample size.
|
||||
|
||||
## Statistical Power
|
||||
|
||||
Power is the probability of detecting a true effect of at least MDE.
|
||||
|
||||
- Common target: 80% (0.8)
|
||||
- Higher power increases sample requirements.
|
||||
|
||||
## Type I and Type II Errors
|
||||
|
||||
- Type I (false positive): claim effect when none exists (controlled by alpha).
|
||||
- Type II (false negative): miss a real effect (controlled by power).
|
||||
|
||||
## Practical Significance
|
||||
|
||||
An effect can be statistically significant but too small to matter.
|
||||
|
||||
Always ask:
|
||||
- Does the effect clear implementation cost?
|
||||
- Does it move strategic KPIs materially?
|
||||
|
||||
## Power Analysis Inputs
|
||||
|
||||
For conversion experiments (two proportions):
|
||||
- Baseline conversion rate
|
||||
- MDE (absolute points or relative uplift)
|
||||
- Alpha (e.g., 0.05)
|
||||
- Power (e.g., 0.8)
|
||||
|
||||
Output:
|
||||
- Required sample size per variant
|
||||
- Total sample size
|
||||
- Approximate runtime based on traffic volume
|
||||
100
product-team/experiment-designer/scripts/sample_size_calculator.py
Executable file
100
product-team/experiment-designer/scripts/sample_size_calculator.py
Executable file
@@ -0,0 +1,100 @@
|
||||
#!/usr/bin/env python3
|
||||
"""Calculate sample size for two-proportion A/B tests."""
|
||||
|
||||
import argparse
|
||||
import math
|
||||
import statistics
|
||||
|
||||
|
||||
def clamp_rate(value: float, name: str) -> float:
|
||||
if value <= 0 or value >= 1:
|
||||
raise ValueError(f"{name} must be between 0 and 1 (exclusive).")
|
||||
return value
|
||||
|
||||
|
||||
def required_sample_size_per_group(
|
||||
baseline_rate: float,
|
||||
target_rate: float,
|
||||
alpha: float,
|
||||
power: float,
|
||||
) -> int:
|
||||
delta = abs(target_rate - baseline_rate)
|
||||
if delta <= 0:
|
||||
raise ValueError("MDE resolves to zero; target and baseline must differ.")
|
||||
|
||||
z_alpha = statistics.NormalDist().inv_cdf(1 - alpha / 2)
|
||||
z_beta = statistics.NormalDist().inv_cdf(power)
|
||||
pooled = (baseline_rate + target_rate) / 2
|
||||
|
||||
numerator = 2 * pooled * (1 - pooled) * (z_alpha + z_beta) ** 2
|
||||
n = numerator / (delta ** 2)
|
||||
return math.ceil(n)
|
||||
|
||||
|
||||
def parse_args() -> argparse.Namespace:
|
||||
parser = argparse.ArgumentParser(
|
||||
description="Compute sample size for two-proportion product experiments."
|
||||
)
|
||||
parser.add_argument("--baseline-rate", type=float, required=True)
|
||||
parser.add_argument(
|
||||
"--mde",
|
||||
type=float,
|
||||
required=True,
|
||||
help="Minimum detectable effect. Absolute points when --mde-type absolute, otherwise relative uplift.",
|
||||
)
|
||||
parser.add_argument("--mde-type", choices=["absolute", "relative"], default="relative")
|
||||
parser.add_argument("--alpha", type=float, default=0.05)
|
||||
parser.add_argument("--power", type=float, default=0.8)
|
||||
parser.add_argument(
|
||||
"--daily-samples",
|
||||
type=int,
|
||||
default=0,
|
||||
help="Optional total daily samples to estimate runtime in days.",
|
||||
)
|
||||
return parser.parse_args()
|
||||
|
||||
|
||||
def main() -> int:
|
||||
args = parse_args()
|
||||
baseline = clamp_rate(args.baseline_rate, "baseline-rate")
|
||||
|
||||
if args.mde <= 0:
|
||||
raise ValueError("mde must be > 0")
|
||||
if args.alpha <= 0 or args.alpha >= 1:
|
||||
raise ValueError("alpha must be between 0 and 1")
|
||||
if args.power <= 0 or args.power >= 1:
|
||||
raise ValueError("power must be between 0 and 1")
|
||||
|
||||
if args.mde_type == "absolute":
|
||||
target = baseline + args.mde
|
||||
else:
|
||||
target = baseline * (1 + args.mde)
|
||||
|
||||
target = clamp_rate(target, "target-rate")
|
||||
|
||||
n_per_group = required_sample_size_per_group(
|
||||
baseline_rate=baseline,
|
||||
target_rate=target,
|
||||
alpha=args.alpha,
|
||||
power=args.power,
|
||||
)
|
||||
total_n = n_per_group * 2
|
||||
|
||||
print("A/B Test Sample Size Estimate")
|
||||
print(f"baseline_rate: {baseline:.6f}")
|
||||
print(f"target_rate: {target:.6f}")
|
||||
print(f"mde_type: {args.mde_type}")
|
||||
print(f"alpha: {args.alpha}")
|
||||
print(f"power: {args.power}")
|
||||
print(f"n_per_group: {n_per_group}")
|
||||
print(f"n_total: {total_n}")
|
||||
|
||||
if args.daily_samples > 0:
|
||||
days = math.ceil(total_n / args.daily_samples)
|
||||
print(f"estimated_days_at_daily_samples_{args.daily_samples}: {days}")
|
||||
|
||||
return 0
|
||||
|
||||
|
||||
if __name__ == "__main__":
|
||||
raise SystemExit(main())
|
||||
@@ -0,0 +1,98 @@
|
||||
# Landing Page Patterns
|
||||
|
||||
This reference captures high-converting page patterns and copy structures.
|
||||
|
||||
## Hero Section Patterns
|
||||
|
||||
### Pattern 1: Problem-Solution Hero
|
||||
- Headline names the painful problem.
|
||||
- Subheadline states the clear outcome.
|
||||
- Primary CTA starts immediately.
|
||||
- Optional supporting visual demonstrates product in context.
|
||||
|
||||
### Pattern 2: Outcome-First Hero
|
||||
- Headline leads with measurable value.
|
||||
- Subheadline clarifies who the page is for.
|
||||
- CTA is action-oriented and specific.
|
||||
|
||||
### Pattern 3: Authority Hero
|
||||
- Headline + trust indicator (logos, testimonial snippet, proof metric).
|
||||
- Useful when category skepticism is high.
|
||||
|
||||
## Social Proof Layouts
|
||||
|
||||
### Logo Strip + Proof Metric
|
||||
- Keep to recognizable logos.
|
||||
- Add one proof metric (e.g., active users, revenue saved, hours reduced).
|
||||
|
||||
### Testimonial Grid
|
||||
- 3-6 testimonials across segments.
|
||||
- Include role/company where possible.
|
||||
- Prefer concrete outcomes over generic praise.
|
||||
|
||||
### Case Study Snapshot
|
||||
- Mini blocks: challenge -> approach -> measurable result.
|
||||
|
||||
## CTA Best Practices
|
||||
|
||||
- Use one dominant CTA per section.
|
||||
- Match CTA verb to user intent ("Start trial", "Get demo", "Run audit").
|
||||
- Keep CTA copy specific; avoid vague labels like "Submit".
|
||||
- Reduce friction near CTA (short form, trust indicators, no surprise commitments).
|
||||
|
||||
## Above-the-Fold Checklist
|
||||
|
||||
- [ ] Clear value proposition in first viewport
|
||||
- [ ] Audience clarity (who this is for)
|
||||
- [ ] One primary CTA visible without scrolling
|
||||
- [ ] Proof element (logos, stat, quote)
|
||||
- [ ] Visual hierarchy emphasizes headline + CTA
|
||||
- [ ] Mobile layout keeps CTA accessible
|
||||
|
||||
## Conversion-Optimized Templates
|
||||
|
||||
### SaaS Demo Page
|
||||
1. Hero with problem-solution framing
|
||||
2. Product walkthrough section
|
||||
3. Social proof strip
|
||||
4. Benefits by persona
|
||||
5. Objection handling FAQ
|
||||
6. Final CTA
|
||||
|
||||
### Lead Magnet Page
|
||||
1. Promise + asset preview
|
||||
2. Bullet outcomes
|
||||
3. Short form
|
||||
4. Trust/privacy note
|
||||
|
||||
### Product Launch Page
|
||||
1. Outcome-first hero
|
||||
2. Why now / differentiation
|
||||
3. Feature blocks
|
||||
4. Testimonials / beta feedback
|
||||
5. Pricing or waitlist CTA
|
||||
|
||||
## Headline Formulas
|
||||
|
||||
### PAS (Problem-Agitate-Solution)
|
||||
- Problem: identify the pain
|
||||
- Agitate: show consequences of inaction
|
||||
- Solution: position the offer as relief
|
||||
|
||||
Example structure:
|
||||
"Still [problem]? Stop [negative consequence] and start [desired outcome]."
|
||||
|
||||
### AIDA (Attention-Interest-Desire-Action)
|
||||
- Attention: pattern interrupt headline
|
||||
- Interest: relevant context and stakes
|
||||
- Desire: proof and benefits
|
||||
- Action: concrete next step
|
||||
|
||||
### 4U Formula
|
||||
- Useful: clear practical value
|
||||
- Urgent: reason to act now
|
||||
- Unique: differentiated promise
|
||||
- Ultra-specific: concrete outcome and scope
|
||||
|
||||
Example structure:
|
||||
"Get [specific result] in [timeframe] without [common pain]."
|
||||
107
product-team/product-analytics/SKILL.md
Normal file
107
product-team/product-analytics/SKILL.md
Normal file
@@ -0,0 +1,107 @@
|
||||
---
|
||||
name: product-analytics
|
||||
description: Use when defining product KPIs, building metric dashboards, running cohort or retention analysis, or interpreting feature adoption trends across product stages.
|
||||
---
|
||||
|
||||
# Product Analytics
|
||||
|
||||
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
|
||||
```
|
||||
@@ -0,0 +1,66 @@
|
||||
# Dashboard Templates
|
||||
|
||||
## 1. Executive Dashboard Template
|
||||
|
||||
Purpose: quick company-level product signal for leadership.
|
||||
|
||||
Sections:
|
||||
1. North Star trend (current, target, trailing 12 periods)
|
||||
2. Growth summary (new users/accounts, activation)
|
||||
3. Retention summary (short-term + medium-term cohorts)
|
||||
4. Revenue-linked product indicators
|
||||
5. Risks and actions
|
||||
|
||||
Suggested KPI block:
|
||||
|
||||
| KPI | Current | Target | Delta | Owner | Action |
|
||||
|---|---:|---:|---:|---|---|
|
||||
| North Star | | | | | |
|
||||
| Activation Rate | | | | | |
|
||||
| W8 Retention | | | | | |
|
||||
| Paid Conversion | | | | | |
|
||||
|
||||
## 2. Product Health Dashboard Template
|
||||
|
||||
Purpose: monitor full user journey and detect bottlenecks.
|
||||
|
||||
Sections:
|
||||
1. Acquisition funnel by channel/segment
|
||||
2. Activation funnel with drop-off points
|
||||
3. Cohort retention matrix + curve chart
|
||||
4. Feature adoption distribution
|
||||
5. Reliability metrics tied to user outcomes
|
||||
|
||||
Recommended views:
|
||||
- Weekly cohort retention heatmap
|
||||
- Funnel stage conversion waterfall
|
||||
- Segment comparison (SMB vs enterprise)
|
||||
- New vs returning user behavior split
|
||||
|
||||
## 3. Feature Adoption Dashboard Template
|
||||
|
||||
Purpose: evaluate feature launch quality and ongoing usage.
|
||||
|
||||
Sections:
|
||||
1. Exposure and eligibility count
|
||||
2. First-use adoption rate
|
||||
3. Repeat usage rate (2nd, 3rd, nth use)
|
||||
4. Time-to-adoption from signup/activation
|
||||
5. Impact on primary outcomes (retention, conversion)
|
||||
|
||||
Adoption KPI examples:
|
||||
|
||||
| Metric | Definition |
|
||||
|---|---|
|
||||
| First-use adoption | Users who used feature at least once / eligible users |
|
||||
| Repeat adoption | Users with 2+ uses / users with first use |
|
||||
| Sustained adoption | Users with usage in 3 of last 4 weeks |
|
||||
| Time to adoption | Median days from eligibility to first use |
|
||||
|
||||
## Dashboard Design Rules
|
||||
|
||||
- Keep each dashboard to one decision horizon (weekly ops vs quarterly strategy).
|
||||
- Always annotate major product releases on charts.
|
||||
- Add threshold bands for risk detection.
|
||||
- Show metric definitions next to charts.
|
||||
- Include a short "what changed" narrative block.
|
||||
@@ -0,0 +1,84 @@
|
||||
# Metrics Frameworks
|
||||
|
||||
## AARRR (Pirate Metrics)
|
||||
|
||||
AARRR breaks the product journey into five stages.
|
||||
|
||||
1. Acquisition
|
||||
- How users discover the product
|
||||
- Example metrics: signups, CAC, channel conversion
|
||||
|
||||
2. Activation
|
||||
- First meaningful value moment
|
||||
- Example metrics: activation rate, time-to-first-value
|
||||
|
||||
3. Retention
|
||||
- Ongoing user return behavior
|
||||
- Example metrics: D7/W4 retention, rolling retained users
|
||||
|
||||
4. Revenue
|
||||
- Monetization and value capture
|
||||
- Example metrics: conversion to paid, ARPU, expansion revenue
|
||||
|
||||
5. Referral
|
||||
- Organic growth from existing users
|
||||
- Example metrics: referral rate, invite conversion, K-factor
|
||||
|
||||
## North Star Metric Framework
|
||||
|
||||
North Star = metric capturing long-term customer value delivered.
|
||||
|
||||
### North Star Criteria
|
||||
- Reflects real user value
|
||||
- Sensitive to product improvements
|
||||
- Predictive of sustainable growth
|
||||
- Understandable across functions
|
||||
|
||||
### Example North Star Metrics
|
||||
- Collaboration SaaS: weekly active teams
|
||||
- Marketplace: successful transactions per active buyer
|
||||
- Content product: hours of qualified consumption
|
||||
|
||||
### Input Metrics
|
||||
Track levers that influence the North Star:
|
||||
- Acquisition quality
|
||||
- Activation quality
|
||||
- Engagement depth
|
||||
- Retention durability
|
||||
|
||||
## HEART Framework
|
||||
|
||||
HEART is a UX-oriented framework from Google.
|
||||
|
||||
- Happiness: satisfaction, NPS, perceived quality
|
||||
- Engagement: interaction depth/frequency
|
||||
- Adoption: first-time use of features/products
|
||||
- Retention: return behavior over time
|
||||
- Task Success: completion rate, error rate, time on task
|
||||
|
||||
### HEART + Goals-Signals-Metrics
|
||||
1. Goals: what UX outcome you want
|
||||
2. Signals: observed behavior indicating movement
|
||||
3. Metrics: measurable indicator for each signal
|
||||
|
||||
## Framework Selection Guide
|
||||
|
||||
| Situation | Recommended Framework |
|
||||
|---|---|
|
||||
| Early growth and funnel bottlenecks | AARRR |
|
||||
| Company-wide strategic alignment | North Star |
|
||||
| UX and product quality optimization | HEART |
|
||||
| Mixed maturity org | North Star + AARRR operational layers |
|
||||
|
||||
## Example: B2B SaaS Product
|
||||
|
||||
- North Star: weekly active accounts completing core workflow
|
||||
- AARRR operational metrics:
|
||||
- Acquisition: qualified signups
|
||||
- Activation: % accounts completing setup in 7 days
|
||||
- Retention: W8 retained accounts
|
||||
- Revenue: paid conversion and expansion rate
|
||||
- Referral: invited teammate activation rate
|
||||
- HEART for onboarding redesign:
|
||||
- Task Success: onboarding completion rate
|
||||
- Happiness: onboarding CSAT
|
||||
155
product-team/product-analytics/scripts/metrics_calculator.py
Executable file
155
product-team/product-analytics/scripts/metrics_calculator.py
Executable file
@@ -0,0 +1,155 @@
|
||||
#!/usr/bin/env python3
|
||||
"""Product metrics calculator: retention, cohort matrix, and funnel conversion."""
|
||||
|
||||
import argparse
|
||||
import csv
|
||||
import datetime as dt
|
||||
from collections import defaultdict
|
||||
|
||||
|
||||
def parse_date(value: str) -> dt.date:
|
||||
return dt.date.fromisoformat(value.strip()[:10])
|
||||
|
||||
|
||||
def load_csv(path: str):
|
||||
with open(path, "r", encoding="utf-8", newline="") as handle:
|
||||
return list(csv.DictReader(handle))
|
||||
|
||||
|
||||
def retention(args: argparse.Namespace) -> int:
|
||||
rows = load_csv(args.input)
|
||||
cohorts = {}
|
||||
activity = defaultdict(set)
|
||||
|
||||
for row in rows:
|
||||
user = row[args.user_column].strip()
|
||||
cohort_date = parse_date(row[args.cohort_column])
|
||||
activity_date = parse_date(row[args.activity_column])
|
||||
cohorts[user] = min(cohorts.get(user, cohort_date), cohort_date)
|
||||
delta = (activity_date - cohorts[user]).days
|
||||
if delta >= 0:
|
||||
activity[delta].add(user)
|
||||
|
||||
base_users = len(cohorts)
|
||||
if base_users == 0:
|
||||
print("No users found.")
|
||||
return 1
|
||||
|
||||
print("Retention by period")
|
||||
print("period,active_users,retention_rate")
|
||||
max_period = args.max_period
|
||||
for period in range(0, max_period + 1):
|
||||
users = len(activity.get(period, set()))
|
||||
rate = users / base_users
|
||||
print(f"{period},{users},{rate:.4f}")
|
||||
return 0
|
||||
|
||||
|
||||
def cohort(args: argparse.Namespace) -> int:
|
||||
rows = load_csv(args.input)
|
||||
cohorts = {}
|
||||
activity = defaultdict(set)
|
||||
|
||||
for row in rows:
|
||||
user = row[args.user_column].strip()
|
||||
cohort_date = parse_date(row[args.cohort_column])
|
||||
activity_date = parse_date(row[args.activity_column])
|
||||
|
||||
if args.cohort_grain == "month":
|
||||
cohort_key = cohort_date.strftime("%Y-%m")
|
||||
else:
|
||||
cohort_key = f"{cohort_date.isocalendar().year}-W{cohort_date.isocalendar().week:02d}"
|
||||
|
||||
cohorts.setdefault(user, cohort_key)
|
||||
age = (activity_date - cohort_date).days
|
||||
if age >= 0:
|
||||
activity[(cohort_key, age)].add(user)
|
||||
|
||||
cohort_sizes = defaultdict(int)
|
||||
for cohort_key in cohorts.values():
|
||||
cohort_sizes[cohort_key] += 1
|
||||
|
||||
cohort_keys = sorted(cohort_sizes.keys())
|
||||
print("cohort,age_days,active_users,cohort_size,retention_rate")
|
||||
for cohort_key in cohort_keys:
|
||||
size = cohort_sizes[cohort_key]
|
||||
for age in range(0, args.max_period + 1):
|
||||
active_users = len(activity.get((cohort_key, age), set()))
|
||||
rate = (active_users / size) if size else 0
|
||||
print(f"{cohort_key},{age},{active_users},{size},{rate:.4f}")
|
||||
return 0
|
||||
|
||||
|
||||
def funnel(args: argparse.Namespace) -> int:
|
||||
rows = load_csv(args.input)
|
||||
stages = [item.strip() for item in args.stages.split(",") if item.strip()]
|
||||
if not stages:
|
||||
print("No stages provided.")
|
||||
return 1
|
||||
|
||||
stage_users = {stage: set() for stage in stages}
|
||||
for row in rows:
|
||||
user = row[args.user_column].strip()
|
||||
stage = row[args.stage_column].strip()
|
||||
if stage in stage_users:
|
||||
stage_users[stage].add(user)
|
||||
|
||||
print("stage,users,conversion_from_previous,conversion_from_first")
|
||||
previous_count = None
|
||||
first_count = None
|
||||
for stage in stages:
|
||||
count = len(stage_users[stage])
|
||||
if first_count is None:
|
||||
first_count = count
|
||||
conv_prev = (count / previous_count) if previous_count else 1.0
|
||||
conv_first = (count / first_count) if first_count else 0
|
||||
print(f"{stage},{count},{conv_prev:.4f},{conv_first:.4f}")
|
||||
previous_count = count
|
||||
return 0
|
||||
|
||||
|
||||
def build_parser() -> argparse.ArgumentParser:
|
||||
parser = argparse.ArgumentParser(
|
||||
description="Calculate retention, cohort, and funnel metrics from CSV data."
|
||||
)
|
||||
subparsers = parser.add_subparsers(dest="command", required=True)
|
||||
|
||||
common = {
|
||||
"help": "CSV input path",
|
||||
}
|
||||
|
||||
retention_parser = subparsers.add_parser("retention", help="Calculate retention by day.")
|
||||
retention_parser.add_argument("input", **common)
|
||||
retention_parser.add_argument("--user-column", default="user_id")
|
||||
retention_parser.add_argument("--cohort-column", default="cohort_date")
|
||||
retention_parser.add_argument("--activity-column", default="activity_date")
|
||||
retention_parser.add_argument("--max-period", type=int, default=30)
|
||||
retention_parser.set_defaults(func=retention)
|
||||
|
||||
cohort_parser = subparsers.add_parser("cohort", help="Build cohort retention matrix rows.")
|
||||
cohort_parser.add_argument("input", **common)
|
||||
cohort_parser.add_argument("--user-column", default="user_id")
|
||||
cohort_parser.add_argument("--cohort-column", default="cohort_date")
|
||||
cohort_parser.add_argument("--activity-column", default="activity_date")
|
||||
cohort_parser.add_argument("--cohort-grain", choices=["week", "month"], default="week")
|
||||
cohort_parser.add_argument("--max-period", type=int, default=30)
|
||||
cohort_parser.set_defaults(func=cohort)
|
||||
|
||||
funnel_parser = subparsers.add_parser("funnel", help="Calculate funnel conversion by stage.")
|
||||
funnel_parser.add_argument("input", **common)
|
||||
funnel_parser.add_argument("--user-column", default="user_id")
|
||||
funnel_parser.add_argument("--stage-column", default="stage")
|
||||
funnel_parser.add_argument("--stages", required=True)
|
||||
funnel_parser.set_defaults(func=funnel)
|
||||
|
||||
return parser
|
||||
|
||||
|
||||
def main() -> int:
|
||||
parser = build_parser()
|
||||
args = parser.parse_args()
|
||||
return args.func(args)
|
||||
|
||||
|
||||
if __name__ == "__main__":
|
||||
raise SystemExit(main())
|
||||
114
product-team/product-discovery/SKILL.md
Normal file
114
product-team/product-discovery/SKILL.md
Normal file
@@ -0,0 +1,114 @@
|
||||
---
|
||||
name: product-discovery
|
||||
description: Use when validating product opportunities, mapping assumptions, planning discovery sprints, or testing problem-solution fit before committing delivery resources.
|
||||
---
|
||||
|
||||
# Product Discovery
|
||||
|
||||
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.
|
||||
@@ -0,0 +1,72 @@
|
||||
# Discovery Frameworks
|
||||
|
||||
## Opportunity Solution Tree (OST)
|
||||
|
||||
Purpose: continuously connect product outcomes to validated opportunities and tested solutions.
|
||||
|
||||
Core structure:
|
||||
- Outcome (metric)
|
||||
- Opportunity nodes (needs/pains)
|
||||
- Solution ideas
|
||||
- Experiments
|
||||
|
||||
OST practice tips:
|
||||
- Keep tree live; update after each interview or test.
|
||||
- Separate opportunity evidence from solution proposals.
|
||||
- Avoid single-branch trees that force one solution.
|
||||
|
||||
## Jobs-to-be-Done (JTBD)
|
||||
|
||||
Use JTBD to understand progress users seek.
|
||||
|
||||
JTBD template:
|
||||
"When [situation], I want to [motivation], so I can [expected outcome]."
|
||||
|
||||
JTBD interview focus:
|
||||
- Trigger moments
|
||||
- Current alternatives and workarounds
|
||||
- Purchase/adoption anxieties
|
||||
- Desired progress and success criteria
|
||||
|
||||
## Kano Model
|
||||
|
||||
Classify features by impact on satisfaction:
|
||||
- Must-be: expected baseline features
|
||||
- Performance: more is better
|
||||
- Delighters: unexpected value multipliers
|
||||
- Indifferent: low impact
|
||||
- Reverse: can reduce satisfaction for some users
|
||||
|
||||
Use Kano when prioritizing solution concepts after problem validation.
|
||||
|
||||
## Design Sprint Methodology
|
||||
|
||||
Typical phases:
|
||||
1. Understand
|
||||
2. Sketch
|
||||
3. Decide
|
||||
4. Prototype
|
||||
5. Test
|
||||
|
||||
Discovery usage:
|
||||
- Compress learning cycle into one week.
|
||||
- Best for high-ambiguity opportunities requiring cross-functional alignment.
|
||||
|
||||
## Assumption Prioritization Matrix
|
||||
|
||||
Map assumptions on two axes:
|
||||
- Risk if wrong (low -> high)
|
||||
- Certainty (low -> high)
|
||||
|
||||
Priority order:
|
||||
1. High risk, low certainty (test first)
|
||||
2. High risk, high certainty (validate quickly)
|
||||
3. Low risk, low certainty (defer)
|
||||
4. Low risk, high certainty (document)
|
||||
|
||||
## Discovery Evidence Rules
|
||||
|
||||
- One source is not enough for major decisions.
|
||||
- Triangulate qualitative and quantitative signals.
|
||||
- Predefine decision criteria before test execution.
|
||||
- Archive evidence with date, segment, and method.
|
||||
123
product-team/product-discovery/scripts/assumption_mapper.py
Executable file
123
product-team/product-discovery/scripts/assumption_mapper.py
Executable file
@@ -0,0 +1,123 @@
|
||||
#!/usr/bin/env python3
|
||||
"""Prioritize product assumptions and suggest validation tests."""
|
||||
|
||||
import argparse
|
||||
import csv
|
||||
from dataclasses import dataclass
|
||||
|
||||
|
||||
@dataclass
|
||||
class Assumption:
|
||||
statement: str
|
||||
category: str
|
||||
risk: float
|
||||
certainty: float
|
||||
|
||||
@property
|
||||
def priority_score(self) -> float:
|
||||
# High-risk, low-certainty assumptions should be tested first.
|
||||
return self.risk * (1.0 - self.certainty)
|
||||
|
||||
|
||||
def parse_float(value: str, field: str) -> float:
|
||||
number = float(value)
|
||||
if number < 0 or number > 1:
|
||||
raise ValueError(f"{field} must be in [0, 1]")
|
||||
return number
|
||||
|
||||
|
||||
def suggest_test(category: str) -> str:
|
||||
category = category.lower().strip()
|
||||
if category == "desirability":
|
||||
return "problem interviews or fake-door test"
|
||||
if category == "viability":
|
||||
return "pricing/willingness-to-pay test"
|
||||
if category == "feasibility":
|
||||
return "technical spike or architecture prototype"
|
||||
if category == "usability":
|
||||
return "moderated usability test"
|
||||
return "smallest possible experiment with clear success criteria"
|
||||
|
||||
|
||||
def load_from_csv(path: str) -> list[Assumption]:
|
||||
assumptions: list[Assumption] = []
|
||||
with open(path, "r", encoding="utf-8", newline="") as handle:
|
||||
reader = csv.DictReader(handle)
|
||||
required = {"assumption", "category", "risk", "certainty"}
|
||||
missing = required - set(reader.fieldnames or [])
|
||||
if missing:
|
||||
missing_str = ", ".join(sorted(missing))
|
||||
raise ValueError(f"Missing required columns: {missing_str}")
|
||||
|
||||
for row in reader:
|
||||
assumptions.append(
|
||||
Assumption(
|
||||
statement=(row.get("assumption") or "").strip(),
|
||||
category=(row.get("category") or "").strip(),
|
||||
risk=parse_float(row.get("risk") or "0", "risk"),
|
||||
certainty=parse_float(row.get("certainty") or "0", "certainty"),
|
||||
)
|
||||
)
|
||||
return assumptions
|
||||
|
||||
|
||||
def parse_inline(items: list[str]) -> list[Assumption]:
|
||||
assumptions: list[Assumption] = []
|
||||
for item in items:
|
||||
# format: statement|category|risk|certainty
|
||||
parts = [part.strip() for part in item.split("|")]
|
||||
if len(parts) != 4:
|
||||
raise ValueError("Inline assumption must be: statement|category|risk|certainty")
|
||||
assumptions.append(
|
||||
Assumption(
|
||||
statement=parts[0],
|
||||
category=parts[1],
|
||||
risk=parse_float(parts[2], "risk"),
|
||||
certainty=parse_float(parts[3], "certainty"),
|
||||
)
|
||||
)
|
||||
return assumptions
|
||||
|
||||
|
||||
def build_parser() -> argparse.ArgumentParser:
|
||||
parser = argparse.ArgumentParser(description="Prioritize assumptions and generate test plan.")
|
||||
parser.add_argument("input", nargs="?", help="CSV file path")
|
||||
parser.add_argument(
|
||||
"--assumption",
|
||||
action="append",
|
||||
default=[],
|
||||
help="Inline assumption: statement|category|risk|certainty",
|
||||
)
|
||||
parser.add_argument("--top", type=int, default=10, help="Maximum assumptions to print")
|
||||
return parser
|
||||
|
||||
|
||||
def main() -> int:
|
||||
parser = build_parser()
|
||||
args = parser.parse_args()
|
||||
|
||||
assumptions: list[Assumption] = []
|
||||
if args.input:
|
||||
assumptions.extend(load_from_csv(args.input))
|
||||
if args.assumption:
|
||||
assumptions.extend(parse_inline(args.assumption))
|
||||
|
||||
if not assumptions:
|
||||
parser.error("Provide a CSV input file or at least one --assumption value.")
|
||||
|
||||
assumptions.sort(key=lambda item: item.priority_score, reverse=True)
|
||||
|
||||
print("prioritized_assumption_test_plan")
|
||||
print("rank,priority_score,category,risk,certainty,test,assumption")
|
||||
for rank, item in enumerate(assumptions[: args.top], start=1):
|
||||
test = suggest_test(item.category)
|
||||
print(
|
||||
f"{rank},{item.priority_score:.4f},{item.category},{item.risk:.2f},"
|
||||
f"{item.certainty:.2f},{test},{item.statement}"
|
||||
)
|
||||
|
||||
return 0
|
||||
|
||||
|
||||
if __name__ == "__main__":
|
||||
raise SystemExit(main())
|
||||
Binary file not shown.
@@ -1,440 +0,0 @@
|
||||
# Product Team Skills Suite Architecture
|
||||
|
||||
## Overview
|
||||
A comprehensive suite of 5 interconnected skills designed for modern product teams, enabling data-driven decisions, user-centered design, and agile delivery.
|
||||
|
||||
## 1. product-strategist (Head of Product)
|
||||
|
||||
### Purpose
|
||||
Strategic product leadership, vision setting, and organizational alignment
|
||||
|
||||
### Core Components
|
||||
|
||||
#### Scripts
|
||||
- `market_analyzer.py` - Competitive analysis and market sizing
|
||||
- `okr_generator.py` - OKR framework and cascade builder
|
||||
- `roadmap_visualizer.py` - Strategic roadmap generation
|
||||
- `metric_dashboard.py` - North star and KPI tracking
|
||||
- `stakeholder_mapper.py` - Influence/interest matrix builder
|
||||
|
||||
#### References
|
||||
- `strategy_frameworks.md` - SWOT, Porter's Five Forces, Blue Ocean
|
||||
- `vision_templates.md` - Product vision and mission statements
|
||||
- `metric_library.md` - Industry-standard KPIs by vertical
|
||||
- `go_to_market_playbook.md` - GTM strategies and launch plans
|
||||
- `team_scaling_guide.md` - Hiring, structure, and culture
|
||||
|
||||
#### Assets
|
||||
- Product vision canvas templates
|
||||
- Executive presentation templates
|
||||
- Strategic planning worksheets
|
||||
- Quarterly business review decks
|
||||
- Board reporting templates
|
||||
|
||||
#### Key Workflows
|
||||
1. **Vision to Execution**
|
||||
- Market opportunity assessment
|
||||
- Vision and strategy definition
|
||||
- OKR cascade creation
|
||||
- Roadmap development
|
||||
- Success metrics definition
|
||||
|
||||
2. **Stakeholder Management**
|
||||
- Executive alignment sessions
|
||||
- Board preparation and reporting
|
||||
- Cross-functional planning
|
||||
- Customer advisory boards
|
||||
|
||||
3. **Team Leadership**
|
||||
- Product org design
|
||||
- Talent development plans
|
||||
- Performance frameworks
|
||||
- Culture building
|
||||
|
||||
---
|
||||
|
||||
## 2. agile-product-owner (Senior Product Owner)
|
||||
|
||||
### Purpose
|
||||
Backlog excellence, sprint execution, and delivery optimization
|
||||
|
||||
### Core Components
|
||||
|
||||
#### Scripts
|
||||
- `user_story_generator.py` - INVEST-compliant story creation
|
||||
- `acceptance_criteria_builder.py` - BDD/Gherkin syntax generator
|
||||
- `sprint_velocity_tracker.py` - Velocity and capacity planning
|
||||
- `dependency_mapper.py` - Cross-team dependency visualization
|
||||
- `backlog_health_analyzer.py` - Backlog quality metrics
|
||||
|
||||
#### References
|
||||
- `scrum_ceremonies.md` - Meeting templates and facilitation
|
||||
- `story_patterns.md` - Common user story templates
|
||||
- `estimation_techniques.md` - Story points, t-shirt sizing
|
||||
- `definition_of_done.md` - DoD templates by product type
|
||||
- `release_planning.md` - Release strategies and rollout plans
|
||||
|
||||
#### Assets
|
||||
- Sprint planning templates
|
||||
- Retrospective formats
|
||||
- Story mapping boards
|
||||
- Release notes templates
|
||||
- Stakeholder update emails
|
||||
|
||||
#### Key Workflows
|
||||
1. **Backlog Management**
|
||||
- Epic breakdown
|
||||
- Story writing and refinement
|
||||
- Prioritization frameworks (WSJF, RICE)
|
||||
- Dependency management
|
||||
- Technical debt tracking
|
||||
|
||||
2. **Sprint Execution**
|
||||
- Sprint planning facilitation
|
||||
- Daily standup optimization
|
||||
- Sprint review preparation
|
||||
- Retrospective facilitation
|
||||
- Impediment resolution
|
||||
|
||||
3. **Stakeholder Communication**
|
||||
- Sprint demos
|
||||
- Release communications
|
||||
- Progress reporting
|
||||
- Risk escalation
|
||||
|
||||
---
|
||||
|
||||
## 3. product-manager-toolkit (Senior Product Manager)
|
||||
|
||||
### Purpose
|
||||
Feature development, market fit, and customer success
|
||||
|
||||
### Core Components
|
||||
|
||||
#### Scripts
|
||||
- `feature_prioritization_matrix.py` - RICE, ICE, Value vs Effort
|
||||
- `customer_interview_analyzer.py` - Interview synthesis and insights
|
||||
- `competitor_feature_tracker.py` - Feature gap analysis
|
||||
- `pricing_calculator.py` - Pricing models and sensitivity
|
||||
- `launch_checklist_generator.py` - Go-to-market readiness
|
||||
|
||||
#### References
|
||||
- `discovery_techniques.md` - Customer development methods
|
||||
- `experimentation_framework.md` - A/B testing and MVPs
|
||||
- `product_analytics.md` - Funnel, cohort, retention analysis
|
||||
- `messaging_framework.md` - Positioning and value props
|
||||
- `partnership_playbook.md` - Integration and partnership strategies
|
||||
|
||||
#### Assets
|
||||
- PRD templates
|
||||
- Business case templates
|
||||
- Feature announcement templates
|
||||
- Customer interview guides
|
||||
- Competitive battlecards
|
||||
|
||||
#### Key Workflows
|
||||
1. **Discovery & Validation**
|
||||
- Problem validation
|
||||
- Solution ideation
|
||||
- Prototype testing
|
||||
- Market sizing
|
||||
- Business case development
|
||||
|
||||
2. **Feature Development**
|
||||
- Requirements gathering
|
||||
- PRD creation
|
||||
- Design partnership
|
||||
- Engineering collaboration
|
||||
- QA planning
|
||||
|
||||
3. **Launch & Growth**
|
||||
- Beta program management
|
||||
- Launch planning
|
||||
- Feature adoption tracking
|
||||
- Customer feedback loops
|
||||
- Iteration planning
|
||||
|
||||
---
|
||||
|
||||
## 4. ux-researcher-designer (Senior UX Designer and Researcher)
|
||||
|
||||
### Purpose
|
||||
User understanding, experience design, and usability optimization
|
||||
|
||||
### Core Components
|
||||
|
||||
#### Scripts
|
||||
- `persona_generator.py` - Data-driven persona creation
|
||||
- `journey_map_builder.py` - Customer journey visualization
|
||||
- `usability_test_analyzer.py` - Test results and insights
|
||||
- `survey_designer.py` - Research survey generation
|
||||
- `heuristic_evaluator.py` - Nielsen heuristics assessment
|
||||
- `accessibility_checker.py` - WCAG compliance validation
|
||||
|
||||
#### References
|
||||
- `research_methods.md` - Qual and quant research techniques
|
||||
- `interview_protocols.md` - User interview best practices
|
||||
- `information_architecture.md` - IA principles and patterns
|
||||
- `interaction_patterns.md` - Common UX patterns library
|
||||
- `cognitive_biases.md` - Design psychology principles
|
||||
- `accessibility_standards.md` - WCAG, ARIA guidelines
|
||||
|
||||
#### Assets
|
||||
- Research plan templates
|
||||
- Interview script templates
|
||||
- Usability test protocols
|
||||
- Journey map templates
|
||||
- Persona templates
|
||||
- Research repository structure
|
||||
|
||||
#### Key Workflows
|
||||
1. **Research Planning**
|
||||
- Research question definition
|
||||
- Method selection
|
||||
- Participant recruitment
|
||||
- Study design
|
||||
- Ethics and consent
|
||||
|
||||
2. **Data Collection & Synthesis**
|
||||
- Interview conducting
|
||||
- Observation and note-taking
|
||||
- Affinity mapping
|
||||
- Insight generation
|
||||
- Recommendation development
|
||||
|
||||
3. **Design Process**
|
||||
- Information architecture
|
||||
- User flow creation
|
||||
- Wireframing
|
||||
- Prototyping
|
||||
- Usability testing
|
||||
- Iteration cycles
|
||||
|
||||
---
|
||||
|
||||
## 5. ui-design-system (Senior UI Designer)
|
||||
|
||||
### Purpose
|
||||
Visual excellence, design systems, and developer handoff
|
||||
|
||||
### Core Components
|
||||
|
||||
#### Scripts
|
||||
- `color_palette_generator.py` - Accessible color system creation
|
||||
- `typography_scale_builder.py` - Type system generator
|
||||
- `spacing_system_calculator.py` - 8pt grid system
|
||||
- `component_documenter.py` - Component library documentation
|
||||
- `design_token_exporter.py` - Design tokens for development
|
||||
- `responsive_breakpoint_calculator.py` - Breakpoint optimization
|
||||
|
||||
#### References
|
||||
- `design_principles.md` - Visual design fundamentals
|
||||
- `design_system_architecture.md` - Atomic design methodology
|
||||
- `animation_guidelines.md` - Motion design principles
|
||||
- `brand_application.md` - Brand to UI translation
|
||||
- `platform_guidelines.md` - iOS, Android, Web standards
|
||||
- `handoff_checklist.md` - Developer collaboration
|
||||
|
||||
#### Assets
|
||||
- Component library templates
|
||||
- Icon libraries
|
||||
- Illustration systems
|
||||
- Design token templates
|
||||
- Responsive grid systems
|
||||
- Annotation templates
|
||||
|
||||
#### Key Workflows
|
||||
1. **Design System Development**
|
||||
- Foundation definition (color, type, spacing)
|
||||
- Component design
|
||||
- Pattern documentation
|
||||
- Token management
|
||||
- Version control
|
||||
|
||||
2. **Visual Design Process**
|
||||
- Mood boards and style tiles
|
||||
- High-fidelity mockups
|
||||
- Responsive design
|
||||
- Interaction design
|
||||
- Micro-interactions
|
||||
- Asset production
|
||||
|
||||
3. **Collaboration & Handoff**
|
||||
- Design review facilitation
|
||||
- Developer pairing
|
||||
- QA collaboration
|
||||
- Design debt tracking
|
||||
- Documentation maintenance
|
||||
|
||||
---
|
||||
|
||||
## Integration Points Between Skills
|
||||
|
||||
### Cross-Functional Workflows
|
||||
|
||||
```mermaid
|
||||
graph LR
|
||||
PS[Product Strategist] --> PM[Product Manager]
|
||||
PM --> PO[Product Owner]
|
||||
PM <--> UX[UX Researcher/Designer]
|
||||
UX <--> UI[UI Designer]
|
||||
UI --> PO
|
||||
PO --> PS
|
||||
```
|
||||
|
||||
### Shared Resources
|
||||
|
||||
1. **Customer Insights Pool**
|
||||
- Shared between PM, UX, and Product Strategist
|
||||
- Centralized research repository
|
||||
- Unified persona definitions
|
||||
|
||||
2. **Design Language System**
|
||||
- Shared between UX and UI
|
||||
- Consistent component library
|
||||
- Unified interaction patterns
|
||||
|
||||
3. **Product Metrics Framework**
|
||||
- Shared across all roles
|
||||
- Consistent KPI definitions
|
||||
- Unified analytics approach
|
||||
|
||||
4. **Roadmap Alignment**
|
||||
- Cascades from Strategist → PM → PO
|
||||
- Feedback loops from PO → PM → Strategist
|
||||
- Design input from UX/UI → PM
|
||||
|
||||
### Handoff Points
|
||||
|
||||
1. **Strategy → Execution**
|
||||
- Vision (Strategist) → Requirements (PM)
|
||||
- Requirements (PM) → Stories (PO)
|
||||
- Stories (PO) → Designs (UX/UI)
|
||||
|
||||
2. **Research → Design**
|
||||
- User Research (UX) → Feature Definition (PM)
|
||||
- Wireframes (UX) → Visual Design (UI)
|
||||
- Prototypes (UI) → Development (via PO)
|
||||
|
||||
3. **Feedback Loops**
|
||||
- Analytics → All roles
|
||||
- Customer feedback → UX → PM → Strategist
|
||||
- Sprint outcomes → PO → PM → Strategist
|
||||
|
||||
## Implementation Approach
|
||||
|
||||
### Phase 1: Foundation (Week 1-2)
|
||||
1. Deploy `product-manager-toolkit` (most central role)
|
||||
2. Establish shared resources and templates
|
||||
3. Create team charter and RACI matrix
|
||||
|
||||
### Phase 2: Design Integration (Week 3-4)
|
||||
1. Deploy `ux-researcher-designer`
|
||||
2. Deploy `ui-design-system`
|
||||
3. Establish design-dev handoff process
|
||||
|
||||
### Phase 3: Execution Layer (Week 5-6)
|
||||
1. Deploy `agile-product-owner`
|
||||
2. Integrate with existing Jira/development tools
|
||||
3. Optimize sprint ceremonies
|
||||
|
||||
### Phase 4: Strategic Layer (Week 7-8)
|
||||
1. Deploy `product-strategist`
|
||||
2. Align OKRs and roadmaps
|
||||
3. Establish governance model
|
||||
|
||||
## Success Metrics
|
||||
|
||||
### Efficiency Metrics
|
||||
- Requirements clarity: +40% improvement
|
||||
- Design-dev handoff time: -50% reduction
|
||||
- Sprint velocity: +25% increase
|
||||
- Research-to-insight time: -60% reduction
|
||||
|
||||
### Quality Metrics
|
||||
- User satisfaction (NPS): +20 points
|
||||
- Feature adoption rate: +35%
|
||||
- Design consistency score: 95%+
|
||||
- Defect escape rate: -40%
|
||||
|
||||
### Business Metrics
|
||||
- Time to market: -30%
|
||||
- Feature success rate: +45%
|
||||
- Customer retention: +15%
|
||||
- Team productivity: +35%
|
||||
|
||||
## Tool Integration Requirements
|
||||
|
||||
### Essential Integrations
|
||||
- **Product Management**: Jira, ProductBoard, Amplitude
|
||||
- **Design**: Figma, Sketch, Adobe XD
|
||||
- **Research**: Dovetail, Miro, UserTesting
|
||||
- **Analytics**: Mixpanel, Google Analytics, Hotjar
|
||||
- **Collaboration**: Slack, Confluence, Notion
|
||||
|
||||
### API Connections Needed
|
||||
- Jira REST API for backlog management
|
||||
- Figma API for design system sync
|
||||
- Analytics APIs for metrics dashboards
|
||||
- Slack webhooks for notifications
|
||||
|
||||
## Training & Adoption Plan
|
||||
|
||||
### Week 1: Kickoff
|
||||
- All-hands skills overview
|
||||
- Role-specific training sessions
|
||||
- Skill champion assignment
|
||||
|
||||
### Week 2-4: Pilot
|
||||
- One squad pilots all skills
|
||||
- Daily check-ins and feedback
|
||||
- Rapid iteration on scripts/templates
|
||||
|
||||
### Week 5-8: Rollout
|
||||
- Gradual team-by-team adoption
|
||||
- Weekly skill clinics
|
||||
- Success story sharing
|
||||
|
||||
### Ongoing: Optimization
|
||||
- Monthly skill retrospectives
|
||||
- Quarterly skill updates
|
||||
- Annual skill assessment
|
||||
|
||||
## ROI Projections
|
||||
|
||||
### Year 1 Impact
|
||||
- **Time Savings**: 200 hours/month across team
|
||||
- **Quality Improvement**: 40% fewer revisions
|
||||
- **Speed to Market**: 6 weeks faster average
|
||||
- **Revenue Impact**: $2M from improved features
|
||||
- **Cost Avoidance**: $500K in prevented rework
|
||||
|
||||
### Investment Required
|
||||
- **Setup Time**: 80 hours total
|
||||
- **Training Time**: 40 hours total
|
||||
- **Maintenance**: 10 hours/month
|
||||
- **Tool Costs**: Existing stack sufficient
|
||||
|
||||
### Payback Period: 2 months
|
||||
|
||||
## Next Steps
|
||||
|
||||
1. **Prioritize First Skill**
|
||||
- Recommend starting with `product-manager-toolkit`
|
||||
- Most central to all workflows
|
||||
- Highest immediate impact
|
||||
|
||||
2. **Gather Existing Resources**
|
||||
- Current templates and processes
|
||||
- Tool access and credentials
|
||||
- Team feedback on pain points
|
||||
|
||||
3. **Customize for Your Context**
|
||||
- Industry-specific adjustments
|
||||
- Company culture alignment
|
||||
- Tool stack integration
|
||||
|
||||
4. **Create Pilot Program**
|
||||
- Select pilot team/squad
|
||||
- Define success criteria
|
||||
- Set 4-week trial period
|
||||
Binary file not shown.
@@ -1,250 +0,0 @@
|
||||
# Product Team Skills Implementation Guide
|
||||
|
||||
## 🎯 Executive Summary
|
||||
|
||||
Your product team skills suite is designed to enhance decision-making speed, improve feature success rates, and create consistent product development practices across all roles.
|
||||
|
||||
## 📦 Delivered Skills
|
||||
|
||||
### 1. product-manager-toolkit ✅
|
||||
**Ready for immediate deployment**
|
||||
|
||||
#### What's Inside:
|
||||
- **RICE Prioritizer**: Automated feature scoring with roadmap generation
|
||||
- **Customer Interview Analyzer**: AI-powered insight extraction from user research
|
||||
- **PRD Templates**: 4 different formats for various feature types
|
||||
- **Frameworks**: Discovery, prioritization, and go-to-market strategies
|
||||
|
||||
#### Quick Demo Results:
|
||||
Running the RICE prioritizer on sample features shows:
|
||||
- Automatic prioritization by impact/effort ratio
|
||||
- Quarterly roadmap with capacity planning
|
||||
- Portfolio balance analysis (quick wins vs big bets)
|
||||
- Clear metrics for decision justification
|
||||
|
||||
## 🏗️ Complete Skills Architecture
|
||||
|
||||
### Role-Based Skills Design
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────┐
|
||||
│ HEAD OF PRODUCT │
|
||||
│ product-strategist (To Be Built) │
|
||||
│ • Vision & Strategy • OKRs │
|
||||
│ • Market Analysis • Team Scaling │
|
||||
└─────────────────────────────────────────────┘
|
||||
↓
|
||||
┌─────────────────────────────────────────────┐
|
||||
│ SENIOR PRODUCT MANAGER │
|
||||
│ product-manager-toolkit (COMPLETE) │
|
||||
│ • Feature Priority • User Research │
|
||||
│ • PRDs • Go-to-Market │
|
||||
└─────────────────────────────────────────────┘
|
||||
↓
|
||||
┌─────────────────────────────────────────────┐
|
||||
│ SENIOR PRODUCT OWNER │
|
||||
│ agile-product-owner (To Be Built) │
|
||||
│ • Backlog Mgmt • Sprint Planning │
|
||||
│ • User Stories • Velocity Tracking │
|
||||
└─────────────────────────────────────────────┘
|
||||
↓
|
||||
┌──────────────────┬──────────────────────────┐
|
||||
│ UX RESEARCHER │ UI DESIGNER │
|
||||
│ ux-researcher │ ui-design-system │
|
||||
│ (To Be Built) │ (To Be Built) │
|
||||
│ • User Research │ • Design Systems │
|
||||
│ • Journey Maps │ • Visual Design │
|
||||
│ • Usability │ • Dev Handoff │
|
||||
└──────────────────┴──────────────────────────┘
|
||||
```
|
||||
|
||||
## 🚀 Implementation Roadmap
|
||||
|
||||
### Week 1-2: Deploy PM Toolkit
|
||||
- [ ] Install product-manager-toolkit with your team
|
||||
- [ ] Run RICE prioritization on current backlog
|
||||
- [ ] Analyze 5 recent customer interviews
|
||||
- [ ] Standardize on one PRD template
|
||||
|
||||
### Week 3-4: Build UX/UI Skills
|
||||
- [ ] Create ux-researcher-designer skill
|
||||
- [ ] Create ui-design-system skill
|
||||
- [ ] Integrate with Figma workflows
|
||||
- [ ] Establish design-dev handoff process
|
||||
|
||||
### Week 5-6: Build Execution Skills
|
||||
- [ ] Create agile-product-owner skill
|
||||
- [ ] Integrate with Jira
|
||||
- [ ] Optimize sprint ceremonies
|
||||
- [ ] Implement velocity tracking
|
||||
|
||||
### Week 7-8: Strategic Layer
|
||||
- [ ] Create product-strategist skill
|
||||
- [ ] Align OKRs across teams
|
||||
- [ ] Establish metrics framework
|
||||
- [ ] Create governance model
|
||||
|
||||
## 💡 How to Use the Skills
|
||||
|
||||
### For Product Managers (Available Now)
|
||||
|
||||
1. **Prioritize Your Backlog**:
|
||||
```bash
|
||||
# Create a CSV with your features
|
||||
# Columns: name,reach,impact,confidence,effort
|
||||
python rice_prioritizer.py your_features.csv
|
||||
|
||||
# Get a quarterly roadmap
|
||||
python rice_prioritizer.py your_features.csv --capacity 15
|
||||
```
|
||||
|
||||
2. **Analyze User Interviews**:
|
||||
```bash
|
||||
# Extract insights from transcripts
|
||||
python customer_interview_analyzer.py interview.txt
|
||||
|
||||
# Get JSON for aggregation
|
||||
python customer_interview_analyzer.py interview.txt json
|
||||
```
|
||||
|
||||
3. **Create PRDs**:
|
||||
- Open prd_templates.md
|
||||
- Choose appropriate template
|
||||
- Fill in sections
|
||||
- Share with stakeholders
|
||||
|
||||
### For Product Team Leads
|
||||
|
||||
**Strategic Benefits**:
|
||||
- 40% faster prioritization decisions
|
||||
- 60% reduction in PRD creation time
|
||||
- 80% consistency in product documentation
|
||||
- 35% improvement in feature success rate
|
||||
|
||||
**Team Benefits**:
|
||||
- Common language and frameworks
|
||||
- Reduced meeting time
|
||||
- Clear decision criteria
|
||||
- Better cross-functional alignment
|
||||
|
||||
## 📊 Success Metrics to Track
|
||||
|
||||
### Efficiency Metrics
|
||||
- Time to prioritize features: -50%
|
||||
- PRD creation time: -60%
|
||||
- Interview analysis time: -80%
|
||||
- Decision-making speed: +40%
|
||||
|
||||
### Quality Metrics
|
||||
- Feature success rate: +35%
|
||||
- Requirements clarity: +40%
|
||||
- Stakeholder satisfaction: +30%
|
||||
- Rework reduction: -25%
|
||||
|
||||
### Business Impact
|
||||
- Time to market: -30%
|
||||
- Customer satisfaction: +20 NPS
|
||||
- Team productivity: +35%
|
||||
- Revenue per feature: +25%
|
||||
|
||||
## 🔧 Technical Integration
|
||||
|
||||
### Current Tool Compatibility
|
||||
The skills are designed to integrate with your existing stack:
|
||||
|
||||
**Already Compatible**:
|
||||
- Jira (via CSV export/import)
|
||||
- Confluence (markdown support)
|
||||
- Google Sheets (CSV format)
|
||||
- Slack (report sharing)
|
||||
|
||||
**Future Integrations**:
|
||||
- ProductBoard API
|
||||
- Amplitude Analytics
|
||||
- Figma Plugins
|
||||
- Linear API
|
||||
|
||||
## 🎓 Training Plan
|
||||
|
||||
### Self-Service Onboarding
|
||||
1. **Watch**: 15-minute demo video
|
||||
2. **Try**: Run scripts on sample data
|
||||
3. **Apply**: Use on real project
|
||||
4. **Share**: Present findings to team
|
||||
|
||||
### Team Workshop Agenda (2 hours)
|
||||
- 0:00-0:15 - Skills overview
|
||||
- 0:15-0:45 - RICE prioritization hands-on
|
||||
- 0:45-1:15 - Interview analysis practice
|
||||
- 1:15-1:45 - PRD template walkthrough
|
||||
- 1:45-2:00 - Q&A and next steps
|
||||
|
||||
## 💰 ROI Calculation
|
||||
|
||||
### Investment
|
||||
- Setup time: 40 hours
|
||||
- Training: 2 hours per person
|
||||
- Maintenance: 5 hours/month
|
||||
|
||||
### Returns (Monthly)
|
||||
- Time saved: 160 hours
|
||||
- Quality improvements: $50K value
|
||||
- Faster delivery: $100K revenue impact
|
||||
- **Total: $150K+ monthly value**
|
||||
|
||||
### Payback Period: < 1 week
|
||||
|
||||
## 🏃 Immediate Next Steps
|
||||
|
||||
### For You (CTO/Leadership):
|
||||
1. Review the product-manager-toolkit functionality
|
||||
2. Identify pilot PM to test the toolkit
|
||||
3. Schedule team training session
|
||||
4. Define success metrics
|
||||
|
||||
### For Product Managers:
|
||||
1. Download product-manager-toolkit.zip
|
||||
2. Try RICE prioritizer on your backlog
|
||||
3. Analyze one recent user interview
|
||||
4. Create next PRD using template
|
||||
|
||||
### For Product Team:
|
||||
1. Provide feedback on additional needs
|
||||
2. Share existing templates/processes
|
||||
3. Identify integration requirements
|
||||
4. Volunteer as skill champions
|
||||
|
||||
## 📚 Resources
|
||||
|
||||
### Available Now:
|
||||
- [product-manager-toolkit.zip](computer:///mnt/user-data/outputs/product-manager-toolkit.zip)
|
||||
- [Product Skills Architecture](computer:///mnt/user-data/outputs/product-skills-architecture.md)
|
||||
|
||||
### Support:
|
||||
- Slack: #product-skills
|
||||
- Wiki: /product/skills
|
||||
- Training: Weekly office hours
|
||||
- Feedback: product-skills@company.com
|
||||
|
||||
## 🎯 Vision
|
||||
|
||||
By implementing these skills across your product organization:
|
||||
|
||||
**In 30 Days**:
|
||||
- Consistent prioritization framework
|
||||
- Faster PRD creation
|
||||
- Better user insights
|
||||
|
||||
**In 60 Days**:
|
||||
- Integrated product workflows
|
||||
- Improved feature success rates
|
||||
- Reduced time to market
|
||||
|
||||
**In 90 Days**:
|
||||
- Data-driven product culture
|
||||
- Predictable delivery
|
||||
- Higher customer satisfaction
|
||||
|
||||
---
|
||||
|
||||
**Ready to transform your product organization?** Start with the product-manager-toolkit today. Each skill builds on the previous, creating a compound effect that will revolutionize how your team builds products.
|
||||
92
product-team/roadmap-communicator/SKILL.md
Normal file
92
product-team/roadmap-communicator/SKILL.md
Normal file
@@ -0,0 +1,92 @@
|
||||
---
|
||||
name: roadmap-communicator
|
||||
description: Use when preparing roadmap narratives, release notes, changelogs, or stakeholder updates tailored for executives, engineering teams, and customers.
|
||||
---
|
||||
|
||||
# Roadmap Communicator
|
||||
|
||||
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.
|
||||
@@ -0,0 +1,63 @@
|
||||
# Communication Templates
|
||||
|
||||
## Stakeholder Update Email
|
||||
|
||||
Subject: Product roadmap update - [Period]
|
||||
|
||||
Hi [Audience],
|
||||
|
||||
Here is the [weekly/monthly/quarterly] product update.
|
||||
|
||||
- Progress:
|
||||
- KPI movement:
|
||||
- Risks/blockers:
|
||||
- Decisions needed:
|
||||
- Next period focus:
|
||||
|
||||
Thanks,
|
||||
[Owner]
|
||||
|
||||
## User-Facing Release Notes Template
|
||||
|
||||
# Release [Version/Date]
|
||||
|
||||
## Highlights
|
||||
- [User value outcome]
|
||||
|
||||
## New
|
||||
- [Feature + benefit]
|
||||
|
||||
## Improved
|
||||
- [Improvement + impact]
|
||||
|
||||
## Fixed
|
||||
- [Issue + user-facing resolution]
|
||||
|
||||
## Known Limitations
|
||||
- [If applicable]
|
||||
|
||||
## Internal Release Notes Template
|
||||
|
||||
# Internal Release [Version/Date]
|
||||
|
||||
## Scope
|
||||
- Included workstreams and commit range
|
||||
|
||||
## Operational Notes
|
||||
- Rollout plan
|
||||
- Monitoring checks
|
||||
- Rollback criteria
|
||||
|
||||
## Risks
|
||||
- Known issues and mitigations
|
||||
|
||||
## Feature Announcement Template
|
||||
|
||||
Title: [Outcome-focused headline]
|
||||
|
||||
1. The problem:
|
||||
2. The new capability:
|
||||
3. Why this matters:
|
||||
4. Who should use it:
|
||||
5. How to start:
|
||||
6. Feedback channel:
|
||||
@@ -0,0 +1,44 @@
|
||||
# Roadmap Templates
|
||||
|
||||
## Now / Next / Later Template
|
||||
|
||||
### Now (0-1 quarter)
|
||||
- Committed initiatives in active execution
|
||||
- Success metrics and owners
|
||||
- Dependencies and known risks
|
||||
|
||||
### Next (1-2 quarters)
|
||||
- Prioritized bets with confidence levels
|
||||
- Discovery items needed before commit
|
||||
- Resource assumptions
|
||||
|
||||
### Later (2+ quarters)
|
||||
- Strategic themes and directional intent
|
||||
- Explicitly marked as non-commitment
|
||||
|
||||
## Quarterly Roadmap Template
|
||||
|
||||
| Quarter | Theme | Key Initiatives | Success Metrics | Risks |
|
||||
|---|---|---|---|---|
|
||||
| Q1 | | | | |
|
||||
| Q2 | | | | |
|
||||
| Q3 | | | | |
|
||||
| Q4 | | | | |
|
||||
|
||||
## Theme-Based Roadmap Template
|
||||
|
||||
| Theme | Problem Statement | Initiatives | KPI Link | Owner |
|
||||
|---|---|---|---|---|
|
||||
| Activation | | | | |
|
||||
| Retention | | | | |
|
||||
| Expansion | | | | |
|
||||
|
||||
## OKR-Aligned Roadmap Template
|
||||
|
||||
| Objective | Key Result | Initiative | Milestone | Team |
|
||||
|---|---|---|---|---|
|
||||
| | | | | |
|
||||
|
||||
Guideline:
|
||||
- Every initiative should map to an objective or key result.
|
||||
- Mark items without alignment as candidate de-scope.
|
||||
151
product-team/roadmap-communicator/scripts/changelog_generator.py
Executable file
151
product-team/roadmap-communicator/scripts/changelog_generator.py
Executable file
@@ -0,0 +1,151 @@
|
||||
#!/usr/bin/env python3
|
||||
"""Generate changelog sections from git log or piped commit messages using conventional commit prefixes."""
|
||||
|
||||
import argparse
|
||||
import shutil
|
||||
import subprocess
|
||||
import sys
|
||||
from collections import defaultdict
|
||||
|
||||
|
||||
SECTIONS = {
|
||||
"feat": "Features",
|
||||
"fix": "Fixes",
|
||||
"docs": "Documentation",
|
||||
"refactor": "Refactors",
|
||||
"test": "Tests",
|
||||
"chore": "Chores",
|
||||
"perf": "Performance",
|
||||
"ci": "CI",
|
||||
"build": "Build",
|
||||
"style": "Style",
|
||||
"revert": "Reverts",
|
||||
}
|
||||
|
||||
DEMO_COMMITS = [
|
||||
"feat: add user dashboard with analytics widgets",
|
||||
"feat: implement dark mode toggle",
|
||||
"fix: resolve crash on empty CSV import",
|
||||
"fix: correct timezone offset in calendar view",
|
||||
"docs: update API reference for v2 endpoints",
|
||||
"refactor: extract shared validation into utils module",
|
||||
"chore: bump dependencies to latest patch versions",
|
||||
"perf: optimize database queries for user listing",
|
||||
]
|
||||
|
||||
|
||||
def parse_args() -> argparse.Namespace:
|
||||
parser = argparse.ArgumentParser(
|
||||
description="Generate changelog from git commits or piped input.",
|
||||
epilog="Examples:\n"
|
||||
" %(prog)s --from v1.0.0 --to HEAD\n"
|
||||
" git log --pretty=format:%%s v1.0..HEAD | %(prog)s --stdin\n"
|
||||
" %(prog)s --demo\n",
|
||||
formatter_class=argparse.RawDescriptionHelpFormatter,
|
||||
)
|
||||
parser.add_argument("--from", dest="from_ref", default="HEAD~50",
|
||||
help="Start ref for git log (default: HEAD~50)")
|
||||
parser.add_argument("--to", dest="to_ref", default="HEAD",
|
||||
help="End ref for git log (default: HEAD)")
|
||||
parser.add_argument("--format", choices=["markdown", "text"], default="markdown",
|
||||
help="Output format (default: markdown)")
|
||||
parser.add_argument("--stdin", action="store_true",
|
||||
help="Read commit subjects from stdin instead of git log")
|
||||
parser.add_argument("--demo", action="store_true",
|
||||
help="Run with sample data (no git required)")
|
||||
return parser.parse_args()
|
||||
|
||||
|
||||
def get_git_log(from_ref: str, to_ref: str) -> list[str]:
|
||||
"""Get commit subjects from git log. Requires git on PATH and a git repo."""
|
||||
if not shutil.which("git"):
|
||||
print("Error: git not found on PATH. Use --stdin or --demo instead.", file=sys.stderr)
|
||||
sys.exit(1)
|
||||
commit_range = f"{from_ref}..{to_ref}"
|
||||
cmd = ["git", "log", "--pretty=format:%s", commit_range]
|
||||
try:
|
||||
result = subprocess.run(cmd, capture_output=True, text=True, timeout=30)
|
||||
except subprocess.TimeoutExpired:
|
||||
print("Error: git log timed out.", file=sys.stderr)
|
||||
sys.exit(1)
|
||||
if result.returncode != 0:
|
||||
print(f"Error: git log failed: {result.stderr.strip()}", file=sys.stderr)
|
||||
sys.exit(1)
|
||||
lines = [line.strip() for line in result.stdout.splitlines() if line.strip()]
|
||||
return lines
|
||||
|
||||
|
||||
def read_stdin() -> list[str]:
|
||||
"""Read commit subjects from stdin, one per line."""
|
||||
return [line.strip() for line in sys.stdin if line.strip()]
|
||||
|
||||
|
||||
def group_commits(subjects: list[str]) -> dict[str, list[str]]:
|
||||
grouped: dict[str, list[str]] = defaultdict(list)
|
||||
|
||||
for subject in subjects:
|
||||
commit_type = "other"
|
||||
for prefix in SECTIONS:
|
||||
if subject.startswith(f"{prefix}:") or subject.startswith(f"{prefix}("):
|
||||
commit_type = prefix
|
||||
break
|
||||
grouped[commit_type].append(subject)
|
||||
|
||||
return grouped
|
||||
|
||||
|
||||
def render_markdown(grouped: dict[str, list[str]]) -> str:
|
||||
out = ["# Changelog", ""]
|
||||
ordered_types = list(SECTIONS.keys()) + ["other"]
|
||||
for commit_type in ordered_types:
|
||||
commits = grouped.get(commit_type, [])
|
||||
if not commits:
|
||||
continue
|
||||
header = SECTIONS.get(commit_type, "Other")
|
||||
out.append(f"## {header}")
|
||||
for item in commits:
|
||||
out.append(f"- {item}")
|
||||
out.append("")
|
||||
return "\n".join(out).rstrip() + "\n"
|
||||
|
||||
|
||||
def render_text(grouped: dict[str, list[str]]) -> str:
|
||||
out: list[str] = []
|
||||
ordered_types = list(SECTIONS.keys()) + ["other"]
|
||||
for commit_type in ordered_types:
|
||||
commits = grouped.get(commit_type, [])
|
||||
if not commits:
|
||||
continue
|
||||
header = SECTIONS.get(commit_type, "Other")
|
||||
out.append(header.upper())
|
||||
for item in commits:
|
||||
out.append(f"* {item}")
|
||||
out.append("")
|
||||
return "\n".join(out).rstrip() + "\n"
|
||||
|
||||
|
||||
def main() -> int:
|
||||
args = parse_args()
|
||||
|
||||
if args.demo:
|
||||
subjects = DEMO_COMMITS
|
||||
elif args.stdin:
|
||||
subjects = read_stdin()
|
||||
else:
|
||||
subjects = get_git_log(args.from_ref, args.to_ref)
|
||||
|
||||
if not subjects:
|
||||
print("No commits found.", file=sys.stderr)
|
||||
return 0
|
||||
|
||||
grouped = group_commits(subjects)
|
||||
|
||||
if args.format == "markdown":
|
||||
print(render_markdown(grouped), end="")
|
||||
else:
|
||||
print(render_text(grouped), end="")
|
||||
return 0
|
||||
|
||||
|
||||
if __name__ == "__main__":
|
||||
raise SystemExit(main())
|
||||
@@ -0,0 +1,100 @@
|
||||
# SaaS Architecture Patterns
|
||||
|
||||
This reference outlines common architecture choices for SaaS products.
|
||||
|
||||
## Multi-Tenant Architecture
|
||||
|
||||
### Shared Database, Shared Schema
|
||||
- Tenant isolation via `tenant_id` columns.
|
||||
- Lowest operational overhead.
|
||||
- Requires strict row-level authorization.
|
||||
|
||||
### Shared Database, Separate Schema
|
||||
- Per-tenant schema boundaries.
|
||||
- Better logical isolation.
|
||||
- Higher migration and operations complexity.
|
||||
|
||||
### Separate Database Per Tenant
|
||||
- Strongest isolation and compliance posture.
|
||||
- Best for enterprise/high-regulatory environments.
|
||||
- Highest cost and operational burden.
|
||||
|
||||
### Tenant Isolation Checklist
|
||||
|
||||
- Enforce tenant filters in all read/write queries.
|
||||
- Validate authorization at API and data layers.
|
||||
- Audit logs include tenant context.
|
||||
- Backups and restores preserve tenant boundaries.
|
||||
|
||||
## Authentication Patterns
|
||||
|
||||
### JWT-Based Session Pattern
|
||||
- Stateless access tokens.
|
||||
- Use short-lived access tokens + refresh tokens.
|
||||
- Rotate signing keys with versioning (`kid` usage).
|
||||
|
||||
### OAuth 2.0 / OIDC Pattern
|
||||
- Preferred for SSO and enterprise identity.
|
||||
- Support common providers (Google, Microsoft, Okta).
|
||||
- Map identity claims to internal roles and tenants.
|
||||
|
||||
### Hybrid Auth Pattern
|
||||
- Email/password for SMB self-serve.
|
||||
- SSO/OAuth for enterprise accounts.
|
||||
|
||||
## Billing Integration Patterns
|
||||
|
||||
### Subscription Lifecycle
|
||||
1. Trial start
|
||||
2. Conversion to paid plan
|
||||
3. Renewal and invoice events
|
||||
4. Grace period / dunning
|
||||
5. Downgrade, cancellation, reactivation
|
||||
|
||||
### Billing Event Handling
|
||||
- Process webhook events idempotently.
|
||||
- Verify provider signatures.
|
||||
- Persist raw event payload for audit/debugging.
|
||||
- Reconcile billing state asynchronously.
|
||||
|
||||
### Entitlement Model
|
||||
- Separate billing plans from feature entitlements.
|
||||
- Resolve effective entitlements per tenant/user at request time.
|
||||
|
||||
## API Versioning Patterns
|
||||
|
||||
### URI Versioning
|
||||
- `/api/v1/...`, `/api/v2/...`
|
||||
- Explicit and easy to route.
|
||||
|
||||
### Header Versioning
|
||||
- Version via request header.
|
||||
- Cleaner URLs, more client coordination required.
|
||||
|
||||
### Versioning Rules
|
||||
- Avoid breaking changes inside a version.
|
||||
- Provide deprecation windows and migration docs.
|
||||
- Track version adoption per client.
|
||||
|
||||
## Database Schema Patterns for SaaS
|
||||
|
||||
### Core Entities
|
||||
- `tenants`
|
||||
- `users`
|
||||
- `memberships` (user-tenant-role mapping)
|
||||
- `plans`
|
||||
- `subscriptions`
|
||||
- `invoices`
|
||||
- `events_audit`
|
||||
|
||||
### Recommended Relationship Pattern
|
||||
- `tenants` 1:N `memberships`
|
||||
- `users` 1:N `memberships`
|
||||
- `tenants` 1:1 active `subscriptions`
|
||||
- `subscriptions` 1:N `invoices`
|
||||
|
||||
### Data Model Guardrails
|
||||
- Unique constraints on tenant-scoped natural keys.
|
||||
- Soft-delete where recoverability matters.
|
||||
- Created/updated timestamps on all mutable entities.
|
||||
- Migration strategy supports zero-downtime changes.
|
||||
Binary file not shown.
Binary file not shown.
Reference in New Issue
Block a user