firefrost-gaming/claude-skills-reference
3
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Dev (#305)

Browse Source 
* chore: update gitignore for audit reports and playwright cache

* fix: add YAML frontmatter (name + description) to all SKILL.md files

- Added frontmatter to 34 skills that were missing it entirely (0% Tessl score)
- Fixed name field format to kebab-case across all 169 skills
- Resolves #284

* chore: sync codex skills symlinks [automated]

* fix: optimize 14 low-scoring skills via Tessl review (#290)

Tessl optimization: 14 skills improved from ≤69% to 85%+. Closes #285, #286.

* chore: sync codex skills symlinks [automated]

* fix: optimize 18 skills via Tessl review + compliance fix (closes #287) (#291)

Phase 1: 18 skills optimized via Tessl (avg 77% → 95%). Closes #287.

* feat: add scripts and references to 4 prompt-only skills + Tessl optimization (#292)

Phase 2: 3 new scripts + 2 reference files for prompt-only skills. Tessl 45-55% → 94-100%.

* feat: add 6 agents + 5 slash commands for full coverage (v2.7.0) (#293)

Phase 3: 6 new agents (all 9 categories covered) + 5 slash commands.

* fix: Phase 5 verification fixes + docs update (#294)

Phase 5 verification fixes

* chore: sync codex skills symlinks [automated]

* fix: marketplace audit — all 11 plugins validated by Claude Code (#295)

Marketplace audit: all 11 plugins validated + installed + tested in Claude Code

* fix: restore 7 removed plugins + revert playwright-pro name to pw

Reverts two overly aggressive audit changes:
- Restored content-creator, demand-gen, fullstack-engineer, aws-architect,
  product-manager, scrum-master, skill-security-auditor to marketplace
- Reverted playwright-pro plugin.json name back to 'pw' (intentional short name)

* refactor: split 21 over-500-line skills into SKILL.md + references (#296)

* chore: sync codex skills symlinks [automated]

* docs: update all documentation with accurate counts and regenerated skill pages

- Update skill count to 170, Python tools to 213, references to 314 across all docs
- Regenerate all 170 skill doc pages from latest SKILL.md sources
- Update CLAUDE.md with v2.1.1 highlights, accurate architecture tree, and roadmap
- Update README.md badges and overview table
- Update marketplace.json metadata description and version
- Update mkdocs.yml, index.md, getting-started.md with correct numbers

* fix: add root-level SKILL.md and .codex/instructions.md to all domains (#301)

Root cause: CLI tools (ai-agent-skills, agent-skills-cli) look for SKILL.md
at the specified install path. 7 of 9 domain directories were missing this
file, causing "Skill not found" errors for bundle installs like:
  npx ai-agent-skills install alirezarezvani/claude-skills/engineering-team

Fix:
- Add root-level SKILL.md with YAML frontmatter to 7 domains
- Add .codex/instructions.md to 8 domains (for Codex CLI discovery)
- Update INSTALLATION.md with accurate skill counts (53→170)
- Add troubleshooting entry for "Skill not found" error

All 9 domains now have: SKILL.md + .codex/instructions.md + plugin.json

Closes #301

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* feat: add Gemini CLI + OpenClaw support, fix Codex missing 25 skills

Gemini CLI:
- Add GEMINI.md with activation instructions
- Add scripts/gemini-install.sh setup script
- Add scripts/sync-gemini-skills.py (194 skills indexed)
- Add .gemini/skills/ with symlinks for all skills, agents, commands
- Remove phantom medium-content-pro entries from sync script
- Add top-level folder filter to prevent gitignored dirs from leaking

Codex CLI:
- Fix sync-codex-skills.py missing "engineering" domain (25 POWERFUL skills)
- Regenerate .codex/skills-index.json: 124 → 149 skills
- Add 25 new symlinks in .codex/skills/

OpenClaw:
- Add OpenClaw installation section to INSTALLATION.md
- Add ClawHub install + manual install + YAML frontmatter docs

Documentation:
- Update INSTALLATION.md with all 4 platforms + accurate counts
- Update README.md: "three platforms" → "four platforms" + Gemini quick start
- Update CLAUDE.md with Gemini CLI support in v2.1.1 highlights
- Update SKILL-AUTHORING-STANDARD.md + SKILL_PIPELINE.md with Gemini steps
- Add OpenClaw + Gemini to installation locations reference table

Marketplace: all 18 plugins validated — sources exist, SKILL.md present

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* feat(product,pm): world-class product & PM skills audit — 6 scripts, 5 agents, 7 commands, 23 references/assets

Phase 1 — Agent & Command Foundation:
- Rewrite cs-project-manager agent (55→515 lines, 4 workflows, 6 skill integrations)
- Expand cs-product-manager agent (408→684 lines, orchestrates all 8 product skills)
- Add 7 slash commands: /rice, /okr, /persona, /user-story, /sprint-health, /project-health, /retro

Phase 2 — Script Gap Closure (2,779 lines):
- jira-expert: jql_query_builder.py (22 patterns), workflow_validator.py
- confluence-expert: space_structure_generator.py, content_audit_analyzer.py
- atlassian-admin: permission_audit_tool.py
- atlassian-templates: template_scaffolder.py (Confluence XHTML generation)

Phase 3 — Reference & Asset Enrichment:
- 9 product references (competitive-teardown, landing-page-generator, saas-scaffolder)
- 6 PM references (confluence-expert, atlassian-admin, atlassian-templates)
- 7 product assets (templates for PRD, RICE, sprint, stories, OKR, research, design system)
- 1 PM asset (permission_scheme_template.json)

Phase 4 — New Agents:
- cs-agile-product-owner, cs-product-strategist, cs-ux-researcher

Phase 5 — Integration & Polish:
- Related Skills cross-references in 8 SKILL.md files
- Updated product-team/CLAUDE.md (5→8 skills, 6→9 tools, 4 agents, 5 commands)
- Updated project-management/CLAUDE.md (0→12 scripts, 3 commands)
- Regenerated docs site (177 pages), updated homepage and getting-started

Quality audit: 31 files reviewed, 29 PASS, 2 fixed (copy-frameworks.md, governance-framework.md)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* fix: audit and repair all plugins, agents, and commands

- Fix 12 command files: correct CLI arg syntax, script paths, and usage docs
- Fix 3 agents with broken script/reference paths (cs-content-creator,
  cs-demand-gen-specialist, cs-financial-analyst)
- Add complete YAML frontmatter to 5 agents (cs-growth-strategist,
  cs-engineering-lead, cs-senior-engineer, cs-financial-analyst,
  cs-quality-regulatory)
- Fix cs-ceo-advisor related agent path
- Update marketplace.json metadata counts (224 tools, 341 refs, 14 agents,
  12 commands)

Verified: all 19 scripts pass --help, all 14 agent paths resolve, mkdocs
builds clean.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* fix: repair 25 Python scripts failing --help across all domains

- Fix Python 3.10+ syntax (float | None → Optional[float]) in 2 scripts
- Add argparse CLI handling to 9 marketing scripts using raw sys.argv
- Fix 10 scripts crashing at module level (wrap in __main__, add argparse)
- Make yaml/prefect/mcp imports conditional with stdlib fallbacks (4 scripts)
- Fix f-string backslash syntax in project_bootstrapper.py
- Fix -h flag conflict in pr_analyzer.py
- Fix tech-debt.md description (score → prioritize)

All 237 scripts now pass python3 --help verification.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* fix(product-team): close 3 verified gaps in product skills

- Fix competitive-teardown/SKILL.md: replace broken references
  DATA_COLLECTION.md → references/data-collection-guide.md and
  TEMPLATES.md → references/analysis-templates.md (workflow was broken
  at steps 2 and 4)

- Upgrade landing_page_scaffolder.py: add TSX + Tailwind output format
  (--format tsx) matching SKILL.md promise of Next.js/React components.
  4 design styles (dark-saas, clean-minimal, bold-startup, enterprise).
  TSX is now default; HTML preserved via --format html

- Rewrite README.md: fix stale counts (was 5 skills/15+ tools, now
  accurately shows 8 skills/9 tools), remove 7 ghost scripts that
  never existed (sprint_planner.py, velocity_tracker.py, etc.)

- Fix tech-debt.md description (score → prioritize)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* release: v2.1.2 — landing page TSX output, brand voice integration, docs update

- Landing page generator defaults to Next.js TSX + Tailwind CSS (4 design styles)
- Brand voice analyzer integrated into landing page generation workflow
- CHANGELOG, CLAUDE.md, README.md updated for v2.1.2
- All 13 plugin.json + marketplace.json bumped to 2.1.2
- Gemini/Codex skill indexes re-synced
- Backward compatible: --format html preserved, no breaking changes

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

---------

Co-authored-by: alirezarezvani <5697919+alirezarezvani@users.noreply.github.com>
Co-authored-by: Leo <leo@openclaw.ai>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Alireza Rezvani
2026-03-10 09:48:49 +01:00
committed by GitHub
parent f6fe59aac4
commit a68ae3a05e
140 changed files with 10924 additions and 891 deletions
Download Patch File Download Diff File Expand all files Collapse all files

48
.claude-plugin/marketplace.json
View File

@@ -4,19 +4,19 @@
"name": "Alireza Rezvani",
"url": "https://alirezarezvani.com"
},
"description": "149 production-ready skill packages for Claude AI across 9 domains: marketing (42), engineering (23+25), C-level advisory (28), regulatory/QMS (12), product (8), project management (6), business growth (4), and finance (1). Includes 213 Python tools, 314 reference documents, 9 agents, and 5 slash commands.",
"description": "149 production-ready skill packages for Claude AI across 9 domains: marketing (42), engineering (23+25), C-level advisory (28), regulatory/QMS (12), product (8), project management (6), business growth (4), and finance (1). Includes 224 Python tools, 341 reference documents, 14 agents, and 12 slash commands.",
"homepage": "https://github.com/alirezarezvani/claude-skills",
"repository": "https://github.com/alirezarezvani/claude-skills",
"metadata": {
"description": "149 production-ready skill packages across 9 domains with 213 Python tools, 314 reference documents, 9 agents, and 5 slash commands. Compatible with Claude Code, Codex CLI, Gemini CLI, and OpenClaw.",
"version": "2.1.1"
"description": "149 production-ready skill packages across 9 domains with 224 Python tools, 341 reference documents, 14 agents, and 12 slash commands. Compatible with Claude Code, Codex CLI, Gemini CLI, and OpenClaw.",
"version": "2.1.2"
},
"plugins": [
{
"name": "marketing-skills",
"source": "./marketing-skill",
"description": "42 marketing skills across 7 pods: Content, SEO, CRO, Channels, Growth, Intelligence, and Sales enablement. 27 Python tools, 60 reference docs.",
"version": "2.1.1",
"description": "42 marketing skills across 7 pods: Content, SEO, CRO, Channels, Growth, Intelligence, and Sales enablement. 46 Python tools, 72 reference docs.",
"version": "2.1.2",
"author": {
"name": "Alireza Rezvani"
},
@@ -38,7 +38,7 @@
"name": "c-level-skills",
"source": "./c-level-advisor",
"description": "28 C-level advisory skills: virtual board of directors (CEO, CTO, COO, CPO, CMO, CFO, CRO, CISO, CHRO), executive mentor, founder coach, orchestration (Chief of Staff, board meetings, decision logger), strategic capabilities (board deck builder, scenario war room, competitive intel, M&A playbook), and culture frameworks.",
"version": "2.1.1",
"version": "2.1.2",
"author": {
"name": "Alireza Rezvani"
},
@@ -58,7 +58,7 @@
"name": "engineering-advanced-skills",
"source": "./engineering",
"description": "25 advanced engineering skills: agent designer, RAG architect, database designer, migration architect, observability designer, dependency auditor, release manager, API reviewer, CI/CD pipeline builder, MCP server builder, skill security auditor, performance profiler, and more.",
"version": "2.1.1",
"version": "2.1.2",
"author": {
"name": "Alireza Rezvani"
},
@@ -81,7 +81,7 @@
"name": "engineering-skills",
"source": "./engineering-team",
"description": "23 engineering skills: architecture, frontend, backend, fullstack, QA, DevOps, security, AI/ML, data engineering, Playwright (9 sub-skills), self-improving agent, Stripe integration, TDD guide, tech stack evaluator.",
"version": "2.1.1",
"version": "2.1.2",
"author": {
"name": "Alireza Rezvani"
},
@@ -103,7 +103,7 @@
"name": "ra-qm-skills",
"source": "./ra-qm-team",
"description": "12 regulatory affairs & quality management skills for HealthTech/MedTech: ISO 13485 QMS, MDR 2017/745, FDA 510(k)/PMA, GDPR/DSGVO, ISO 27001 ISMS, CAPA management, risk management, clinical evaluation.",
"version": "2.1.1",
"version": "2.1.2",
"author": {
"name": "Alireza Rezvani"
},
@@ -122,8 +122,8 @@
{
"name": "product-skills",
"source": "./product-team",
"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, SaaS scaffolder.",
"version": "2.1.1",
"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.",
"version": "2.1.2",
"author": {
"name": "Alireza Rezvani"
},
@@ -142,8 +142,8 @@
{
"name": "pm-skills",
"source": "./project-management",
"description": "6 project management skills: senior PM, scrum master, Jira expert, Confluence expert, Atlassian admin, template creator.",
"version": "2.1.1",
"description": "6 project management skills with 12 Python tools: senior PM, scrum master, Jira expert, Confluence expert, Atlassian admin, template creator.",
"version": "2.1.2",
"author": {
"name": "Alireza Rezvani"
},
@@ -161,7 +161,7 @@
"name": "business-growth-skills",
"source": "./business-growth",
"description": "4 business & growth skills: customer success manager, sales engineer, revenue operations, contract & proposal writer.",
"version": "2.1.1",
"version": "2.1.2",
"author": {
"name": "Alireza Rezvani"
},
@@ -178,7 +178,7 @@
"name": "finance-skills",
"source": "./finance",
"description": "1 finance skill: financial analyst with ratio analysis, DCF valuation, budgeting, and forecasting. 4 Python automation tools.",
"version": "2.1.1",
"version": "2.1.2",
"author": {
"name": "Alireza Rezvani"
},
@@ -195,7 +195,7 @@
"name": "pw",
"source": "./engineering-team/playwright-pro",
"description": "Production-grade Playwright testing toolkit. 9 skills, 3 agents, 55 templates, TestRail + BrowserStack MCP integrations. Generate tests, fix flaky failures, migrate from Cypress/Selenium.",
"version": "2.1.1",
"version": "2.1.2",
"author": {
"name": "Alireza Rezvani"
},
@@ -214,7 +214,7 @@
"name": "self-improving-agent",
"source": "./engineering-team/self-improving-agent",
"description": "Curate auto-memory, promote learnings to CLAUDE.md and rules, extract patterns into skills.",
"version": "2.1.1",
"version": "2.1.2",
"author": {
"name": "Alireza Rezvani"
},
@@ -230,7 +230,7 @@
"name": "content-creator",
"source": "./marketing-skill/content-creator",
"description": "SEO-optimized marketing content with brand voice analysis, content frameworks, and social media templates.",
"version": "2.1.1",
"version": "2.1.2",
"author": {
"name": "Alireza Rezvani"
},
@@ -246,7 +246,7 @@
"name": "demand-gen",
"source": "./marketing-skill/marketing-demand-acquisition",
"description": "Multi-channel demand generation, paid media optimization, SEO strategy, and partnership programs.",
"version": "2.1.1",
"version": "2.1.2",
"author": {
"name": "Alireza Rezvani"
},
@@ -261,7 +261,7 @@
"name": "fullstack-engineer",
"source": "./engineering-team/senior-fullstack",
"description": "Full-stack engineering with React, Node, databases, and deployment.",
"version": "2.1.1",
"version": "2.1.2",
"author": {
"name": "Alireza Rezvani"
},
@@ -277,7 +277,7 @@
"name": "aws-architect",
"source": "./engineering-team/aws-solution-architect",
"description": "AWS serverless architecture design with IaC templates, cost optimization, and CI/CD pipelines.",
"version": "2.1.1",
"version": "2.1.2",
"author": {
"name": "Alireza Rezvani"
},
@@ -293,7 +293,7 @@
"name": "product-manager",
"source": "./product-team/product-manager-toolkit",
"description": "Product management toolkit with RICE scoring, customer interview analysis, and PRD generation.",
"version": "2.1.1",
"version": "2.1.2",
"author": {
"name": "Alireza Rezvani"
},
@@ -309,7 +309,7 @@
"name": "scrum-master",
"source": "./project-management/scrum-master",
"description": "Sprint health analysis, velocity tracking, and retrospective facilitation.",
"version": "2.1.1",
"version": "2.1.2",
"author": {
"name": "Alireza Rezvani"
},
@@ -325,7 +325,7 @@
"name": "skill-security-auditor",
"source": "./engineering/skill-security-auditor",
"description": "Security audit and vulnerability scanner for AI agent skills. Scans for malicious patterns, prompt injection, data exfiltration, and unsafe file operations.",
"version": "2.1.1",
"version": "2.1.2",
"author": {
"name": "Alireza Rezvani"
},

60
.gemini/skills-index.json
View File

@@ -1,8 +1,13 @@
{
"version": "1.0.0",
"name": "gemini-cli-skills",
"total_skills": 194,
"total_skills": 204,
"skills": [
{
"name": "cs-agile-product-owner",
"category": "agent",
"description": "Agile product owner agent for epic breakdown, sprint planning, backlog refinement, and INVEST-compliant user story generation"
},
{
"name": "cs-ceo-advisor",
"category": "agent",
@@ -43,10 +48,15 @@
"category": "agent",
"description": "Product management agent for feature prioritization, customer discovery, PRD development, and roadmap planning using RICE framework"
},
{
"name": "cs-product-strategist",
"category": "agent",
"description": "Product strategy agent for quarterly OKR planning, competitive landscape analysis, product vision development, and strategy pivot evaluation"
},
{
"name": "cs-project-manager",
"category": "agent",
"description": "Project Manager agent for sprint planning, Jira/Confluence workflows, Scrum ceremonies, and stakeholder reporting. Orchestrates project-management skills. Spawn when users need sprint planning, Jira configuration, workflow design, retrospectives, or project status dashboards."
"description": "Project Manager agent for sprint planning, Jira/Confluence workflows, Scrum ceremonies, and stakeholder reporting. Orchestrates project-management skills."
},
{
"name": "cs-quality-regulatory",
@@ -58,6 +68,11 @@
"category": "agent",
"description": "Senior Engineer agent for architecture decisions, code review, DevOps, and API design. Orchestrates engineering and engineering-team skills for technical implementation work. Spawn when users need system design, code quality review, CI/CD pipeline setup, or infrastructure decisions."
},
{
"name": "cs-ux-researcher",
"category": "agent",
"description": "UX research agent for research planning, persona generation, journey mapping, and usability test analysis"
},
{
"name": "business-growth-bundle",
"category": "business-growth",
@@ -263,11 +278,41 @@
"category": "command",
"description": "Build competitive analysis matrices with scoring and gap analysis. Usage: /competitive-matrix <analyze> [options]"
},
{
"name": "okr",
"category": "command",
"description": "Generate OKR cascades from company strategy to team objectives. Usage: /okr generate <strategy>"
},
{
"name": "persona",
"category": "command",
"description": "Generate data-driven user personas for UX research and product design. Usage: /persona generate [options]"
},
{
"name": "pipeline",
"category": "command",
"description": "Detect stack and generate CI/CD pipeline configs. Usage: /pipeline <detect|generate> [options]"
},
{
"name": "project-health",
"category": "command",
"description": "Portfolio health dashboard and risk matrix analysis. Usage: /project-health <dashboard|risk> [options]"
},
{
"name": "retro",
"category": "command",
"description": "Analyze sprint retrospectives for patterns and action item tracking. Usage: /retro analyze <retro_data.json>"
},
{
"name": "rice",
"category": "command",
"description": "RICE feature prioritization with scoring and capacity planning. Usage: /rice prioritize <features.csv> [options]"
},
{
"name": "sprint-health",
"category": "command",
"description": "Sprint health scoring and velocity analysis for agile teams. Usage: /sprint-health <analyze|velocity> [options]"
},
{
"name": "tdd",
"category": "command",
@@ -276,7 +321,12 @@
{
"name": "tech-debt",
"category": "command",
"description": "Score, track, and prioritize technical debt. Usage: /tech-debt <scan|score|report> [options]"
"description": "Scan, prioritize, and report technical debt. Usage: /tech-debt <scan|prioritize|report> [options]"
},
{
"name": "user-story",
"category": "command",
"description": "Generate user stories with acceptance criteria and sprint planning. Usage: /user-story <generate|sprint> [options]"
},
{
"name": "aws-solution-architect",
@@ -976,7 +1026,7 @@
],
"categories": {
"agent": {
"count": 11,
"count": 14,
"description": "Agent resources"
},
"business-growth": {
@@ -988,7 +1038,7 @@
"description": "C-level resources"
},
"command": {
"count": 5,
"count": 12,
"description": "Command resources"
},
"engineering": {

1
.gemini/skills/cs-agile-product-owner/SKILL.md Symbolic link
View File

@@ -0,0 +1 @@
../../../agents/product/cs-agile-product-owner.md

1
.gemini/skills/cs-product-strategist/SKILL.md Symbolic link
View File

@@ -0,0 +1 @@
../../../agents/product/cs-product-strategist.md

1
.gemini/skills/cs-ux-researcher/SKILL.md Symbolic link
View File

@@ -0,0 +1 @@
../../../agents/product/cs-ux-researcher.md

1
.gemini/skills/okr/SKILL.md Symbolic link
View File

@@ -0,0 +1 @@
../../../commands/okr.md

1
.gemini/skills/persona/SKILL.md Symbolic link
View File

@@ -0,0 +1 @@
../../../commands/persona.md

1
.gemini/skills/project-health/SKILL.md Symbolic link
View File

@@ -0,0 +1 @@
../../../commands/project-health.md

1
.gemini/skills/retro/SKILL.md Symbolic link
View File

@@ -0,0 +1 @@
../../../commands/retro.md

1
.gemini/skills/rice/SKILL.md Symbolic link
View File

@@ -0,0 +1 @@
../../../commands/rice.md

1
.gemini/skills/sprint-health/SKILL.md Symbolic link
View File

@@ -0,0 +1 @@
../../../commands/sprint-health.md

1
.gemini/skills/user-story/SKILL.md Symbolic link
View File

@@ -0,0 +1 @@
../../../commands/user-story.md

39
CHANGELOG.md
View File

@@ -5,6 +5,39 @@ All notable changes to the Claude Skills Library will be documented in this file
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [2.1.2] - 2026-03-10
### Changed — Product Team Quality & Cross-Domain Integration
**Landing Page Generator — TSX + Brand Voice Integration:**
- Landing page scaffolder now defaults to **Next.js/React TSX output** with Tailwind CSS (HTML preserved via `--format html`)
- 4 Tailwind design styles: `dark-saas`, `clean-minimal`, `bold-startup`, `enterprise` with complete class mappings
- 7 section generators: nav, hero, features, testimonials, pricing, CTA, footer
- Brand voice integration: generation workflow now includes brand voice analysis (step 2) using `marketing-skill/content-production/scripts/brand_voice_analyzer.py` to map voice profile to design style + copy framework
- Added Related Skills cross-references to SKILL.md
**Documentation Updates:**
- `product-team/CLAUDE.md` — Added Workflow 4 (Brand-Aligned Landing Page), updated scaffolder section with TSX docs, added Cross-Domain Integration section
- `product-team/README.md` — Fixed ghost script references (removed 7 scripts that never existed), corrected skill/tool/agent/command counts
- `product-team/.codex/instructions.md` — Added brand voice cross-domain workflow and TSX default note
### Fixed
- **competitive-teardown/SKILL.md** — Fixed 6 broken file references (`DATA_COLLECTION.md` → `references/data-collection-guide.md`, `TEMPLATES.md` → `references/analysis-templates.md`)
- **saas-scaffolder/scripts/project_bootstrapper.py** — Fixed f-string backslash syntax incompatible with Python <3.12
- **237 Python scripts verified** — All pass `--help` without errors (previous session fixed 25 scripts across all domains)
### Added
- `landing-page-generator/SKILL.md` — Brand voice analysis as prerequisite step in generation workflow
- Codex and Gemini skill indexes re-synced with updated SKILL.md content
### Backward Compatibility
- `--format html` still works for landing page scaffolder (TSX is new default)
- All existing script CLIs and arguments unchanged
- No skill removals or renames
- Plugin source paths unchanged — existing installations will not break
---
## [2.1.1] - 2026-03-07
### Changed — Tessl Quality Optimization (#287)
@@ -320,6 +353,8 @@ Major rewrite of existing skills following Anthropic's agent skills specificatio
| Version | Date | Skills | Domains | Key Changes |
|---------|------|--------|---------|-------------|
| 2.1.2 | 2026-03-10 | 170 | 9 | Landing page TSX output, brand voice integration, 25 script fixes |
| 2.1.1 | 2026-03-07 | 170 | 9 | 18 skills optimized via Tessl, YAML frontmatter, agents + commands |
| 2.0.0 | 2026-02-16 | 86 | 9 | 26 POWERFUL-tier skills, 37 refactored, Codex support, 3 new domains |
| 1.1.0 | 2025-10-21 | 42 | 6 | Anthropic best practices refactoring (5 skills) |
| 1.0.2 | 2025-10-21 | 42 | 6 | GitHub repository pages (LICENSE, CONTRIBUTING, etc.) |
@@ -336,7 +371,9 @@ Major rewrite of existing skills following Anthropic's agent skills specificatio
---
[Unreleased]: https://github.com/alirezarezvani/claude-skills/compare/v2.0.0...HEAD
[Unreleased]: https://github.com/alirezarezvani/claude-skills/compare/v2.1.2...HEAD
[2.1.2]: https://github.com/alirezarezvani/claude-skills/compare/v2.1.1...v2.1.2
[2.1.1]: https://github.com/alirezarezvani/claude-skills/compare/v2.0.0...v2.1.1
[2.0.0]: https://github.com/alirezarezvani/claude-skills/compare/v1.0.2...v2.0.0
[1.1.0]: https://github.com/alirezarezvani/claude-skills/compare/v1.0.1...v1.1.0
[1.0.2]: https://github.com/alirezarezvani/claude-skills/compare/v1.0.1...v1.0.2

21
CLAUDE.md
View File

@@ -124,15 +124,20 @@ See [standards/git/git-workflow-standards.md](standards/git/git-workflow-standar
## Current Version
**Version:** v2.1.1 (latest)
**Version:** v2.1.2 (latest)
**v2.1.1 Highlights:**
**v2.1.2 Highlights:**
- Landing page generator now outputs **Next.js TSX + Tailwind CSS** by default (4 design styles, 7 section generators)
- **Brand voice integration** — landing page workflow uses marketing brand voice analyzer to match copy tone to design style
- 25 Python scripts fixed across all domains (syntax, dependencies, argparse)
- 237/237 scripts verified passing `--help`
- Competitive teardown SKILL.md fixed (6 broken file references)
- Cross-domain workflows documented (product + marketing skill integration)
**v2.1.1 (2026-03-07):**
- 18 skills optimized from 66-83% to 85-100% via Tessl quality review
- 21 over-500-line skills split into SKILL.md + references/
- YAML frontmatter (name + description) added to all SKILL.md files
- 6 new agents + 5 slash commands for full domain coverage
- **Gemini CLI support added** (scripts/gemini-install.sh + GEMINI.md)
- MkDocs Material documentation site at alirezarezvani.github.io/claude-skills
- 6 new agents + 5 slash commands, Gemini CLI support, MkDocs docs site
**v2.0.0 (2026-02-16):**
- 25 POWERFUL-tier engineering skills added (engineering/ folder)
@@ -185,6 +190,6 @@ See domain-specific roadmaps in each skill folder's README.md or roadmap files.
---
**Last Updated:** March 2026
**Version:** v2.1.1
**Last Updated:** March 10, 2026
**Version:** v2.1.2
**Status:** 170 skills deployed across 9 domains, 18 marketplace plugins, docs site live

20
README.md
View File

@@ -1,6 +1,6 @@
# Claude Code Skills & Plugins
**170 production-ready skills and plugins for Claude Code, OpenAI Codex, and OpenClaw** — reusable expertise bundles that transform AI coding agents into specialized professionals across engineering, product, marketing, compliance, and more.
**170 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.
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
[![Skills](https://img.shields.io/badge/Skills-170-brightgreen.svg)](#skills-overview)
@@ -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.
**One repo, four platforms:** Works natively as Claude Code plugins, OpenAI Codex CLI and agents, Gemini CLI skills, and OpenClaw skills. All 237 Python tools are stdlib-only and verified working.
---
@@ -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, SaaS scaffolder | [product-team/](product-team/) |
| **🎯 Product** | 8 | Product manager, agile PO, strategist, UX researcher, UI design, landing pages (TSX + Tailwind), SaaS scaffolder | [product-team/](product-team/) |
| **📣 Marketing** | 42 | 7 pods: Content (8), SEO (5), CRO (6), Channels (5), Growth (4), Intelligence (4), Sales (2) + context foundation + orchestration router. 27 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,11 +189,11 @@ for MDR Annex II compliance gaps.
## Python Analysis Tools
210+ CLI tools ship with the skills:
237 CLI tools ship with the skills (all verified, stdlib-only):
```bash
# Brand voice analysis
python3 marketing-skill/content-creator/scripts/brand_voice_analyzer.py article.txt
python3 marketing-skill/content-production/scripts/brand_voice_analyzer.py article.txt
# Tech debt scoring
python3 c-level-advisor/cto-advisor/scripts/tech_debt_analyzer.py /path/to/codebase
@@ -203,6 +203,9 @@ python3 product-team/product-manager-toolkit/scripts/rice_prioritizer.py feature
# Security audit
python3 engineering/skill-security-auditor/scripts/skill_security_auditor.py /path/to/skill/
# Landing page (TSX + Tailwind)
python3 product-team/landing-page-generator/scripts/landing_page_scaffolder.py config.json --format tsx
```
---
@@ -223,10 +226,13 @@ python3 engineering/skill-security-auditor/scripts/skill_security_auditor.py /pa
Add the marketplace with `/plugin marketplace add alirezarezvani/claude-skills`, then install any skill bundle with `/plugin install <name>@claude-code-skills`.
**Do these skills work with OpenAI Codex?**
Yes. Skills work natively with Claude Code, OpenAI Codex, and OpenClaw. See Quick Install above.
Yes. Skills work natively with Claude Code, OpenAI Codex, Gemini CLI, and OpenClaw. See Quick Install above.
**Will updating break my installation?**
No. We follow semantic versioning and maintain backward compatibility within patch releases. Existing script arguments, plugin source paths, and SKILL.md structures are never changed in patch versions. See the [CHANGELOG](CHANGELOG.md) for details on each release.
**Are the Python tools dependency-free?**
Yes. All 210+ Python CLI tools use the standard library only — zero pip installs required.
Yes. All 237 Python CLI tools use the standard library only — zero pip installs required. Every script is verified to run with `--help`.
**How do I create my own Claude Code skill?**
Each skill is a folder with a `SKILL.md` (frontmatter + instructions), optional `scripts/`, `references/`, and `assets/`. See the [Skills & Agents Factory](https://github.com/alirezarezvani/claude-code-skills-agents-factory) for a step-by-step guide.

16
agents/business-growth/cs-growth-strategist.md
View File

@@ -1,6 +1,10 @@
---
name: cs-growth-strategist
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.
skills: business-growth
domain: business-growth
model: sonnet
tools: [Read, Write, Bash, Grep, Glob]
---
# cs-growth-strategist
@@ -48,3 +52,15 @@ Growth-focused operator covering the full revenue lifecycle: pipeline management
- Pipeline reports → JSON with visual summary
- Health scores → segment-aware (Enterprise/Mid-Market/SMB)
- Proposals → structured with pricing tables and ROI projections
## Success Metrics
- **Pipeline Coverage:** Maintain 3x+ pipeline-to-quota ratio across segments
- **Churn Rate:** Reduce gross churn by 15%+ quarter-over-quarter
- **Expansion Revenue:** Achieve 120%+ net revenue retention (NRR)
- **Forecast Accuracy:** Weighted forecast within 10% of actual bookings
## Related Agents
- [cs-product-manager](../product/cs-product-manager.md) -- Product roadmap alignment for sales positioning and feature prioritization
- [cs-financial-analyst](../finance/cs-financial-analyst.md) -- Revenue forecasting validation and financial modeling support

2
agents/c-level/cs-ceo-advisor.md
View File

@@ -344,7 +344,7 @@ esac
- [cs-cto-advisor](cs-cto-advisor.md) - Technology strategy and engineering leadership (CTO counterpart)
- [cs-product-manager](../product/cs-product-manager.md) - Product strategy and roadmap execution (planned)
- [cs-growth-strategist](../marketing/cs-growth-strategist.md) - Growth strategy and market expansion (planned)
- [cs-growth-strategist](../business-growth/cs-growth-strategist.md) - Growth strategy and market expansion (planned)
## References

16
agents/engineering-team/cs-engineering-lead.md
View File

@@ -1,6 +1,10 @@
---
name: cs-engineering-lead
description: Engineering Team Lead agent for coordinating QA, security, data engineering, ML, and frontend/backend teams. Orchestrates engineering-team skills for team-level technical decisions. Spawn when users need team coordination, tech stack evaluation, incident response, or cross-functional engineering work.
skills: engineering-team
domain: engineering
model: sonnet
tools: [Read, Write, Bash, Grep, Glob]
---
# cs-engineering-lead
@@ -68,3 +72,15 @@ Engineering team lead coordinating across specializations: frontend, backend, QA
- Incident reports → timeline, RCA, 5-Why, action items with owners
- Evaluations → scoring matrix with weighted dimensions
- Feature plans → RACI matrix with milestone dates
## Success Metrics
- **Incident MTTR:** Mean time to resolve P1/P2 incidents under 2 hours
- **Deployment Frequency:** Ship to production 5+ times per week
- **Cross-Team Delivery:** 90%+ of cross-functional features delivered on schedule
- **Engineering Health:** Test coverage >80%, CI pipeline green rate >95%
## Related Agents
- [cs-senior-engineer](../engineering/cs-senior-engineer.md) -- Architecture decisions, code review, and CI/CD pipeline setup
- [cs-product-manager](../product/cs-product-manager.md) -- Feature prioritization and requirements alignment

16
agents/engineering/cs-senior-engineer.md
View File

@@ -1,6 +1,10 @@
---
name: cs-senior-engineer
description: Senior Engineer agent for architecture decisions, code review, DevOps, and API design. Orchestrates engineering and engineering-team skills for technical implementation work. Spawn when users need system design, code quality review, CI/CD pipeline setup, or infrastructure decisions.
skills: engineering
domain: engineering
model: sonnet
tools: [Read, Write, Bash, Grep, Glob]
---
# cs-senior-engineer
@@ -71,6 +75,14 @@ Cross-cutting senior engineer covering architecture, backend, DevOps, security,
- Pipeline configs → validated YAML with comments
- All recommendations include tradeoff analysis
## Success Metrics
- **Code Review Turnaround:** PR reviews completed within 4 hours during business hours
- **Architecture Decision Quality:** ADRs reviewed and approved with no major reversals within 6 months
- **Pipeline Reliability:** CI/CD pipeline success rate >95%, deploy rollback rate <2%
- **Technical Debt Ratio:** Maintain tech debt backlog below 15% of total sprint capacity
## Related Agents
- `cs-cto-advisor` — Strategic technology decisions
- `cs-product-manager` — Feature prioritization context
- [cs-engineering-lead](../engineering-team/cs-engineering-lead.md) -- Team coordination, incident response, and cross-functional delivery
- [cs-product-manager](../product/cs-product-manager.md) -- Feature prioritization and requirements context

26
agents/finance/cs-financial-analyst.md
View File

@@ -1,6 +1,10 @@
---
name: cs-financial-analyst
description: Financial Analyst agent for DCF valuation, financial modeling, budgeting, and forecasting. Orchestrates finance skills. Spawn when users need financial statements analysis, valuation models, budget planning, ratio analysis, or industry benchmarking.
skills: finance
domain: finance
model: sonnet
tools: [Read, Write, Bash, Grep, Glob]
---
# cs-financial-analyst
@@ -12,20 +16,20 @@ Financial analyst covering valuation, ratio analysis, forecasting, and industry-
## Skill Integration
- `finance/financial-analyst` — DCF modeling, ratio analysis, forecasting, scenario planning
- Scripts: `dcf_calculator.py`, `ratio_analyzer.py`, `forecast_generator.py`, `scenario_modeler.py`
- Scripts: `dcf_valuation.py`, `ratio_calculator.py`, `forecast_builder.py`, `budget_variance_analyzer.py`
- References: `financial-ratios-guide.md`, `valuation-methodology.md`, `forecasting-best-practices.md`, `industry-adaptations.md`
## Core Workflows
### 1. Company Valuation
1. Gather financial data (revenue, costs, growth rate, WACC)
2. Run DCF model via `dcf_calculator.py`
2. Run DCF model via `dcf_valuation.py`
3. Calculate comparables (EV/EBITDA, P/E, EV/Revenue)
4. Adjust for industry via `industry-adaptations.md`
5. Present valuation range with sensitivity analysis
### 2. Financial Health Assessment
1. Run ratio analysis via `ratio_analyzer.py`
1. Run ratio analysis via `ratio_calculator.py`
2. Assess liquidity (current, quick ratio)
3. Assess profitability (gross margin, EBITDA margin, ROE)
4. Assess leverage (debt/equity, interest coverage)
@@ -33,8 +37,8 @@ Financial analyst covering valuation, ratio analysis, forecasting, and industry-
### 3. Revenue Forecasting
1. Analyze historical trends
2. Generate forecast via `forecast_generator.py`
3. Run scenarios (bull/base/bear) via `scenario_modeler.py`
2. Generate forecast via `forecast_builder.py`
3. Run scenarios (bull/base/bear) via `budget_variance_analyzer.py`
4. Calculate confidence intervals
5. Present with assumptions clearly stated
@@ -50,3 +54,15 @@ Financial analyst covering valuation, ratio analysis, forecasting, and industry-
- Ratios → benchmarked against industry with trend arrows
- Forecasts → 3 scenarios with probability weights
- All models include key assumptions section
## Success Metrics
- **Forecast Accuracy:** Revenue forecasts within 5% of actuals over trailing 4 quarters
- **Valuation Precision:** DCF valuations within 15% of market transaction comparables
- **Budget Variance:** Departmental budgets maintained within 10% of plan
- **Analysis Turnaround:** Financial models delivered within 48 hours of data receipt
## Related Agents
- [cs-ceo-advisor](../c-level/cs-ceo-advisor.md) -- Strategic financial decisions, board reporting, and fundraising planning
- [cs-growth-strategist](../business-growth/cs-growth-strategist.md) -- Revenue operations data and pipeline forecasting inputs

138
agents/marketing/cs-content-creator.md
View File

@@ -23,19 +23,7 @@ The cs-content-creator agent bridges the gap between creative content production
### Python Tools
1. **Brand Voice Analyzer**
- **Purpose:** Analyzes text for formality, tone, perspective, and readability to ensure brand consistency
- **Path:** `../../marketing-skill/content-creator/scripts/brand_voice_analyzer.py`
- **Usage:** `python ../../marketing-skill/content-creator/scripts/brand_voice_analyzer.py content.txt`
- **Output Formats:** Human-readable report or JSON for integrations
- **Use Cases:** Pre-publish content review, brand audit, voice consistency checking
2. **SEO Optimizer**
- **Purpose:** Comprehensive SEO analysis with keyword density, structure evaluation, and actionable recommendations
- **Path:** `../../marketing-skill/content-creator/scripts/seo_optimizer.py`
- **Usage:** `python ../../marketing-skill/content-creator/scripts/seo_optimizer.py article.md "primary keyword" "secondary,keywords"`
- **Features:** Keyword analysis, content structure, meta tags, SEO score (0-100), improvement recommendations
- **Use Cases:** Blog post optimization, landing page SEO, content audit
No Python tools — this skill relies on SKILL.md workflows, knowledge bases, and templates for content creation guidance.
### Knowledge Bases
@@ -54,20 +42,17 @@ The cs-content-creator agent bridges the gap between creative content production
- **Content:** Platform-specific best practices for LinkedIn (1,300 chars, professional tone), Twitter/X (280 chars, concise), Instagram (visual-first, caption strategy), Facebook (engagement tactics), TikTok (short-form video)
- **Use Case:** Platform optimization, social media strategy, content adaptation
4. **Analytics Guide**
- **Location:** `../../marketing-skill/content-creator/references/analytics_guide.md`
- **Content:** Content performance analytics and measurement frameworks
- **Use Case:** Content performance tracking, reporting, data-driven optimization
### Templates
1. **Content Calendar Template**
- **Location:** `../../marketing-skill/content-creator/assets/content-calendar.md`
- **Location:** `../../marketing-skill/content-creator/assets/content_calendar_template.md`
- **Use Case:** Planning monthly content, tracking production pipeline
2. **SEO Checklist**
- **Location:** `../../marketing-skill/content-creator/assets/seo-checklist.md`
- **Use Case:** Pre-publish validation, SEO audit
3. **Content Brief Template**
- **Location:** `../../marketing-skill/content-creator/assets/content-brief.md`
- **Use Case:** Writer briefing, stakeholder alignment
## Workflows
### Workflow 1: Blog Post Creation & Optimization
@@ -76,28 +61,27 @@ The cs-content-creator agent bridges the gap between creative content production
**Steps:**
1. **Draft Content** - Write initial blog post draft in markdown format
2. **Analyze Brand Voice** - Run brand voice analyzer to check tone and readability
2. **Reference Brand Guidelines** - Review brand voice requirements for tone and readability
```bash
python ../../marketing-skill/content-creator/scripts/brand_voice_analyzer.py draft-post.md
cat ../../marketing-skill/content-creator/references/brand_guidelines.md
```
3. **Review Feedback** - Adjust content based on formality score, tone, and readability metrics
4. **Optimize for SEO** - Run SEO optimizer with target keywords
3. **Review Content Frameworks** - Select appropriate blog post template (how-to, listicle, case study)
```bash
python ../../marketing-skill/content-creator/scripts/seo_optimizer.py draft-post.md "target keyword" "secondary,keywords,here"
cat ../../marketing-skill/content-creator/references/content_frameworks.md
```
4. **Optimize for SEO** - Apply SEO best practices from SKILL.md workflows (keyword placement, structure, meta description)
5. **Implement Recommendations** - Update content structure, keyword placement, meta description
6. **Final Validation** - Re-run both analyzers to verify improvements
6. **Final Validation** - Review against brand guidelines and content frameworks
**Expected Output:** SEO score 80+ with consistent brand voice alignment
**Expected Output:** SEO-optimized blog post with consistent brand voice alignment
**Time Estimate:** 2-3 hours for 1,500-word blog post
**Example:**
```bash
# Complete workflow
echo "# Blog Post Draft" > post.md
python ../../marketing-skill/content-creator/scripts/brand_voice_analyzer.py post.md
python ../../marketing-skill/content-creator/scripts/seo_optimizer.py post.md "content marketing" "SEO,strategy"
# Review guidelines before writing
cat ../../marketing-skill/content-creator/references/brand_guidelines.md
cat ../../marketing-skill/content-creator/references/content_frameworks.md
```
### Workflow 2: Multi-Platform Content Adaptation
@@ -113,10 +97,9 @@ python ../../marketing-skill/content-creator/scripts/seo_optimizer.py post.md "c
3. **Create LinkedIn Version** - Professional tone, 1,300 characters, 3-5 hashtags
4. **Create Twitter/X Thread** - Break into 280-char tweets, engaging hook
5. **Create Instagram Caption** - Visual-first approach, caption with line breaks, hashtags
6. **Validate Brand Voice** - Ensure consistency across all versions
6. **Validate Brand Voice** - Ensure consistency across all versions by reviewing against brand guidelines
```bash
python ../../marketing-skill/content-creator/scripts/brand_voice_analyzer.py linkedin-post.txt
python ../../marketing-skill/content-creator/scripts/brand_voice_analyzer.py twitter-thread.txt
cat ../../marketing-skill/content-creator/references/brand_guidelines.md
```
**Expected Output:** 4-5 platform-optimized versions from single source
@@ -129,19 +112,14 @@ python ../../marketing-skill/content-creator/scripts/seo_optimizer.py post.md "c
**Steps:**
1. **Collect Content** - Gather markdown files for all published content
2. **Batch Brand Voice Analysis** - Run analyzer on all content pieces
2. **Brand Voice Review** - Review each content piece against brand guidelines for consistency
```bash
for file in content/*.md; do
echo "Analyzing: $file"
python ../../marketing-skill/content-creator/scripts/brand_voice_analyzer.py "$file" json >> audit-results.json
done
cat ../../marketing-skill/content-creator/references/brand_guidelines.md
```
3. **Identify Inconsistencies** - Review formality scores, tone patterns, readability metrics
4. **SEO Audit** - Run SEO optimizer on key landing pages and blog posts
3. **Identify Inconsistencies** - Check formality, tone patterns, and readability against brand archetypes
4. **SEO Audit** - Review content structure against content frameworks best practices
```bash
for file in landing-pages/*.md; do
python ../../marketing-skill/content-creator/scripts/seo_optimizer.py "$file" "target-keyword"
done
cat ../../marketing-skill/content-creator/references/content_frameworks.md
```
5. **Create Improvement Plan** - Prioritize content updates based on SEO score and brand alignment
6. **Implement Updates** - Revise content following brand guidelines and SEO recommendations
@@ -152,12 +130,9 @@ python ../../marketing-skill/content-creator/scripts/seo_optimizer.py post.md "c
**Example:**
```bash
# Quick audit of top 5 blog posts
ls -t blog/*.md | head -5 | while read file; do
echo "=== $file ==="
python ../../marketing-skill/content-creator/scripts/brand_voice_analyzer.py "$file"
python ../../marketing-skill/content-creator/scripts/seo_optimizer.py "$file" "main-keyword"
done
# Review brand guidelines and frameworks before auditing content
cat ../../marketing-skill/content-creator/references/brand_guidelines.md
cat ../../marketing-skill/content-creator/references/analytics_guide.md
```
### Workflow 4: Campaign Content Planning
@@ -171,7 +146,7 @@ done
```
2. **Copy Content Calendar** - Use template for campaign planning
```bash
cp ../../marketing-skill/content-creator/assets/content-calendar.md campaign-calendar.md
cp ../../marketing-skill/content-creator/assets/content_calendar_template.md campaign-calendar.md
```
3. **Define Brand Voice Target** - Reference brand guidelines for campaign tone
```bash
@@ -179,10 +154,10 @@ done
```
4. **Create Content Briefs** - Use brief template for each content piece
5. **Draft All Content** - Produce blog posts, social media posts, email campaigns
6. **Validate Before Publishing** - Run analyzers on all campaign content
6. **Validate Before Publishing** - Review all campaign content against brand guidelines and social media optimization guides
```bash
python ../../marketing-skill/content-creator/scripts/brand_voice_analyzer.py campaign-email.md
python ../../marketing-skill/content-creator/scripts/seo_optimizer.py campaign-landing-page.md "campaign keyword"
cat ../../marketing-skill/content-creator/references/brand_guidelines.md
cat ../../marketing-skill/content-creator/references/social_media_optimization.md
```
**Expected Output:** Complete campaign content library with consistent brand voice and optimized SEO
@@ -191,52 +166,47 @@ done
## Integration Examples
### Example 1: Real-Time Content Feedback Loop
### Example 1: Content Quality Review Workflow
```bash
#!/bin/bash
# content-feedback.sh - Automated content quality check
# content-review.sh - Content quality review using knowledge bases
CONTENT_FILE=$1
PRIMARY_KEYWORD=$2
echo "🎨 Checking brand voice..."
python ../../marketing-skill/content-creator/scripts/brand_voice_analyzer.py "$CONTENT_FILE"
echo "Reviewing brand voice guidelines..."
cat ../../marketing-skill/content-creator/references/brand_guidelines.md
echo ""
echo "🔍 Checking SEO optimization..."
python ../../marketing-skill/content-creator/scripts/seo_optimizer.py "$CONTENT_FILE" "$PRIMARY_KEYWORD"
echo "Reviewing content frameworks..."
cat ../../marketing-skill/content-creator/references/content_frameworks.md
echo ""
echo "✅ Analysis complete! Review feedback above and revise content."
echo "Review complete. Compare $CONTENT_FILE against the guidelines above."
```
**Usage:** `./content-feedback.sh blog-post.md "target keyword"`
**Usage:** `./content-review.sh blog-post.md`
### Example 2: JSON Output for CMS Integration
### Example 2: Platform-Specific Content Adaptation
```bash
# Generate JSON reports for automated publishing pipeline
python ../../marketing-skill/content-creator/scripts/brand_voice_analyzer.py article.md json > voice-report.json
python ../../marketing-skill/content-creator/scripts/seo_optimizer.py article.md "keyword" --json > seo-report.json
# Review platform guidelines before adapting content
cat ../../marketing-skill/content-creator/references/social_media_optimization.md
# Use in CI/CD pipeline to block publishing if quality thresholds not met
SEO_SCORE=$(jq '.overall_score' seo-report.json)
if [ "$SEO_SCORE" -lt 70 ]; then
echo "❌ SEO score too low: $SEO_SCORE. Minimum required: 70"
exit 1
fi
# Key platform limits to follow:
# - LinkedIn: 1,300 chars, professional tone, 3-5 hashtags
# - Twitter/X: 280 chars per tweet, engaging hook
# - Instagram: Visual-first, caption with line breaks
```
### Example 3: Weekly Content Performance Review
### Example 3: Campaign Content Planning
```bash
# Analyze all content published this week
WEEK_START="2025-11-01"
find blog/ -name "*.md" -newermt "$WEEK_START" | while read file; do
echo "=== Weekly Review: $file ==="
python ../../marketing-skill/content-creator/scripts/brand_voice_analyzer.py "$file"
done
# Set up content calendar from template
cp ../../marketing-skill/content-creator/assets/content_calendar_template.md campaign-calendar.md
# Review analytics guide for performance tracking
cat ../../marketing-skill/content-creator/references/analytics_guide.md
```
## Success Metrics
@@ -259,8 +229,8 @@ done
## Related Agents
- [cs-demand-gen-specialist](cs-demand-gen-specialist.md) - Demand generation and acquisition campaigns
- [cs-product-marketing](../product/cs-product-marketing.md) - Product positioning and messaging (planned)
- [cs-social-media-manager](cs-social-media-manager.md) - Social media management and scheduling (planned)
- cs-product-marketing - Product positioning and messaging (planned)
- cs-social-media-manager - Social media management and scheduling (planned)
## References

73
agents/marketing/cs-demand-gen-specialist.md
View File

@@ -34,30 +34,29 @@ The cs-demand-gen-specialist agent bridges the gap between marketing strategy an
### Knowledge Bases
1. **Acquisition Frameworks**
- **Location:** `../../marketing-skill/marketing-demand-acquisition/references/acquisition_frameworks.md`
- **Content:** Lead generation strategies, conversion optimization frameworks, acquisition funnel templates
- **Use Case:** Campaign planning, strategy development, funnel design
1. **Attribution Guide**
- **Location:** `../../marketing-skill/marketing-demand-acquisition/references/attribution-guide.md`
- **Content:** Marketing attribution models, channel attribution, ROI measurement frameworks
- **Use Case:** Campaign attribution, channel performance analysis, budget justification
2. **Channel Best Practices**
- **Location:** `../../marketing-skill/marketing-demand-acquisition/references/channel_best_practices.md`
- **Content:** Paid search (Google Ads), paid social (LinkedIn, Facebook), content marketing, email campaigns
- **Use Case:** Channel-specific optimization, budget allocation, A/B testing
2. **Campaign Templates**
- **Location:** `../../marketing-skill/marketing-demand-acquisition/references/campaign-templates.md`
- **Content:** Reusable campaign structures, launch checklists, multi-channel campaign blueprints
- **Use Case:** Campaign planning, rapid campaign setup, standardized launch processes
3. **Conversion Optimization**
- **Location:** `../../marketing-skill/marketing-demand-acquisition/references/conversion_optimization.md`
- **Content:** Landing page best practices, CTA optimization, form optimization, lead magnets
- **Use Case:** Conversion rate improvement, landing page design, lead capture optimization
3. **HubSpot Workflows**
- **Location:** `../../marketing-skill/marketing-demand-acquisition/references/hubspot-workflows.md`
- **Content:** HubSpot automation workflows, lead nurturing sequences, CRM integration patterns
- **Use Case:** Marketing automation, lead scoring, nurture campaign setup
4. **International Playbooks**
- **Location:** `../../marketing-skill/marketing-demand-acquisition/references/international-playbooks.md`
- **Content:** International market expansion strategies, localization best practices, regional channel optimization
- **Use Case:** Global campaign planning, market entry strategy, cross-border demand generation
### Templates
1. **Campaign Planning Template**
- **Location:** `../../marketing-skill/marketing-demand-acquisition/assets/campaign-plan.md`
- **Use Case:** Multi-channel campaign planning, goal setting
2. **Funnel Analysis Template**
- **Location:** `../../marketing-skill/marketing-demand-acquisition/assets/funnel-analysis.md`
- **Use Case:** Conversion funnel mapping, bottleneck identification
No asset templates currently available — use campaign-templates.md reference for campaign structure guidance.
## Workflows
@@ -67,21 +66,21 @@ The cs-demand-gen-specialist agent bridges the gap between marketing strategy an
**Steps:**
1. **Define Campaign Goals** - Set targets for leads, MQLs, SQLs, conversion rates
2. **Reference Acquisition Frameworks** - Review proven lead generation strategies
2. **Reference Campaign Templates** - Review proven campaign structures and launch checklists
```bash
cat ../../marketing-skill/marketing-demand-acquisition/references/acquisition_frameworks.md
cat ../../marketing-skill/marketing-demand-acquisition/references/campaign-templates.md
```
3. **Select Channels** - Choose optimal mix based on target audience and budget
3. **Select Channels** - Choose optimal mix based on target audience, budget, and attribution models
```bash
cat ../../marketing-skill/marketing-demand-acquisition/references/channel_best_practices.md
cat ../../marketing-skill/marketing-demand-acquisition/references/attribution-guide.md
```
4. **Create Campaign Plan** - Use template to structure multi-channel approach
4. **Set Up Automation** - Configure HubSpot workflows for lead nurturing
```bash
cp ../../marketing-skill/marketing-demand-acquisition/assets/campaign-plan.md q4-demand-gen-campaign.md
cat ../../marketing-skill/marketing-demand-acquisition/references/hubspot-workflows.md
```
5. **Design Landing Pages** - Reference conversion optimization best practices
5. **Plan International Reach** - Reference international playbooks if targeting multiple markets
```bash
cat ../../marketing-skill/marketing-demand-acquisition/references/conversion_optimization.md
cat ../../marketing-skill/marketing-demand-acquisition/references/international-playbooks.md
```
6. **Launch and Monitor** - Deploy campaigns, track metrics, collect data
@@ -99,18 +98,18 @@ The cs-demand-gen-specialist agent bridges the gap between marketing strategy an
```bash
python ../../marketing-skill/marketing-demand-acquisition/scripts/calculate_cac.py campaign-spend.csv conversions.csv
```
3. **Map Conversion Funnel** - Use template to visualize drop-off points
3. **Map Conversion Funnel** - Visualize drop-off points using campaign templates as structure guide
```bash
cp ../../marketing-skill/marketing-demand-acquisition/assets/funnel-analysis.md current-funnel-analysis.md
cat ../../marketing-skill/marketing-demand-acquisition/references/campaign-templates.md
```
4. **Identify Bottlenecks** - Analyze conversion rates at each funnel stage:
- Awareness → Interest (CTR)
- Interest → Consideration (landing page conversion)
- Consideration → Intent (form completion)
- Intent → Purchase/MQL (qualification rate)
5. **Reference Optimization Guides** - Review best practices for problem areas
5. **Reference Attribution Guide** - Review attribution models to identify problem areas
```bash
cat ../../marketing-skill/marketing-demand-acquisition/references/conversion_optimization.md
cat ../../marketing-skill/marketing-demand-acquisition/references/attribution-guide.md
```
6. **Implement A/B Tests** - Test hypotheses for improvement
7. **Re-calculate CAC Post-Optimization** - Measure cost efficiency improvements
@@ -145,9 +144,9 @@ cat cac-report.txt
```bash
python ../../marketing-skill/marketing-demand-acquisition/scripts/calculate_cac.py channel-spend.csv channel-conversions.csv
```
3. **Reference Channel Best Practices** - Understand benchmarks for each channel
3. **Reference Attribution Guide** - Understand attribution models and benchmarks for each channel
```bash
cat ../../marketing-skill/marketing-demand-acquisition/references/channel_best_practices.md
cat ../../marketing-skill/marketing-demand-acquisition/references/attribution-guide.md
```
4. **Calculate Key Metrics:**
- CAC (Customer Acquisition Cost) by channel
@@ -167,9 +166,9 @@ cat cac-report.txt
**Steps:**
1. **Define Lead Magnet** - Choose format: ebook, webinar, template, assessment, free trial
2. **Reference Conversion Best Practices** - Review lead capture optimization strategies
2. **Reference Campaign Templates** - Review lead capture and campaign structure best practices
```bash
cat ../../marketing-skill/marketing-demand-acquisition/references/conversion_optimization.md
cat ../../marketing-skill/marketing-demand-acquisition/references/campaign-templates.md
```
3. **Create Landing Page** - Design high-converting landing page with:
- Clear value proposition
@@ -273,8 +272,8 @@ fi
## Related Agents
- [cs-content-creator](cs-content-creator.md) - Content creation for demand gen campaigns
- [cs-product-marketing](../product/cs-product-marketing.md) - Product positioning and messaging (planned)
- [cs-growth-marketer](cs-growth-marketer.md) - Growth hacking and viral acquisition (planned)
- cs-product-marketing - Product positioning and messaging (planned)
- cs-growth-marketer - Growth hacking and viral acquisition (planned)
## References

416
agents/product/cs-agile-product-owner.md Normal file
View File

@@ -0,0 +1,416 @@
---
name: cs-agile-product-owner
description: Agile product owner agent for epic breakdown, sprint planning, backlog refinement, and INVEST-compliant user story generation
skills: product-team/agile-product-owner, product-team/product-manager-toolkit
domain: product
model: sonnet
tools: [Read, Write, Bash, Grep, Glob]
---
# Agile Product Owner Agent
## Purpose
The cs-agile-product-owner agent is a specialized agile product ownership agent focused on backlog management, sprint planning, user story creation, and epic decomposition. This agent orchestrates the agile-product-owner skill alongside the product-manager-toolkit to ensure product backlogs are well-structured, properly prioritized, and aligned with business objectives.
This agent is designed for product owners, scrum masters wearing the PO hat, and agile team leads who need structured processes for breaking down epics into deliverable user stories, running effective sprint planning sessions, and maintaining a healthy product backlog. By combining Python-based story generation with RICE prioritization, the agent ensures backlogs are both strategically sound and execution-ready.
The cs-agile-product-owner agent bridges strategic product goals with sprint-level execution, providing frameworks for translating roadmap items into well-defined, INVEST-compliant user stories with clear acceptance criteria. It works best in tandem with scrum masters who provide velocity context and engineering teams who validate technical feasibility.
## Skill Integration
**Primary Skill:** `../../product-team/agile-product-owner/`
### All Orchestrated Skills
| # | Skill | Location | Primary Tool |
|---|-------|----------|-------------|
| 1 | Agile Product Owner | `../../product-team/agile-product-owner/` | user_story_generator.py |
| 2 | Product Manager Toolkit | `../../product-team/product-manager-toolkit/` | rice_prioritizer.py |
### Python Tools
1. **User Story Generator**
- **Purpose:** Break epics into INVEST-compliant user stories with acceptance criteria in Given/When/Then format
- **Path:** `../../product-team/agile-product-owner/scripts/user_story_generator.py`
- **Usage:** `python ../../product-team/agile-product-owner/scripts/user_story_generator.py epic.yaml`
- **Features:** Epic decomposition, acceptance criteria generation, story point estimation, dependency mapping
- **Use Cases:** Sprint planning, backlog refinement, story writing workshops
2. **RICE Prioritizer**
- **Purpose:** RICE framework for backlog prioritization with portfolio analysis
- **Path:** `../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py`
- **Usage:** `python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py backlog.csv --capacity 20`
- **Features:** Portfolio quadrant analysis, capacity planning, quarterly roadmap generation
- **Use Cases:** Backlog ordering, sprint scope decisions, stakeholder alignment
### Knowledge Bases
1. **Sprint Planning Guide**
- **Location:** `../../product-team/agile-product-owner/references/sprint-planning-guide.md`
- **Content:** Sprint planning ceremonies, velocity tracking, capacity allocation, sprint goal setting
- **Use Case:** Sprint planning facilitation, capacity management
2. **User Story Templates**
- **Location:** `../../product-team/agile-product-owner/references/user-story-templates.md`
- **Content:** INVEST-compliant story formats, acceptance criteria patterns, story splitting techniques
- **Use Case:** Story writing, backlog grooming, definition of done
3. **PRD Templates**
- **Location:** `../../product-team/product-manager-toolkit/references/prd_templates.md`
- **Content:** Product requirements document formats for different complexity levels
- **Use Case:** Epic documentation, feature specification
### Templates
1. **Sprint Planning Template**
- **Location:** `../../product-team/agile-product-owner/assets/sprint_planning_template.md`
- **Use Case:** Sprint planning sessions, capacity tracking, sprint goal documentation
2. **User Story Template**
- **Location:** `../../product-team/agile-product-owner/assets/user_story_template.md`
- **Use Case:** Consistent story format, acceptance criteria structure
3. **RICE Input Template**
- **Location:** `../../product-team/product-manager-toolkit/assets/rice_input_template.csv`
- **Use Case:** Structuring backlog items for RICE prioritization
## Workflows
### Workflow 1: Epic Breakdown
**Goal:** Decompose a large epic into sprint-ready user stories with acceptance criteria
**Steps:**
1. **Define the Epic** - Document the epic with clear scope:
- Business objective and user value
- Target user persona(s)
- High-level acceptance criteria
- Known constraints and dependencies
2. **Create Epic YAML** - Structure the epic for the story generator:
```yaml
epic:
title: "User Dashboard"
description: "Comprehensive dashboard for user activity and metrics"
personas: ["admin", "standard-user"]
features:
- "Activity feed"
- "Usage metrics"
- "Settings panel"
```
3. **Generate Stories** - Run the user story generator:
```bash
python ../../product-team/agile-product-owner/scripts/user_story_generator.py epic.yaml
```
4. **Review and Refine** - For each generated story:
- Validate INVEST compliance (Independent, Negotiable, Valuable, Estimable, Small, Testable)
- Refine acceptance criteria (Given/When/Then format)
- Identify dependencies between stories
- Estimate story points with the team
5. **Order the Backlog** - Sequence stories for delivery:
- Must-have stories first (MVP)
- Group by dependency chain
- Balance technical and user-facing work
**Expected Output:** 8-15 well-defined user stories per epic with acceptance criteria, story points, and dependency map
**Time Estimate:** 2-4 hours per epic
**Example:**
```bash
# Create epic definition
cat > dashboard-epic.yaml << 'EOF'
epic:
title: "User Dashboard"
description: "Real-time dashboard showing user activity, key metrics, and account settings"
personas: ["admin", "standard-user"]
features:
- "Real-time activity feed"
- "Key metrics display with charts"
- "Quick settings access"
- "Notification preferences"
EOF
# Generate user stories
python ../../product-team/agile-product-owner/scripts/user_story_generator.py dashboard-epic.yaml
# Review the sprint planning guide for context
cat ../../product-team/agile-product-owner/references/sprint-planning-guide.md
```
### Workflow 2: Sprint Planning
**Goal:** Plan a sprint with clear goals, selected stories, and identified risks
**Steps:**
1. **Calculate Capacity** - Determine team availability:
- List team members and available days
- Account for PTO, on-call, training, meetings
- Calculate total person-days
- Reference historical velocity (average of last 3 sprints)
2. **Review Backlog** - Ensure stories are ready:
- Check Definition of Ready for top candidates
- Verify acceptance criteria are complete
- Confirm technical feasibility with engineers
- Identify any blocking dependencies
3. **Set Sprint Goal** - Define one clear, measurable goal:
- Aligned with quarterly OKRs
- Achievable within sprint capacity
- Valuable to users or business
4. **Select Stories** - Pull from prioritized backlog:
```bash
# Prioritize candidates if not already ordered
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py sprint-candidates.csv --capacity 12
```
5. **Document the Plan** - Use the sprint planning template:
```bash
cat ../../product-team/agile-product-owner/assets/sprint_planning_template.md
```
6. **Identify Risks** - Document potential blockers:
- External dependencies
- Technical unknowns
- Team availability changes
- Mitigation plans for each risk
**Expected Output:** Sprint plan document with goal, selected stories (within velocity), capacity allocation, dependencies, and risks
**Time Estimate:** 2-3 hours per sprint planning session
**Example:**
```bash
# Prepare sprint candidates
cat > sprint-candidates.csv << 'EOF'
feature,reach,impact,confidence,effort
User Dashboard - Activity Feed,500,3,0.8,3
User Dashboard - Metrics Charts,500,2,0.9,5
Notification Preferences,300,1,1.0,2
Password Reset Flow Fix,1000,2,1.0,1
EOF
# Run prioritization
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py sprint-candidates.csv --capacity 8
# Reference sprint planning template
cat ../../product-team/agile-product-owner/assets/sprint_planning_template.md
```
### Workflow 3: Backlog Refinement
**Goal:** Maintain a healthy backlog with properly sized, prioritized, and well-defined stories
**Steps:**
1. **Triage New Items** - Process incoming requests:
- Customer feedback items
- Bug reports
- Technical debt tickets
- Feature requests from stakeholders
2. **Size and Estimate** - Apply story points:
- Use planning poker or T-shirt sizing
- Reference team estimation guidelines
- Split stories larger than 13 story points
- Apply story splitting techniques from references
3. **Prioritize with RICE** - Score backlog items:
```bash
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py backlog.csv
```
4. **Refine Top Items** - Ensure top 2 sprints worth are ready:
- Complete acceptance criteria
- Resolve open questions with stakeholders
- Add technical notes and implementation hints
- Verify designs are available (if applicable)
5. **Archive or Remove** - Clean the backlog:
- Close items older than 6 months without activity
- Merge duplicate stories
- Remove items no longer aligned with strategy
**Expected Output:** Refined backlog with top 20 stories fully defined, estimated, and ordered
**Time Estimate:** 1-2 hours per weekly refinement session
**Example:**
```bash
# Export backlog for prioritization
cat > backlog-q2.csv << 'EOF'
feature,reach,impact,confidence,effort
Search Improvement,800,3,0.8,5
Mobile Responsive Tables,600,2,0.7,3
API Rate Limiting,400,2,0.9,2
Onboarding Wizard,1000,3,0.6,8
Export to PDF,200,1,1.0,1
Dark Mode,300,1,0.8,3
EOF
# Run full prioritization with capacity
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py backlog-q2.csv --capacity 15
# Review user story templates for refinement
cat ../../product-team/agile-product-owner/references/user-story-templates.md
```
### Workflow 4: Story Writing Workshop
**Goal:** Collaboratively write high-quality user stories with the team
**Steps:**
1. **Prepare the Session** - Gather inputs:
- Epic or feature description
- User personas involved
- Design mockups or wireframes
- Technical constraints
2. **Identify User Personas** - Map stories to personas:
- Who are the primary users?
- What are their goals?
- What are their constraints?
3. **Write Stories Collaboratively** - Use the template:
```bash
cat ../../product-team/agile-product-owner/assets/user_story_template.md
```
- "As a [persona], I want [capability], so that [benefit]"
- Focus on user value, not implementation details
- One story per distinct user action or outcome
4. **Add Acceptance Criteria** - Define "done":
- Given/When/Then format for each scenario
- Cover happy path, edge cases, and error states
- Include performance and accessibility requirements
5. **Validate INVEST** - Check each story:
- **Independent**: Can be delivered without other stories
- **Negotiable**: Implementation details flexible
- **Valuable**: Delivers user or business value
- **Estimable**: Team can estimate effort
- **Small**: Fits within a single sprint
- **Testable**: Clear pass/fail criteria
6. **Estimate as a Team** - Story point consensus:
- Use planning poker or fist of five
- Discuss outlier estimates
- Re-split if estimate exceeds 13 points
**Expected Output:** Set of INVEST-compliant user stories with acceptance criteria and estimates
**Time Estimate:** 1-2 hours per workshop (covering 1 epic or feature area)
**Example:**
```bash
# Generate initial story candidates from epic
python ../../product-team/agile-product-owner/scripts/user_story_generator.py feature-epic.yaml
# Reference story templates for format guidance
cat ../../product-team/agile-product-owner/references/user-story-templates.md
# Reference sprint planning guide for estimation practices
cat ../../product-team/agile-product-owner/references/sprint-planning-guide.md
```
## Integration Examples
### Example 1: End-to-End Sprint Cycle
```bash
#!/bin/bash
# sprint-cycle.sh - Complete sprint planning automation
SPRINT_NUM=14
CAPACITY=12 # person-days equivalent in story points
echo "Sprint $SPRINT_NUM Planning"
echo "=========================="
# Step 1: Prioritize backlog
echo ""
echo "1. Backlog Prioritization:"
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py backlog.csv --capacity $CAPACITY
# Step 2: Generate stories for top epic
echo ""
echo "2. Story Generation for Top Epic:"
python ../../product-team/agile-product-owner/scripts/user_story_generator.py top-epic.yaml
# Step 3: Reference planning template
echo ""
echo "3. Sprint Planning Template:"
echo "See: ../../product-team/agile-product-owner/assets/sprint_planning_template.md"
```
### Example 2: Backlog Health Check
```bash
#!/bin/bash
# backlog-health.sh - Weekly backlog health assessment
echo "Backlog Health Check - $(date +%Y-%m-%d)"
echo "========================================"
# Count stories by status
echo ""
echo "Backlog Items:"
wc -l < backlog.csv
echo "items in backlog"
# Run prioritization
echo ""
echo "Current Priorities:"
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py backlog.csv --capacity 20
# Check story templates
echo ""
echo "Story Template Reference:"
echo "Location: ../../product-team/agile-product-owner/references/user-story-templates.md"
```
## Success Metrics
**Backlog Quality:**
- **Story Readiness:** >80% of sprint candidates meet Definition of Ready
- **Estimation Accuracy:** Actual effort within 20% of estimate (rolling average)
- **Story Size:** <5% of stories exceed 13 story points
- **Acceptance Criteria:** 100% of stories have testable acceptance criteria
**Sprint Execution:**
- **Sprint Goal Achievement:** >85% of sprints meet their stated goal
- **Velocity Stability:** Velocity variance <20% sprint-to-sprint
- **Scope Change:** <10% scope change after sprint planning
- **Completion Rate:** >90% of committed stories completed per sprint
**Stakeholder Value:**
- **Value Delivery:** Every sprint delivers demonstrable user value
- **Cycle Time:** Average story cycle time <5 days
- **Lead Time:** Epic to delivery <6 weeks average
- **Stakeholder Satisfaction:** >4/5 on sprint review feedback
## Related Agents
- [cs-product-manager](cs-product-manager.md) - Full product management lifecycle (RICE, interviews, PRDs)
- [cs-product-strategist](cs-product-strategist.md) - OKR cascade and strategic planning for roadmap alignment
- [cs-ux-researcher](cs-ux-researcher.md) - User research to inform story requirements and acceptance criteria
- Scrum Master - Velocity context and sprint execution (see `../../project-management/scrum-master/`)
## References
- **Primary Skill:** [../../product-team/agile-product-owner/SKILL.md](../../product-team/agile-product-owner/SKILL.md)
- **RICE Framework:** [../../product-team/product-manager-toolkit/SKILL.md](../../product-team/product-manager-toolkit/SKILL.md)
- **Product Domain Guide:** [../../product-team/CLAUDE.md](../../product-team/CLAUDE.md)
- **Agent Development Guide:** [../CLAUDE.md](../CLAUDE.md)
- **Scrum Master Skill:** [../../project-management/scrum-master/SKILL.md](../../project-management/scrum-master/SKILL.md)
---
**Last Updated:** March 9, 2026
**Status:** Production Ready
**Version:** 1.0

305
agents/product/cs-product-manager.md
View File

@@ -1,7 +1,7 @@
---
name: cs-product-manager
description: Product management agent for feature prioritization, customer discovery, PRD development, and roadmap planning using RICE framework
skills: product-team/product-manager-toolkit
skills: product-team/product-manager-toolkit, product-team/agile-product-owner, product-team/product-strategist, product-team/ux-researcher-designer, product-team/ui-design-system, product-team/competitive-teardown, product-team/landing-page-generator, product-team/saas-scaffolder
domain: product
model: sonnet
tools: [Read, Write, Bash, Grep, Glob]
@@ -11,7 +11,7 @@ tools: [Read, Write, Bash, Grep, Glob]
## Purpose
The cs-product-manager agent is a specialized product management agent focused on feature prioritization, customer discovery, requirements documentation, and data-driven roadmap planning. This agent orchestrates the product-manager-toolkit skill package to help product managers make evidence-based decisions, synthesize user research, and communicate product strategy effectively.
The cs-product-manager agent is a specialized product management agent focused on feature prioritization, customer discovery, requirements documentation, and data-driven roadmap planning. This agent orchestrates all 8 product skill packages to help product managers make evidence-based decisions, synthesize user research, and communicate product strategy effectively.
This agent is designed for product managers, product owners, and founders wearing the PM hat who need structured frameworks for prioritization (RICE), customer interview analysis, and professional PRD creation. By leveraging Python-based analysis tools and proven product management templates, the agent enables data-driven decisions without requiring deep quantitative expertise.
@@ -19,7 +19,20 @@ The cs-product-manager agent bridges the gap between customer insights and produ
## Skill Integration
**Skill Location:** `../../product-team/product-manager-toolkit/`
**Primary Skill:** `../../product-team/product-manager-toolkit/`
### All Orchestrated Skills
| # | Skill | Location | Primary Tool |
|---|-------|----------|-------------|
| 1 | Product Manager Toolkit | `../../product-team/product-manager-toolkit/` | rice_prioritizer.py, customer_interview_analyzer.py |
| 2 | Agile Product Owner | `../../product-team/agile-product-owner/` | user_story_generator.py |
| 3 | Product Strategist | `../../product-team/product-strategist/` | okr_cascade_generator.py |
| 4 | UX Researcher & Designer | `../../product-team/ux-researcher-designer/` | persona_generator.py |
| 5 | UI Design System | `../../product-team/ui-design-system/` | design_token_generator.py |
| 6 | Competitive Teardown | `../../product-team/competitive-teardown/` | competitive_matrix_builder.py |
| 7 | Landing Page Generator | `../../product-team/landing-page-generator/` | landing_page_scaffolder.py |
| 8 | SaaS Scaffolder | `../../product-team/saas-scaffolder/` | project_bootstrapper.py |
### Python Tools
@@ -38,6 +51,48 @@ The cs-product-manager agent bridges the gap between customer insights and produ
- **Features:** Pain point extraction with severity, feature request identification, jobs-to-be-done patterns, sentiment analysis, theme extraction
- **Use Cases:** User research synthesis, discovery validation, problem prioritization, insight generation
3. **User Story Generator**
- **Purpose:** Break epics into INVEST-compliant user stories with acceptance criteria
- **Path:** `../../product-team/agile-product-owner/scripts/user_story_generator.py`
- **Usage:** `python ../../product-team/agile-product-owner/scripts/user_story_generator.py epic.yaml`
- **Use Cases:** Sprint planning, backlog refinement, story decomposition
4. **OKR Cascade Generator**
- **Purpose:** Generate cascaded OKRs from company objectives to team-level key results
- **Path:** `../../product-team/product-strategist/scripts/okr_cascade_generator.py`
- **Usage:** `python ../../product-team/product-strategist/scripts/okr_cascade_generator.py growth`
- **Use Cases:** Quarterly planning, strategic alignment, goal setting
5. **Persona Generator**
- **Purpose:** Create data-driven user personas from research inputs
- **Path:** `../../product-team/ux-researcher-designer/scripts/persona_generator.py`
- **Usage:** `python ../../product-team/ux-researcher-designer/scripts/persona_generator.py research-data.json`
- **Use Cases:** User research synthesis, persona development, journey mapping
6. **Design Token Generator**
- **Purpose:** Generate design tokens for consistent UI implementation
- **Path:** `../../product-team/ui-design-system/scripts/design_token_generator.py`
- **Usage:** `python ../../product-team/ui-design-system/scripts/design_token_generator.py theme.json`
- **Use Cases:** Design system creation, developer handoff, theming
7. **Competitive Matrix Builder**
- **Purpose:** Build competitive analysis matrices and feature comparison grids
- **Path:** `../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py`
- **Usage:** `python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py competitors.csv`
- **Use Cases:** Competitive intelligence, market positioning, feature gap analysis
8. **Landing Page Scaffolder**
- **Purpose:** Generate conversion-optimized landing page scaffolds
- **Path:** `../../product-team/landing-page-generator/scripts/landing_page_scaffolder.py`
- **Usage:** `python ../../product-team/landing-page-generator/scripts/landing_page_scaffolder.py config.yaml`
- **Use Cases:** Product launches, A/B testing, GTM campaigns
9. **Project Bootstrapper**
- **Purpose:** Scaffold SaaS project structures with boilerplate and configurations
- **Path:** `../../product-team/saas-scaffolder/scripts/project_bootstrapper.py`
- **Usage:** `python ../../product-team/saas-scaffolder/scripts/project_bootstrapper.py --stack nextjs --name my-saas`
- **Use Cases:** MVP scaffolding, project kickoff, SaaS prototype creation
### Knowledge Bases
1. **PRD Templates**
@@ -45,6 +100,66 @@ The cs-product-manager agent bridges the gap between customer insights and produ
- **Content:** Multiple PRD formats (Standard PRD, One-Page PRD, Feature Brief, Agile Epic), structure guidelines, best practices
- **Use Case:** Requirements documentation, stakeholder communication, engineering handoff
2. **Sprint Planning Guide**
- **Location:** `../../product-team/agile-product-owner/references/sprint-planning-guide.md`
- **Content:** Sprint planning ceremonies, velocity tracking, capacity allocation
- **Use Case:** Sprint execution, backlog refinement, agile ceremonies
3. **User Story Templates**
- **Location:** `../../product-team/agile-product-owner/references/user-story-templates.md`
- **Content:** INVEST-compliant story formats, acceptance criteria patterns, story splitting techniques
- **Use Case:** Story writing, backlog grooming, definition of done
4. **OKR Framework**
- **Location:** `../../product-team/product-strategist/references/okr_framework.md`
- **Content:** OKR methodology, cascade patterns, scoring guidelines
- **Use Case:** Quarterly planning, strategic alignment, goal tracking
5. **Strategy Types**
- **Location:** `../../product-team/product-strategist/references/strategy_types.md`
- **Content:** Product strategy frameworks, competitive positioning, growth strategies
- **Use Case:** Strategic planning, market analysis, product vision
6. **Persona Methodology**
- **Location:** `../../product-team/ux-researcher-designer/references/persona-methodology.md`
- **Content:** Research-backed persona creation methodology, data collection, validation
- **Use Case:** Persona development, user segmentation, research planning
7. **Example Personas**
- **Location:** `../../product-team/ux-researcher-designer/references/example-personas.md`
- **Content:** Sample persona documents with demographics, goals, pain points, behaviors
- **Use Case:** Persona templates, research documentation
8. **Journey Mapping Guide**
- **Location:** `../../product-team/ux-researcher-designer/references/journey-mapping-guide.md`
- **Content:** Customer journey mapping methodology, touchpoint analysis, emotion mapping
- **Use Case:** Experience design, touchpoint optimization, service design
9. **Usability Testing Frameworks**
- **Location:** `../../product-team/ux-researcher-designer/references/usability-testing-frameworks.md`
- **Content:** Usability test planning, task design, analysis methods
- **Use Case:** Usability studies, prototype validation, UX evaluation
10. **Component Architecture**
- **Location:** `../../product-team/ui-design-system/references/component-architecture.md`
- **Content:** Component hierarchy, atomic design patterns, composition strategies
- **Use Case:** Design system architecture, component libraries
11. **Developer Handoff**
- **Location:** `../../product-team/ui-design-system/references/developer-handoff.md`
- **Content:** Design-to-dev handoff process, specification formats, asset delivery
- **Use Case:** Engineering collaboration, implementation specs
12. **Responsive Calculations**
- **Location:** `../../product-team/ui-design-system/references/responsive-calculations.md`
- **Content:** Responsive design formulas, breakpoint strategies, fluid typography
- **Use Case:** Responsive implementation, cross-device design
13. **Token Generation**
- **Location:** `../../product-team/ui-design-system/references/token-generation.md`
- **Content:** Design token standards, naming conventions, platform-specific output
- **Use Case:** Design system tokens, theming, multi-platform consistency
## Workflows
### Workflow 1: Feature Prioritization & Roadmap Planning
@@ -229,32 +344,37 @@ cat roadmap.txt
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py q4-candidates.csv --capacity 18
```
3. **Define Product OKRs** - Set ambitious but achievable goals:
3. **Generate OKR Cascade** - Use the OKR cascade generator to create aligned objectives
```bash
python ../../product-team/product-strategist/scripts/okr_cascade_generator.py growth
```
4. **Define Product OKRs** - Set ambitious but achievable goals:
- **Objective**: Qualitative, inspirational (e.g., "Become the easiest platform to onboard")
- **Key Results**: Quantitative, measurable (e.g., "Reduce onboarding time from 30min to 10min")
- **Initiatives**: Features that drive key results
- **Metrics**: How we'll track progress weekly
4. **Capacity Planning** - Allocate team resources:
5. **Capacity Planning** - Allocate team resources:
- Engineering capacity: Person-months available
- Design capacity: UI/UX support needed
- Buffer allocation: 20% for bugs, support, unknowns
- Dependency tracking: External blockers
5. **Risk Assessment** - Identify what could go wrong:
6. **Risk Assessment** - Identify what could go wrong:
- Technical risks (scalability, performance)
- Market risks (competition, demand)
- Execution risks (dependencies, team velocity)
- Mitigation plans for each risk
6. **Stakeholder Review** - Present quarterly plan:
7. **Stakeholder Review** - Present quarterly plan:
- OKRs with supporting initiatives
- RICE-justified priorities
- Resource allocation and capacity
- Risks and mitigation strategies
- Success metrics and tracking cadence
7. **Track Progress** - Weekly OKR check-ins:
8. **Track Progress** - Weekly OKR check-ins:
- Update key result progress
- Adjust priorities if needed
- Communicate blockers early
@@ -263,6 +383,164 @@ cat roadmap.txt
**Time Estimate:** 1 week for quarterly planning (last week of previous quarter)
### Workflow 5: User Research to Personas
**Goal:** Generate data-driven personas from user research to align the team on target users
**Steps:**
1. **Collect Research Data** - Aggregate findings from interviews, surveys, and analytics:
- Interview transcripts and notes
- Survey responses and demographics
- Behavioral analytics (usage patterns, feature adoption)
- Support ticket themes
2. **Review Persona Methodology** - Understand research-backed persona creation
```bash
cat ../../product-team/ux-researcher-designer/references/persona-methodology.md
```
3. **Generate Personas** - Create structured personas from research inputs
```bash
python ../../product-team/ux-researcher-designer/scripts/persona_generator.py research-data.json
```
4. **Map Customer Journeys** - Reference journey mapping guide for each persona
```bash
cat ../../product-team/ux-researcher-designer/references/journey-mapping-guide.md
```
5. **Review Example Personas** - Compare output against proven persona formats
```bash
cat ../../product-team/ux-researcher-designer/references/example-personas.md
```
6. **Validate and Iterate** - Share personas with stakeholders:
- Cross-reference with interview insights from customer_interview_analyzer.py
- Verify demographics and behaviors match real user data
- Update personas quarterly as new research emerges
**Expected Output:** 3-5 data-driven user personas with demographics, goals, pain points, behaviors, and mapped customer journeys
**Time Estimate:** 1-2 weeks (research collection + persona generation + validation)
**Example:**
```bash
# Complete persona generation workflow
python ../../product-team/ux-researcher-designer/scripts/persona_generator.py user-research-q4.json > personas.md
# Cross-reference with interview analysis
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interviews-batch.txt > insights.txt
# Review journey mapping methodology
cat ../../product-team/ux-researcher-designer/references/journey-mapping-guide.md
```
### Workflow 6: Sprint Story Generation
**Goal:** Break epics into INVEST-compliant user stories ready for sprint planning
**Steps:**
1. **Define the Epic** - Structure epic with clear scope and acceptance criteria:
- Business objective and user value
- Functional requirements
- Non-functional requirements (performance, security)
- Dependencies and constraints
2. **Review Story Templates** - Load INVEST-compliant story patterns
```bash
cat ../../product-team/agile-product-owner/references/user-story-templates.md
```
3. **Generate User Stories** - Break the epic into sprint-sized stories
```bash
python ../../product-team/agile-product-owner/scripts/user_story_generator.py epic.yaml
```
4. **Review Sprint Planning Guide** - Ensure stories fit sprint capacity
```bash
cat ../../product-team/agile-product-owner/references/sprint-planning-guide.md
```
5. **Refine and Estimate** - Groom generated stories:
- Verify each story meets INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable)
- Add story points based on team velocity
- Identify dependencies between stories
- Write acceptance criteria in Given/When/Then format
6. **Prioritize for Sprint** - Use RICE scores to sequence stories
```bash
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py sprint-stories.csv --capacity 8
```
**Expected Output:** Sprint-ready backlog of INVEST-compliant user stories with acceptance criteria, story points, and priority order
**Time Estimate:** 2-4 hours per epic decomposition
**Example:**
```bash
# End-to-end story generation workflow
python ../../product-team/agile-product-owner/scripts/user_story_generator.py onboarding-epic.yaml > stories.md
# Prioritize stories for sprint
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py stories.csv --capacity 8 > sprint-plan.txt
# Review sprint planning best practices
cat ../../product-team/agile-product-owner/references/sprint-planning-guide.md
```
### Workflow 7: Competitive Intelligence
**Goal:** Build competitive analysis matrices to identify market positioning and feature gaps
**Steps:**
1. **Identify Competitors** - Map the competitive landscape:
- Direct competitors (same category, same audience)
- Indirect competitors (different category, same job-to-be-done)
- Emerging threats (startups, adjacent products)
2. **Gather Competitive Data** - Structure competitor information in CSV:
```csv
competitor,feature_1,feature_2,feature_3,pricing,market_share
Competitor A,yes,partial,no,$49/mo,35%
Competitor B,yes,yes,yes,$99/mo,25%
Our Product,yes,no,partial,$39/mo,15%
```
3. **Build Competitive Matrix** - Generate visual comparison
```bash
python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py competitors.csv
```
4. **Analyze Gaps** - Identify strategic opportunities:
- Feature parity gaps (what competitors have that we lack)
- Differentiation opportunities (where we can lead)
- Pricing positioning (value vs premium vs budget)
- Underserved segments (unmet user needs)
5. **Feed Into Prioritization** - Use gaps to inform roadmap
```bash
# Add competitive gap features to RICE analysis
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py competitive-features.csv --capacity 20
```
6. **Track Over Time** - Update competitive matrix quarterly:
- Monitor competitor launches and pricing changes
- Re-run matrix builder with updated data
- Adjust positioning strategy based on market shifts
**Expected Output:** Competitive analysis matrix with feature comparison, gap analysis, and prioritized list of competitive features for the roadmap
**Time Estimate:** 1-2 days for initial matrix, 2-4 hours for quarterly updates
**Example:**
```bash
# Full competitive intelligence workflow
python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py q4-competitors.csv > competitive-matrix.md
# Prioritize competitive gap features
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py gap-features.csv --capacity 12 > competitive-roadmap.txt
```
## Integration Examples
### Example 1: Weekly Product Review Dashboard
@@ -389,9 +667,9 @@ echo "Report: $QUARTER-roadmap.txt"
## Related Agents
- [cs-agile-product-owner](cs-agile-product-owner.md) - Sprint planning and user story generation (planned)
- [cs-product-strategist](cs-product-strategist.md) - OKR cascade and strategic planning (planned)
- [cs-ux-researcher](cs-ux-researcher.md) - Persona generation and user research (planned)
- [cs-agile-product-owner](cs-agile-product-owner.md) - Sprint planning and user story generation
- [cs-product-strategist](cs-product-strategist.md) - OKR cascade and strategic planning
- [cs-ux-researcher](cs-ux-researcher.md) - Persona generation and user research
## References
@@ -401,7 +679,6 @@ echo "Report: $QUARTER-roadmap.txt"
---
**Last Updated:** November 5, 2025
**Sprint:** sprint-11-05-2025 (Day 4)
**Last Updated:** March 9, 2026
**Status:** Production Ready
**Version:** 1.0
**Version:** 2.0

487
agents/product/cs-product-strategist.md Normal file
View File

@@ -0,0 +1,487 @@
---
name: cs-product-strategist
description: Product strategy agent for quarterly OKR planning, competitive landscape analysis, product vision development, and strategy pivot evaluation
skills: product-team/product-strategist, product-team/competitive-teardown, product-team/product-manager-toolkit
domain: product
model: sonnet
tools: [Read, Write, Bash, Grep, Glob]
---
# Product Strategist Agent
## Purpose
The cs-product-strategist agent is a specialized strategic planning agent focused on product vision, OKR cascading, competitive intelligence, and strategy formulation. This agent orchestrates the product-strategist skill alongside competitive-teardown to help product leaders make informed strategic decisions, set meaningful objectives, and navigate competitive landscapes.
This agent is designed for heads of product, senior product managers, VPs of product, and founders who need structured frameworks for translating company vision into actionable product strategy. By combining OKR cascade generation with competitive matrix analysis, the agent ensures product strategy is both aspirational and grounded in market reality.
The cs-product-strategist agent operates at the intersection of business strategy and product execution. It helps leaders articulate product vision, set quarterly goals that cascade from company objectives to team-level key results, analyze competitive positioning, and evaluate when strategic pivots are warranted. Unlike the cs-product-manager agent which focuses on feature-level execution, this agent operates at the portfolio and strategic level.
## Skill Integration
**Primary Skill:** `../../product-team/product-strategist/`
### All Orchestrated Skills
| # | Skill | Location | Primary Tool |
|---|-------|----------|-------------|
| 1 | Product Strategist | `../../product-team/product-strategist/` | okr_cascade_generator.py |
| 2 | Competitive Teardown | `../../product-team/competitive-teardown/` | competitive_matrix_builder.py |
| 3 | Product Manager Toolkit | `../../product-team/product-manager-toolkit/` | rice_prioritizer.py |
### Python Tools
1. **OKR Cascade Generator**
- **Purpose:** Generate cascaded OKRs from company objectives to team-level key results with initiative mapping
- **Path:** `../../product-team/product-strategist/scripts/okr_cascade_generator.py`
- **Usage:** `python ../../product-team/product-strategist/scripts/okr_cascade_generator.py growth`
- **Features:** Multi-level cascade (company > product > team), initiative mapping, scoring framework, tracking cadence
- **Use Cases:** Quarterly planning, strategic alignment, goal setting, annual planning
2. **Competitive Matrix Builder**
- **Purpose:** Build competitive analysis matrices, feature comparison grids, and positioning maps
- **Path:** `../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py`
- **Usage:** `python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py competitors.csv`
- **Features:** Multi-dimensional scoring, weighted comparison, gap analysis, positioning visualization
- **Use Cases:** Competitive intelligence, market positioning, feature gap analysis, strategic differentiation
3. **RICE Prioritizer**
- **Purpose:** Strategic initiative prioritization using RICE framework for portfolio-level decisions
- **Path:** `../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py`
- **Usage:** `python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py initiatives.csv --capacity 50`
- **Features:** Portfolio quadrant analysis (big bets, quick wins), capacity planning, strategic roadmap generation
- **Use Cases:** Initiative prioritization, resource allocation, strategic portfolio management
### Knowledge Bases
1. **OKR Framework**
- **Location:** `../../product-team/product-strategist/references/okr_framework.md`
- **Content:** OKR methodology, cascade patterns, scoring guidelines, common pitfalls
- **Use Case:** OKR education, quarterly planning preparation
2. **Strategy Types**
- **Location:** `../../product-team/product-strategist/references/strategy_types.md`
- **Content:** Product strategy frameworks, competitive positioning models, growth strategies
- **Use Case:** Strategy formulation, market analysis, product vision development
3. **Data Collection Guide**
- **Location:** `../../product-team/competitive-teardown/references/data-collection-guide.md`
- **Content:** Sources and methods for gathering competitive intelligence ethically
- **Use Case:** Competitive research planning, data source identification
4. **Scoring Rubric**
- **Location:** `../../product-team/competitive-teardown/references/scoring-rubric.md`
- **Content:** Standardized scoring criteria for competitive dimensions (1-10 scale)
- **Use Case:** Consistent competitor evaluation, bias mitigation
5. **Analysis Templates**
- **Location:** `../../product-team/competitive-teardown/references/analysis-templates.md`
- **Content:** SWOT, Porter's Five Forces, positioning maps, battle cards, win/loss analysis
- **Use Case:** Structured competitive analysis, sales enablement
### Templates
1. **OKR Template**
- **Location:** `../../product-team/product-strategist/assets/okr_template.md`
- **Use Case:** Quarterly OKR documentation with tracking structure
2. **PRD Template**
- **Location:** `../../product-team/product-manager-toolkit/assets/prd_template.md`
- **Use Case:** Documenting strategic initiatives as formal requirements
## Workflows
### Workflow 1: Quarterly OKR Planning
**Goal:** Set ambitious, aligned quarterly OKRs that cascade from company objectives to product team key results
**Steps:**
1. **Review Company Strategy** - Gather strategic context:
- Company-level OKRs or annual goals
- Board priorities and investor expectations
- Revenue and growth targets
- Previous quarter's OKR results and learnings
2. **Analyze Market Context** - Understand external factors:
```bash
# Build competitive landscape
python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py competitors.csv
```
- Review competitive movements from past quarter
- Identify market trends and opportunities
- Assess customer feedback themes
3. **Generate OKR Cascade** - Create aligned objectives:
```bash
# Generate OKRs for growth strategy
python ../../product-team/product-strategist/scripts/okr_cascade_generator.py growth
```
4. **Define Product Objectives** - Set 2-3 product objectives:
- Each objective qualitative and inspirational
- Directly supports company-level objectives
- Achievable within the quarter with stretch
5. **Set Key Results** - 3-4 measurable KRs per objective:
- Specific, measurable, with baseline and target
- Mix of leading and lagging indicators
- Target 70% achievement (if consistently hitting 100%, not ambitious enough)
6. **Map Initiatives to KRs** - Connect work to outcomes:
```bash
# Prioritize strategic initiatives
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py initiatives.csv --capacity 50
```
7. **Stakeholder Alignment** - Present and iterate:
- Review with engineering leads for feasibility
- Align with marketing/sales for GTM coordination
- Get executive sign-off on objectives and KRs
8. **Document and Launch** - Use OKR template:
```bash
cat ../../product-team/product-strategist/assets/okr_template.md
```
**Expected Output:** Quarterly OKR document with 2-3 objectives, 8-12 key results, mapped initiatives, and stakeholder alignment
**Time Estimate:** 1 week (end of previous quarter)
**Example:**
```bash
# Full quarterly planning flow
echo "Q3 2026 OKR Planning"
echo "===================="
# Step 1: Competitive context
python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py q3-competitors.csv
# Step 2: Generate OKR cascade
python ../../product-team/product-strategist/scripts/okr_cascade_generator.py growth
# Step 3: Prioritize initiatives
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py q3-initiatives.csv --capacity 45
# Step 4: Review OKR template
cat ../../product-team/product-strategist/assets/okr_template.md
```
### Workflow 2: Competitive Landscape Review
**Goal:** Conduct a comprehensive competitive analysis to inform product positioning and feature prioritization
**Steps:**
1. **Identify Competitors** - Map the competitive landscape:
- Direct competitors (same solution, same market)
- Indirect competitors (different solution, same problem)
- Potential entrants (adjacent market players)
2. **Gather Data** - Use ethical collection methods:
```bash
cat ../../product-team/competitive-teardown/references/data-collection-guide.md
```
- Public sources: G2, Capterra, pricing pages, changelogs
- Market reports: Gartner, Forrester, analyst briefings
- Customer intelligence: Win/loss interviews, churn reasons
3. **Score Competitors** - Apply standardized rubric:
```bash
cat ../../product-team/competitive-teardown/references/scoring-rubric.md
```
- Score across 7 dimensions (UX, features, pricing, integrations, support, performance, security)
- Use multiple scorers to reduce bias
- Document evidence for each score
4. **Build Competitive Matrix** - Generate comparison:
```bash
python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py competitors-scored.csv
```
5. **Identify Gaps and Opportunities** - Analyze the matrix:
- Where do we lead? (defend and communicate)
- Where do we lag? (close gaps or differentiate)
- White space opportunities (unserved needs)
6. **Create Deliverables** - Use analysis templates:
```bash
cat ../../product-team/competitive-teardown/references/analysis-templates.md
```
- SWOT analysis per major competitor
- Positioning map (2x2)
- Battle cards for sales team
- Feature gap prioritization
**Expected Output:** Competitive analysis report with scoring matrix, positioning map, battle cards, and strategic recommendations
**Time Estimate:** 2-3 weeks for comprehensive analysis (refresh quarterly)
**Example:**
```bash
# Competitive analysis workflow
cat > competitors.csv << 'EOF'
competitor,ux,features,pricing,integrations,support,performance,security
Our Product,8,7,7,8,7,9,8
Competitor A,7,8,6,9,6,7,7
Competitor B,9,6,8,5,8,6,6
Competitor C,5,9,5,7,5,8,9
EOF
python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py competitors.csv
```
### Workflow 3: Product Vision Document
**Goal:** Articulate a clear, compelling product vision that aligns the organization around a shared future state
**Steps:**
1. **Gather Inputs** - Collect strategic context:
- Company mission and long-term vision
- Market trends and industry analysis
- Customer research insights and unmet needs
- Technology trends and enablers
- Competitive landscape analysis
2. **Define the Vision** - Answer key questions:
- What world are we trying to create for our users?
- What will be fundamentally different in 3-5 years?
- How does our product uniquely enable this future?
- What do we believe that others do not?
3. **Map the Strategy** - Connect vision to execution:
```bash
# Review strategy frameworks
cat ../../product-team/product-strategist/references/strategy_types.md
```
- Choose strategic posture (category leader, disruptor, fast follower)
- Define competitive moats (technology, network effects, data, brand)
- Identify strategic pillars (3-4 themes that organize the roadmap)
4. **Create the Roadmap Narrative** - Multi-horizon plan:
- **Horizon 1 (Now - 6 months):** Current priorities, committed work
- **Horizon 2 (6-18 months):** Emerging opportunities, bets to place
- **Horizon 3 (18-36 months):** Transformative ideas, vision investments
5. **Validate with Stakeholders** - Test the vision:
- Engineering: Technical feasibility of long-term bets
- Sales: Market resonance of positioning
- Executive: Strategic alignment and resource commitment
- Customers: Problem validation for future state
6. **Document and Communicate** - Create living document:
- One-page vision summary (elevator pitch)
- Detailed vision document with supporting evidence
- Roadmap visualization by horizon
- Strategic principles for decision-making
**Expected Output:** Product vision document with 3-5 year direction, strategic pillars, multi-horizon roadmap, and competitive positioning
**Time Estimate:** 2-4 weeks for initial vision (annual refresh)
### Workflow 4: Strategy Pivot Analysis
**Goal:** Evaluate whether a strategic pivot is warranted and plan the transition if so
**Steps:**
1. **Identify Pivot Signals** - Recognize warning signs:
- Stalled growth metrics (revenue, users, engagement)
- Persistent product-market fit challenges
- Major competitive disruption
- Customer segment shift or churn pattern
- Technology paradigm change
2. **Quantify Current Performance** - Baseline analysis:
```bash
# Assess current initiative portfolio
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py current-initiatives.csv
```
- Revenue trajectory and unit economics
- Customer acquisition cost trends
- Retention and engagement metrics
- Competitive position changes
3. **Evaluate Pivot Options** - Analyze alternatives:
- **Customer pivot:** Same product, different market segment
- **Problem pivot:** Same customer, different problem to solve
- **Solution pivot:** Same problem, different approach
- **Channel pivot:** Same product, different distribution
- **Technology pivot:** Same value, different technology platform
- **Revenue model pivot:** Same product, different monetization
4. **Score Each Option** - Structured evaluation:
```bash
# Build comparison matrix for pivot options
python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py pivot-options.csv
```
- Market size and growth potential
- Competitive intensity in new direction
- Required investment and timeline
- Leverage of existing assets (team, tech, brand, customers)
- Risk profile and reversibility
5. **Plan the Transition** - If pivot is warranted:
- Phase 1: Validate new direction (2-4 weeks, minimal investment)
- Phase 2: Build MVP for new direction (4-8 weeks)
- Phase 3: Measure early signals (4 weeks)
- Phase 4: Commit or revert based on data
- Communication plan for team, customers, investors
6. **Set Pivot OKRs** - Define success for the new direction:
```bash
python ../../product-team/product-strategist/scripts/okr_cascade_generator.py pivot
```
**Expected Output:** Pivot analysis document with current state assessment, option evaluation, recommended path, transition plan, and pivot-specific OKRs
**Time Estimate:** 2-3 weeks for thorough pivot analysis
**Example:**
```bash
# Pivot evaluation workflow
cat > pivot-options.csv << 'EOF'
option,market_size,competition,investment,leverage,risk
Stay the Course,6,7,2,9,3
Customer Pivot to Enterprise,9,5,6,7,5
Problem Pivot to Workflow,8,6,7,5,6
Technology Pivot to AI-Native,9,4,8,4,7
EOF
python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py pivot-options.csv
# Generate OKRs for recommended pivot direction
python ../../product-team/product-strategist/scripts/okr_cascade_generator.py growth
```
## Integration Examples
### Example 1: Annual Strategic Planning
```bash
#!/bin/bash
# annual-strategy.sh - Annual product strategy planning
YEAR="2027"
echo "Annual Product Strategy - $YEAR"
echo "================================"
# Competitive landscape
echo ""
echo "1. Competitive Analysis:"
python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py annual-competitors.csv
# Strategy reference
echo ""
echo "2. Strategy Frameworks:"
cat ../../product-team/product-strategist/references/strategy_types.md | head -50
# Annual OKR cascade
echo ""
echo "3. Annual OKR Cascade:"
python ../../product-team/product-strategist/scripts/okr_cascade_generator.py growth
# Initiative prioritization
echo ""
echo "4. Strategic Initiative Prioritization:"
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py annual-initiatives.csv --capacity 180
```
### Example 2: Monthly Strategy Review
```bash
#!/bin/bash
# strategy-review.sh - Monthly strategy check-in
echo "Monthly Strategy Review - $(date +%Y-%m-%d)"
echo "============================================"
# Competitive movements
echo ""
echo "Competitive Updates:"
echo "Review: ../../product-team/competitive-teardown/references/data-collection-guide.md"
# OKR progress
echo ""
echo "OKR Progress:"
echo "Review: ../../product-team/product-strategist/assets/okr_template.md"
# Initiative status
echo ""
echo "Initiative Portfolio:"
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py current-initiatives.csv
```
### Example 3: Board Preparation
```bash
#!/bin/bash
# board-prep.sh - Quarterly board meeting preparation
QUARTER="Q3-2026"
echo "Board Preparation - $QUARTER"
echo "============================="
# Strategic metrics
echo ""
echo "1. Product Strategy Performance:"
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py $QUARTER-delivered.csv
# Competitive position
echo ""
echo "2. Competitive Positioning:"
python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py board-competitors.csv
# Next quarter OKRs
echo ""
echo "3. Next Quarter OKR Proposal:"
python ../../product-team/product-strategist/scripts/okr_cascade_generator.py growth
```
## Success Metrics
**Strategic Alignment:**
- **OKR Cascade Clarity:** 100% of team OKRs trace to company objectives
- **Strategy Communication:** >90% of product team can articulate product vision
- **Cross-Functional Alignment:** Product, engineering, and GTM teams aligned on priorities
- **Decision Speed:** Strategic decisions made within 1 week of analysis completion
**Competitive Intelligence:**
- **Market Awareness:** Competitive analysis refreshed quarterly
- **Win Rate Impact:** Win rate improves >5% after battle card distribution
- **Positioning Clarity:** Clear differentiation articulated for top 3 competitors
- **Blind Spot Reduction:** No competitive surprises in customer conversations
**OKR Effectiveness:**
- **Achievement Rate:** Average OKR score 0.6-0.7 (ambitious but achievable)
- **Cascade Quality:** All key results measurable with baseline and target
- **Initiative Impact:** >70% of completed initiatives move their associated KR
- **Quarterly Rhythm:** OKR planning completed before quarter starts
**Business Impact:**
- **Revenue Alignment:** Product strategy directly tied to revenue growth targets
- **Market Position:** Maintain or improve position on competitive map
- **Customer Retention:** Strategic decisions reduce churn by measurable percentage
- **Innovation Pipeline:** Horizon 2-3 initiatives represent >20% of roadmap investment
## Related Agents
- [cs-product-manager](cs-product-manager.md) - Feature-level execution, RICE prioritization, PRD development
- [cs-agile-product-owner](cs-agile-product-owner.md) - Sprint-level planning and backlog management
- [cs-ux-researcher](cs-ux-researcher.md) - User research to validate strategic assumptions
- [cs-ceo-advisor](../c-level/cs-ceo-advisor.md) - Company-level strategic alignment
- Senior PM Skill - Portfolio context (see `../../project-management/senior-pm/`)
## References
- **Primary Skill:** [../../product-team/product-strategist/SKILL.md](../../product-team/product-strategist/SKILL.md)
- **Competitive Teardown Skill:** [../../product-team/competitive-teardown/SKILL.md](../../product-team/competitive-teardown/SKILL.md)
- **OKR Framework:** [../../product-team/product-strategist/references/okr_framework.md](../../product-team/product-strategist/references/okr_framework.md)
- **Strategy Types:** [../../product-team/product-strategist/references/strategy_types.md](../../product-team/product-strategist/references/strategy_types.md)
- **Product Domain Guide:** [../../product-team/CLAUDE.md](../../product-team/CLAUDE.md)
- **Agent Development Guide:** [../CLAUDE.md](../CLAUDE.md)
---
**Last Updated:** March 9, 2026
**Status:** Production Ready
**Version:** 1.0

531
agents/product/cs-ux-researcher.md Normal file
View File

@@ -0,0 +1,531 @@
---
name: cs-ux-researcher
description: UX research agent for research planning, persona generation, journey mapping, and usability test analysis
skills: product-team/ux-researcher-designer, product-team/product-manager-toolkit, product-team/ui-design-system
domain: product
model: sonnet
tools: [Read, Write, Bash, Grep, Glob]
---
# UX Researcher Agent
## Purpose
The cs-ux-researcher agent is a specialized user experience research agent focused on research planning, persona creation, journey mapping, and usability test analysis. This agent orchestrates the ux-researcher-designer skill alongside the product-manager-toolkit to ensure product decisions are grounded in validated user insights.
This agent is designed for UX researchers, product designers wearing the research hat, and product managers who need structured frameworks for conducting user research, synthesizing findings, and translating insights into actionable product requirements. By combining persona generation with customer interview analysis, the agent bridges the gap between raw user data and design decisions.
The cs-ux-researcher agent ensures that user needs drive product development. It provides methodological rigor for research planning, data-driven persona creation, systematic journey mapping, and structured usability evaluation. The agent works closely with the ui-design-system skill for design handoff and with the product-manager-toolkit for translating research insights into prioritized feature requirements.
## Skill Integration
**Primary Skill:** `../../product-team/ux-researcher-designer/`
### All Orchestrated Skills
| # | Skill | Location | Primary Tool |
|---|-------|----------|-------------|
| 1 | UX Researcher & Designer | `../../product-team/ux-researcher-designer/` | persona_generator.py |
| 2 | Product Manager Toolkit | `../../product-team/product-manager-toolkit/` | customer_interview_analyzer.py |
| 3 | UI Design System | `../../product-team/ui-design-system/` | design_token_generator.py |
### Python Tools
1. **Persona Generator**
- **Purpose:** Create data-driven user personas from research inputs including demographics, goals, pain points, and behavioral patterns
- **Path:** `../../product-team/ux-researcher-designer/scripts/persona_generator.py`
- **Usage:** `python ../../product-team/ux-researcher-designer/scripts/persona_generator.py research-data.json`
- **Features:** Multiple persona generation, behavioral segmentation, needs hierarchy mapping, empathy map creation
- **Use Cases:** Persona development, user segmentation, design alignment, stakeholder communication
2. **Customer Interview Analyzer**
- **Purpose:** NLP-based analysis of interview transcripts to extract pain points, feature requests, themes, and sentiment
- **Path:** `../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py`
- **Usage:** `python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview.txt`
- **Features:** Pain point extraction with severity scoring, feature request identification, jobs-to-be-done patterns, theme clustering, key quote extraction
- **Use Cases:** Interview synthesis, discovery validation, problem prioritization, insight aggregation
3. **Design Token Generator**
- **Purpose:** Generate design tokens for consistent UI implementation across platforms
- **Path:** `../../product-team/ui-design-system/scripts/design_token_generator.py`
- **Usage:** `python ../../product-team/ui-design-system/scripts/design_token_generator.py theme.json`
- **Use Cases:** Research-informed design system updates, accessibility token adjustments
### Knowledge Bases
1. **Persona Methodology**
- **Location:** `../../product-team/ux-researcher-designer/references/persona-methodology.md`
- **Content:** Research-backed persona creation methodology, data collection strategies, validation approaches
- **Use Case:** Methodological guidance for persona projects
2. **Example Personas**
- **Location:** `../../product-team/ux-researcher-designer/references/example-personas.md`
- **Content:** Sample persona documents with demographics, goals, pain points, behaviors, scenarios
- **Use Case:** Persona format reference, team training
3. **Journey Mapping Guide**
- **Location:** `../../product-team/ux-researcher-designer/references/journey-mapping-guide.md`
- **Content:** Customer journey mapping methodology, touchpoint analysis, emotion mapping, opportunity identification
- **Use Case:** Journey map creation, experience design, service design
4. **Usability Testing Frameworks**
- **Location:** `../../product-team/ux-researcher-designer/references/usability-testing-frameworks.md`
- **Content:** Test planning, task design, analysis methods, severity ratings, reporting formats
- **Use Case:** Usability study design, prototype validation, UX evaluation
5. **Component Architecture**
- **Location:** `../../product-team/ui-design-system/references/component-architecture.md`
- **Content:** Component hierarchy, atomic design patterns, composition strategies
- **Use Case:** Research-to-design translation, component recommendations
6. **Developer Handoff**
- **Location:** `../../product-team/ui-design-system/references/developer-handoff.md`
- **Content:** Design-to-dev handoff process, specification formats, asset delivery
- **Use Case:** Translating research findings into implementation specs
### Templates
1. **Research Plan Template**
- **Location:** `../../product-team/ux-researcher-designer/assets/research_plan_template.md`
- **Use Case:** Structuring research studies with methodology, participants, and analysis plan
2. **Design System Documentation Template**
- **Location:** `../../product-team/ui-design-system/assets/design_system_doc_template.md`
- **Use Case:** Documenting research-informed design system decisions
## Workflows
### Workflow 1: Research Plan Creation
**Goal:** Design a rigorous research study that answers specific product questions with appropriate methodology
**Steps:**
1. **Define Research Questions** - Identify what needs to be learned:
- What are the top 3-5 questions stakeholders need answered?
- What do we already know from existing data?
- What assumptions need validation?
- What decisions will this research inform?
2. **Select Methodology** - Choose the right approach:
```bash
# Review usability testing frameworks for method selection
cat ../../product-team/ux-researcher-designer/references/usability-testing-frameworks.md
```
- **Exploratory** (interviews, contextual inquiry): When learning about problem space
- **Evaluative** (usability testing, A/B tests): When validating solutions
- **Generative** (diary studies, card sorting): When discovering new opportunities
- **Quantitative** (surveys, analytics): When measuring scale and significance
3. **Define Participants** - Screen for the right users:
- Target persona(s) to recruit
- Screening criteria (role, experience, usage patterns)
- Sample size justification
- Recruitment channels and incentives
4. **Create Study Materials** - Prepare research instruments:
```bash
# Use the research plan template
cat ../../product-team/ux-researcher-designer/assets/research_plan_template.md
```
- Interview guide or test script
- Task scenarios (for usability tests)
- Consent form and recording permissions
- Analysis framework and coding scheme
5. **Align with Stakeholders** - Get buy-in:
- Share research plan with product and engineering leads
- Invite stakeholders to observe sessions
- Set expectations for timeline and deliverables
- Define how findings will be actioned
**Expected Output:** Complete research plan with questions, methodology, participant criteria, study materials, timeline, and stakeholder alignment
**Time Estimate:** 2-3 days for plan creation
**Example:**
```bash
# Create research plan from template
cp ../../product-team/ux-researcher-designer/assets/research_plan_template.md onboarding-research-plan.md
# Review methodology options
cat ../../product-team/ux-researcher-designer/references/usability-testing-frameworks.md
# Review persona methodology for participant criteria
cat ../../product-team/ux-researcher-designer/references/persona-methodology.md
```
### Workflow 2: Persona Generation
**Goal:** Create data-driven user personas from research data that align product teams around real user needs
**Steps:**
1. **Gather Research Data** - Collect inputs from multiple sources:
- Interview transcripts (analyzed for themes)
- Survey responses (demographic and behavioral data)
- Analytics data (usage patterns, feature adoption)
- Support tickets (common issues, pain points)
- Sales call notes (buyer motivations, objections)
2. **Analyze Interview Data** - Extract structured insights:
```bash
# Analyze each interview transcript
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-001.txt > insights-001.json
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-002.txt > insights-002.json
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-003.txt > insights-003.json
```
3. **Identify Behavioral Segments** - Cluster users by:
- Goals and motivations (what they are trying to achieve)
- Behaviors and workflows (how they work today)
- Pain points and frustrations (what blocks them)
- Technical sophistication (how they interact with tools)
- Decision-making factors (what drives their choices)
4. **Generate Personas** - Create data-backed personas:
```bash
# Generate personas from aggregated research
python ../../product-team/ux-researcher-designer/scripts/persona_generator.py research-data.json
```
5. **Validate Personas** - Ensure accuracy:
- Cross-reference with quantitative data (segment sizes)
- Review with customer-facing teams (sales, support)
- Test with stakeholders who interact with users
- Confirm each persona represents a meaningful segment
6. **Socialize Personas** - Make personas actionable:
```bash
# Review example personas for format guidance
cat ../../product-team/ux-researcher-designer/references/example-personas.md
```
- Create one-page persona cards for team walls/wikis
- Present to product, engineering, and design teams
- Map personas to product areas and features
- Reference personas in PRDs and design briefs
**Expected Output:** 3-5 validated user personas with demographics, goals, pain points, behaviors, and scenarios
**Time Estimate:** 1-2 weeks (data collection through socialization)
**Example:**
```bash
# Full persona generation workflow
echo "Persona Generation Workflow"
echo "==========================="
# Step 1: Analyze interviews
for f in interviews/*.txt; do
base=$(basename "$f" .txt)
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py "$f" json > "insights-$base.json"
echo "Analyzed: $f"
done
# Step 2: Review persona methodology
cat ../../product-team/ux-researcher-designer/references/persona-methodology.md
# Step 3: Generate personas
python ../../product-team/ux-researcher-designer/scripts/persona_generator.py research-data.json
# Step 4: Review example format
cat ../../product-team/ux-researcher-designer/references/example-personas.md
```
### Workflow 3: Journey Mapping
**Goal:** Map the complete user journey to identify pain points, opportunities, and moments that matter
**Steps:**
1. **Define Journey Scope** - Set boundaries:
- Which persona is this journey for?
- What is the starting trigger?
- What is the end state (success)?
- What timeframe does the journey cover?
2. **Review Journey Mapping Methodology** - Understand the framework:
```bash
cat ../../product-team/ux-researcher-designer/references/journey-mapping-guide.md
```
3. **Map Journey Stages** - Identify key phases:
- **Awareness:** How users discover the product
- **Consideration:** How users evaluate and compare
- **Onboarding:** First-time setup and activation
- **Regular Use:** Core workflow and daily interactions
- **Growth:** Expanding usage, inviting team, upgrading
- **Advocacy:** Referring others, providing feedback
4. **Document Touchpoints** - For each stage:
- User actions (what they do)
- Channels (where they interact)
- Emotions (how they feel)
- Pain points (what frustrates them)
- Opportunities (how we can improve)
5. **Identify Moments of Truth** - Critical experience points:
- First-time use (aha moment)
- First success (value realization)
- First problem (support experience)
- Upgrade decision (value justification)
- Referral moment (advocacy trigger)
6. **Prioritize Opportunities** - Focus on highest-impact improvements:
```bash
# Prioritize journey improvement opportunities
cat > journey-opportunities.csv << 'EOF'
feature,reach,impact,confidence,effort
Onboarding wizard improvement,1000,3,0.9,3
First-success celebration,800,2,0.7,1
Self-service help in context,600,2,0.8,2
Upgrade prompt optimization,400,3,0.6,2
EOF
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py journey-opportunities.csv
```
**Expected Output:** Visual journey map with stages, touchpoints, emotions, pain points, and prioritized improvement opportunities
**Time Estimate:** 1-2 weeks for research-backed journey map
**Example:**
```bash
# Journey mapping workflow
echo "Journey Mapping - Onboarding Flow"
echo "=================================="
# Review journey mapping methodology
cat ../../product-team/ux-researcher-designer/references/journey-mapping-guide.md
# Analyze relevant interview transcripts for journey insights
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py onboarding-interview-01.txt
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py onboarding-interview-02.txt
# Prioritize improvement opportunities
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py journey-opportunities.csv
```
### Workflow 4: Usability Test Analysis
**Goal:** Conduct and analyze usability tests to evaluate design solutions and identify critical UX issues
**Steps:**
1. **Plan the Test** - Design the study:
```bash
# Review usability testing frameworks
cat ../../product-team/ux-researcher-designer/references/usability-testing-frameworks.md
```
- Define test objectives (what decisions will this inform)
- Select test type (moderated/unmoderated, remote/in-person)
- Write task scenarios (realistic, goal-oriented)
- Set success criteria per task (completion, time, errors)
2. **Prepare Materials** - Set up the test:
- Prototype or staging environment ready
- Test script with introduction, tasks, and debrief questions
- Recording tools configured
- Note-taking template for observers
- Use research plan template for documentation:
```bash
cat ../../product-team/ux-researcher-designer/assets/research_plan_template.md
```
3. **Conduct Sessions** - Run 5-8 sessions:
- Follow consistent script for each participant
- Use think-aloud protocol
- Note task completion, errors, and verbal feedback
- Capture quotes and emotional reactions
- Debrief after each session
4. **Analyze Results** - Synthesize findings:
- Calculate task success rates
- Measure time-on-task per scenario
- Categorize usability issues by severity:
- **Critical:** Prevents task completion
- **Major:** Causes significant difficulty or errors
- **Minor:** Creates confusion but user recovers
- **Cosmetic:** Aesthetic or minor friction
- Identify patterns across participants
5. **Analyze Verbal Feedback** - Extract qualitative insights:
```bash
# Analyze session transcripts for themes
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py usability-session-01.txt
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py usability-session-02.txt
```
6. **Create Report and Recommendations** - Deliver findings:
- Executive summary (key findings in 3-5 bullets)
- Task-by-task results with evidence
- Prioritized issue list with severity
- Recommended design changes
- Highlight reel of key moments (video clips)
7. **Inform Design Iteration** - Close the loop:
- Review findings with design team
- Map issues to components in design system:
```bash
cat ../../product-team/ui-design-system/references/component-architecture.md
```
- Create Jira tickets for each issue
- Plan re-test for critical issues after fixes
**Expected Output:** Usability test report with task metrics, severity-rated issues, recommendations, and design iteration plan
**Time Estimate:** 2-3 weeks (planning through report delivery)
**Example:**
```bash
# Usability test analysis workflow
echo "Usability Test Analysis"
echo "======================="
# Review frameworks
cat ../../product-team/ux-researcher-designer/references/usability-testing-frameworks.md
# Analyze each session transcript
for i in 1 2 3 4 5; do
echo "Session $i Analysis:"
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py "usability-session-0$i.txt"
echo ""
done
# Review component architecture for design recommendations
cat ../../product-team/ui-design-system/references/component-architecture.md
```
## Integration Examples
### Example 1: Discovery Sprint Research
```bash
#!/bin/bash
# discovery-research.sh - 2-week discovery sprint
echo "Discovery Sprint Research"
echo "========================="
# Week 1: Research execution
echo ""
echo "Week 1: Conduct & Analyze Interviews"
echo "-------------------------------------"
# Analyze all interview transcripts
for f in discovery-interviews/*.txt; do
base=$(basename "$f" .txt)
echo "Analyzing: $base"
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py "$f" json > "insights/$base.json"
done
# Week 2: Synthesis
echo ""
echo "Week 2: Generate Personas & Journey Map"
echo "----------------------------------------"
# Generate personas from aggregated data
python ../../product-team/ux-researcher-designer/scripts/persona_generator.py aggregated-research.json
# Reference journey mapping guide
echo "Journey mapping guide: ../../product-team/ux-researcher-designer/references/journey-mapping-guide.md"
```
### Example 2: Research Repository Update
```bash
#!/bin/bash
# research-update.sh - Monthly research insights update
echo "Research Repository Update - $(date +%Y-%m-%d)"
echo "================================================"
# Process new interviews
echo ""
echo "New Interview Analysis:"
for f in new-interviews/*.txt; do
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py "$f"
echo "---"
done
# Review and refresh personas
echo ""
echo "Persona Review:"
echo "Current personas: ../../product-team/ux-researcher-designer/references/example-personas.md"
echo "Methodology: ../../product-team/ux-researcher-designer/references/persona-methodology.md"
```
### Example 3: Design Handoff with Research Context
```bash
#!/bin/bash
# research-handoff.sh - Prepare research context for design team
echo "Research Handoff Package"
echo "========================"
# Persona context
echo ""
echo "1. Active Personas:"
cat ../../product-team/ux-researcher-designer/references/example-personas.md | head -30
# Journey context
echo ""
echo "2. Journey Map Reference:"
echo "See: ../../product-team/ux-researcher-designer/references/journey-mapping-guide.md"
# Design system alignment
echo ""
echo "3. Component Architecture:"
echo "See: ../../product-team/ui-design-system/references/component-architecture.md"
# Developer handoff process
echo ""
echo "4. Handoff Process:"
echo "See: ../../product-team/ui-design-system/references/developer-handoff.md"
```
## Success Metrics
**Research Quality:**
- **Study Rigor:** 100% of studies have documented research plan with methodology justification
- **Participant Quality:** >90% of participants match screening criteria
- **Insight Actionability:** >80% of research findings result in backlog items or design changes
- **Stakeholder Engagement:** >2 stakeholders observe each research session
**Persona Effectiveness:**
- **Team Adoption:** >80% of PRDs reference a specific persona
- **Validation Rate:** Personas validated with quantitative data (segment sizes, usage patterns)
- **Refresh Cadence:** Personas reviewed and updated at least semi-annually
- **Decision Influence:** Personas cited in >50% of product design decisions
**Usability Impact:**
- **Issue Detection:** 5+ unique usability issues identified per study
- **Fix Rate:** >70% of critical/major issues resolved within 2 sprints
- **Task Success:** Average task success rate improves by >15% after design iteration
- **User Satisfaction:** SUS score improves by >5 points after research-informed redesign
**Business Impact:**
- **Customer Satisfaction:** NPS improvement correlated with research-informed changes
- **Onboarding Conversion:** First-time user activation rate improvement
- **Support Ticket Reduction:** Fewer UX-related support requests
- **Feature Adoption:** Research-informed features show >20% higher adoption rates
## Related Agents
- [cs-product-manager](cs-product-manager.md) - Product management lifecycle, interview analysis, PRD development
- [cs-agile-product-owner](cs-agile-product-owner.md) - Translating research findings into user stories
- [cs-product-strategist](cs-product-strategist.md) - Strategic research to validate product vision and positioning
- UI Design System - Design handoff and component recommendations (see `../../product-team/ui-design-system/`)
## References
- **Primary Skill:** [../../product-team/ux-researcher-designer/SKILL.md](../../product-team/ux-researcher-designer/SKILL.md)
- **Interview Analyzer:** [../../product-team/product-manager-toolkit/SKILL.md](../../product-team/product-manager-toolkit/SKILL.md)
- **Persona Methodology:** [../../product-team/ux-researcher-designer/references/persona-methodology.md](../../product-team/ux-researcher-designer/references/persona-methodology.md)
- **Journey Mapping Guide:** [../../product-team/ux-researcher-designer/references/journey-mapping-guide.md](../../product-team/ux-researcher-designer/references/journey-mapping-guide.md)
- **Usability Testing:** [../../product-team/ux-researcher-designer/references/usability-testing-frameworks.md](../../product-team/ux-researcher-designer/references/usability-testing-frameworks.md)
- **Design System:** [../../product-team/ui-design-system/SKILL.md](../../product-team/ui-design-system/SKILL.md)
- **Product Domain Guide:** [../../product-team/CLAUDE.md](../../product-team/CLAUDE.md)
- **Agent Development Guide:** [../CLAUDE.md](../CLAUDE.md)
---
**Last Updated:** March 9, 2026
**Status:** Production Ready
**Version:** 1.0

539
agents/project-management/cs-project-manager.md
View File

@@ -1,54 +1,515 @@
---
name: cs-project-manager
description: Project Manager agent for sprint planning, Jira/Confluence workflows, Scrum ceremonies, and stakeholder reporting. Orchestrates project-management skills. Spawn when users need sprint planning, Jira configuration, workflow design, retrospectives, or project status dashboards.
description: Project Manager agent for sprint planning, Jira/Confluence workflows, Scrum ceremonies, and stakeholder reporting. Orchestrates project-management skills.
skills: project-management
domain: pm
model: sonnet
tools: [Read, Write, Bash, Grep, Glob]
---
# cs-project-manager
# Project Manager Agent
## Role & Expertise
## Purpose
Experienced PM covering agile delivery, Atlassian administration, and stakeholder management. Runs sprints, designs workflows, creates templates, and generates reports.
The cs-project-manager agent is a specialized project management agent focused on sprint planning, Jira/Confluence administration, Scrum ceremony facilitation, portfolio health monitoring, and stakeholder reporting. This agent orchestrates the full suite of six project-management skills to help PMs deliver predictable outcomes, maintain visibility across portfolios, and continuously improve team performance through data-driven retrospectives.
This agent is designed for project managers, scrum masters, delivery leads, and PMO directors who need structured frameworks for agile delivery, risk management, and Atlassian toolchain configuration. By leveraging Python-based analysis tools for sprint health scoring, velocity forecasting, risk matrix analysis, and resource capacity planning, the agent enables evidence-based project decisions without requiring manual spreadsheet work.
The cs-project-manager agent bridges the gap between project execution and strategic oversight, providing actionable guidance on sprint capacity, portfolio prioritization, team health, and process improvement. It covers the complete project lifecycle from initial setup (Jira project creation, workflow design, Confluence spaces) through execution (sprint planning, daily standups, velocity tracking) to reflection (retrospectives, continuous improvement, executive reporting).
## Skill Integration
- `project-management/jira-expert` — JQL, workflows, automation, dashboards
- `project-management/confluence-expert` — Documentation, templates, knowledge bases
- `project-management/scrum-master` — Sprint health, velocity, retrospectives
- `project-management/senior-pm` — Risk analysis, resource optimization, portfolio management
- `project-management/atlassian-admin` — User provisioning, permissions, integrations
- `project-management/atlassian-templates` — Blueprints, custom layouts, reusable components
### Senior PM
## Core Workflows
**Skill Location:** `../../project-management/senior-pm/`
### 1. Sprint Planning
1. Review backlog via `jira-expert` (JQL for upcoming items)
2. Estimate capacity using `scrum-master` velocity tools
3. Prioritize with WSJF via `senior-pm`
4. Create sprint in Jira with goals and scope
5. Document sprint plan in Confluence via `confluence-expert`
**Python Tools:**
### 2. Jira Workflow Design
1. Map team process to workflow states
2. Design transitions, conditions, validators (ref: `jira-expert/references/WORKFLOWS.md`)
3. Set up automation rules (ref: `jira-expert/references/AUTOMATION.md`)
4. Create dashboards for visibility
5. Test with pilot team, iterate
1. **Project Health Dashboard**
- **Purpose:** Generate portfolio-level health dashboard with RAG status across all active projects
- **Path:** `../../project-management/senior-pm/scripts/project_health_dashboard.py`
- **Usage:** `python ../../project-management/senior-pm/scripts/project_health_dashboard.py sample_project_data.json`
- **Features:** Schedule variance, budget tracking, risk exposure, milestone status, RAG indicators
### 3. Retrospective Facilitation
1. Gather sprint metrics via `scrum-master` scripts
2. Calculate sprint health score
3. Run retro format (Start/Stop/Continue, 4Ls, or Sailboat)
4. Document action items in Confluence
5. Create Jira tickets for improvement items
2. **Risk Matrix Analyzer**
- **Purpose:** Quantitative risk analysis with probability-impact matrices and Expected Monetary Value (EMV)
- **Path:** `../../project-management/senior-pm/scripts/risk_matrix_analyzer.py`
- **Usage:** `python ../../project-management/senior-pm/scripts/risk_matrix_analyzer.py risks.json`
- **Features:** Risk scoring, heat map generation, mitigation tracking, EMV calculation
### 4. Stakeholder Reporting
1. Pull project metrics via `senior-pm` scripts
2. Generate risk assessment with EMV analysis
3. Create executive dashboard in Confluence
4. Schedule automated Jira reports
3. **Resource Capacity Planner**
- **Purpose:** Team resource allocation and capacity forecasting across sprints and projects
- **Path:** `../../project-management/senior-pm/scripts/resource_capacity_planner.py`
- **Usage:** `python ../../project-management/senior-pm/scripts/resource_capacity_planner.py team_data.json`
- **Features:** Utilization analysis, over-allocation detection, capacity forecasting, cross-project balancing
## Output Standards
- Sprint plans → Confluence page with Jira macro embedding
- Reports → structured with RAG status, risks, actions
- Workflows → documented with transition diagrams
- All time estimates include confidence ranges
**Knowledge Bases:**
- `../../project-management/senior-pm/references/portfolio-prioritization-models.md` -- WSJF, MoSCoW, Cost of Delay, portfolio scoring frameworks
- `../../project-management/senior-pm/references/risk-management-framework.md` -- Risk identification, qualitative/quantitative analysis, response strategies
- `../../project-management/senior-pm/references/portfolio-kpis.md` -- KPI definitions, tracking cadences, executive reporting metrics
**Templates:**
- `../../project-management/senior-pm/assets/executive_report_template.md` -- Executive status report with RAG, risks, decisions needed
- `../../project-management/senior-pm/assets/project_charter_template.md` -- Project charter with scope, objectives, constraints, stakeholders
- `../../project-management/senior-pm/assets/raci_matrix_template.md` -- Responsibility assignment matrix for cross-functional teams
### Scrum Master
**Skill Location:** `../../project-management/scrum-master/`
**Python Tools:**
1. **Sprint Health Scorer**
- **Purpose:** Quantitative sprint health assessment across scope, velocity, quality, and team morale
- **Path:** `../../project-management/scrum-master/scripts/sprint_health_scorer.py`
- **Usage:** `python ../../project-management/scrum-master/scripts/sprint_health_scorer.py sample_sprint_data.json`
- **Features:** Multi-dimensional scoring (0-100), trend analysis, health indicators, actionable recommendations
2. **Velocity Analyzer**
- **Purpose:** Historical velocity analysis with forecasting and confidence intervals
- **Path:** `../../project-management/scrum-master/scripts/velocity_analyzer.py`
- **Usage:** `python ../../project-management/scrum-master/scripts/velocity_analyzer.py sprint_history.json`
- **Features:** Rolling averages, standard deviation, sprint-over-sprint trends, capacity prediction
3. **Retrospective Analyzer**
- **Purpose:** Structured retrospective analysis with action item tracking and theme extraction
- **Path:** `../../project-management/scrum-master/scripts/retrospective_analyzer.py`
- **Usage:** `python ../../project-management/scrum-master/scripts/retrospective_analyzer.py retro_notes.json`
- **Features:** Theme clustering, sentiment analysis, action item extraction, trend tracking across sprints
**Knowledge Bases:**
- `../../project-management/scrum-master/references/retro-formats.md` -- Start/Stop/Continue, 4Ls, Sailboat, Mad/Sad/Glad, Starfish formats
- `../../project-management/scrum-master/references/team-dynamics-framework.md` -- Tuckman stages, psychological safety, conflict resolution
- `../../project-management/scrum-master/references/velocity-forecasting-guide.md` -- Monte Carlo simulation, confidence ranges, capacity planning
**Templates:**
- `../../project-management/scrum-master/assets/sprint_report_template.md` -- Sprint review report with burndown, velocity, demo notes
- `../../project-management/scrum-master/assets/team_health_check_template.md` -- Spotify-style team health check across 8 dimensions
### Jira Expert
**Skill Location:** `../../project-management/jira-expert/`
**Knowledge Bases:**
- `../../project-management/jira-expert/references/jql-examples.md` -- JQL query patterns for backlog grooming, sprint reporting, SLA tracking
- `../../project-management/jira-expert/references/automation-examples.md` -- Jira automation rule templates for common workflows
- `../../project-management/jira-expert/references/AUTOMATION.md` -- Comprehensive automation guide with triggers, conditions, actions
- `../../project-management/jira-expert/references/WORKFLOWS.md` -- Workflow design patterns, transition rules, validators, post-functions
### Confluence Expert
**Skill Location:** `../../project-management/confluence-expert/`
**Knowledge Bases:**
- `../../project-management/confluence-expert/references/templates.md` -- Page templates for sprint plans, meeting notes, decision logs, architecture docs
### Atlassian Admin
**Skill Location:** `../../project-management/atlassian-admin/`
Covers user provisioning, permission schemes, project configuration, and integration setup. No scripts or references yet -- relies on SKILL.md workflows.
### Atlassian Templates
**Skill Location:** `../../project-management/atlassian-templates/`
Covers blueprint creation, custom page layouts, and reusable Confluence/Jira components. No scripts or references yet -- relies on SKILL.md workflows.
## Workflows
### Workflow 1: Sprint Planning and Execution
**Goal:** Plan a sprint with data-driven capacity, clear backlog priorities, and documented sprint goals published to Confluence.
**Steps:**
1. **Analyze Velocity History** - Review past sprint performance to set realistic capacity:
```bash
python ../../project-management/scrum-master/scripts/velocity_analyzer.py sprint_history.json
```
- Review rolling average velocity and standard deviation
- Identify trends (accelerating, decelerating, stable)
- Set sprint capacity at 80% of average velocity (buffer for unknowns)
2. **Query Backlog via JQL** - Use jira-expert JQL patterns to pull prioritized candidates:
- Reference: `../../project-management/jira-expert/references/jql-examples.md`
- Filter by priority, story points estimated, team assignment
- Identify blocked items, external dependencies, carry-overs from previous sprint
3. **Check Resource Availability** - Verify team capacity for the sprint window:
```bash
python ../../project-management/senior-pm/scripts/resource_capacity_planner.py team_data.json
```
- Account for PTO, holidays, shared resources
- Flag over-allocated team members
- Adjust sprint capacity based on actual availability
4. **Select Sprint Backlog** - Commit items within capacity:
- Apply WSJF or priority-based selection (ref: `../../project-management/senior-pm/references/portfolio-prioritization-models.md`)
- Ensure sprint goal alignment -- every item should contribute to 1-2 goals
- Include 10-15% capacity for bug fixes and operational work
5. **Document Sprint Plan** - Create Confluence sprint plan page:
- Use template from `../../project-management/confluence-expert/references/templates.md`
- Include sprint goal, committed stories, capacity breakdown, risks
- Link to Jira sprint board for live tracking
6. **Set Up Sprint Tracking** - Configure dashboards and automation:
- Create burndown/burnup dashboard (ref: `../../project-management/jira-expert/references/AUTOMATION.md`)
- Set up daily standup reminder automation
- Configure sprint scope change alerts
**Expected Output:** Sprint plan Confluence page with committed backlog, velocity-based capacity justification, team availability matrix, and linked Jira sprint board.
**Time Estimate:** 2-4 hours for complete sprint planning session (including backlog refinement)
**Example:**
```bash
# Full sprint planning workflow
python ../../project-management/scrum-master/scripts/velocity_analyzer.py sprint_history.json > velocity_report.txt
python ../../project-management/senior-pm/scripts/resource_capacity_planner.py team_data.json > capacity_report.txt
cat velocity_report.txt
cat capacity_report.txt
# Use velocity average and capacity data to commit sprint items
```
### Workflow 2: Portfolio Health Review
**Goal:** Generate an executive-level portfolio health dashboard with RAG status, risk exposure, and resource utilization across all active projects.
**Steps:**
1. **Collect Project Data** - Gather metrics from all active projects:
- Schedule performance (planned vs actual milestones)
- Budget consumption (actual vs forecast)
- Scope changes (CRs approved, backlog growth)
- Quality metrics (defect rates, test coverage)
2. **Generate Health Dashboard** - Run project health analysis:
```bash
python ../../project-management/senior-pm/scripts/project_health_dashboard.py portfolio_data.json
```
- Review per-project RAG status (Red/Amber/Green)
- Identify projects requiring intervention
- Track schedule and budget variance percentages
3. **Analyze Risk Exposure** - Quantify portfolio-level risk:
```bash
python ../../project-management/senior-pm/scripts/risk_matrix_analyzer.py portfolio_risks.json
```
- Calculate EMV for each risk
- Identify top-10 risks by exposure
- Review mitigation plan progress
- Flag risks with no assigned owner
4. **Review Resource Utilization** - Check cross-project allocation:
```bash
python ../../project-management/senior-pm/scripts/resource_capacity_planner.py all_teams.json
```
- Identify over-allocated individuals (>100% utilization)
- Find under-utilized capacity for rebalancing
- Forecast resource needs for next quarter
5. **Prepare Executive Report** - Assemble findings into report:
- Use template: `../../project-management/senior-pm/assets/executive_report_template.md`
- Include RAG summary, risk heatmap, resource utilization chart
- Highlight decisions needed from leadership
- Provide recommendations with supporting data
6. **Publish to Confluence** - Create executive dashboard page:
- Reference KPI definitions from `../../project-management/senior-pm/references/portfolio-kpis.md`
- Embed Jira macros for live data
- Set up weekly refresh cadence
**Expected Output:** Executive portfolio dashboard with per-project RAG status, top risks with EMV, resource utilization heatmap, and leadership decision requests.
**Time Estimate:** 3-5 hours for complete portfolio review (monthly cadence recommended)
**Example:**
```bash
# Portfolio health review automation
python ../../project-management/senior-pm/scripts/project_health_dashboard.py portfolio_data.json > health_dashboard.txt
python ../../project-management/senior-pm/scripts/risk_matrix_analyzer.py portfolio_risks.json > risk_report.txt
python ../../project-management/senior-pm/scripts/resource_capacity_planner.py all_teams.json > resource_report.txt
cat health_dashboard.txt
cat risk_report.txt
cat resource_report.txt
```
### Workflow 3: Retrospective and Continuous Improvement
**Goal:** Facilitate a structured retrospective, extract actionable themes, track improvement metrics, and ensure action items drive measurable change.
**Steps:**
1. **Gather Sprint Metrics** - Collect quantitative data before the retro:
```bash
python ../../project-management/scrum-master/scripts/sprint_health_scorer.py sprint_data.json
```
- Review sprint health score (0-100)
- Identify scoring dimensions that dropped (scope, velocity, quality, morale)
- Compare against previous sprint scores for trend analysis
2. **Select Retro Format** - Choose format based on team needs:
- Reference: `../../project-management/scrum-master/references/retro-formats.md`
- **Start/Stop/Continue**: General-purpose, good for new teams
- **4Ls (Liked/Learned/Lacked/Longed For)**: Focuses on learning and growth
- **Sailboat**: Visual metaphor for anchors (blockers) and wind (accelerators)
- **Mad/Sad/Glad**: Emotion-focused, good for addressing team morale
- **Starfish**: Five categories for nuanced feedback
3. **Facilitate Retrospective** - Run the session:
- Present sprint metrics as context (not judgment)
- Time-box each section (5 min brainstorm, 10 min discuss, 5 min vote)
- Use dot voting to prioritize discussion topics
- Reference team dynamics from `../../project-management/scrum-master/references/team-dynamics-framework.md`
4. **Analyze Retro Output** - Extract structured insights:
```bash
python ../../project-management/scrum-master/scripts/retrospective_analyzer.py retro_notes.json
```
- Identify recurring themes across sprints
- Cluster related items into improvement areas
- Track action item completion from previous retros
5. **Create Action Items** - Convert insights to trackable work:
- Limit to 2-3 action items per sprint (avoid overcommitment)
- Assign clear owners and due dates
- Create Jira tickets for process improvements
- Add action items to next sprint backlog
6. **Document in Confluence** - Publish retro summary:
- Use sprint report template: `../../project-management/scrum-master/assets/sprint_report_template.md`
- Include sprint health score, retro themes, action items, metrics trends
- Link to previous retro pages for longitudinal tracking
7. **Track Improvement Over Time** - Measure continuous improvement:
- Compare sprint health scores quarter-over-quarter
- Track action item completion rate (target: >80%)
- Monitor velocity stability as proxy for process maturity
**Expected Output:** Retro summary with prioritized themes, 2-3 owned action items with Jira tickets, sprint health trend chart, and Confluence documentation.
**Time Estimate:** 1.5-2 hours (30 min prep + 60 min retro + 30 min documentation)
**Example:**
```bash
# Pre-retro data collection
python ../../project-management/scrum-master/scripts/sprint_health_scorer.py sprint_data.json > health_score.txt
python ../../project-management/scrum-master/scripts/velocity_analyzer.py sprint_history.json > velocity_trend.txt
cat health_score.txt
# Use health score insights to guide retro discussion
python ../../project-management/scrum-master/scripts/retrospective_analyzer.py retro_notes.json > retro_analysis.txt
cat retro_analysis.txt
```
### Workflow 4: Jira/Confluence Setup for New Teams
**Goal:** Stand up a complete Atlassian environment for a new team including Jira project, workflows, automation, Confluence space, and templates.
**Steps:**
1. **Define Team Process** - Map the team's delivery methodology:
- Scrum vs Kanban vs Scrumban
- Issue types needed (Epic, Story, Task, Bug, Spike)
- Custom fields required (team, component, environment)
- Workflow states matching actual process
2. **Create Jira Project** - Set up project structure:
- Select project template (Scrum board, Kanban board, Company-managed)
- Configure issue type scheme with required types
- Set up components and versions
- Define priority scheme and SLA targets
3. **Design Workflows** - Build workflows matching team process:
- Reference: `../../project-management/jira-expert/references/WORKFLOWS.md`
- Map states: Backlog > Ready > In Progress > Review > QA > Done
- Add transitions with conditions (e.g., assignee required for In Progress)
- Configure validators (e.g., story points required before Done)
- Set up post-functions (e.g., auto-assign reviewer, notify channel)
4. **Configure Automation** - Set up time-saving automation rules:
- Reference: `../../project-management/jira-expert/references/AUTOMATION.md`
- Examples from: `../../project-management/jira-expert/references/automation-examples.md`
- Auto-transition: Move to In Progress when branch created
- Auto-assign: Rotate assignments based on workload
- Notifications: Slack alerts for blocked items, SLA breaches
- Cleanup: Auto-close stale items after 30 days
5. **Set Up Confluence Space** - Create team knowledge base:
- Reference: `../../project-management/confluence-expert/references/templates.md`
- Create space with standard page hierarchy:
- Home (team overview, quick links)
- Sprint Plans (per-sprint documentation)
- Meeting Notes (standup, planning, retro)
- Decision Log (ADRs, trade-off decisions)
- Runbooks (operational procedures)
- Link Confluence space to Jira project
6. **Create Dashboards** - Build visibility for team and stakeholders:
- Sprint board with swimlanes by assignee
- Burndown/burnup chart gadget
- Velocity chart for historical tracking
- SLA compliance tracker
- Use JQL patterns from `../../project-management/jira-expert/references/jql-examples.md`
7. **Onboard Team** - Walk team through the setup:
- Document workflow rules and why they exist
- Create quick-reference guide for common Jira operations
- Run a pilot sprint to validate configuration
- Iterate on feedback within first 2 sprints
**Expected Output:** Fully configured Jira project with custom workflows and automation, Confluence space with page hierarchy and templates, team dashboards, and onboarding documentation.
**Time Estimate:** 1-2 days for complete environment setup (excluding pilot sprint)
## Integration Examples
### Example 1: Weekly Project Status Report
```bash
#!/bin/bash
# weekly-status.sh - Automated weekly project status generation
echo "Weekly Project Status - $(date +%Y-%m-%d)"
echo "============================================"
# Sprint health assessment
echo ""
echo "Sprint Health:"
python ../../project-management/scrum-master/scripts/sprint_health_scorer.py current_sprint.json
# Velocity trend
echo ""
echo "Velocity Trend:"
python ../../project-management/scrum-master/scripts/velocity_analyzer.py sprint_history.json
# Risk exposure
echo ""
echo "Active Risks:"
python ../../project-management/senior-pm/scripts/risk_matrix_analyzer.py active_risks.json
# Resource utilization
echo ""
echo "Team Capacity:"
python ../../project-management/senior-pm/scripts/resource_capacity_planner.py team_data.json
```
### Example 2: Sprint Retrospective Pipeline
```bash
#!/bin/bash
# retro-pipeline.sh - End-of-sprint analysis pipeline
SPRINT_NUM=$1
echo "Sprint $SPRINT_NUM Retrospective Pipeline"
echo "=========================================="
# Step 1: Score sprint health
echo ""
echo "1. Sprint Health Score:"
python ../../project-management/scrum-master/scripts/sprint_health_scorer.py sprint_${SPRINT_NUM}.json > sprint_health.txt
cat sprint_health.txt
# Step 2: Analyze velocity trend
echo ""
echo "2. Velocity Analysis:"
python ../../project-management/scrum-master/scripts/velocity_analyzer.py velocity_history.json > velocity.txt
cat velocity.txt
# Step 3: Process retro notes
echo ""
echo "3. Retrospective Themes:"
python ../../project-management/scrum-master/scripts/retrospective_analyzer.py retro_sprint_${SPRINT_NUM}.json > retro_analysis.txt
cat retro_analysis.txt
echo ""
echo "Pipeline complete. Review outputs above for retro facilitation."
```
### Example 3: Portfolio Dashboard Generation
```bash
#!/bin/bash
# portfolio-dashboard.sh - Monthly executive portfolio review
MONTH=$(date +%Y-%m)
echo "Portfolio Dashboard - $MONTH"
echo "================================"
# Project health across portfolio
echo ""
echo "Project Health (All Active):"
python ../../project-management/senior-pm/scripts/project_health_dashboard.py portfolio_$MONTH.json > dashboard.txt
cat dashboard.txt
# Risk heatmap
echo ""
echo "Risk Exposure Summary:"
python ../../project-management/senior-pm/scripts/risk_matrix_analyzer.py risks_$MONTH.json > risks.txt
cat risks.txt
# Resource forecast
echo ""
echo "Resource Utilization:"
python ../../project-management/senior-pm/scripts/resource_capacity_planner.py resources_$MONTH.json > capacity.txt
cat capacity.txt
echo ""
echo "Dashboard generated. Use executive_report_template.md to assemble final report."
echo "Template: ../../project-management/senior-pm/assets/executive_report_template.md"
```
## Success Metrics
**Sprint Delivery:**
- **Velocity Stability:** Standard deviation <15% of average velocity over 6 sprints
- **Sprint Goal Achievement:** >85% of sprint goals fully met
- **Scope Change Rate:** <10% of committed stories changed mid-sprint
- **Carry-Over Rate:** <5% of committed stories carry over to next sprint
**Portfolio Health:**
- **On-Time Delivery:** >80% of milestones hit within 1 week of target
- **Budget Variance:** <10% deviation from approved budget
- **Risk Mitigation:** >90% of identified risks have assigned owners and active mitigation plans
- **Resource Utilization:** 75-85% utilization (avoiding burnout while maximizing throughput)
**Process Improvement:**
- **Retro Action Completion:** >80% of action items completed within 2 sprints
- **Sprint Health Trend:** Positive quarter-over-quarter sprint health score trend
- **Cycle Time Reduction:** 15%+ reduction in average story cycle time over 6 months
- **Team Satisfaction:** Health check scores stable or improving across all dimensions
**Stakeholder Communication:**
- **Report Cadence:** 100% on-time delivery of weekly/monthly status reports
- **Decision Turnaround:** <3 days from escalation to leadership decision
- **Stakeholder Confidence:** >90% satisfaction in quarterly PM effectiveness surveys
- **Transparency:** All project data accessible via self-service dashboards
## Related Agents
- [cs-product-manager](../product/cs-product-manager.md) -- Product prioritization with RICE, customer discovery, PRD development
- [cs-agile-product-owner](../product/cs-agile-product-owner.md) -- User story generation, backlog management, acceptance criteria (planned)
- [cs-scrum-master](cs-scrum-master.md) -- Dedicated Scrum ceremony facilitation and team coaching (planned)
## References
- **Senior PM Skill:** [../../project-management/senior-pm/SKILL.md](../../project-management/senior-pm/SKILL.md)
- **Scrum Master Skill:** [../../project-management/scrum-master/SKILL.md](../../project-management/scrum-master/SKILL.md)
- **Jira Expert Skill:** [../../project-management/jira-expert/SKILL.md](../../project-management/jira-expert/SKILL.md)
- **Confluence Expert Skill:** [../../project-management/confluence-expert/SKILL.md](../../project-management/confluence-expert/SKILL.md)
- **Atlassian Admin Skill:** [../../project-management/atlassian-admin/SKILL.md](../../project-management/atlassian-admin/SKILL.md)
- **PM Domain Guide:** [../../project-management/CLAUDE.md](../../project-management/CLAUDE.md)
- **Agent Development Guide:** [../CLAUDE.md](../CLAUDE.md)
---
**Last Updated:** March 9, 2026
**Version:** 2.0
**Status:** Production Ready

16
agents/ra-qm-team/cs-quality-regulatory.md
View File

@@ -1,6 +1,10 @@
---
name: cs-quality-regulatory
description: Quality & Regulatory agent for ISO 13485 QMS, MDR compliance, FDA submissions, GDPR/DSGVO, and ISMS audits. Orchestrates ra-qm-team skills. Spawn when users need regulatory strategy, audit preparation, CAPA management, risk management, or compliance documentation.
skills: ra-qm-team
domain: ra-qm
model: sonnet
tools: [Read, Write, Bash, Grep, Glob]
---
# cs-quality-regulatory
@@ -68,3 +72,15 @@ Regulatory affairs and quality management specialist for medical device and heal
- Technical files → structured per Annex II/III with cross-references
- CAPAs → ISO 13485 Section 8.5.2/8.5.3 compliant format
- All outputs traceable to regulatory requirements
## Success Metrics
- **Audit Readiness:** Zero critical findings in external audits (ISO 13485, ISO 27001)
- **CAPA Effectiveness:** 95%+ of CAPAs closed within target timeline with verified effectiveness
- **Regulatory Submission Success:** First-time acceptance rate >90% for MDR/FDA submissions
- **Compliance Coverage:** 100% of processing activities documented with valid legal basis (GDPR)
## Related Agents
- [cs-engineering-lead](../engineering-team/cs-engineering-lead.md) -- Engineering process alignment for design controls and software validation
- [cs-product-manager](../product/cs-product-manager.md) -- Product requirements traceability and risk-benefit analysis coordination

2
business-growth/.claude-plugin/plugin.json
View File

@@ -1,7 +1,7 @@
{
"name": "business-growth-skills",
"description": "4 business & growth skills: customer success manager, sales engineer, revenue operations, and contract & proposal writer",
"version": "2.1.1",
"version": "2.1.2",
"author": {
"name": "Alireza Rezvani",
"url": "https://alirezarezvani.com"

2
c-level-advisor/.claude-plugin/plugin.json
View File

@@ -1,7 +1,7 @@
{
"name": "c-level-skills",
"description": "28 C-level advisory skills: complete virtual board of directors with CEO, CTO, COO, CPO, CMO, CFO, CRO, CISO, CHRO advisors, executive mentor, founder coach, Chief of Staff router, board meetings, decision logger, board deck builder, scenario war room, competitive intel, org health diagnostic, M&A playbook, international expansion, culture architect, change management, strategic alignment, and more",
"version": "2.1.1",
"version": "2.1.2",
"author": {
"name": "Alireza Rezvani",
"url": "https://alirezarezvani.com"

4
c-level-advisor/coo-advisor/scripts/ops_efficiency_analyzer.py
View File

@@ -18,7 +18,7 @@ import sys
import argparse
import math
from datetime import datetime
from typing import Any
from typing import Any, Optional
# ---------------------------------------------------------------------------
@@ -458,7 +458,7 @@ def _dept_revenue_benchmark(dept_name: str, stage: str) -> int:
return stage_data.get(dept_key, stage_data["default"])
def _efficiency_status(efficiency_pct: float | None) -> str:
def _efficiency_status(efficiency_pct: Optional[float]) -> str:
if efficiency_pct is None:
return "N/A"
if efficiency_pct >= 90:

60
c-level-advisor/cto-advisor/scripts/team_scaling_calculator.py
View File

@@ -323,8 +323,30 @@ class TeamScalingCalculator:
'designer': 120000,
'data_engineer': 140000
},
'EU': {k: v * 0.8 for k, v in salary_bands.get('US', {}).items()},
'APAC': {k: v * 0.6 for k, v in salary_bands.get('US', {}).items()}
'EU': {
'engineering_manager': 160000,
'tech_lead': 144000,
'senior_engineer': 128000,
'mid_engineer': 96000,
'junior_engineer': 68000,
'devops': 120000,
'qa': 80000,
'product_manager': 120000,
'designer': 96000,
'data_engineer': 112000
},
'APAC': {
'engineering_manager': 120000,
'tech_lead': 108000,
'senior_engineer': 96000,
'mid_engineer': 72000,
'junior_engineer': 51000,
'devops': 90000,
'qa': 60000,
'product_manager': 90000,
'designer': 72000,
'data_engineer': 84000
}
}
location_salaries = salary_bands.get(location, salary_bands['US'])
@@ -493,8 +515,28 @@ def calculate_team_scaling(current_state: Dict, growth_targets: Dict) -> str:
return '\n'.join(output)
if __name__ == "__main__":
# Example usage
example_current = {
import argparse
parser = argparse.ArgumentParser(
description="Engineering Team Scaling Calculator - Optimize team growth and structure"
)
parser.add_argument(
"input_file", nargs="?", default=None,
help="JSON file with current_state and growth_targets (default: run with sample data)"
)
parser.add_argument(
"--json", action="store_true",
help="Output raw JSON instead of formatted report"
)
args = parser.parse_args()
if args.input_file:
with open(args.input_file) as f:
data = json.load(f)
current_state = data["current_state"]
growth_targets = data["growth_targets"]
else:
current_state = {
'headcount': 25,
'velocity': 450,
'roles': {
@@ -507,10 +549,14 @@ if __name__ == "__main__":
'attrition_rate': 12,
'location': 'US'
}
example_targets = {
growth_targets = {
'target_headcount': 75,
'timeline_quarters': 4
}
print(calculate_team_scaling(example_current, example_targets))
if args.json:
calculator = TeamScalingCalculator()
results = calculator.calculate_scaling_plan(current_state, growth_targets)
print(json.dumps(results, indent=2))
else:
print(calculate_team_scaling(current_state, growth_targets))

14
commands/changelog.md
View File

@@ -10,21 +10,21 @@ Generate Keep a Changelog entries from git history and validate commit message f
## Usage
```
/changelog generate [--from <tag>] [--to HEAD] Generate changelog entries
/changelog lint [--range <from>..<to>] Lint commit messages
/changelog generate [--from-tag <tag>] [--to-tag <tag>] Generate changelog entries
/changelog lint [--from-ref <ref>] [--to-ref <ref>] Lint commit messages
```
## Examples
```
/changelog generate --from v2.0.0
/changelog lint --range main..dev
/changelog generate --from v2.0.0 --to v2.1.0 --format markdown
/changelog generate --from-tag v2.0.0
/changelog lint --from-ref main --to-ref dev
/changelog generate --from-tag v2.0.0 --to-tag v2.1.0 --format markdown
```
## Scripts
- `engineering/changelog-generator/scripts/generate_changelog.py` — Parse commits, render changelog
- `engineering/changelog-generator/scripts/commit_linter.py` — Validate conventional commit format
- `engineering/changelog-generator/scripts/generate_changelog.py` — Parse commits, render changelog (`--from-tag`, `--to-tag`, `--from-ref`, `--to-ref`, `--format markdown|json`)
- `engineering/changelog-generator/scripts/commit_linter.py` — Validate conventional commit format (`--from-ref`, `--to-ref`, `--strict`, `--format text|json`)
## Skill Reference
→ `engineering/changelog-generator/SKILL.md`

37
commands/okr.md Normal file
View File

@@ -0,0 +1,37 @@
---
name: okr
description: Generate OKR cascades from company strategy to team objectives. Usage: /okr generate <strategy>
---
# /okr
Generate cascaded OKR frameworks from company-level strategy down to team-level key results.
## Usage
```
/okr generate <strategy> Generate OKR cascade
```
Supported strategies: `growth`, `retention`, `revenue`, `innovation`, `operational`
## Input Format
Pass a strategy keyword directly. The generator produces company, department, and team-level OKRs aligned to the chosen strategy.
## Examples
```
/okr generate growth
/okr generate retention
/okr generate revenue
/okr generate innovation
/okr generate operational
/okr generate growth --json
```
## Scripts
- `product-team/product-strategist/scripts/okr_cascade_generator.py` — OKR cascade generator (`<strategy> [--teams "A,B,C"] [--contribution 0.3] [--json]`)
## Skill Reference
> `product-team/product-strategist/SKILL.md`

40
commands/persona.md Normal file
View File

@@ -0,0 +1,40 @@
---
name: persona
description: Generate data-driven user personas for UX research and product design. Usage: /persona generate [options]
---
# /persona
Generate structured user personas with demographics, goals, pain points, and behavioral patterns.
## Usage
```
/persona generate Generate persona (interactive)
/persona generate json Generate persona as JSON
```
## Input Format
Interactive mode prompts for product context. Alternatively, provide context inline:
```
/persona generate
> Product: B2B project management tool
> Target: Engineering managers at mid-size companies
> Key problem: Cross-team visibility
```
## Examples
```
/persona generate
/persona generate json
/persona generate json > persona-eng-manager.json
```
## Scripts
- `product-team/ux-researcher-designer/scripts/persona_generator.py` — Persona generator (positional `json` arg for JSON output)
## Skill Reference
> `product-team/ux-researcher-designer/SKILL.md`

14
commands/pipeline.md
View File

@@ -10,21 +10,21 @@ Detect project stack and generate CI/CD pipeline configurations for GitHub Actio
## Usage
```
/pipeline detect [<project-dir>] Detect stack, tools, and services
/pipeline generate [--platform github|gitlab] Generate pipeline YAML
/pipeline detect [--repo <project-dir>] Detect stack, tools, and services
/pipeline generate --platform github|gitlab [--repo <project-dir>] Generate pipeline YAML
```
## Examples
```
/pipeline detect ./my-project
/pipeline generate --platform github
/pipeline generate --platform gitlab --stages build,test,deploy
/pipeline detect --repo ./my-project
/pipeline generate --platform github --repo .
/pipeline generate --platform gitlab --repo .
```
## Scripts
- `engineering/ci-cd-pipeline-builder/scripts/stack_detector.py` — Detect stack and tooling
- `engineering/ci-cd-pipeline-builder/scripts/pipeline_generator.py` — Generate pipeline YAML
- `engineering/ci-cd-pipeline-builder/scripts/stack_detector.py` — Detect stack and tooling (`--repo <path>`, `--format text|json`)
- `engineering/ci-cd-pipeline-builder/scripts/pipeline_generator.py` — Generate pipeline YAML (`--platform github|gitlab`, `--repo <path>`, `--input <stack.json>`, `--output <file>`)
## Skill Reference
→ `engineering/ci-cd-pipeline-builder/SKILL.md`

43
commands/project-health.md Normal file
View File

@@ -0,0 +1,43 @@
---
name: project-health
description: Portfolio health dashboard and risk matrix analysis. Usage: /project-health <dashboard|risk> [options]
---
# /project-health
Generate portfolio health dashboards and risk matrices for project oversight.
## Usage
```
/project-health dashboard <project_data.json> Portfolio health dashboard
/project-health risk <risk_data.json> Risk matrix analysis
```
## Input Format
```json
{
"project_name": "Platform Rewrite",
"schedule": {"planned_end": "2026-06-30", "projected_end": "2026-07-15", "milestones_hit": 4, "milestones_total": 6},
"budget": {"allocated": 500000, "spent": 320000, "forecast": 520000},
"scope": {"features_planned": 40, "features_delivered": 28, "change_requests": 3},
"quality": {"defect_rate": 0.05, "test_coverage": 0.82},
"risks": [{"description": "Key engineer leaving", "probability": 0.3, "impact": 0.8}]
}
```
## Examples
```
/project-health dashboard portfolio-q2.json
/project-health risk risk-register.json
/project-health dashboard portfolio-q2.json --format json
```
## Scripts
- `project-management/senior-pm/scripts/project_health_dashboard.py` — Health dashboard (`<data_file> [--format text|json]`)
- `project-management/senior-pm/scripts/risk_matrix_analyzer.py` — Risk matrix analyzer (`<data_file> [--format text|json]`)
## Skill Reference
> `project-management/senior-pm/SKILL.md`

42
commands/retro.md Normal file
View File

@@ -0,0 +1,42 @@
---
name: retro
description: Analyze sprint retrospectives for patterns and action item tracking. Usage: /retro analyze <retro_data.json>
---
# /retro
Analyze retrospective data for recurring themes, sentiment trends, and action item effectiveness.
## Usage
```
/retro analyze <retro_data.json> Full retrospective analysis
```
## Input Format
```json
{
"sprint_name": "Sprint 24",
"went_well": ["CI pipeline improvements", "Pair programming sessions"],
"improvements": ["Too many meetings", "Flaky integration tests"],
"action_items": [
{"description": "Reduce standup to 10 min", "owner": "SM", "status": "done"},
{"description": "Fix flaky tests", "owner": "QA Lead", "status": "in_progress"}
],
"participants": 8
}
```
## Examples
```
/retro analyze sprint-24-retro.json
/retro analyze sprint-24-retro.json --format json
```
## Scripts
- `project-management/scrum-master/scripts/retrospective_analyzer.py` — Retrospective analyzer (`<data_file> [--format text|json]`)
## Skill Reference
> `project-management/scrum-master/SKILL.md`

39
commands/rice.md Normal file
View File

@@ -0,0 +1,39 @@
---
name: rice
description: RICE feature prioritization with scoring and capacity planning. Usage: /rice prioritize <features.csv> [options]
---
# /rice
Prioritize features using RICE scoring (Reach, Impact, Confidence, Effort) with optional capacity constraints.
## Usage
```
/rice prioritize <features.csv> Score and rank features
/rice prioritize <features.csv> --capacity 20 Rank with effort capacity limit
```
## Input Format
```csv
feature,reach,impact,confidence,effort
Dark mode,5000,2,0.8,3
API v2,12000,3,0.9,8
SSO integration,3000,2,0.7,5
Mobile app,20000,3,0.5,13
```
## Examples
```
/rice prioritize features.csv
/rice prioritize features.csv --capacity 20
/rice prioritize features.csv --output json
```
## Scripts
- `product-team/product-manager-toolkit/scripts/rice_prioritizer.py` — RICE prioritizer (`<input.csv> [--capacity N] [--output text|json|csv]`)
## Skill Reference
> `product-team/product-manager-toolkit/SKILL.md`

43
commands/sprint-health.md Normal file
View File

@@ -0,0 +1,43 @@
---
name: sprint-health
description: Sprint health scoring and velocity analysis for agile teams. Usage: /sprint-health <analyze|velocity> [options]
---
# /sprint-health
Score sprint health across delivery, quality, and team metrics with velocity trend analysis.
## Usage
```
/sprint-health analyze <sprint_data.json> Full sprint health score
/sprint-health velocity <sprint_data.json> Velocity trend analysis
```
## Input Format
```json
{
"sprint_name": "Sprint 24",
"committed_points": 34,
"completed_points": 29,
"stories": {"total": 12, "completed": 10, "carried_over": 2},
"blockers": [{"description": "API dependency", "days_blocked": 3}],
"ceremonies": {"planning": true, "daily": true, "review": true, "retro": true}
}
```
## Examples
```
/sprint-health analyze sprint-24.json
/sprint-health velocity last-6-sprints.json
/sprint-health analyze sprint-24.json --format json
```
## Scripts
- `project-management/scrum-master/scripts/sprint_health_scorer.py` — Sprint health scorer (`<data_file> [--format text|json]`)
- `project-management/scrum-master/scripts/velocity_analyzer.py` — Velocity analyzer (`<data_file> [--format text|json]`)
## Skill Reference
> `project-management/scrum-master/SKILL.md`

10
commands/tdd.md
View File

@@ -24,9 +24,13 @@ Generate tests, analyze coverage, and validate test quality using the TDD Guide
```
## Scripts
- `engineering-team/tdd-guide/scripts/test_generator.py` — Generate test cases
- `engineering-team/tdd-guide/scripts/coverage_analyzer.py` — Coverage analysis
- `engineering-team/tdd-guide/scripts/test_quality_checker.py` — Quality validation
- `engineering-team/tdd-guide/scripts/test_generator.py` — Test case generation (library module)
- `engineering-team/tdd-guide/scripts/coverage_analyzer.py` — Coverage analysis (library module)
- `engineering-team/tdd-guide/scripts/tdd_workflow.py` — TDD workflow orchestration (library module)
- `engineering-team/tdd-guide/scripts/fixture_generator.py` — Test fixture generation (library module)
- `engineering-team/tdd-guide/scripts/metrics_calculator.py` — TDD metrics calculation (library module)
> **Note:** These scripts are library modules without CLI entry points. Import them in Python or use via the SKILL.md workflow guidance.
## Skill Reference
→ `engineering-team/tdd-guide/SKILL.md`

18
commands/tech-debt.md
View File

@@ -1,6 +1,6 @@
---
name: tech-debt
description: Score, track, and prioritize technical debt. Usage: /tech-debt <scan|score|report> [options]
description: Scan, prioritize, and report technical debt. Usage: /tech-debt <scan|prioritize|report> [options]
---
# /tech-debt
@@ -11,24 +11,22 @@ Scan codebases for technical debt, score severity, and generate prioritized reme
```
/tech-debt scan <project-dir> Scan for debt indicators
/tech-debt score <project-dir> Calculate debt score (0-100)
/tech-debt report <project-dir> Full report with remediation plan
/tech-debt prioritize <inventory.json> Prioritize debt backlog
/tech-debt report <project-dir> Full dashboard with trends
```
## Examples
```
/tech-debt scan ./src
/tech-debt score . --format json
/tech-debt report . --output debt-report.md
/tech-debt scan . --format json
/tech-debt report . --format json --output debt-report.json
```
## Scripts
- `engineering/tech-debt-tracker/scripts/debt_scanner.py` — Detect debt patterns
- `engineering/tech-debt-tracker/scripts/debt_scorer.py` — Calculate severity scores
- `engineering/tech-debt-tracker/scripts/remediation_planner.py` — Generate fix plans
- `engineering/tech-debt-tracker/scripts/trend_tracker.py` — Track debt over time
- `engineering/tech-debt-tracker/scripts/cost_estimator.py` — Estimate remediation cost
- `engineering/tech-debt-tracker/scripts/debt_scanner.py` — Scan for debt patterns (`debt_scanner.py <directory> [--format json] [--output file]`)
- `engineering/tech-debt-tracker/scripts/debt_prioritizer.py` — Prioritize debt backlog (`debt_prioritizer.py <inventory.json> [--framework cost_of_delay|wsjf|rice] [--format json]`)
- `engineering/tech-debt-tracker/scripts/debt_dashboard.py` — Generate debt dashboard (`debt_dashboard.py [files...] [--input-dir dir] [--period weekly|monthly|quarterly] [--format json]`)
## Skill Reference
→ `engineering/tech-debt-tracker/SKILL.md`

43
commands/user-story.md Normal file
View File

@@ -0,0 +1,43 @@
---
name: user-story
description: Generate user stories with acceptance criteria and sprint planning. Usage: /user-story <generate|sprint> [options]
---
# /user-story
Generate structured user stories with acceptance criteria, story points, and sprint capacity planning.
## Usage
```
/user-story generate Generate user stories (interactive)
/user-story sprint <capacity> Plan sprint with story point capacity
```
## Input Format
Interactive mode prompts for feature context. For sprint planning, provide capacity as story points:
```
/user-story generate
> Feature: User authentication
> Persona: Engineering manager
> Epic: Platform Security
/user-story sprint 21
> Stories are ranked by priority and fit within 21-point capacity
```
## Examples
```
/user-story generate
/user-story sprint 34
/user-story sprint 21
```
## Scripts
- `product-team/agile-product-owner/scripts/user_story_generator.py` — User story generator (positional args: `sprint <capacity>`)
## Skill Reference
> `product-team/agile-product-owner/SKILL.md`

2
docs/getting-started.md
View File

@@ -99,7 +99,7 @@ AI-augmented development. Optimize for SEO.
## Python Tools
All 210+ tools use the standard library only — zero pip installs.
All 218+ tools use the standard library only — zero pip installs.
```bash
# Security audit a skill before installing

8
docs/index.md
View File

@@ -1,6 +1,6 @@
---
title: Claude Code Skills & Plugins
description: "170 production-ready skills and plugins for Claude Code, OpenAI Codex, and OpenClaw. Reusable expertise bundles for engineering, product, marketing, compliance, and more."
description: "177 production-ready skills and plugins for Claude Code, OpenAI Codex, and OpenClaw. Reusable expertise bundles for engineering, product, marketing, compliance, and more."
hide:
- toc
- edit
@@ -14,7 +14,7 @@ hide:
# Claude Code Skills
170 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** | **OpenClaw**
@@ -27,13 +27,13 @@ hide:
<div class="grid cards" markdown>
- :material-counter:{ .lg .middle } **170**
- :material-counter:{ .lg .middle } **177**
---
Production-ready skills
- :material-language-python:{ .lg .middle } **210+**
- :material-language-python:{ .lg .middle } **218+**
---

50
docs/skills/business-growth/business-growth.md Normal file
View File

@@ -0,0 +1,50 @@
---
title: "Business & Growth Skills"
description: "Business & Growth Skills - Claude Code skill from the Business & Growth domain."
---
# Business & Growth Skills
**Domain:** Business & Growth | **Skill:** `business-growth` | **Source:** [`business-growth/SKILL.md`](https://github.com/alirezarezvani/claude-skills/tree/main/business-growth/SKILL.md)
---
# Business & Growth Skills
4 production-ready skills for customer success, sales, and revenue operations.
## Quick Start
### Claude Code
```
/read business-growth/customer-success-manager/SKILL.md
```
### Codex CLI
```bash
npx agent-skills-cli add alirezarezvani/claude-skills/business-growth
```
## Skills Overview
| Skill | Folder | Focus |
|-------|--------|-------|
| Customer Success Manager | `customer-success-manager/` | Health scoring, churn prediction, expansion |
| Sales Engineer | `sales-engineer/` | RFP analysis, competitive matrices, PoC planning |
| Revenue Operations | `revenue-operations/` | Pipeline analysis, forecast accuracy, GTM metrics |
| Contract & Proposal Writer | `contract-and-proposal-writer/` | Proposal generation, contract templates |
## Python Tools
9 scripts, all stdlib-only:
```bash
python3 customer-success-manager/scripts/health_score_calculator.py --help
python3 revenue-operations/scripts/pipeline_analyzer.py --help
```
## Rules
- Load only the specific skill SKILL.md you need
- Use Python tools for scoring and metrics, not manual estimates

3
docs/skills/business-growth/index.md
View File

@@ -5,10 +5,11 @@ description: "All Business & Growth skills for Claude Code, OpenAI Codex, and Op
# Business & Growth Skills
4 skills in this domain.
5 skills in this domain.
| Skill | Description |
|-------|-------------|
| [Business & Growth Skills](business-growth.md) | `business-growth` |
| [Contract & Proposal Writer](contract-and-proposal-writer.md) | `contract-and-proposal-writer` |
| [Customer Success Manager](customer-success-manager.md) | `customer-success-manager` |
| [Revenue Operations](revenue-operations.md) | `revenue-operations` |

83
docs/skills/engineering-team/engineering-team.md Normal file
View File

@@ -0,0 +1,83 @@
---
title: "Engineering Team Skills"
description: "Engineering Team Skills - Claude Code skill from the Engineering - Core domain."
---
# Engineering Team Skills
**Domain:** Engineering - Core | **Skill:** `engineering-team` | **Source:** [`engineering-team/SKILL.md`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/SKILL.md)
---
# Engineering Team Skills
23 production-ready engineering skills organized into core engineering, AI/ML/Data, and specialized tools.
## Quick Start
### Claude Code
```
/read engineering-team/senior-fullstack/SKILL.md
```
### Codex CLI
```bash
npx agent-skills-cli add alirezarezvani/claude-skills/engineering-team
```
## Skills Overview
### Core Engineering (13 skills)
| Skill | Folder | Focus |
|-------|--------|-------|
| Senior Architect | `senior-architect/` | System design, architecture patterns |
| Senior Frontend | `senior-frontend/` | React, Next.js, TypeScript, Tailwind |
| Senior Backend | `senior-backend/` | API design, database optimization |
| Senior Fullstack | `senior-fullstack/` | Project scaffolding, code quality |
| Senior QA | `senior-qa/` | Test generation, coverage analysis |
| Senior DevOps | `senior-devops/` | CI/CD, infrastructure, containers |
| Senior SecOps | `senior-secops/` | Security operations, vulnerability management |
| Code Reviewer | `code-reviewer/` | PR review, code quality analysis |
| Senior Security | `senior-security/` | Threat modeling, STRIDE, penetration testing |
| AWS Solution Architect | `aws-solution-architect/` | Serverless, CloudFormation, cost optimization |
| MS365 Tenant Manager | `ms365-tenant-manager/` | Microsoft 365 administration |
| TDD Guide | `tdd-guide/` | Test-driven development workflows |
| Tech Stack Evaluator | `tech-stack-evaluator/` | Technology comparison, TCO analysis |
### AI/ML/Data (5 skills)
| Skill | Folder | Focus |
|-------|--------|-------|
| Senior Data Scientist | `senior-data-scientist/` | Statistical modeling, experimentation |
| Senior Data Engineer | `senior-data-engineer/` | Pipelines, ETL, data quality |
| Senior ML Engineer | `senior-ml-engineer/` | Model deployment, MLOps, LLM integration |
| Senior Prompt Engineer | `senior-prompt-engineer/` | Prompt optimization, RAG, agents |
| Senior Computer Vision | `senior-computer-vision/` | Object detection, segmentation |
### Specialized Tools (5 skills)
| Skill | Folder | Focus |
|-------|--------|-------|
| Playwright Pro | `playwright-pro/` | E2E testing (9 sub-skills) |
| Self-Improving Agent | `self-improving-agent/` | Memory curation (5 sub-skills) |
| Stripe Integration | `stripe-integration-expert/` | Payment integration, webhooks |
| Incident Commander | `incident-commander/` | Incident response workflows |
| Email Template Builder | `email-template-builder/` | HTML email generation |
## Python Tools
30+ scripts, all stdlib-only. Run directly:
```bash
python3 <skill>/scripts/<tool>.py --help
```
No pip install needed. Scripts include embedded samples for demo mode.
## Rules
- Load only the specific skill SKILL.md you need — don't bulk-load all 23
- Use Python tools for analysis and scaffolding, not manual judgment
- Check CLAUDE.md for tool usage examples and workflows

3
docs/skills/engineering-team/index.md
View File

@@ -5,13 +5,14 @@ description: "All Engineering - Core skills for Claude Code, OpenAI Codex, and O
# Engineering - Core Skills
37 skills in this domain.
38 skills in this domain.
| Skill | Description |
|-------|-------------|
| [AWS Solution Architect](aws-solution-architect.md) | `aws-solution-architect` |
| [Code Reviewer](code-reviewer.md) | `code-reviewer` |
| [Email Template Builder](email-template-builder.md) | `email-template-builder` |
| [Engineering Team Skills](engineering-team.md) | `engineering-team` |
| [Incident Commander Skill](incident-commander.md) | `incident-commander` |
| [Microsoft 365 Tenant Manager](ms365-tenant-manager.md) | `ms365-tenant-manager` |
| [Playwright Pro](playwright-pro.md) | `playwright-pro` |

62
docs/skills/engineering/engineering.md Normal file
View File

@@ -0,0 +1,62 @@
---
title: "Engineering Advanced Skills (POWERFUL Tier)"
description: "Engineering Advanced Skills (POWERFUL Tier) - Claude Code skill from the Engineering - POWERFUL domain."
---
# Engineering Advanced Skills (POWERFUL Tier)
**Domain:** Engineering - POWERFUL | **Skill:** `engineering` | **Source:** [`engineering/SKILL.md`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering/SKILL.md)
---
# Engineering Advanced Skills (POWERFUL Tier)
25 advanced engineering skills for complex architecture, automation, and platform operations.
## Quick Start
### Claude Code
```
/read engineering/agent-designer/SKILL.md
```
### Codex CLI
```bash
npx agent-skills-cli add alirezarezvani/claude-skills/engineering
```
## Skills Overview
| Skill | Folder | Focus |
|-------|--------|-------|
| Agent Designer | `agent-designer/` | Multi-agent architecture patterns |
| Agent Workflow Designer | `agent-workflow-designer/` | Workflow orchestration |
| API Design Reviewer | `api-design-reviewer/` | REST/GraphQL linting, breaking changes |
| API Test Suite Builder | `api-test-suite-builder/` | API test generation |
| Changelog Generator | `changelog-generator/` | Automated changelogs |
| CI/CD Pipeline Builder | `ci-cd-pipeline-builder/` | Pipeline generation |
| Codebase Onboarding | `codebase-onboarding/` | New dev onboarding guides |
| Database Designer | `database-designer/` | Schema design, migrations |
| Database Schema Designer | `database-schema-designer/` | ERD, normalization |
| Dependency Auditor | `dependency-auditor/` | Dependency security scanning |
| Env Secrets Manager | `env-secrets-manager/` | Secrets rotation, vault |
| Git Worktree Manager | `git-worktree-manager/` | Parallel branch workflows |
| Interview System Designer | `interview-system-designer/` | Hiring pipeline design |
| MCP Server Builder | `mcp-server-builder/` | MCP tool creation |
| Migration Architect | `migration-architect/` | System migration planning |
| Monorepo Navigator | `monorepo-navigator/` | Monorepo tooling |
| Observability Designer | `observability-designer/` | SLOs, alerts, dashboards |
| Performance Profiler | `performance-profiler/` | CPU, memory, load profiling |
| PR Review Expert | `pr-review-expert/` | Pull request analysis |
| RAG Architect | `rag-architect/` | RAG system design |
| Release Manager | `release-manager/` | Release orchestration |
| Runbook Generator | `runbook-generator/` | Operational runbooks |
| Skill Security Auditor | `skill-security-auditor/` | Skill vulnerability scanning |
| Skill Tester | `skill-tester/` | Skill quality evaluation |
| Tech Debt Tracker | `tech-debt-tracker/` | Technical debt management |
## Rules
- Load only the specific skill SKILL.md you need
- These are advanced skills — combine with engineering-team/ core skills as needed

3
docs/skills/engineering/index.md
View File

@@ -5,7 +5,7 @@ description: "All Engineering - POWERFUL skills for Claude Code, OpenAI Codex, a
# Engineering - POWERFUL Skills
25 skills in this domain.
26 skills in this domain.
| Skill | Description |
|-------|-------------|
@@ -19,6 +19,7 @@ description: "All Engineering - POWERFUL skills for Claude Code, OpenAI Codex, a
| [Database Designer - POWERFUL Tier Skill](database-designer.md) | `database-designer` |
| [Database Schema Designer](database-schema-designer.md) | `database-schema-designer` |
| [Dependency Auditor](dependency-auditor.md) | `dependency-auditor` |
| [Engineering Advanced Skills (POWERFUL Tier)](engineering.md) | `engineering` |
| [Env & Secrets Manager](env-secrets-manager.md) | `env-secrets-manager` |
| [Git Worktree Manager](git-worktree-manager.md) | `git-worktree-manager` |
| [Interview System Designer](interview-system-designer.md) | `interview-system-designer` |

49
docs/skills/finance/finance.md Normal file
View File

@@ -0,0 +1,49 @@
---
title: "Finance Skills"
description: "Finance Skills - Claude Code skill from the Finance domain."
---
# Finance Skills
**Domain:** Finance | **Skill:** `finance` | **Source:** [`finance/SKILL.md`](https://github.com/alirezarezvani/claude-skills/tree/main/finance/SKILL.md)
---
# Finance Skills
Production-ready financial analysis skill for strategic decision-making.
## Quick Start
### Claude Code
```
/read finance/financial-analyst/SKILL.md
```
### Codex CLI
```bash
npx agent-skills-cli add alirezarezvani/claude-skills/finance
```
## Skills Overview
| Skill | Folder | Focus |
|-------|--------|-------|
| Financial Analyst | `financial-analyst/` | Ratio analysis, DCF, budget variance, forecasting |
## Python Tools
4 scripts, all stdlib-only:
```bash
python3 financial-analyst/scripts/ratio_calculator.py --help
python3 financial-analyst/scripts/dcf_valuation.py --help
python3 financial-analyst/scripts/budget_variance_analyzer.py --help
python3 financial-analyst/scripts/forecast_builder.py --help
```
## Rules
- Load only the specific skill SKILL.md you need
- Always validate financial outputs against source data

3
docs/skills/finance/index.md
View File

@@ -5,8 +5,9 @@ description: "All Finance skills for Claude Code, OpenAI Codex, and OpenClaw."
# Finance Skills
1 skills in this domain.
2 skills in this domain.
| Skill | Description |
|-------|-------------|
| [Finance Skills](finance.md) | `finance` |
| [Financial Analyst Skill](financial-analyst.md) | `financial-analyst` |

5
docs/skills/product-team/agile-product-owner.md
View File

@@ -383,3 +383,8 @@ Story is complete when:
- [ ] Deployed to staging environment
- [ ] Product Owner accepted
- [ ] No critical bugs remaining
## Related Skills
- **Scrum Master** (`project-management/scrum-master/`) — Velocity data and sprint ceremonies complement backlog management
- **Product Manager Toolkit** (`product-team/product-manager-toolkit/`) — RICE prioritization feeds backlog ordering

17
docs/skills/product-team/competitive-teardown.md
View File

@@ -33,11 +33,11 @@ description: "Competitive Teardown - Claude Code skill from the Product domain."
Follow these steps in sequence to produce a complete teardown:
1. **Define competitors** — List 2–4 competitors to analyze. Confirm which is the primary focus.
2. **Collect data** — Use `DATA_COLLECTION.md` to gather raw signals from at least 3 sources per competitor (website, reviews, job postings, SEO, social).
2. **Collect data** — Use `references/data-collection-guide.md` to gather raw signals from at least 3 sources per competitor (website, reviews, job postings, SEO, social).
_Validation checkpoint: Before proceeding, confirm you have pricing data, at least 20 reviews, and job posting counts for each competitor._
3. **Score using rubric** — Apply the 12-dimension rubric below to produce a numeric scorecard for each competitor and your own product.
_Validation checkpoint: Every dimension should have a score and at least one supporting evidence note._
4. **Generate outputs** — Populate the templates in `TEMPLATES.md` (Feature Matrix, Pricing Analysis, SWOT, Positioning Map, UX Audit).
4. **Generate outputs** — Populate the templates in `references/analysis-templates.md` (Feature Matrix, Pricing Analysis, SWOT, Positioning Map, UX Audit).
5. **Build action plan** — Translate findings into the Action Items template (quick wins / medium-term / strategic).
6. **Package for stakeholders** — Assemble the Stakeholder Presentation using outputs from steps 3–5.
@@ -45,7 +45,7 @@ Follow these steps in sequence to produce a complete teardown:
## Data Collection Guide
> Full executable scripts for each source are in `DATA_COLLECTION.md`. Summaries of what to capture are below.
> Full executable scripts for each source are in `references/data-collection-guide.md`. Summaries of what to capture are below.
### 1. Website Analysis
@@ -92,7 +92,7 @@ SEO signals to capture:
### 5. Social Media Sentiment
Capture recent mentions via Twitter/X API v2, Reddit, or LinkedIn. Look for recurring praise, complaints, and feature requests. See `DATA_COLLECTION.md` for API query examples.
Capture recent mentions via Twitter/X API v2, Reddit, or LinkedIn. Look for recurring praise, complaints, and feature requests. See `references/data-collection-guide.md` for API query examples.
---
@@ -125,7 +125,7 @@ Apply this pattern to all 12 dimensions for each competitor.
## Templates
> Full template markdown is in `TEMPLATES.md`. Abbreviated reference below.
> Full template markdown is in `references/analysis-templates.md`. Abbreviated reference below.
### Feature Comparison Matrix
@@ -145,7 +145,7 @@ For each competitor: 3–5 bullets per quadrant (Strengths, Weaknesses, Opportun
### Positioning Map
2x2 axes (e.g., Simple ↔ Complex / Low Value ↔ High Value). Place each competitor and your product. Bubble size = market share or funding. See `TEMPLATES.md` for ASCII and editable versions.
2x2 axes (e.g., Simple ↔ Complex / Low Value ↔ High Value). Place each competitor and your product. Bubble size = market share or funding. See `references/analysis-templates.md` for ASCII and editable versions.
### UX Audit Checklist
@@ -171,3 +171,8 @@ Navigation: global search, keyboard shortcuts, in-app help.
5. **UX Highlights** — What they do better (3 bullets) vs. where we win (3 bullets)
6. **Voice of Customer** — Top 3 review complaints (quoted or paraphrased)
7. **Our Action Plan** — Quick wins, medium-term, strategic priorities; Appendix with raw data
## Related Skills
- **Product Strategist** (`product-team/product-strategist/`) — Competitive insights feed OKR and strategy planning
- **Landing Page Generator** (`product-team/landing-page-generator/`) — Competitive positioning informs landing page messaging

3
docs/skills/product-team/index.md
View File

@@ -5,7 +5,7 @@ description: "All Product skills for Claude Code, OpenAI Codex, and OpenClaw."
# Product Skills
8 skills in this domain.
9 skills in this domain.
| Skill | Description |
|-------|-------------|
@@ -14,6 +14,7 @@ description: "All Product skills for Claude Code, OpenAI Codex, and OpenClaw."
| [Landing Page Generator](landing-page-generator.md) | `landing-page-generator` |
| [Product Manager Toolkit](product-manager-toolkit.md) | `product-manager-toolkit` |
| [Product Strategist](product-strategist.md) | `product-strategist` |
| [Product Team Skills](product-team.md) | `product-team` |
| [SaaS Scaffolder](saas-scaffolder.md) | `saas-scaffolder` |
| [UI Design System](ui-design-system.md) | `ui-design-system` |
| [UX Researcher & Designer](ux-researcher-designer.md) | `ux-researcher-designer` |

5
docs/skills/product-team/product-strategist.md
View File

@@ -227,3 +227,8 @@ See `references/examples/sample_growth_okrs.json` for a complete example.
- Adjust contribution percentages based on team size
- Platform/Infrastructure teams often support all objectives
- Specialized teams (ML, Data) may only support relevant objectives
## Related Skills
- **Senior PM** (`project-management/senior-pm/`) — Portfolio management and risk analysis inform strategic planning
- **Competitive Teardown** (`product-team/competitive-teardown/`) — Competitive intelligence feeds product strategy

54
docs/skills/product-team/product-team.md Normal file
View File

@@ -0,0 +1,54 @@
---
title: "Product Team Skills"
description: "Product Team Skills - Claude Code skill from the Product domain."
---
# Product Team Skills
**Domain:** Product | **Skill:** `product-team` | **Source:** [`product-team/SKILL.md`](https://github.com/alirezarezvani/claude-skills/tree/main/product-team/SKILL.md)
---
# Product Team Skills
8 production-ready product skills covering product management, UX/UI design, and SaaS development.
## Quick Start
### Claude Code
```
/read product-team/product-manager-toolkit/SKILL.md
```
### Codex CLI
```bash
npx agent-skills-cli add alirezarezvani/claude-skills/product-team
```
## Skills Overview
| Skill | Folder | Focus |
|-------|--------|-------|
| Product Manager Toolkit | `product-manager-toolkit/` | RICE prioritization, customer discovery, PRDs |
| Agile Product Owner | `agile-product-owner/` | User stories, sprint planning, backlog |
| Product Strategist | `product-strategist/` | OKR cascades, market analysis, vision |
| UX Researcher Designer | `ux-researcher-designer/` | Personas, journey maps, usability testing |
| UI Design System | `ui-design-system/` | Design tokens, component docs, responsive |
| Competitive Teardown | `competitive-teardown/` | Systematic competitor analysis |
| Landing Page Generator | `landing-page-generator/` | Conversion-optimized pages |
| SaaS Scaffolder | `saas-scaffolder/` | Production SaaS boilerplate |
## Python Tools
9 scripts, all stdlib-only:
```bash
python3 product-manager-toolkit/scripts/rice_prioritizer.py --help
python3 product-strategist/scripts/okr_cascade_generator.py --help
```
## Rules
- Load only the specific skill SKILL.md you need
- Use Python tools for scoring and analysis, not manual judgment

5
docs/skills/product-team/ux-researcher-designer.md
View File

@@ -419,3 +419,8 @@ Detailed reference guides in `references/`:
- [ ] Findings include evidence
- [ ] Recommendations are actionable
- [ ] Priorities justified
## Related Skills
- **UI Design System** (`product-team/ui-design-system/`) — Research findings inform design system decisions
- **Product Manager Toolkit** (`product-team/product-manager-toolkit/`) — Customer interview analysis complements persona research

5
docs/skills/project-management/confluence-expert.md
View File

@@ -375,3 +375,8 @@ const example = "code here";
- Duplicate content
- Broken links
- Empty spaces
## Related Skills
- **Jira Expert** (`project-management/jira-expert/`) — Jira issue macros and linking complement Confluence docs
- **Atlassian Templates** (`project-management/atlassian-templates/`) — Template patterns for Confluence content creation

3
docs/skills/project-management/index.md
View File

@@ -5,7 +5,7 @@ description: "All Project Management skills for Claude Code, OpenAI Codex, and O
# Project Management Skills
6 skills in this domain.
7 skills in this domain.
| Skill | Description |
|-------|-------------|
@@ -13,5 +13,6 @@ description: "All Project Management skills for Claude Code, OpenAI Codex, and O
| [Atlassian Template & Files Creator Expert](atlassian-templates.md) | `atlassian-templates` |
| [Atlassian Confluence Expert](confluence-expert.md) | `confluence-expert` |
| [Atlassian Jira Expert](jira-expert.md) | `jira-expert` |
| [Project Management Skills](project-management.md) | `project-management` |
| [Scrum Master Expert](scrum-master.md) | `scrum-master` |
| [Senior Project Management Expert](senior-pm.md) | `senior-pm` |

5
docs/skills/project-management/jira-expert.md
View File

@@ -305,3 +305,8 @@ mcp jira create_filter --name "Open Blockers" --jql "priority = Blocker AND stat
- Configure sprint boards for Scrum Master
- Create documentation pages for Confluence Expert
- Support template creation for Template Creator
## Related Skills
- **Confluence Expert** (`project-management/confluence-expert/`) — Documentation complements Jira workflows
- **Atlassian Admin** (`project-management/atlassian-admin/`) — Permission and user management for Jira projects

52
docs/skills/project-management/project-management.md Normal file
View File

@@ -0,0 +1,52 @@
---
title: "Project Management Skills"
description: "Project Management Skills - Claude Code skill from the Project Management domain."
---
# Project Management Skills
**Domain:** Project Management | **Skill:** `project-management` | **Source:** [`project-management/SKILL.md`](https://github.com/alirezarezvani/claude-skills/tree/main/project-management/SKILL.md)
---
# Project Management Skills
6 production-ready project management skills with Atlassian MCP integration.
## Quick Start
### Claude Code
```
/read project-management/jira-expert/SKILL.md
```
### Codex CLI
```bash
npx agent-skills-cli add alirezarezvani/claude-skills/project-management
```
## Skills Overview
| Skill | Folder | Focus |
|-------|--------|-------|
| Senior PM | `senior-pm/` | Portfolio management, risk analysis, resource planning |
| Scrum Master | `scrum-master/` | Velocity forecasting, sprint health, retrospectives |
| Jira Expert | `jira-expert/` | JQL queries, workflows, automation, dashboards |
| Confluence Expert | `confluence-expert/` | Knowledge bases, page layouts, macros |
| Atlassian Admin | `atlassian-admin/` | User management, permissions, integrations |
| Atlassian Templates | `atlassian-templates/` | Blueprints, custom layouts, reusable content |
## Python Tools
6 scripts, all stdlib-only:
```bash
python3 senior-pm/scripts/project_health_dashboard.py --help
python3 scrum-master/scripts/velocity_analyzer.py --help
```
## Rules
- Load only the specific skill SKILL.md you need
- Use MCP tools for live Jira/Confluence operations when available

7
docs/skills/project-management/scrum-master.md
View File

@@ -210,4 +210,11 @@ Apply stage-specific facilitation (details in `references/team-dynamics-framewor
---
## Related Skills
- **Agile Product Owner** (`product-team/agile-product-owner/`) — User stories and backlog feed sprint planning
- **Senior PM** (`project-management/senior-pm/`) — Portfolio health context informs sprint priorities
---
*For deep framework references see `references/velocity-forecasting-guide.md` and `references/team-dynamics-framework.md`. For template assets see `assets/sprint_report_template.md` and `assets/team_health_check_template.md`.*

5
docs/skills/project-management/senior-pm.md
View File

@@ -408,3 +408,8 @@ Reference: `references/portfolio-kpis.md` for full definitions and measurement g
- Executive interview feedback on decision support quality
- Team feedback on process efficiency and effectiveness
- Customer impact assessment of portfolio decisions
## Related Skills
- **Product Strategist** (`product-team/product-strategist/`) — Product OKRs align with portfolio objectives
- **Scrum Master** (`project-management/scrum-master/`) — Sprint velocity data feeds project health dashboards

3
docs/skills/ra-qm-team/index.md
View File

@@ -5,7 +5,7 @@ description: "All Regulatory & Quality skills for Claude Code, OpenAI Codex, and
# Regulatory & Quality Skills
12 skills in this domain.
13 skills in this domain.
| Skill | Description |
|-------|-------------|
@@ -19,5 +19,6 @@ description: "All Regulatory & Quality skills for Claude Code, OpenAI Codex, and
| [Quality Documentation Manager](quality-documentation-manager.md) | `quality-documentation-manager` |
| [Senior Quality Manager Responsible Person (QMR)](quality-manager-qmr.md) | `quality-manager-qmr` |
| [Quality Manager - QMS ISO 13485 Specialist](quality-manager-qms-iso13485.md) | `quality-manager-qms-iso13485` |
| [Regulatory Affairs & Quality Management Skills](ra-qm-team.md) | `ra-qm-team` |
| [Head of Regulatory Affairs](regulatory-affairs-head.md) | `regulatory-affairs-head` |
| [Risk Management Specialist](risk-management-specialist.md) | `risk-management-specialist` |

58
docs/skills/ra-qm-team/ra-qm-team.md Normal file
View File

@@ -0,0 +1,58 @@
---
title: "Regulatory Affairs & Quality Management Skills"
description: "Regulatory Affairs & Quality Management Skills - Claude Code skill from the Regulatory & Quality domain."
---
# Regulatory Affairs & Quality Management Skills
**Domain:** Regulatory & Quality | **Skill:** `ra-qm-team` | **Source:** [`ra-qm-team/SKILL.md`](https://github.com/alirezarezvani/claude-skills/tree/main/ra-qm-team/SKILL.md)
---
# Regulatory Affairs & Quality Management Skills
12 production-ready compliance skills for HealthTech and MedTech organizations.
## Quick Start
### Claude Code
```
/read ra-qm-team/regulatory-affairs-head/SKILL.md
```
### Codex CLI
```bash
npx agent-skills-cli add alirezarezvani/claude-skills/ra-qm-team
```
## Skills Overview
| Skill | Folder | Focus |
|-------|--------|-------|
| Regulatory Affairs Head | `regulatory-affairs-head/` | FDA/MDR strategy, submissions |
| Quality Manager (QMR) | `quality-manager-qmr/` | QMS governance, management review |
| Quality Manager (ISO 13485) | `quality-manager-qms-iso13485/` | QMS implementation, doc control |
| Risk Management Specialist | `risk-management-specialist/` | ISO 14971, FMEA, risk files |
| CAPA Officer | `capa-officer/` | Root cause analysis, corrective actions |
| Quality Documentation Manager | `quality-documentation-manager/` | Document control, 21 CFR Part 11 |
| QMS Audit Expert | `qms-audit-expert/` | ISO 13485 internal audits |
| ISMS Audit Expert | `isms-audit-expert/` | ISO 27001 security audits |
| Information Security Manager | `information-security-manager-iso27001/` | ISMS implementation |
| MDR 745 Specialist | `mdr-745-specialist/` | EU MDR classification, CE marking |
| FDA Consultant | `fda-consultant-specialist/` | 510(k), PMA, QSR compliance |
| GDPR/DSGVO Expert | `gdpr-dsgvo-expert/` | Privacy compliance, DPIA |
## Python Tools
17 scripts, all stdlib-only:
```bash
python3 risk-management-specialist/scripts/risk_matrix_calculator.py --help
python3 gdpr-dsgvo-expert/scripts/gdpr_compliance_checker.py --help
```
## Rules
- Load only the specific skill SKILL.md you need
- Always verify compliance outputs against current regulations

2
engineering-team/.claude-plugin/plugin.json
View File

@@ -1,7 +1,7 @@
{
"name": "engineering-skills",
"description": "23 production-ready engineering skills: architecture, frontend, backend, fullstack, QA, DevOps, security, AI/ML, data engineering, Playwright (9 sub-skills), self-improving agent, Stripe integration, TDD guide, and more",
"version": "2.1.1",
"version": "2.1.2",
"author": {
"name": "Alireza Rezvani",
"url": "https://alirezarezvani.com"

2
engineering-team/code-reviewer/scripts/pr_analyzer.py
View File

@@ -455,7 +455,7 @@ def main():
help="Base branch for comparison (default: main)"
)
parser.add_argument(
"--head", "-h",
"--head",
default="HEAD",
help="Head branch/commit for comparison (default: HEAD)"
)

7
engineering-team/senior-data-engineer/scripts/pipeline_orchestrator.py
View File

@@ -15,7 +15,11 @@ Usage:
import os
import sys
import json
try:
import yaml
HAS_YAML = True
except ImportError:
HAS_YAML = False
import logging
import argparse
from pathlib import Path
@@ -774,7 +778,10 @@ Examples:
# Load config if provided
if args.config:
with open(args.config) as f:
if HAS_YAML:
config_data = yaml.safe_load(f)
else:
config_data = json.load(f)
config = PipelineConfig(**config_data)
else:
# Build config from arguments

2
engineering/.claude-plugin/plugin.json
View File

@@ -1,7 +1,7 @@
{
"name": "engineering-advanced-skills",
"description": "25 advanced engineering skills: agent designer, RAG architect, database designer, migration architect, observability designer, dependency auditor, release manager, API reviewer, CI/CD pipeline builder, MCP server builder, skill security auditor, performance profiler, and more",
"version": "2.1.1",
"version": "2.1.2",
"author": {
"name": "Alireza Rezvani",
"url": "https://alirezarezvani.com"

15
engineering/skill-tester/scripts/quality_scorer.py
View File

@@ -23,7 +23,22 @@ import sys
from datetime import datetime
from pathlib import Path
from typing import Dict, List, Any, Optional, Tuple
try:
import yaml
except ImportError:
# Minimal YAML subset: parse simple key: value frontmatter without pyyaml
class _YamlStub:
class YAMLError(Exception):
pass
@staticmethod
def safe_load(text):
result = {}
for line in text.strip().splitlines():
if ':' in line:
key, _, value = line.partition(':')
result[key.strip()] = value.strip()
return result if result else None
yaml = _YamlStub()
class QualityDimension:

15
engineering/skill-tester/scripts/skill_validator.py
View File

@@ -19,7 +19,22 @@ import ast
import json
import re
import sys
try:
import yaml
except ImportError:
# Minimal YAML subset: parse simple key: value frontmatter without pyyaml
class _YamlStub:
class YAMLError(Exception):
pass
@staticmethod
def safe_load(text):
result = {}
for line in text.strip().splitlines():
if ':' in line:
key, _, value = line.partition(':')
result[key.strip()] = value.strip()
return result if result else None
yaml = _YamlStub()
import datetime as dt
from pathlib import Path
from typing import Dict, List, Any, Optional, Tuple

2
finance/.claude-plugin/plugin.json
View File

@@ -1,7 +1,7 @@
{
"name": "finance-skills",
"description": "1 finance skill: financial analyst with ratio analysis, DCF valuation, budgeting, and forecasting. 4 Python automation tools",
"version": "2.1.1",
"version": "2.1.2",
"author": {
"name": "Alireza Rezvani",
"url": "https://alirezarezvani.com"

2
marketing-skill/.claude-plugin/plugin.json
View File

@@ -1,7 +1,7 @@
{
"name": "marketing-skills",
"description": "42 production-ready marketing skills across 7 pods: Content (copywriting, content strategy, content production), SEO (audits, schema markup, programmatic SEO, site architecture), CRO (A/B testing, forms, popups, signup flows, pricing, onboarding), Channels (email sequences, social media, paid ads, cold email), Growth (launch strategy, referral programs, free tools), Intelligence (competitor analysis, marketing psychology, analytics tracking), and Sales enablement",
"version": "2.1.1",
"version": "2.1.2",
"author": {
"name": "Alireza Rezvani",
"url": "https://alirezarezvani.com"

17
marketing-skill/ad-creative/scripts/ad_copy_validator.py
View File

@@ -416,12 +416,25 @@ SAMPLE_ADS = [
# ---------------------------------------------------------------------------
def main():
import argparse
parser = argparse.ArgumentParser(
description="Validates ad copy against platform specs. "
"Checks character counts, rejection triggers, and scores each ad 0-100."
)
parser.add_argument(
"file", nargs="?", default=None,
help="Path to a JSON file containing ad data. "
"If omitted, reads from stdin or runs embedded sample."
)
args = parser.parse_args()
# Load from file or stdin, else use sample
ads = None
if len(sys.argv) > 1:
if args.file:
try:
with open(sys.argv[1]) as f:
with open(args.file) as f:
data = json.load(f)
ads = data if isinstance(data, list) else [data]
except Exception as e:

23
marketing-skill/analytics-tracking/scripts/tracking_plan_generator.py
View File

@@ -352,18 +352,33 @@ def print_report(result, inputs):
def main():
if len(sys.argv) > 1 and sys.argv[1] != "--json":
with open(sys.argv[1]) as f:
import argparse
parser = argparse.ArgumentParser(
description="Tracking plan generator — produces event taxonomy, GTM config, and GA4 dimension recommendations."
)
parser.add_argument(
"input_file", nargs="?", default=None,
help="JSON file with business config (default: run with sample SaaS data)"
)
parser.add_argument(
"--json", action="store_true",
help="Output full config as JSON"
)
args = parser.parse_args()
if args.input_file:
with open(args.input_file) as f:
inputs = json.load(f)
else:
if "--json" not in sys.argv:
if not args.json:
print("No input file provided. Running with sample data...\n")
inputs = SAMPLE_INPUT
result = generate_tracking_plan(inputs)
print_report(result, inputs)
if "--json" in sys.argv:
if args.json:
print(json.dumps(result, indent=2))

22
marketing-skill/churn-prevention/scripts/churn_impact_calculator.py
View File

@@ -164,8 +164,23 @@ def print_report(result):
def main():
if len(sys.argv) > 1:
with open(sys.argv[1]) as f:
import argparse
parser = argparse.ArgumentParser(
description="Churn impact calculator — models revenue impact of churn reduction improvements."
)
parser.add_argument(
"input_file", nargs="?", default=None,
help="JSON file with churn metrics (default: run with sample data)"
)
parser.add_argument(
"--json", action="store_true",
help="Output results as JSON"
)
args = parser.parse_args()
if args.input_file:
with open(args.input_file) as f:
inputs = json.load(f)
else:
print("No input file provided. Running with sample data...\n")
@@ -176,8 +191,7 @@ def main():
result = calculate(inputs)
print_report(result)
# Also dump JSON for programmatic use
if "--json" in sys.argv:
if args.json:
print(json.dumps(result, indent=2))

23
marketing-skill/cold-email/scripts/email_sequence_analyzer.py
View File

@@ -439,16 +439,29 @@ SAMPLE_SEQUENCE = [
# ─── Main ─────────────────────────────────────────────────────────────────────
def main():
if len(sys.argv) > 1:
arg = sys.argv[1]
if arg == "-":
import argparse
parser = argparse.ArgumentParser(
description="Analyzes a cold email sequence for quality signals. "
"Evaluates word count, reading level, personalization, CTA clarity, "
"spam triggers, and subject lines. Scores each email 0-100."
)
parser.add_argument(
"file", nargs="?", default=None,
help="Path to a JSON file containing the email sequence. "
"Use '-' to read from stdin. If omitted, runs embedded sample."
)
args = parser.parse_args()
if args.file:
if args.file == "-":
sequence = json.load(sys.stdin)
else:
try:
with open(arg, "r", encoding="utf-8") as f:
with open(args.file, "r", encoding="utf-8") as f:
sequence = json.load(f)
except FileNotFoundError:
print(f"Error: File not found: {arg}", file=sys.stderr)
print(f"Error: File not found: {args.file}", file=sys.stderr)
sys.exit(1)
except json.JSONDecodeError as e:
print(f"Error: Invalid JSON: {e}", file=sys.stderr)

29
marketing-skill/content-humanizer/scripts/humanizer_scorer.py
View File

@@ -448,7 +448,25 @@ def print_report(result: dict, label: str = "") -> None:
def main():
if len(sys.argv) == 1:
import argparse
parser = argparse.ArgumentParser(
description="Scores content 0-100 on 'humanity' by detecting AI writing patterns. "
"Checks AI vocabulary, sentence variance, passive voice, hedging, "
"em-dash overuse, and paragraph variety."
)
parser.add_argument(
"file", nargs="?", default=None,
help="Path to a text file to analyze. If omitted, runs demo comparing "
"human vs AI sample content."
)
parser.add_argument(
"--json", action="store_true",
help="Also output results as JSON."
)
args = parser.parse_args()
if args.file is None:
# Demo mode: compare human vs AI sample
print("[Demo mode — comparing human vs AI sample content]")
print()
@@ -468,18 +486,17 @@ def main():
print(f" Difference: {r1['humanity_score'] - r2['humanity_score']} points")
print()
else:
filepath = sys.argv[1]
try:
with open(filepath, 'r', encoding='utf-8') as f:
with open(args.file, 'r', encoding='utf-8') as f:
text = f.read()
except FileNotFoundError:
print(f"Error: file not found: {filepath}", file=sys.stderr)
print(f"Error: file not found: {args.file}", file=sys.stderr)
sys.exit(1)
result = score_humanity(text)
print_report(result, filepath)
print_report(result, args.file)
if "--json" in sys.argv:
if args.json:
print(json.dumps(result, indent=2))

24
marketing-skill/content-production/scripts/brand_voice_analyzer.py
View File

@@ -174,12 +174,24 @@ def analyze_content(content: str, output_format: str = 'json') -> str:
if __name__ == "__main__":
import sys
import argparse
if len(sys.argv) > 1:
with open(sys.argv[1], 'r') as f:
parser = argparse.ArgumentParser(
description="Brand Voice Analyzer - Analyzes content to establish and maintain brand voice consistency"
)
parser.add_argument(
"file", nargs="?", default=None,
help="Text file to analyze"
)
parser.add_argument(
"--format", choices=["json", "text"], default="text",
help="Output format (default: text)"
)
args = parser.parse_args()
if args.file:
with open(args.file, 'r') as f:
content = f.read()
output_format = sys.argv[2] if len(sys.argv) > 2 else 'text'
print(analyze_content(content, output_format))
print(analyze_content(content, args.format))
else:
print("Usage: python brand_voice_analyzer.py <file> [json|text]")
print("Usage: python brand_voice_analyzer.py <file> [--format json|text]")

32
marketing-skill/content-production/scripts/content_scorer.py
View File

@@ -401,11 +401,31 @@ def print_report(result: dict, title: str, keyword: str) -> None:
def main():
import argparse
parser = argparse.ArgumentParser(
description="Scores content 0-100 on readability, SEO, structure, and engagement."
)
parser.add_argument(
"file", nargs="?", default=None,
help="Path to a text/markdown file to analyze. If omitted, runs demo "
"with embedded sample content."
)
parser.add_argument(
"keyword", nargs="?", default="",
help="Target SEO keyword to check density and placement."
)
parser.add_argument(
"--json", action="store_true",
help="Also output results as JSON."
)
args = parser.parse_args()
title = ""
keyword = ""
keyword = args.keyword
text = ""
if len(sys.argv) == 1:
if args.file is None:
# Demo mode — use embedded sample
print("[Demo mode — using embedded sample content]")
text = SAMPLE_CONTENT
@@ -413,13 +433,11 @@ def main():
keyword = SAMPLE_KEYWORD
else:
# Read from file
filepath = sys.argv[1]
keyword = sys.argv[2] if len(sys.argv) > 2 else ""
try:
with open(filepath, 'r', encoding='utf-8') as f:
with open(args.file, 'r', encoding='utf-8') as f:
text = f.read()
except FileNotFoundError:
print(f"Error: file not found: {filepath}", file=sys.stderr)
print(f"Error: file not found: {args.file}", file=sys.stderr)
sys.exit(1)
# Extract title from first H1 or first line
@@ -438,7 +456,7 @@ def main():
print_report(result, title, keyword)
# JSON output for programmatic use
if "--json" in sys.argv:
if args.json:
print(json.dumps(result, indent=2))

30
marketing-skill/content-production/scripts/seo_optimizer.py
View File

@@ -406,14 +406,28 @@ def optimize_content(content: str, keyword: str = None,
if __name__ == "__main__":
import sys
import argparse
if len(sys.argv) > 1:
with open(sys.argv[1], 'r') as f:
parser = argparse.ArgumentParser(
description="SEO Content Optimizer - Analyzes and optimizes content for SEO"
)
parser.add_argument(
"file", nargs="?", default=None,
help="Text file to analyze"
)
parser.add_argument(
"--keyword", "-k", default=None,
help="Primary keyword to optimize for"
)
parser.add_argument(
"--secondary", "-s", default=None,
help="Comma-separated secondary keywords"
)
args = parser.parse_args()
if args.file:
with open(args.file, 'r') as f:
content = f.read()
keyword = sys.argv[2] if len(sys.argv) > 2 else None
secondary = sys.argv[3] if len(sys.argv) > 3 else None
print(optimize_content(content, keyword, secondary))
print(optimize_content(content, args.keyword, args.secondary))
else:
print("Usage: python seo_optimizer.py <file> [primary_keyword] [secondary_keywords]")
print("Usage: python seo_optimizer.py <file> [--keyword primary] [--secondary kw1,kw2]")

18
marketing-skill/free-tool-strategy/scripts/tool_roi_estimator.py
View File

@@ -330,11 +330,25 @@ DEFAULT_PARAMS = {
# ---------------------------------------------------------------------------
def main():
import argparse
parser = argparse.ArgumentParser(
description="Estimates ROI of building a free marketing tool. "
"Models return given build cost, maintenance, traffic, "
"conversion rate, and lead value."
)
parser.add_argument(
"file", nargs="?", default=None,
help="Path to a JSON file with tool parameters. "
"If omitted, reads from stdin or runs embedded sample."
)
args = parser.parse_args()
params = None
if len(sys.argv) > 1:
if args.file:
try:
with open(sys.argv[1]) as f:
with open(args.file) as f:
params = json.load(f)
except Exception as e:
print(f"Error reading file: {e}", file=sys.stderr)

23
marketing-skill/marketing-context/scripts/context_validator.py
View File

@@ -123,8 +123,25 @@ def print_report(results: dict):
def main():
if len(sys.argv) > 1:
filepath = Path(sys.argv[1])
import argparse
parser = argparse.ArgumentParser(
description="Validates marketing context completeness. "
"Scores 0-100 based on required and optional section coverage."
)
parser.add_argument(
"file", nargs="?", default=None,
help="Path to a marketing context markdown file. "
"If omitted, runs demo with embedded sample data."
)
parser.add_argument(
"--json", action="store_true",
help="Also output results as JSON."
)
args = parser.parse_args()
if args.file:
filepath = Path(args.file)
if not filepath.exists():
print(f"Error: File not found: {filepath}", file=sys.stderr)
sys.exit(1)
@@ -194,7 +211,7 @@ def main():
results = validate_context(content)
print_report(results)
if "--json" in sys.argv:
if args.json:
print(f"\n{json.dumps(results, indent=2)}")

21
marketing-skill/marketing-ops/scripts/campaign_tracker.py
View File

@@ -119,8 +119,23 @@ def print_report(analysis: dict):
def main():
if len(sys.argv) > 1:
filepath = Path(sys.argv[1])
import argparse
parser = argparse.ArgumentParser(
description="Track campaign status across marketing skills — tasks, owners, deadlines."
)
parser.add_argument(
"input_file", nargs="?", default=None,
help="JSON file with campaign data (default: run with sample data)"
)
parser.add_argument(
"--json", action="store_true",
help="Also output results as JSON"
)
args = parser.parse_args()
if args.input_file:
filepath = Path(args.input_file)
if filepath.exists():
campaign = json.loads(filepath.read_text())
else:
@@ -133,7 +148,7 @@ def main():
analysis = analyze_campaign(campaign)
print_report(analysis)
if "--json" in sys.argv:
if args.json:
print(f"\n{json.dumps(analysis, indent=2)}")

23
marketing-skill/pricing-strategy/scripts/pricing_modeler.py
View File

@@ -207,11 +207,26 @@ def print_report(result, inputs):
def main():
if len(sys.argv) > 1 and sys.argv[1] != "--json":
with open(sys.argv[1]) as f:
import argparse
parser = argparse.ArgumentParser(
description="Pricing modeler — projects revenue at different price points and recommends tier structure."
)
parser.add_argument(
"input_file", nargs="?", default=None,
help="JSON file with pricing data (default: run with sample data)"
)
parser.add_argument(
"--json", action="store_true",
help="Output results as JSON"
)
args = parser.parse_args()
if args.input_file:
with open(args.input_file) as f:
inputs = json.load(f)
else:
if "--json" not in sys.argv:
if not args.json:
print("No input file provided. Running with sample data...\n")
inputs = SAMPLE_INPUT
@@ -260,7 +275,7 @@ def main():
print_report(result, inputs)
if "--json" in sys.argv:
if args.json:
print(json.dumps(result, indent=2))

18
marketing-skill/referral-program/scripts/referral_roi_calculator.py
View File

@@ -353,11 +353,25 @@ def run(params):
# ---------------------------------------------------------------------------
def main():
import argparse
parser = argparse.ArgumentParser(
description="Calculates referral program ROI. "
"Models economics given LTV, CAC, referral rate, reward cost, "
"and conversion rate."
)
parser.add_argument(
"file", nargs="?", default=None,
help="Path to a JSON file with referral program parameters. "
"If omitted, reads from stdin or runs embedded sample."
)
args = parser.parse_args()
params = None
if len(sys.argv) > 1:
if args.file:
try:
with open(sys.argv[1]) as f:
with open(args.file) as f:
params = json.load(f)
except Exception as e:
print(f"Error reading file: {e}", file=sys.stderr)

22
marketing-skill/schema-markup/scripts/schema_validator.py
View File

@@ -390,16 +390,28 @@ SAMPLE_HTML = """<!DOCTYPE html>
# ─── Main ─────────────────────────────────────────────────────────────────────
def main():
if len(sys.argv) > 1:
arg = sys.argv[1]
if arg == "-":
import argparse
parser = argparse.ArgumentParser(
description="Extracts and validates JSON-LD structured data from HTML. "
"Scores 0-100 per schema block based on required/recommended field coverage."
)
parser.add_argument(
"file", nargs="?", default=None,
help="Path to an HTML file to validate. "
"Use '-' to read from stdin. If omitted, runs embedded sample."
)
args = parser.parse_args()
if args.file:
if args.file == "-":
html = sys.stdin.read()
else:
try:
with open(arg, "r", encoding="utf-8") as f:
with open(args.file, "r", encoding="utf-8") as f:
html = f.read()
except FileNotFoundError:
print(f"Error: File not found: {arg}", file=sys.stderr)
print(f"Error: File not found: {args.file}", file=sys.stderr)
sys.exit(1)
else:
print("No file provided — running on embedded sample HTML.\n")

20
marketing-skill/site-architecture/scripts/sitemap_analyzer.py
View File

@@ -328,12 +328,24 @@ def load_content(source: str) -> str:
def main():
if len(sys.argv) > 1:
arg = sys.argv[1]
if arg == "-":
import argparse
parser = argparse.ArgumentParser(
description="Analyzes sitemap.xml files for structure, depth, and potential issues. "
"Reports depth distribution, URL patterns, orphan candidates, and duplicates."
)
parser.add_argument(
"file", nargs="?", default=None,
help="Path to a sitemap.xml file or URL (https://...). "
"Use '-' to read from stdin. If omitted, runs embedded sample."
)
args = parser.parse_args()
if args.file:
if args.file == "-":
content = sys.stdin.read()
else:
content = load_content(arg)
content = load_content(args.file)
else:
print("No file or URL provided — running on embedded sample sitemap.\n")
content = SAMPLE_SITEMAP

2
mkdocs.yml
View File

@@ -1,6 +1,6 @@
site_name: Claude Code Skills & Plugins
site_url: https://alirezarezvani.github.io/claude-skills
site_description: "170 production-ready skills and plugins for Claude Code, OpenAI Codex, and OpenClaw. Reusable expertise for engineering, product, marketing, compliance, and more."
site_description: "177 production-ready skills and plugins for Claude Code, OpenAI Codex, 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

2
product-team/.claude-plugin/plugin.json
View File

@@ -1,7 +1,7 @@
{
"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",
"version": "2.1.1",
"version": "2.1.2",
"author": {
"name": "Alireza Rezvani",
"url": "https://alirezarezvani.com"

10
product-team/.codex/instructions.md
View File

@@ -29,7 +29,17 @@ python3 product-team/product-strategist/scripts/okr_cascade_generator.py --help
| Landing pages | landing-page-generator |
| SaaS boilerplate | saas-scaffolder |
## Cross-Domain Workflows
**Landing page + brand voice:** Before generating landing pages, run the brand voice analyzer to match copy tone:
```bash
python3 marketing-skill/content-production/scripts/brand_voice_analyzer.py brand_copy.txt --format json
python3 product-team/landing-page-generator/scripts/landing_page_scaffolder.py config.json --format tsx
```
Voice profile maps to design styles: formal+professional→enterprise, casual+friendly→bold-startup, professional+authoritative→dark-saas, casual+conversational→clean-minimal.
## Rules
- Load only 1-2 skills per request — don't bulk-load
- Use Python tools for scoring and analysis
- Landing page scaffolder defaults to TSX output (Next.js + Tailwind). Use `--format html` for standalone HTML.

136
product-team/CLAUDE.md
View File

@@ -1,6 +1,6 @@
# Product Team Skills - Claude Code Guidance
This guide covers the 5 production-ready product management skills and their Python automation tools.
This guide covers the 8 production-ready product management skills and their Python automation tools.
## Product Skills Overview
@@ -10,8 +10,15 @@ This guide covers the 5 production-ready product management skills and their Pyt
3. **product-strategist/** - OKR cascade, strategic planning (1 tool)
4. **ux-researcher-designer/** - Persona generation, user research (1 tool)
5. **ui-design-system/** - Design token generation, component systems (1 tool)
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)
**Total Tools:** 6 Python automation tools
**Total Tools:** 9 Python automation tools
**Agents:** 4 (cs-product-manager, cs-agile-product-owner, cs-product-strategist, cs-ux-researcher)
**Slash Commands:** 5 (/rice, /okr, /persona, /user-story, /competitive-matrix)
## Python Automation Tools
@@ -157,6 +164,76 @@ python ui-design-system/scripts/design_token_generator.py "#0066CC" modern scss
python ui-design-system/scripts/design_token_generator.py "#0066CC" modern json
```
### 7. Competitive Matrix Builder (`competitive-teardown/scripts/competitive_matrix_builder.py`)
**Purpose:** Weighted competitive scoring with gap analysis
**Usage:**
```bash
python competitive-teardown/scripts/competitive_matrix_builder.py competitors.json
```
### 8. Landing Page Scaffolder (`landing-page-generator/scripts/landing_page_scaffolder.py`)
**Purpose:** Generate production-ready landing pages as Next.js/React TSX components with Tailwind CSS (default) or plain HTML.
**Features:**
- TSX output (default): Next.js 14+ App Router components with Tailwind classes
- 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`)
**Purpose:** SaaS project scaffolding with auth, billing, and API setup
**Usage:**
```bash
python saas-scaffolder/scripts/project_bootstrapper.py project_config.json
```
## Product Workflows
### Workflow 1: Feature Prioritization
@@ -202,6 +279,31 @@ python agile-product-owner/scripts/user_story_generator.py sprint $CAPACITY
python product-manager-toolkit/scripts/rice_prioritizer.py features.csv --output json > priorities.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
@@ -239,30 +341,28 @@ python ux-researcher-designer/scripts/persona_generator.py --output json > perso
- Standard library only (minimal dependencies)
- Actionable recommendations
## Roadmap
## Cross-Domain Integration
**Current (Phase 1):** 5 skills deployed with 6 tools
### Brand Voice → Landing Page
**Phase 2 (Q1 2026):** Product analytics
- A/B test analyzer
- Funnel conversion tracker
- Cohort retention analyzer
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.
**Phase 3 (Q2 2026):** Advanced PM tools
- Competitive analysis framework
- Product-market fit assessment
- Revenue impact calculator
### Design Tokens → Landing Page
See `product_team_implementation_guide.md` for detailed plans.
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
- **Implementation Guide:** `product_team_implementation_guide.md`
- **Real-World Scenario:** `REAL_WORLD_SCENARIO.md` (if exists)
- **Main Documentation:** `../CLAUDE.md`
- **Marketing Brand Voice:** `../marketing-skill/content-production/scripts/brand_voice_analyzer.py`
---
**Last Updated:** November 5, 2025
**Skills Deployed:** 5/5 product skills production-ready
**Total Tools:** 6 Python automation tools
**Last Updated:** March 10, 2026
**Skills Deployed:** 8/8 product skills production-ready
**Total Tools:** 9 Python automation tools
**Agents:** 4 | **Commands:** 5

464
product-team/README.md
View File

@@ -1,448 +1,116 @@
# Product Team Skills Collection
**Complete suite of 5 expert product skills** covering product management, agile delivery, strategy, UX research, and design systems.
**8 production-ready product skills** covering product management, agile delivery, strategy, UX research, design systems, competitive intelligence, landing pages, and SaaS scaffolding.
---
## 📚 Table of Contents
## Overview
- [Installation](#installation)
- [Overview](#overview)
- [Skills Catalog](#skills-catalog)
- [Quick Start Guide](#quick-start-guide)
- [Team Structure Recommendations](#team-structure-recommendations)
- [Common Workflows](#common-workflows)
- [Success Metrics](#success-metrics)
- **8 skills** covering the full product lifecycle from discovery to delivery
- **9 Python automation tools** (stdlib only, zero dependencies)
- **4 agents** orchestrating skills across product workflows
- **5 slash commands** for quick access to common operations
---
## ⚡ Installation
### Quick Install (Recommended)
Install all product team skills with one command:
```bash
# Install all product skills to all supported agents
npx ai-agent-skills install alirezarezvani/claude-skills/product-team
# Install to Claude Code only
npx ai-agent-skills install alirezarezvani/claude-skills/product-team --agent claude
# Install to Cursor only
npx ai-agent-skills install alirezarezvani/claude-skills/product-team --agent cursor
```
### Install Individual Skills
```bash
# Product Manager Toolkit
npx ai-agent-skills install alirezarezvani/claude-skills/product-team/product-manager-toolkit
# Agile Product Owner
npx ai-agent-skills install alirezarezvani/claude-skills/product-team/agile-product-owner
# Product Strategist
npx ai-agent-skills install alirezarezvani/claude-skills/product-team/product-strategist
# UX Researcher Designer
npx ai-agent-skills install alirezarezvani/claude-skills/product-team/ux-researcher-designer
# UI Design System
npx ai-agent-skills install alirezarezvani/claude-skills/product-team/ui-design-system
```
**Supported Agents:** Claude Code, Cursor, VS Code, Copilot, Goose, Amp, Codex
**Complete Installation Guide:** See [../INSTALLATION.md](../INSTALLATION.md) for detailed instructions, troubleshooting, and manual installation.
---
## 🎯 Overview
This product team skills collection provides comprehensive product management capabilities from discovery through delivery, covering strategy, execution, research, and design.
**What's Included:**
- **5 expert-level skills** covering product management, agile, strategy, UX, and design
- **15+ Python automation tools** for prioritization, analysis, and generation
- **Comprehensive frameworks** for discovery, delivery, research, and design systems
- **Ready-to-use templates** for PRDs, user stories, OKRs, personas, and design tokens
**Ideal For:**
- Product teams at startups and scale-ups
- Solo PMs managing multiple products
- Product leaders building product organizations
- Cross-functional product delivery teams
**Key Benefits:**
- ⚡ **40% time savings** on product planning and documentation
- 🎯 **Data-driven decisions** with RICE prioritization and analytics
- 📈 **Consistent delivery** with agile frameworks and automation
- 🚀 **Faster time-to-market** with proven templates and workflows
---
## 📦 Skills Catalog
## Skills Catalog
### 1. Product Manager Toolkit
**Status:** ✅ Production Ready | **Version:** 1.0
**Python Tools:** `rice_prioritizer.py`, `customer_interview_analyzer.py`
**Purpose:** Essential tools and frameworks for modern product management, from discovery to delivery.
**Key Capabilities:**
- RICE prioritization with portfolio analysis
- Customer interview analysis and insight extraction
- PRD templates (4 comprehensive formats)
- Discovery frameworks and hypothesis testing
- Metrics and analytics dashboards
**Python Tools:**
- `rice_prioritizer.py` - Automated feature prioritization
- `customer_interview_analyzer.py` - AI-powered insight extraction
**Use When:** Feature prioritization, customer discovery, PRD creation, product metrics
**Learn More:** [product-manager-toolkit/SKILL.md](product-manager-toolkit/SKILL.md)
---
RICE prioritization with portfolio analysis, customer interview NLP analysis, PRD templates, and discovery frameworks.
### 2. Agile Product Owner
**Status:** ✅ Production Ready | **Version:** 1.0
**Python Tools:** `user_story_generator.py`
**Purpose:** Sprint execution and backlog management tools for agile product delivery.
**Key Capabilities:**
- INVEST-compliant user story generation
- Sprint planning with capacity allocation
- Epic breakdown and story mapping
- Velocity tracking and burndown analysis
- Agile ceremonies frameworks
**Python Tools:**
- `user_story_generator.py` - Generate user stories with acceptance criteria
- `sprint_planner.py` - Capacity-based sprint planning
- `velocity_tracker.py` - Sprint metrics and analysis
**Use When:** Backlog refinement, sprint planning, user story writing, velocity tracking
**Learn More:** [agile-product-owner/SKILL.md](agile-product-owner/SKILL.md)
---
INVEST-compliant user story generation, sprint planning with capacity allocation, epic breakdown, and acceptance criteria.
### 3. Product Strategist
**Status:** ✅ Production Ready | **Version:** 1.0
**Python Tools:** `okr_cascade_generator.py`
**Purpose:** Strategic planning and vision alignment for heads of product and product leaders.
**Key Capabilities:**
- OKR cascade generation (company → product → team)
- Alignment scoring and measurement
- Strategy templates (growth, retention, revenue, innovation)
- Team scaling and organizational design
- Vision frameworks and roadmap development
**Python Tools:**
- `okr_cascade_generator.py` - Automated OKR hierarchy generation
- `alignment_scorer.py` - Vertical and horizontal alignment measurement
**Use When:** Strategic planning, OKR setting, product vision, roadmap development, team scaling
**Learn More:** [product-strategist/SKILL.md](product-strategist/SKILL.md)
---
OKR cascade generation (company to product to team), alignment scoring, and 5 strategy templates.
### 4. UX Researcher Designer
**Status:** ✅ Production Ready | **Version:** 1.0
**Python Tools:** `persona_generator.py`
**Purpose:** User research and experience design frameworks for creating user-centered products.
**Key Capabilities:**
- Data-driven persona creation from user research
- Customer journey mapping and visualization
- Research synthesis and pattern identification
- Usability testing protocols and heuristic evaluation
- Design thinking and workshop facilitation
**Python Tools:**
- `persona_generator.py` - Generate personas from research data
- `journey_mapper.py` - Customer journey visualization
- `research_synthesizer.py` - Pattern identification from interviews
**Use When:** User research, persona development, journey mapping, usability testing
**Learn More:** [ux-researcher-designer/SKILL.md](ux-researcher-designer/SKILL.md)
---
Data-driven persona generation, journey mapping frameworks, usability testing protocols, and empathy maps.
### 5. UI Design System
**Status:** ✅ Production Ready | **Version:** 1.0
**Python Tools:** `design_token_generator.py`
**Purpose:** Visual design systems and component architecture for consistent user interfaces.
Design token generation from brand color (CSS, JSON, SCSS), typography scales, spacing grids, and responsive breakpoints.
**Key Capabilities:**
- Complete design token system generation
- Atomic design component architecture
- Responsive breakpoint and grid system calculation
- Export formats (JSON, CSS, SCSS) for development handoff
- Storybook integration and component documentation
### 6. Competitive Teardown
**Python Tools:** `competitive_matrix_builder.py`
**Python Tools:**
- `design_token_generator.py` - Generate complete token system from brand colors
- `component_architect.py` - Atomic design implementation
- `responsive_calculator.py` - Breakpoint and grid generation
12-dimension competitive scoring, feature matrices, SWOT analysis, positioning maps, and stakeholder presentations.
**Use When:** Design system creation, component library architecture, design-dev handoff
### 7. Landing Page Generator
**Python Tools:** `landing_page_scaffolder.py`
**Learn More:** [ui-design-system/SKILL.md](ui-design-system/SKILL.md)
Next.js/React TSX components with Tailwind CSS, 4 design styles, copy frameworks (PAS, AIDA, BAB), SEO optimization. Also supports HTML output.
### 8. SaaS Scaffolder
**Python Tools:** `project_bootstrapper.py`
Production SaaS boilerplate with Next.js, TypeScript, auth (NextAuth/Clerk/Supabase), payments (Stripe/Lemon Squeezy), and Docker.
---
## 🚀 Quick Start Guide
## Slash Commands
### For Product Managers
| Command | Script | Purpose |
|---------|--------|---------|
| `/rice` | `rice_prioritizer.py` | Feature prioritization |
| `/okr` | `okr_cascade_generator.py` | OKR cascade generation |
| `/persona` | `persona_generator.py` | Persona generation |
| `/user-story` | `user_story_generator.py` | User story generation |
| `/competitive-matrix` | `competitive_matrix_builder.py` | Competitive analysis |
---
## Quick Start
1. **Install Product Manager Toolkit:**
```bash
npx ai-agent-skills install alirezarezvani/claude-skills/product-team/product-manager-toolkit
```
# Prioritize your backlog
python product-manager-toolkit/scripts/rice_prioritizer.py features.csv --capacity 20
2. **Prioritize Your Backlog:**
```bash
python product-manager-toolkit/scripts/rice_prioritizer.py features.csv
```
3. **Analyze Customer Interviews:**
```bash
python product-manager-toolkit/scripts/customer_interview_analyzer.py interview.txt
```
### For Product Owners
1. **Install Agile Product Owner:**
```bash
npx ai-agent-skills install alirezarezvani/claude-skills/product-team/agile-product-owner
```
2. **Generate User Stories:**
```bash
python agile-product-owner/scripts/user_story_generator.py
```
3. **Plan Your Sprint:**
```bash
# Generate user stories for a sprint
python agile-product-owner/scripts/user_story_generator.py sprint 30
```
### For Product Leaders
1. **Install Product Strategist:**
```bash
npx ai-agent-skills install alirezarezvani/claude-skills/product-team/product-strategist
```
2. **Generate OKR Cascade:**
```bash
# Create OKR cascade
python product-strategist/scripts/okr_cascade_generator.py growth
```
### For UX Researchers
1. **Install UX Researcher Designer:**
```bash
npx ai-agent-skills install alirezarezvani/claude-skills/product-team/ux-researcher-designer
```
2. **Create Personas:**
```bash
# Generate personas
python ux-researcher-designer/scripts/persona_generator.py
```
### For UI Designers
1. **Install UI Design System:**
```bash
npx ai-agent-skills install alirezarezvani/claude-skills/product-team/ui-design-system
```
2. **Generate Design Tokens:**
```bash
# Generate design tokens
python ui-design-system/scripts/design_token_generator.py "#0066CC" modern css
# Competitive analysis
python competitive-teardown/scripts/competitive_matrix_builder.py competitors.json
# Scaffold a landing page (TSX + Tailwind)
python landing-page-generator/scripts/landing_page_scaffolder.py config.json --format tsx
# Bootstrap a SaaS project
python saas-scaffolder/scripts/project_bootstrapper.py config.json
```
---
## 👥 Team Structure Recommendations
## Agents
### Small Team (1-5 people)
**Recommended Skills:**
- Product Manager Toolkit (PM/Product Owner combo role)
- UX Researcher Designer (PM with UX responsibilities)
**Rationale:** Hybrid roles, focus on execution over specialization
| Agent | Skills Orchestrated |
|-------|-------------------|
| `cs-product-manager` | All 8 product skills |
| `cs-agile-product-owner` | Agile product owner + product manager toolkit |
| `cs-product-strategist` | Product strategist + competitive teardown |
| `cs-ux-researcher` | UX researcher + product manager toolkit + UI design system |
---
### Medium Team (6-15 people)
**Recommended Skills:**
- Product Manager Toolkit (Product Manager)
- Agile Product Owner (separate Product Owner role)
- UX Researcher Designer (dedicated UX Researcher)
- UI Design System (if building design system)
**Rationale:** Specialized roles, better separation of concerns
---
### Large Team (16+ people)
**Recommended Skills:**
- All 5 skills for complete product organization
- Product Strategist (Head of Product / CPO)
- Product Manager Toolkit (multiple Product Managers)
- Agile Product Owner (multiple Product Owners)
- UX Researcher Designer (UX Research team)
- UI Design System (Design Systems team)
**Rationale:** Full specialization, scaled product delivery
---
## 🔄 Common Workflows
### Workflow 1: New Feature Development
```
1. Discovery → Product Manager Toolkit
- Customer interviews
- Problem validation
- Opportunity sizing
2. Prioritization → Product Manager Toolkit
- RICE scoring
- Portfolio analysis
- Resource allocation
3. Story Writing → Agile Product Owner
- Epic breakdown
- User story generation
- Acceptance criteria
4. UX Research → UX Researcher Designer
- User testing
- Journey mapping
- Usability validation
5. Sprint Execution → Agile Product Owner
- Sprint planning
- Velocity tracking
- Burndown monitoring
```
### Workflow 2: Strategic Planning (Quarterly)
```
1. Vision Setting → Product Strategist
- Product vision
- Strategic themes
- Market positioning
2. OKR Cascade → Product Strategist
- Company → Product → Team goals
- Alignment measurement
- Success metrics
3. Roadmap Planning → Product Manager Toolkit
- Feature mapping
- Release planning
- Stakeholder alignment
4. Resource Planning → Product Strategist
- Team capacity
- Hiring needs
- Budget allocation
```
### Workflow 3: Design System Creation
```
1. Brand Foundation → UI Design System
- Design tokens
- Color system
- Typography scale
2. Component Architecture → UI Design System
- Atomic design
- Component library
- Documentation
3. User Validation → UX Researcher Designer
- Usability testing
- Component feedback
- Pattern validation
4. Developer Handoff → UI Design System
- CSS/JSON export
- Implementation guide
- Component specs
```
---
## 📊 Success Metrics
### Time Savings
- **Product Planning:** 40% reduction in PRD creation time
- **Backlog Management:** 50% reduction in user story writing time
- **Research Synthesis:** 60% reduction in interview analysis time
- **Design Systems:** 70% reduction in token generation time
### Quality Improvements
- **Feature Prioritization:** 30% improvement in delivery ROI
- **User Story Quality:** 40% improvement in acceptance criteria clarity
- **Research Insights:** 35% improvement in insight extraction accuracy
- **Design Consistency:** 80% improvement in design system consistency
### Delivery Velocity
- **Sprint Predictability:** 25% improvement in sprint completion rates
- **Discovery Efficiency:** 45% reduction in time-to-validation
- **OKR Alignment:** 50% improvement in goal alignment scores
- **UX Iteration:** 40% reduction in design iteration cycles
---
## 🔗 Integration with Other Teams
**Product ↔ Engineering:**
- User stories → Engineering implementation
- Technical feasibility → Product prioritization
- Design system → Frontend development
**Product ↔ Marketing:**
- Product strategy → Go-to-market strategy
- Customer insights → Marketing messaging
- Feature launches → Marketing campaigns
**Product ↔ C-Level:**
- OKRs → Company strategy
- Product metrics → Board reporting
- Resource needs → Budget planning
---
## 📚 Additional Resources
- **Product Team Guide:** `product_team_implementation_guide.md` (if exists)
- **CLAUDE.md:** [product-team/CLAUDE.md](CLAUDE.md) - Claude Code specific guidance
- **Main Documentation:** [../CLAUDE.md](../CLAUDE.md)
- **Installation Guide:** [../INSTALLATION.md](../INSTALLATION.md)
---
**Last Updated:** January 2026
**Skills Deployed:** 5/5 product team skills production-ready
**Total Tools:** 15+ Python automation tools
**Last Updated:** March 10, 2026
**Version:** v2.1.2
**Skills Deployed:** 8/8 production-ready
**Total Tools:** 9 Python automation tools

5
product-team/agile-product-owner/SKILL.md
View File

@@ -389,3 +389,8 @@ Story is complete when:
- [ ] Deployed to staging environment
- [ ] Product Owner accepted
- [ ] No critical bugs remaining
## Related Skills
- **Scrum Master** (`project-management/scrum-master/`) — Velocity data and sprint ceremonies complement backlog management
- **Product Manager Toolkit** (`product-team/product-manager-toolkit/`) — RICE prioritization feeds backlog ordering

84
product-team/agile-product-owner/assets/sprint_planning_template.md Normal file
View File

@@ -0,0 +1,84 @@
# Sprint Planning Document
## Sprint Info
| Field | Value |
|-------|-------|
| **Sprint** | Sprint [Number] |
| **Dates** | [Start Date] - [End Date] |
| **Sprint Goal** | [One sentence describing what this sprint achieves] |
| **Scrum Master** | [Name] |
| **Product Owner** | [Name] |
---
## Sprint Goal
[Expand on the sprint goal. What is the single most important outcome? What does "done" look like for this sprint? 2-3 sentences.]
---
## Team Capacity
| Team Member | Available Days | Notes |
|------------|---------------|-------|
| [Name] | [X] / [Total] | [PTO, training, on-call, etc.] |
| [Name] | [X] / [Total] | |
| [Name] | [X] / [Total] | |
**Total Capacity:** [X] person-days
**Historical Velocity:** [X] story points (avg of last 3 sprints)
**Planned Velocity:** [X] story points (adjusted for capacity)
---
## Selected Stories
| # | Story | Points | Assignee | Priority | Status |
|---|-------|--------|----------|----------|--------|
| 1 | [Story title with ticket link] | [SP] | [Name] | Must Have | To Do |
| 2 | [Story title with ticket link] | [SP] | [Name] | Must Have | To Do |
| 3 | [Story title with ticket link] | [SP] | [Name] | Should Have | To Do |
| 4 | [Story title with ticket link] | [SP] | [Name] | Nice to Have | To Do |
**Total Planned:** [X] story points
---
## Dependencies
| Dependency | Blocking Story | Owner | Status | Due Date |
|-----------|---------------|-------|--------|----------|
| [External API ready] | [Story #] | [Name/Team] | [Status] | [Date] |
| [Design review complete] | [Story #] | [Name] | [Status] | [Date] |
---
## Risks
| Risk | Impact | Likelihood | Mitigation |
|------|--------|-----------|-----------|
| [Risk description] | High/Med/Low | High/Med/Low | [Plan] |
| [Risk description] | High/Med/Low | High/Med/Low | [Plan] |
---
## Definition of Done
- [ ] Code complete and peer reviewed
- [ ] Unit tests written and passing
- [ ] Acceptance criteria verified
- [ ] Documentation updated (if applicable)
- [ ] Deployed to staging environment
- [ ] QA sign-off received
- [ ] Product Owner acceptance
---
## Sprint Ceremonies
| Ceremony | Day/Time | Duration |
|----------|----------|----------|
| Daily Standup | [Day] [Time] | 15 min |
| Sprint Review | [Date] [Time] | 60 min |
| Sprint Retrospective | [Date] [Time] | 60 min |

60
product-team/agile-product-owner/assets/user_story_template.md Normal file
View File

@@ -0,0 +1,60 @@
# User Story
## Story Info
| Field | Value |
|-------|-------|
| **Title** | [Short descriptive title] |
| **Epic** | [Parent epic name/link] |
| **Story Points** | [Estimate] |
| **Priority** | Must Have / Should Have / Nice to Have |
| **Assignee** | [Name] |
| **Sprint** | [Sprint number] |
---
## User Story
**As a** [type of user/role],
**I want** [capability or feature],
**So that** [benefit or value I receive].
---
## Acceptance Criteria
### Scenario 1: [Happy Path]
- **Given** [precondition or context]
- **When** [action the user takes]
- **Then** [expected outcome]
### Scenario 2: [Alternative Path]
- **Given** [precondition or context]
- **When** [action the user takes]
- **Then** [expected outcome]
### Scenario 3: [Edge Case / Error]
- **Given** [precondition or context]
- **When** [action the user takes]
- **Then** [expected error handling or outcome]
---
## Notes
- [Technical notes, design references, API details]
- [Dependencies on other stories or external systems]
- [Out of scope items for this story]
- [Links to mockups, prototypes, or design files]
---
## Definition of Done
- [ ] Acceptance criteria met
- [ ] Code reviewed and approved
- [ ] Tests written and passing
- [ ] Documentation updated
- [ ] Product Owner accepted

17
product-team/competitive-teardown/SKILL.md
View File

@@ -26,11 +26,11 @@ description: "Analyzes competitor products and companies by synthesizing data fr
Follow these steps in sequence to produce a complete teardown:
1. **Define competitors** — List 2–4 competitors to analyze. Confirm which is the primary focus.
2. **Collect data** — Use `DATA_COLLECTION.md` to gather raw signals from at least 3 sources per competitor (website, reviews, job postings, SEO, social).
2. **Collect data** — Use `references/data-collection-guide.md` to gather raw signals from at least 3 sources per competitor (website, reviews, job postings, SEO, social).
_Validation checkpoint: Before proceeding, confirm you have pricing data, at least 20 reviews, and job posting counts for each competitor._
3. **Score using rubric** — Apply the 12-dimension rubric below to produce a numeric scorecard for each competitor and your own product.
_Validation checkpoint: Every dimension should have a score and at least one supporting evidence note._
4. **Generate outputs** — Populate the templates in `TEMPLATES.md` (Feature Matrix, Pricing Analysis, SWOT, Positioning Map, UX Audit).
4. **Generate outputs** — Populate the templates in `references/analysis-templates.md` (Feature Matrix, Pricing Analysis, SWOT, Positioning Map, UX Audit).
5. **Build action plan** — Translate findings into the Action Items template (quick wins / medium-term / strategic).
6. **Package for stakeholders** — Assemble the Stakeholder Presentation using outputs from steps 3–5.
@@ -38,7 +38,7 @@ Follow these steps in sequence to produce a complete teardown:
## Data Collection Guide
> Full executable scripts for each source are in `DATA_COLLECTION.md`. Summaries of what to capture are below.
> Full executable scripts for each source are in `references/data-collection-guide.md`. Summaries of what to capture are below.
### 1. Website Analysis
@@ -85,7 +85,7 @@ SEO signals to capture:
### 5. Social Media Sentiment
Capture recent mentions via Twitter/X API v2, Reddit, or LinkedIn. Look for recurring praise, complaints, and feature requests. See `DATA_COLLECTION.md` for API query examples.
Capture recent mentions via Twitter/X API v2, Reddit, or LinkedIn. Look for recurring praise, complaints, and feature requests. See `references/data-collection-guide.md` for API query examples.
---
@@ -118,7 +118,7 @@ Apply this pattern to all 12 dimensions for each competitor.
## Templates
> Full template markdown is in `TEMPLATES.md`. Abbreviated reference below.
> Full template markdown is in `references/analysis-templates.md`. Abbreviated reference below.
### Feature Comparison Matrix
@@ -138,7 +138,7 @@ For each competitor: 3–5 bullets per quadrant (Strengths, Weaknesses, Opportun
### Positioning Map
2x2 axes (e.g., Simple ↔ Complex / Low Value ↔ High Value). Place each competitor and your product. Bubble size = market share or funding. See `TEMPLATES.md` for ASCII and editable versions.
2x2 axes (e.g., Simple ↔ Complex / Low Value ↔ High Value). Place each competitor and your product. Bubble size = market share or funding. See `references/analysis-templates.md` for ASCII and editable versions.
### UX Audit Checklist
@@ -164,3 +164,8 @@ Navigation: global search, keyboard shortcuts, in-app help.
5. **UX Highlights** — What they do better (3 bullets) vs. where we win (3 bullets)
6. **Voice of Customer** — Top 3 review complaints (quoted or paraphrased)
7. **Our Action Plan** — Quick wins, medium-term, strategic priorities; Appendix with raw data
## Related Skills
- **Product Strategist** (`product-team/product-strategist/`) — Competitive insights feed OKR and strategy planning
- **Landing Page Generator** (`product-team/landing-page-generator/`) — Competitive positioning informs landing page messaging

203
product-team/competitive-teardown/references/analysis-templates.md Normal file
View File

@@ -0,0 +1,203 @@
# Competitive Analysis Templates
## 1. SWOT Analysis Template
### Company/Product: [Competitor Name]
**Date:** [Analysis Date] | **Analyst:** [Name] | **Version:** [1.0]
#### Strengths (Internal Advantages)
| # | Strength | Evidence | Impact |
|---|----------|----------|--------|
| 1 | [e.g., Strong brand recognition] | [Source/data point] | High/Med/Low |
| 2 | | | |
| 3 | | | |
#### Weaknesses (Internal Limitations)
| # | Weakness | Evidence | Exploitability |
|---|----------|----------|---------------|
| 1 | [e.g., Limited API capabilities] | [Source/data point] | High/Med/Low |
| 2 | | | |
| 3 | | | |
#### Opportunities (External Favorable)
| # | Opportunity | Timeframe | Our Advantage |
|---|------------|-----------|---------------|
| 1 | [e.g., Competitor slow to adopt AI] | Short/Med/Long | [How we capitalize] |
| 2 | | | |
| 3 | | | |
#### Threats (External Unfavorable)
| # | Threat | Likelihood | Mitigation |
|---|--------|-----------|-----------|
| 1 | [e.g., Competitor acquired by larger company] | High/Med/Low | [Our response plan] |
| 2 | | | |
| 3 | | | |
---
## 2. Porter's Five Forces (Product Application)
### Market: [Your Product Category]
#### Force 1: Competitive Rivalry (Intensity: High/Med/Low)
- Number of direct competitors: ___
- Market growth rate: ___% annually
- Product differentiation level: High/Med/Low
- Switching costs for customers: High/Med/Low
- Exit barriers: High/Med/Low
- **Assessment:** [Summary of competitive rivalry intensity]
#### Force 2: Threat of New Entrants (Intensity: High/Med/Low)
- Capital requirements: High/Med/Low
- Technology barriers: High/Med/Low
- Network effects strength: Strong/Moderate/Weak
- Regulatory barriers: High/Med/Low
- Brand loyalty in market: Strong/Moderate/Weak
- **Assessment:** [Summary of new entrant threat]
#### Force 3: Threat of Substitutes (Intensity: High/Med/Low)
- Alternative solutions: [List substitutes]
- Price-performance of substitutes: Better/Same/Worse
- Switching costs to substitutes: High/Med/Low
- Customer propensity to switch: High/Med/Low
- **Assessment:** [Summary of substitute threat]
#### Force 4: Bargaining Power of Buyers (Power: High/Med/Low)
- Buyer concentration: Concentrated/Fragmented
- Price sensitivity: High/Med/Low
- Information availability: Full/Partial/Limited
- Switching costs: High/Med/Low
- Volume of purchases: High/Med/Low
- **Assessment:** [Summary of buyer power]
#### Force 5: Bargaining Power of Suppliers (Power: High/Med/Low)
- Key technology dependencies: [List]
- Cloud provider lock-in: High/Med/Low
- Talent market tightness: Tight/Balanced/Loose
- Data source dependencies: Critical/Important/Optional
- **Assessment:** [Summary of supplier power]
#### Overall Industry Attractiveness: [Score 1-10]
---
## 3. Competitive Positioning Map
### Axis Definitions
- **X-Axis:** [e.g., Ease of Use] (Low to High)
- **Y-Axis:** [e.g., Feature Completeness] (Low to High)
### Competitor Positions
| Competitor | X Score (1-10) | Y Score (1-10) | Quadrant |
|-----------|---------------|---------------|----------|
| Your Product | ___ | ___ | ___ |
| Competitor A | ___ | ___ | ___ |
| Competitor B | ___ | ___ | ___ |
| Competitor C | ___ | ___ | ___ |
| Competitor D | ___ | ___ | ___ |
### Quadrant Definitions
- **Top-Right (Leaders):** High on both axes - market leaders
- **Top-Left (Feature-Rich):** High features, lower ease of use - complex tools
- **Bottom-Right (Simple):** Easy to use, fewer features - niche players
- **Bottom-Left (Laggards):** Low on both axes - disruption candidates
### Positioning Insights
- **White space opportunities:** [Areas with no competitor presence]
- **Crowded areas:** [Where competition is fiercest]
- **Our trajectory:** [Direction we're moving on the map]
---
## 4. Win/Loss Analysis Template
### Deal: [Opportunity Name]
**Date:** [Close Date] | **Result:** Won / Lost | **Competitor:** [Name]
#### Deal Context
- **Deal Size:** $___
- **Sales Cycle:** ___ days
- **Segment:** SMB / Mid-Market / Enterprise
- **Industry:** ___
- **Decision Makers:** [Roles involved]
- **Evaluation Criteria:** [What mattered most to buyer]
#### Competitive Comparison (Buyer Perspective)
| Factor | Us (Score 1-5) | Competitor (Score 1-5) | Decisive? |
|--------|---------------|----------------------|-----------|
| Product Fit | | | Yes/No |
| Pricing | | | Yes/No |
| Ease of Use | | | Yes/No |
| Support Quality | | | Yes/No |
| Integration | | | Yes/No |
| Brand/Trust | | | Yes/No |
| Implementation | | | Yes/No |
#### Win/Loss Factors
- **Primary reason for outcome:** [Single most important factor]
- **Secondary factors:** [Supporting reasons]
- **Buyer quotes:** ["Direct quotes from debrief"]
#### Action Items
| # | Action | Owner | Due Date |
|---|--------|-------|----------|
| 1 | [e.g., Improve onboarding flow] | [Name] | [Date] |
| 2 | | | |
---
## 5. Battle Card Template
### Competitor: [Name]
**Last Updated:** [Date] | **Confidence:** High/Med/Low
#### Quick Facts
- **Founded:** ___
- **Funding:** $___
- **Employees:** ___
- **Customers:** ___
- **HQ:** ___
#### Elevator Pitch (Their Positioning)
> [How the competitor describes themselves in one sentence]
#### Our Positioning Against Them
> [How we differentiate - our one-liner against this competitor]
#### Where They Win
| Strength | Our Counter |
|----------|------------|
| [e.g., Lower price point] | [e.g., Emphasize TCO including implementation costs] |
| [e.g., Larger integration marketplace] | [e.g., Highlight quality over quantity, key integrations] |
| | |
#### Where We Win
| Our Strength | Evidence |
|-------------|----------|
| [e.g., Superior onboarding experience] | [Metric or customer quote] |
| [e.g., Better enterprise security] | [Certification or feature] |
| | |
#### Landmines to Set
Questions to ask prospects that expose competitor weaknesses:
1. "Have you evaluated how [specific capability] scales beyond [threshold]?"
2. "What's their approach to [area where competitor is weak]?"
3. "Can you share their uptime SLA and historical performance?"
#### Objection Handling
| Objection | Response |
|-----------|----------|
| "[Competitor] is cheaper" | [Value-based response] |
| "[Competitor] has more features" | [Quality/relevance response] |
| "We already use [Competitor]" | [Migration/coexistence story] |
#### Trap Questions They Set
Questions competitors ask about us, and how to respond:
1. **Q:** "[Our known weakness]?" **A:** [Honest, redirect response]
2. **Q:** "[Feature gap]?" **A:** [Roadmap or alternative approach]
#### Recent Intel
- [Date]: [Notable change - pricing, feature, hire, funding]
- [Date]: [Notable change]

Some files were not shown because too many files have changed in this diff Show More