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>
This commit is contained in:
Reza Rezvani
36
commands/okr.md
Normal file
36
commands/okr.md
Normal file
@@ -0,0 +1,36 @@
|
||||
---
|
||||
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`
|
||||
|
||||
## 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 growth --format json --output okrs.json
|
||||
```
|
||||
|
||||
## Scripts
|
||||
- `product-team/product-strategist/scripts/okr_cascade_generator.py` — OKR cascade generator
|
||||
|
||||
## Skill Reference
|
||||
> `product-team/product-strategist/SKILL.md`
|
||||
40
commands/persona.md
Normal file
40
commands/persona.md
Normal 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 --output 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 --output json
|
||||
/persona generate --output json > persona-eng-manager.json
|
||||
```
|
||||
|
||||
## Scripts
|
||||
- `product-team/ux-researcher-designer/scripts/persona_generator.py` — Persona generator
|
||||
|
||||
## Skill Reference
|
||||
> `product-team/ux-researcher-designer/SKILL.md`
|
||||
43
commands/project-health.md
Normal file
43
commands/project-health.md
Normal 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 --output dashboard.json
|
||||
```
|
||||
|
||||
## Scripts
|
||||
- `project-management/senior-pm/scripts/project_health_dashboard.py` — Health dashboard
|
||||
- `project-management/senior-pm/scripts/risk_matrix_analyzer.py` — Risk matrix analyzer
|
||||
|
||||
## Skill Reference
|
||||
> `project-management/senior-pm/SKILL.md`
|
||||
42
commands/retro.md
Normal file
42
commands/retro.md
Normal 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 --output retro-report.json
|
||||
```
|
||||
|
||||
## Scripts
|
||||
- `project-management/scrum-master/scripts/retrospective_analyzer.py` — Retrospective analyzer
|
||||
|
||||
## Skill Reference
|
||||
> `project-management/scrum-master/SKILL.md`
|
||||
39
commands/rice.md
Normal file
39
commands/rice.md
Normal 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 --format json --output prioritized.json
|
||||
```
|
||||
|
||||
## Scripts
|
||||
- `product-team/product-manager-toolkit/scripts/rice_prioritizer.py` — RICE prioritizer
|
||||
|
||||
## Skill Reference
|
||||
> `product-team/product-manager-toolkit/SKILL.md`
|
||||
43
commands/sprint-health.md
Normal file
43
commands/sprint-health.md
Normal 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 --output report.json
|
||||
```
|
||||
|
||||
## Scripts
|
||||
- `project-management/scrum-master/scripts/sprint_health_scorer.py` — Sprint health scorer
|
||||
- `project-management/scrum-master/scripts/velocity_analyzer.py` — Velocity analyzer
|
||||
|
||||
## Skill Reference
|
||||
> `project-management/scrum-master/SKILL.md`
|
||||
44
commands/user-story.md
Normal file
44
commands/user-story.md
Normal file
@@ -0,0 +1,44 @@
|
||||
---
|
||||
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 generate --output json
|
||||
/user-story sprint 34
|
||||
/user-story sprint 21 --format json --output sprint-plan.json
|
||||
```
|
||||
|
||||
## Scripts
|
||||
- `product-team/agile-product-owner/scripts/user_story_generator.py` — User story generator
|
||||
|
||||
## Skill Reference
|
||||
> `product-team/agile-product-owner/SKILL.md`
|
||||
Reference in New Issue
Block a user