diff --git a/docs/agents/cs-agile-product-owner.md b/docs/agents/cs-agile-product-owner.md
new file mode 100644
index 0000000..0051499
--- /dev/null
+++ b/docs/agents/cs-agile-product-owner.md
@@ -0,0 +1,419 @@
+---
+title: "Agile Product Owner Agent"
+description: "Agile Product Owner Agent - Claude Code agent for Product."
+---
+
+# Agile Product Owner Agent
+
+**Type:** Agent | **Domain:** Product | **Source:** [`agents/product/cs-agile-product-owner.md`](https://github.com/alirezarezvani/claude-skills/tree/main/agents/product/cs-agile-product-owner.md)
+
+---
+
+
+# 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
diff --git a/docs/agents/cs-ceo-advisor.md b/docs/agents/cs-ceo-advisor.md
new file mode 100644
index 0000000..d02631e
--- /dev/null
+++ b/docs/agents/cs-ceo-advisor.md
@@ -0,0 +1,363 @@
+---
+title: "CEO Advisor Agent"
+description: "CEO Advisor Agent - Claude Code agent for C-Level Advisory."
+---
+
+# CEO Advisor Agent
+
+**Type:** Agent | **Domain:** C-Level Advisory | **Source:** [`agents/c-level/cs-ceo-advisor.md`](https://github.com/alirezarezvani/claude-skills/tree/main/agents/c-level/cs-ceo-advisor.md)
+
+---
+
+
+# CEO Advisor Agent
+
+## Purpose
+
+The cs-ceo-advisor agent is a specialized executive leadership agent focused on strategic decision-making, organizational development, and stakeholder management. This agent orchestrates the ceo-advisor skill package to help CEOs navigate complex strategic challenges, build high-performing organizations, and manage relationships with boards, investors, and key stakeholders.
+
+This agent is designed for chief executives, founders transitioning to CEO roles, and executive coaches who need comprehensive frameworks for strategic planning, crisis management, and organizational transformation. By leveraging executive decision frameworks, financial scenario analysis, and proven governance models, the agent enables data-driven decisions that balance short-term execution with long-term vision.
+
+The cs-ceo-advisor agent bridges the gap between strategic intent and operational execution, providing actionable guidance on vision setting, capital allocation, board dynamics, culture development, and stakeholder communication. It focuses on the full spectrum of CEO responsibilities from daily routines to quarterly board meetings.
+
+## Skill Integration
+
+**Skill Location:** `../../c-level-advisor/ceo-advisor/`
+
+### Python Tools
+
+1. **Strategy Analyzer**
+   - **Purpose:** Analyzes strategic position using multiple frameworks (SWOT, Porter's Five Forces) and generates actionable recommendations
+   - **Path:** `../../c-level-advisor/ceo-advisor/scripts/strategy_analyzer.py`
+   - **Usage:** `python ../../c-level-advisor/ceo-advisor/scripts/strategy_analyzer.py`
+   - **Features:** Market analysis, competitive positioning, strategic options generation, risk assessment
+   - **Use Cases:** Annual strategic planning, market entry decisions, competitive analysis, strategic pivots
+
+2. **Financial Scenario Analyzer**
+   - **Purpose:** Models different business scenarios with risk-adjusted financial projections and capital allocation recommendations
+   - **Path:** `../../c-level-advisor/ceo-advisor/scripts/financial_scenario_analyzer.py`
+   - **Usage:** `python ../../c-level-advisor/ceo-advisor/scripts/financial_scenario_analyzer.py`
+   - **Features:** Scenario modeling, capital allocation optimization, runway analysis, valuation projections
+   - **Use Cases:** Fundraising planning, budget allocation, M&A evaluation, strategic investment decisions
+
+### Knowledge Bases
+
+1. **Executive Decision Framework**
+   - **Location:** `../../c-level-advisor/ceo-advisor/references/executive_decision_framework.md`
+   - **Content:** Structured decision-making process for go/no-go decisions, major pivots, M&A opportunities, crisis response
+   - **Use Case:** High-stakes decision making, option evaluation, stakeholder alignment
+
+2. **Board Governance & Investor Relations**
+   - **Location:** `../../c-level-advisor/ceo-advisor/references/board_governance_investor_relations.md`
+   - **Content:** Board meeting preparation, board package templates, investor communication cadence, fundraising playbooks
+   - **Use Case:** Board management, quarterly reporting, fundraising execution, investor updates
+
+3. **Leadership & Organizational Culture**
+   - **Location:** `../../c-level-advisor/ceo-advisor/references/leadership_organizational_culture.md`
+   - **Content:** Culture transformation frameworks, leadership development, change management, organizational design
+   - **Use Case:** Culture building, organizational change, leadership team development, transformation management
+
+## Workflows
+
+### Workflow 1: Annual Strategic Planning
+
+**Goal:** Develop comprehensive annual strategic plan with board-ready presentation
+
+**Steps:**
+1. **Environmental Scan** - Analyze market trends, competitive landscape, regulatory changes
+   ```bash
+   python ../../c-level-advisor/ceo-advisor/scripts/strategy_analyzer.py
+   ```
+2. **Reference Strategic Frameworks** - Review executive decision-making best practices
+   ```bash
+   cat ../../c-level-advisor/ceo-advisor/references/executive_decision_framework.md
+   ```
+3. **Strategic Options Development** - Generate and evaluate strategic alternatives:
+   - Market expansion opportunities
+   - Product/service innovations
+   - M&A targets
+   - Partnership strategies
+4. **Financial Modeling** - Run scenario analysis for each strategic option
+   ```bash
+   python ../../c-level-advisor/ceo-advisor/scripts/financial_scenario_analyzer.py
+   ```
+5. **Create Board Package** - Reference governance best practices for presentation
+   ```bash
+   cat ../../c-level-advisor/ceo-advisor/references/board_governance_investor_relations.md
+   ```
+6. **Strategy Communication** - Cascade strategic priorities to organization
+
+**Expected Output:** Board-approved strategic plan with financial projections, risk assessment, and execution roadmap
+
+**Time Estimate:** 4-6 weeks for complete strategic planning cycle
+
+### Workflow 2: Board Meeting Preparation & Execution
+
+**Goal:** Prepare and deliver high-impact quarterly board meeting
+
+**Steps:**
+1. **Review Board Best Practices** - Study board governance frameworks
+   ```bash
+   cat ../../c-level-advisor/ceo-advisor/references/board_governance_investor_relations.md
+   ```
+2. **Preparation Timeline** (T-4 weeks to meeting):
+   - **T-4 weeks**: Develop agenda with board chair
+   - **T-2 weeks**: Prepare materials (CEO letter, dashboard, financial review, strategic updates)
+   - **T-1 week**: Distribute board package
+   - **T-0**: Execute meeting with confidence
+3. **Board Package Components** (create each):
+   - CEO Letter (1-2 pages): Key achievements, challenges, priorities
+   - Dashboard (1 page): KPIs, financial metrics, operational highlights
+   - Financial Review (5 pages): P&L, cash flow, runway analysis
+   - Strategic Updates (10 pages): Initiative progress, market insights
+   - Risk Register (2 pages): Top risks and mitigation plans
+4. **Run Financial Scenarios** - Model different growth paths for board discussion
+   ```bash
+   python ../../c-level-advisor/ceo-advisor/scripts/financial_scenario_analyzer.py
+   ```
+5. **Meeting Execution** - Lead discussion, address questions, secure decisions
+6. **Post-Meeting Follow-Up** - Action items, decisions documented, communication to team
+
+**Expected Output:** Successful board meeting with clear decisions, alignment on strategy, and strong board confidence
+
+**Time Estimate:** 20-30 hours across 4-week preparation cycle
+
+### Workflow 3: Fundraising Campaign Execution
+
+**Goal:** Plan and execute successful fundraising round
+
+**Steps:**
+1. **Reference Investor Relations Playbook** - Study fundraising best practices
+   ```bash
+   cat ../../c-level-advisor/ceo-advisor/references/board_governance_investor_relations.md
+   ```
+2. **Financial Scenario Planning** - Model different raise amounts and runway scenarios
+   ```bash
+   python ../../c-level-advisor/ceo-advisor/scripts/financial_scenario_analyzer.py
+   ```
+3. **Develop Fundraising Materials**:
+   - Pitch deck (10-12 slides): Problem, solution, market, product, business model, GTM, competition, team, financials, ask
+   - Financial model (3-5 years): Revenue projections, unit economics, burn rate, milestones
+   - Executive summary (2 pages): Investment highlights
+   - Data room: Customer metrics, financial details, legal documents
+4. **Strategic Positioning** - Use strategy analyzer to articulate competitive advantage
+   ```bash
+   python ../../c-level-advisor/ceo-advisor/scripts/strategy_analyzer.py
+   ```
+5. **Investor Outreach** - Target list, warm intros, meeting scheduling
+6. **Pitch Refinement** - Practice, feedback, iteration
+7. **Due Diligence Management** - Coordinate cross-functional responses
+8. **Term Sheet Negotiation** - Valuation, board seats, terms
+9. **Close and Communication** - Internal announcement, external PR
+
+**Expected Output:** Successfully closed fundraising round at target valuation with strategic investors
+
+**Time Estimate:** 3-6 months from planning to close
+
+**Example:**
+```bash
+# Complete fundraising planning workflow
+python ../../c-level-advisor/ceo-advisor/scripts/financial_scenario_analyzer.py > scenarios.txt
+python ../../c-level-advisor/ceo-advisor/scripts/strategy_analyzer.py > competitive-position.txt
+# Use outputs to build compelling pitch deck and financial model
+```
+
+### Workflow 4: Organizational Culture Transformation
+
+**Goal:** Design and implement culture transformation initiative
+
+**Steps:**
+1. **Culture Assessment** - Evaluate current state through:
+   - Employee surveys (engagement, values alignment)
+   - Exit interviews analysis
+   - 360 leadership feedback
+   - Cultural artifacts review (meetings, rituals, symbols)
+2. **Reference Culture Frameworks** - Study transformation best practices
+   ```bash
+   cat ../../c-level-advisor/ceo-advisor/references/leadership_organizational_culture.md
+   ```
+3. **Define Target Culture**:
+   - Core values (3-5 values)
+   - Behavioral expectations
+   - Leadership principles
+   - Cultural rituals and symbols
+4. **Culture Transformation Timeline**:
+   - **Months 1-2**: Assessment and design phase
+   - **Months 2-3**: Communication and launch
+   - **Months 4-12**: Implementation and embedding
+   - **Months 12+**: Measurement and reinforcement
+5. **Key Transformation Levers**:
+   - Leadership modeling (executives embody values)
+   - Communication (town halls, values stories)
+   - Systems alignment (hiring, performance, promotion aligned to values)
+   - Recognition (celebrate values in action)
+   - Accountability (address misalignment)
+6. **Measure Progress**:
+   - Quarterly engagement surveys
+   - Culture KPIs (values adoption, behavior change)
+   - Exit interview trends
+   - External employer brand metrics
+
+**Expected Output:** Measurably improved culture with higher engagement, lower attrition, and stronger employer brand
+
+**Time Estimate:** 12-18 months for full transformation, ongoing reinforcement
+
+## Integration Examples
+
+### Example 1: Quarterly Strategic Review Dashboard
+
+```bash
+#!/bin/bash
+# ceo-quarterly-review.sh - Comprehensive CEO dashboard for board meetings
+
+echo "📊 Quarterly CEO Strategic Review - $(date +%Y-Q%d)"
+echo "=================================================="
+
+# Strategic analysis
+echo ""
+echo "🎯 Strategic Position:"
+python ../../c-level-advisor/ceo-advisor/scripts/strategy_analyzer.py
+
+# Financial scenarios
+echo ""
+echo "💰 Financial Scenarios:"
+python ../../c-level-advisor/ceo-advisor/scripts/financial_scenario_analyzer.py
+
+# Board package reminder
+echo ""
+echo "📋 Board Package Components:"
+echo "✓ CEO Letter (1-2 pages)"
+echo "✓ KPI Dashboard (1 page)"
+echo "✓ Financial Review (5 pages)"
+echo "✓ Strategic Updates (10 pages)"
+echo "✓ Risk Register (2 pages)"
+
+echo ""
+echo "📚 Reference Materials:"
+echo "- Board governance: ../../c-level-advisor/ceo-advisor/references/board_governance_investor_relations.md"
+echo "- Culture frameworks: ../../c-level-advisor/ceo-advisor/references/leadership_organizational_culture.md"
+```
+
+### Example 2: Strategic Decision Evaluation
+
+```bash
+# Evaluate major strategic decision (M&A, pivot, market expansion)
+
+echo "🔍 Strategic Decision Analysis"
+echo "================================"
+
+# Analyze strategic position
+python ../../c-level-advisor/ceo-advisor/scripts/strategy_analyzer.py > strategic-position.txt
+
+# Model financial scenarios
+python ../../c-level-advisor/ceo-advisor/scripts/financial_scenario_analyzer.py > financial-scenarios.txt
+
+# Reference decision framework
+echo ""
+echo "📖 Applying Executive Decision Framework:"
+cat ../../c-level-advisor/ceo-advisor/references/executive_decision_framework.md
+
+# Decision checklist
+echo ""
+echo "✅ Decision Checklist:"
+echo "☐ Problem clearly defined"
+echo "☐ Data/evidence gathered"
+echo "☐ Options evaluated"
+echo "☐ Stakeholders consulted"
+echo "☐ Risks assessed"
+echo "☐ Implementation planned"
+echo "☐ Success metrics defined"
+echo "☐ Communication prepared"
+```
+
+### Example 3: Weekly CEO Rhythm
+
+```bash
+# ceo-weekly-rhythm.sh - Maintain consistent CEO routines
+
+DAY_OF_WEEK=$(date +%A)
+
+echo "📅 CEO Weekly Rhythm - $DAY_OF_WEEK"
+echo "======================================"
+
+case $DAY_OF_WEEK in
+  Monday)
+    echo "🎯 Strategy & Planning Focus"
+    echo "- Executive team meeting"
+    echo "- Metrics review"
+    echo "- Week planning"
+    python ../../c-level-advisor/ceo-advisor/scripts/strategy_analyzer.py
+    ;;
+  Tuesday)
+    echo "🤝 External Focus"
+    echo "- Customer meetings"
+    echo "- Partner discussions"
+    echo "- Investor relations"
+    ;;
+  Wednesday)
+    echo "⚙️ Operations Focus"
+    echo "- Deep dives"
+    echo "- Problem solving"
+    echo "- Process review"
+    ;;
+  Thursday)
+    echo "👥 People & Culture Focus"
+    echo "- 1-on-1s with directs"
+    echo "- Talent reviews"
+    echo "- Culture initiatives"
+    cat ../../c-level-advisor/ceo-advisor/references/leadership_organizational_culture.md
+    ;;
+  Friday)
+    echo "🚀 Innovation & Future Focus"
+    echo "- Strategic projects"
+    echo "- Learning time"
+    echo "- Planning ahead"
+    python ../../c-level-advisor/ceo-advisor/scripts/financial_scenario_analyzer.py
+    ;;
+esac
+```
+
+## Success Metrics
+
+**Strategic Success:**
+- **Vision Clarity:** 90%+ employee understanding of company vision and strategy
+- **Strategy Execution:** 80%+ of strategic initiatives on track or ahead
+- **Market Position:** Improving competitive position quarter-over-quarter
+- **Innovation Pipeline:** 3-5 strategic initiatives in development at all times
+
+**Financial Success:**
+- **Revenue Growth:** Meeting or exceeding targets (ARR, bookings, revenue)
+- **Profitability:** Path to profitability clear with improving unit economics
+- **Cash Position:** 18+ months runway maintained, extending with growth
+- **Valuation Growth:** 2-3x valuation increase between funding rounds
+
+**Organizational Success:**
+- **Culture Thriving:** Employee engagement >80%, eNPS >40
+- **Talent Retained:** Executive attrition <10% annually, key talent retention >90%
+- **Leadership Bench:** 2+ internal successors identified and developed for each role
+- **Diversity & Inclusion:** Improving representation across all levels
+
+**Stakeholder Success:**
+- **Board Confidence:** Board satisfaction >8/10, strong working relationships
+- **Investor Satisfaction:** Proactive communication, no surprises, meeting expectations
+- **Customer NPS:** >50 NPS score, improving customer satisfaction
+- **Employee Approval:** >80% CEO approval rating (Glassdoor, internal surveys)
+
+## Related Agents
+
+- [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](../business-growth/cs-growth-strategist.md) - Growth strategy and market expansion (planned)
+
+## References
+
+- **Skill Documentation:** [../../c-level-advisor/ceo-advisor/SKILL.md](../../c-level-advisor/ceo-advisor/SKILL.md)
+- **C-Level Domain Guide:** [../../c-level-advisor/CLAUDE.md](../../c-level-advisor/CLAUDE.md)
+- **Agent Development Guide:** [../CLAUDE.md](../CLAUDE.md)
+
+---
+
+**Last Updated:** November 5, 2025
+**Sprint:** sprint-11-05-2025 (Day 3)
+**Status:** Production Ready
+**Version:** 1.0
diff --git a/docs/agents/cs-content-creator.md b/docs/agents/cs-content-creator.md
new file mode 100644
index 0000000..060b125
--- /dev/null
+++ b/docs/agents/cs-content-creator.md
@@ -0,0 +1,250 @@
+---
+title: "Content Creator Agent"
+description: "Content Creator Agent - Claude Code agent for Marketing."
+---
+
+# Content Creator Agent
+
+**Type:** Agent | **Domain:** Marketing | **Source:** [`agents/marketing/cs-content-creator.md`](https://github.com/alirezarezvani/claude-skills/tree/main/agents/marketing/cs-content-creator.md)
+
+---
+
+
+# Content Creator Agent
+
+## Purpose
+
+The cs-content-creator agent is a specialized marketing agent that orchestrates the content-creator skill package to help teams produce high-quality, on-brand content at scale. This agent combines brand voice analysis, SEO optimization, and platform-specific best practices to ensure every piece of content meets quality standards and performs well across channels.
+
+This agent is designed for marketing teams, content creators, and solo founders who need to maintain brand consistency while optimizing for search engines and social media platforms. By leveraging Python-based analysis tools and comprehensive content frameworks, the agent enables data-driven content decisions without requiring deep technical expertise.
+
+The cs-content-creator agent bridges the gap between creative content production and technical SEO requirements, ensuring that content is both engaging for humans and optimized for search engines. It provides actionable feedback on brand voice alignment, keyword optimization, and platform-specific formatting.
+
+## Skill Integration
+
+**Skill Location:** `../../marketing-skill/content-creator/`
+
+### Python Tools
+
+No Python tools — this skill relies on SKILL.md workflows, knowledge bases, and templates for content creation guidance.
+
+### Knowledge Bases
+
+1. **Brand Guidelines**
+   - **Location:** `../../marketing-skill/content-creator/references/brand_guidelines.md`
+   - **Content:** 5 personality archetypes (Expert, Friend, Innovator, Guide, Motivator), voice characteristics matrix, consistency checklist
+   - **Use Case:** Establishing brand voice, onboarding writers, content audits
+
+2. **Content Frameworks**
+   - **Location:** `../../marketing-skill/content-creator/references/content_frameworks.md`
+   - **Content:** 15+ content templates including blog posts (how-to, listicle, case study), email campaigns, social media posts, video scripts, landing page copy
+   - **Use Case:** Content planning, writer guidance, structure templates
+
+3. **Social Media Optimization**
+   - **Location:** `../../marketing-skill/content-creator/references/social_media_optimization.md`
+   - **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_template.md`
+   - **Use Case:** Planning monthly content, tracking production pipeline
+
+## Workflows
+
+### Workflow 1: Blog Post Creation & Optimization
+
+**Goal:** Create SEO-optimized blog post with consistent brand voice
+
+**Steps:**
+1. **Draft Content** - Write initial blog post draft in markdown format
+2. **Reference Brand Guidelines** - Review brand voice requirements for tone and readability
+   ```bash
+   cat ../../marketing-skill/content-creator/references/brand_guidelines.md
+   ```
+3. **Review Content Frameworks** - Select appropriate blog post template (how-to, listicle, case study)
+   ```bash
+   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** - Review against brand guidelines and content frameworks
+
+**Expected Output:** SEO-optimized blog post with consistent brand voice alignment
+
+**Time Estimate:** 2-3 hours for 1,500-word blog post
+
+**Example:**
+```bash
+# 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
+
+**Goal:** Adapt single piece of content for multiple social media platforms
+
+**Steps:**
+1. **Start with Core Content** - Begin with blog post or long-form content
+2. **Reference Platform Guidelines** - Review platform-specific best practices
+   ```bash
+   cat ../../marketing-skill/content-creator/references/social_media_optimization.md
+   ```
+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 by reviewing against brand guidelines
+   ```bash
+   cat ../../marketing-skill/content-creator/references/brand_guidelines.md
+   ```
+
+**Expected Output:** 4-5 platform-optimized versions from single source
+
+**Time Estimate:** 1-2 hours for complete adaptation
+
+### Workflow 3: Content Audit & Brand Consistency Check
+
+**Goal:** Audit existing content library for brand voice consistency and SEO optimization
+
+**Steps:**
+1. **Collect Content** - Gather markdown files for all published content
+2. **Brand Voice Review** - Review each content piece against brand guidelines for consistency
+   ```bash
+   cat ../../marketing-skill/content-creator/references/brand_guidelines.md
+   ```
+3. **Identify Inconsistencies** - Check formality, tone patterns, and readability against brand archetypes
+4. **SEO Audit** - Review content structure against content frameworks best practices
+   ```bash
+   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
+
+**Expected Output:** Comprehensive audit report with prioritized improvement list
+
+**Time Estimate:** 4-6 hours for 20-30 content pieces
+
+**Example:**
+```bash
+# 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
+
+**Goal:** Plan and structure content for multi-channel marketing campaign
+
+**Steps:**
+1. **Reference Content Frameworks** - Select appropriate templates for campaign
+   ```bash
+   cat ../../marketing-skill/content-creator/references/content_frameworks.md
+   ```
+2. **Copy Content Calendar** - Use template for campaign planning
+   ```bash
+   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
+   cat ../../marketing-skill/content-creator/references/brand_guidelines.md
+   ```
+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** - Review all campaign content against brand guidelines and social media optimization guides
+   ```bash
+   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
+
+**Time Estimate:** 8-12 hours for full campaign (10-15 content pieces)
+
+## Integration Examples
+
+### Example 1: Content Quality Review Workflow
+
+```bash
+#!/bin/bash
+# content-review.sh - Content quality review using knowledge bases
+
+CONTENT_FILE=$1
+
+echo "Reviewing brand voice guidelines..."
+cat ../../marketing-skill/content-creator/references/brand_guidelines.md
+
+echo ""
+echo "Reviewing content frameworks..."
+cat ../../marketing-skill/content-creator/references/content_frameworks.md
+
+echo ""
+echo "Review complete. Compare $CONTENT_FILE against the guidelines above."
+```
+
+**Usage:** `./content-review.sh blog-post.md`
+
+### Example 2: Platform-Specific Content Adaptation
+
+```bash
+# Review platform guidelines before adapting content
+cat ../../marketing-skill/content-creator/references/social_media_optimization.md
+
+# 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: Campaign Content Planning
+
+```bash
+# 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
+
+**Content Quality Metrics:**
+- **Brand Voice Consistency:** 80%+ of content scores within target formality range (60-80 for professional brands)
+- **Readability Score:** Flesch Reading Ease 60-80 (standard audience) or 80-90 (general audience)
+- **SEO Performance:** Average SEO score 75+ across all published content
+
+**Efficiency Metrics:**
+- **Content Production Speed:** 40% faster with analyzer feedback vs manual review
+- **Revision Cycles:** 30% reduction in editorial rounds
+- **Time to Publish:** 25% faster from draft to publication
+
+**Business Metrics:**
+- **Organic Traffic:** 20-30% increase within 3 months of SEO optimization
+- **Engagement Rate:** 15-25% improvement with platform-specific optimization
+- **Brand Consistency:** 90%+ brand voice alignment across all channels
+
+## Related Agents
+
+- [cs-demand-gen-specialist](cs-demand-gen-specialist.md) - Demand generation and acquisition campaigns
+- cs-product-marketing - Product positioning and messaging (planned)
+- cs-social-media-manager - Social media management and scheduling (planned)
+
+## References
+
+- **Skill Documentation:** [../../marketing-skill/content-creator/SKILL.md](../../marketing-skill/content-creator/SKILL.md)
+- **Marketing Domain Guide:** [../../marketing-skill/CLAUDE.md](../../marketing-skill/CLAUDE.md)
+- **Agent Development Guide:** [../CLAUDE.md](../CLAUDE.md)
+- **Marketing Roadmap:** [../../marketing-skill/marketing_skills_roadmap.md](../../marketing-skill/marketing_skills_roadmap.md)
+
+---
+
+**Last Updated:** November 5, 2025
+**Sprint:** sprint-11-05-2025 (Day 2)
+**Status:** Production Ready
+**Version:** 1.0
diff --git a/docs/agents/cs-cto-advisor.md b/docs/agents/cs-cto-advisor.md
new file mode 100644
index 0000000..0f4a967
--- /dev/null
+++ b/docs/agents/cs-cto-advisor.md
@@ -0,0 +1,415 @@
+---
+title: "CTO Advisor Agent"
+description: "CTO Advisor Agent - Claude Code agent for C-Level Advisory."
+---
+
+# CTO Advisor Agent
+
+**Type:** Agent | **Domain:** C-Level Advisory | **Source:** [`agents/c-level/cs-cto-advisor.md`](https://github.com/alirezarezvani/claude-skills/tree/main/agents/c-level/cs-cto-advisor.md)
+
+---
+
+
+# CTO Advisor Agent
+
+## Purpose
+
+The cs-cto-advisor agent is a specialized technical leadership agent focused on technology strategy, engineering team scaling, architecture governance, and operational excellence. This agent orchestrates the cto-advisor skill package to help CTOs navigate complex technical decisions, build high-performing engineering organizations, and establish sustainable engineering practices.
+
+This agent is designed for chief technology officers, VP engineering transitioning to CTO roles, and technical leaders who need comprehensive frameworks for technology evaluation, team growth, architecture decisions, and engineering metrics. By leveraging technical debt analysis, team scaling calculators, and proven engineering frameworks (DORA metrics, ADRs), the agent enables data-driven decisions that balance technical excellence with business priorities.
+
+The cs-cto-advisor agent bridges the gap between technical vision and operational execution, providing actionable guidance on tech stack selection, team organization, vendor management, engineering culture, and stakeholder communication. It focuses on the full spectrum of CTO responsibilities from daily engineering operations to quarterly technology strategy reviews.
+
+## Skill Integration
+
+**Skill Location:** `../../c-level-advisor/cto-advisor/`
+
+### Python Tools
+
+1. **Tech Debt Analyzer**
+   - **Purpose:** Analyzes system architecture, identifies technical debt, and provides prioritized reduction plan
+   - **Path:** `../../c-level-advisor/cto-advisor/scripts/tech_debt_analyzer.py`
+   - **Usage:** `python ../../c-level-advisor/cto-advisor/scripts/tech_debt_analyzer.py`
+   - **Features:** Debt categorization (critical/high/medium/low), capacity allocation recommendations, remediation roadmap
+   - **Use Cases:** Quarterly planning, architecture reviews, resource allocation, legacy system assessment
+
+2. **Team Scaling Calculator**
+   - **Purpose:** Calculates optimal hiring plan and team structure based on growth projections and engineering ratios
+   - **Path:** `../../c-level-advisor/cto-advisor/scripts/team_scaling_calculator.py`
+   - **Usage:** `python ../../c-level-advisor/cto-advisor/scripts/team_scaling_calculator.py`
+   - **Features:** Team size modeling, ratio optimization (manager:engineer, senior:mid:junior), capacity planning
+   - **Use Cases:** Annual planning, rapid growth scaling, team reorg, hiring roadmap development
+
+### Knowledge Bases
+
+1. **Architecture Decision Records (ADR)**
+   - **Location:** `../../c-level-advisor/cto-advisor/references/architecture_decision_records.md`
+   - **Content:** ADR templates, examples, decision-making frameworks, architectural patterns
+   - **Use Case:** Technology selection, architecture changes, documenting technical decisions, stakeholder alignment
+
+2. **Engineering Metrics**
+   - **Location:** `../../c-level-advisor/cto-advisor/references/engineering_metrics.md`
+   - **Content:** DORA metrics implementation, quality metrics (test coverage, code review), team health indicators
+   - **Use Case:** Performance measurement, continuous improvement, board reporting, benchmarking
+
+3. **Technology Evaluation Framework**
+   - **Location:** `../../c-level-advisor/cto-advisor/references/technology_evaluation_framework.md`
+   - **Content:** Vendor selection criteria, build vs buy analysis, technology assessment templates
+   - **Use Case:** Technology stack decisions, vendor evaluation, platform selection, procurement
+
+## Workflows
+
+### Workflow 1: Quarterly Technical Debt Assessment & Planning
+
+**Goal:** Assess technical debt portfolio and create quarterly reduction plan
+
+**Steps:**
+1. **Run Debt Analysis** - Identify and categorize technical debt across systems
+   ```bash
+   python ../../c-level-advisor/cto-advisor/scripts/tech_debt_analyzer.py
+   ```
+2. **Categorize Debt** - Sort debt by severity:
+   - **Critical**: System failure risk, blocking new features
+   - **High**: Slowing development velocity significantly
+   - **Medium**: Accumulating complexity, maintainability issues
+   - **Low**: Nice-to-have refactoring, code cleanup
+3. **Allocate Capacity** - Distribute engineering time across debt categories:
+   - Critical debt: 40% of engineering capacity
+   - High debt: 25% of engineering capacity
+   - Medium debt: 15% of engineering capacity
+   - Low debt: Ongoing maintenance budget
+4. **Create Remediation Roadmap** - Prioritize debt items by business impact
+5. **Reference Architecture Frameworks** - Document decisions using ADR template
+   ```bash
+   cat ../../c-level-advisor/cto-advisor/references/architecture_decision_records.md
+   ```
+6. **Communicate Plan** - Present to executive team and engineering org
+
+**Expected Output:** Quarterly technical debt reduction plan with allocated resources and clear priorities
+
+**Time Estimate:** 1-2 weeks for complete assessment and planning
+
+### Workflow 2: Engineering Team Scaling & Hiring Plan
+
+**Goal:** Develop data-driven hiring plan aligned with business growth
+
+**Steps:**
+1. **Assess Current State** - Document existing team:
+   - Team size by function (frontend, backend, mobile, DevOps, QA)
+   - Current ratios (manager:engineer, senior:mid:junior)
+   - Capacity utilization
+   - Key skill gaps
+2. **Run Scaling Calculator** - Model team growth scenarios
+   ```bash
+   python ../../c-level-advisor/cto-advisor/scripts/team_scaling_calculator.py
+   ```
+3. **Optimize Ratios** - Maintain healthy team structure:
+   - Manager:Engineer = 1:8 (avoid too many managers)
+   - Senior:Mid:Junior = 3:4:2 (balance experience levels)
+   - Product:Engineering = 1:10 (PM support)
+   - QA:Engineering = 1.5:10 (quality coverage)
+4. **Reference Engineering Metrics** - Ensure team health indicators support scaling
+   ```bash
+   cat ../../c-level-advisor/cto-advisor/references/engineering_metrics.md
+   ```
+5. **Create Hiring Roadmap**:
+   - Q1-Q4 hiring targets by role
+   - Interview panel assignments
+   - Onboarding capacity planning
+   - Budget allocation
+6. **Plan Onboarding** - Scale onboarding capacity with hiring velocity
+
+**Expected Output:** 12-month hiring roadmap with quarterly targets, budget requirements, and team structure evolution
+
+**Time Estimate:** 2-3 weeks for comprehensive planning
+
+### Workflow 3: Technology Stack Evaluation & Decision
+
+**Goal:** Evaluate and select technology vendor/platform using structured framework
+
+**Steps:**
+1. **Define Requirements** - Document business and technical needs:
+   - Functional requirements
+   - Non-functional requirements (scalability, security, compliance)
+   - Integration needs
+   - Budget constraints
+   - Timeline considerations
+2. **Reference Evaluation Framework** - Use systematic assessment criteria
+   ```bash
+   cat ../../c-level-advisor/cto-advisor/references/technology_evaluation_framework.md
+   ```
+3. **Market Research** (Weeks 1-2):
+   - Identify vendor options (3-5 candidates)
+   - Initial feature comparison
+   - Pricing models
+   - Customer references
+4. **Deep Evaluation** (Weeks 2-4):
+   - Technical POCs with top 2-3 vendors
+   - Security review
+   - Performance testing
+   - Integration testing
+   - Cost modeling (TCO over 3 years)
+5. **Document Decision** - Create ADR for transparency
+   ```bash
+   cat ../../c-level-advisor/cto-advisor/references/architecture_decision_records.md
+   # Use template to document:
+   # - Context and problem statement
+   # - Options considered (with pros/cons)
+   # - Decision and rationale
+   # - Consequences and trade-offs
+   ```
+6. **Stakeholder Alignment** - Present recommendation to CEO, CFO, relevant executives
+7. **Contract Negotiation** - Work with procurement on terms
+
+**Expected Output:** Technology vendor selected with documented ADR, contract negotiated, implementation plan ready
+
+**Time Estimate:** 4-6 weeks from requirements to decision
+
+**Example:**
+```bash
+# Complete technology evaluation workflow
+cat ../../c-level-advisor/cto-advisor/references/technology_evaluation_framework.md > evaluation-criteria.txt
+# Create comparison spreadsheet using criteria
+# Document final decision in ADR format
+```
+
+### Workflow 4: Engineering Metrics Dashboard Implementation
+
+**Goal:** Implement comprehensive engineering metrics tracking (DORA + custom KPIs)
+
+**Steps:**
+1. **Reference Metrics Framework** - Study industry standards
+   ```bash
+   cat ../../c-level-advisor/cto-advisor/references/engineering_metrics.md
+   ```
+2. **Select Metrics Categories**:
+   - **DORA Metrics** (industry standard for DevOps performance):
+     - Deployment Frequency: How often deploying to production
+     - Lead Time for Changes: Time from commit to production
+     - Mean Time to Recovery (MTTR): How fast fixing incidents
+     - Change Failure Rate: % of deployments causing failures
+   - **Quality Metrics**:
+     - Test Coverage: % of code covered by tests
+     - Code Review Rate: % of code reviewed before merge
+     - Technical Debt %: Estimated debt vs total codebase
+   - **Team Health Metrics**:
+     - Sprint Velocity: Story points completed per sprint
+     - Unplanned Work: % of capacity on reactive work
+     - On-call Incidents: Number of production incidents
+     - Employee Satisfaction: eNPS, engagement scores
+3. **Implement Instrumentation**:
+   - Deploy tracking tools (DataDog, Grafana, LinearB)
+   - Configure CI/CD pipeline metrics
+   - Set up incident tracking
+   - Survey team health quarterly
+4. **Set Target Benchmarks**:
+   - Deployment Frequency: >1/day (elite performers)
+   - Lead Time: <1 day (elite performers)
+   - MTTR: <1 hour (elite performers)
+   - Change Failure Rate: <15% (elite performers)
+   - Test Coverage: >80%
+   - Sprint Velocity: ±10% variance (stable)
+5. **Create Dashboards**:
+   - Real-time operations dashboard
+   - Weekly team health dashboard
+   - Monthly executive summary
+   - Quarterly board report
+6. **Establish Review Cadence**:
+   - Daily: Operational metrics (incidents, deployments)
+   - Weekly: Team health (velocity, unplanned work)
+   - Monthly: Trend analysis, goal progress
+   - Quarterly: Strategic review, benchmark comparison
+
+**Expected Output:** Comprehensive metrics dashboard with DORA metrics, quality indicators, and team health tracking
+
+**Time Estimate:** 4-6 weeks for implementation and baseline establishment
+
+## Integration Examples
+
+### Example 1: CTO Weekly Dashboard Script
+
+```bash
+#!/bin/bash
+# cto-weekly-dashboard.sh - Comprehensive CTO metrics summary
+
+DAY_OF_WEEK=$(date +%A)
+echo "📊 CTO Weekly Dashboard - $(date +%Y-%m-%d) ($DAY_OF_WEEK)"
+echo "=========================================================="
+
+# Technical debt assessment
+echo ""
+echo "⚠️ Technical Debt Status:"
+python ../../c-level-advisor/cto-advisor/scripts/tech_debt_analyzer.py
+
+# Team scaling status
+echo ""
+echo "👥 Team Scaling & Capacity:"
+python ../../c-level-advisor/cto-advisor/scripts/team_scaling_calculator.py
+
+# Engineering metrics
+echo ""
+echo "📈 Engineering Metrics (DORA):"
+echo "- Deployment Frequency: [from monitoring tool]"
+echo "- Lead Time: [from CI/CD metrics]"
+echo "- MTTR: [from incident tracking]"
+echo "- Change Failure Rate: [from deployment logs]"
+
+# Weekly focus
+case $DAY_OF_WEEK in
+  Monday)
+    echo ""
+    echo "🎯 Monday: Leadership & Strategy"
+    echo "- Leadership team sync"
+    echo "- Review metrics dashboard"
+    echo "- Address escalations"
+    ;;
+  Tuesday)
+    echo ""
+    echo "🏗️ Tuesday: Architecture & Technical"
+    echo "- Architecture review"
+    cat ../../c-level-advisor/cto-advisor/references/architecture_decision_records.md | grep -A 5 "Template"
+    ;;
+  Friday)
+    echo ""
+    echo "🚀 Friday: Strategic Planning"
+    echo "- Review technical debt backlog"
+    echo "- Plan next week priorities"
+    ;;
+esac
+```
+
+### Example 2: Quarterly Tech Strategy Review
+
+```bash
+# Quarterly technology strategy comprehensive review
+
+echo "🎯 Quarterly Technology Strategy Review - Q$(date +%q) $(date +%Y)"
+echo "================================================================"
+
+# Technical debt assessment
+echo ""
+echo "1. Technical Debt Assessment:"
+python ../../c-level-advisor/cto-advisor/scripts/tech_debt_analyzer.py > q$(date +%q)-debt-report.txt
+cat q$(date +%q)-debt-report.txt
+
+# Team scaling analysis
+echo ""
+echo "2. Team Scaling & Organization:"
+python ../../c-level-advisor/cto-advisor/scripts/team_scaling_calculator.py > q$(date +%q)-team-scaling.txt
+cat q$(date +%q)-team-scaling.txt
+
+# Engineering metrics review
+echo ""
+echo "3. Engineering Metrics Review:"
+cat ../../c-level-advisor/cto-advisor/references/engineering_metrics.md
+
+# Technology evaluation status
+echo ""
+echo "4. Technology Evaluation Framework:"
+cat ../../c-level-advisor/cto-advisor/references/technology_evaluation_framework.md
+
+# Board package reminder
+echo ""
+echo "📋 Board Package Components:"
+echo "✓ Technology Strategy Update"
+echo "✓ Team Growth & Health Metrics"
+echo "✓ Innovation Highlights"
+echo "✓ Risk Register"
+```
+
+### Example 3: Real-Time Incident Response Coordination
+
+```bash
+# incident-response.sh - CTO incident coordination
+
+SEVERITY=$1  # P0, P1, P2, P3
+INCIDENT_DESC=$2
+
+echo "🚨 Incident Response Activated - Severity: $SEVERITY"
+echo "=================================================="
+echo "Incident: $INCIDENT_DESC"
+echo "Time: $(date)"
+echo ""
+
+case $SEVERITY in
+  P0)
+    echo "⚠️ CRITICAL - All Hands Response"
+    echo "1. Activate incident commander"
+    echo "2. Pull engineering team"
+    echo "3. Update status page"
+    echo "4. Brief CEO/executives"
+    echo "5. Prepare customer communication"
+    ;;
+  P1)
+    echo "⚠️ HIGH - Immediate Response"
+    echo "1. Assign incident lead"
+    echo "2. Assemble response team"
+    echo "3. Monitor systems"
+    echo "4. Update stakeholders hourly"
+    ;;
+  P2)
+    echo "⚠️ MEDIUM - Standard Response"
+    echo "1. Assign engineer"
+    echo "2. Monitor progress"
+    echo "3. Update stakeholders as needed"
+    ;;
+esac
+
+echo ""
+echo "📊 Post-Incident Requirements:"
+echo "- Root cause analysis (48-72 hours)"
+echo "- Action items documented"
+echo "- Process improvements identified"
+```
+
+## Success Metrics
+
+**Technical Excellence:**
+- **System Uptime:** 99.9%+ availability across all critical systems
+- **Deployment Frequency:** >1 deployment/day (DORA elite performer benchmark)
+- **Lead Time:** <1 day from commit to production (DORA elite)
+- **MTTR:** <1 hour mean time to recovery (DORA elite)
+- **Change Failure Rate:** <15% of deployments (DORA elite)
+- **Technical Debt:** <10% of total codebase capacity allocated to debt
+- **Test Coverage:** >80% automated test coverage
+- **Security Incidents:** Zero major security breaches
+
+**Team Success:**
+- **Team Satisfaction:** >8/10 employee engagement score, eNPS >40
+- **Attrition Rate:** <10% annual voluntary attrition
+- **Hiring Success:** >90% of open positions filled within SLA
+- **Diversity & Inclusion:** Improving representation quarter-over-quarter
+- **Onboarding Effectiveness:** New hires productive within 30 days
+- **Career Development:** Clear growth paths, 80%+ promotion from within
+
+**Business Impact:**
+- **On-Time Delivery:** >80% of features delivered on schedule
+- **Engineering Enables Revenue:** Technology directly drives business growth
+- **Cost Efficiency:** Cost per transaction/user decreasing with scale
+- **Innovation ROI:** R&D investments leading to competitive advantages
+- **Technical Scalability:** Infrastructure costs growing slower than revenue
+
+**Strategic Leadership:**
+- **Technology Vision:** Clear 3-5 year roadmap communicated and understood
+- **Board Confidence:** Strong working relationship, proactive communication
+- **Cross-Functional Partnership:** Effective collaboration with product, sales, marketing
+- **Vendor Relationships:** Optimized vendor portfolio, SLAs met
+
+## Related Agents
+
+- [cs-ceo-advisor](cs-ceo-advisor.md) - Strategic leadership and organizational development (CEO counterpart)
+- [cs-fullstack-engineer](../engineering/cs-fullstack-engineer.md) - Fullstack development coordination (planned)
+- [cs-devops-specialist](../engineering/cs-devops-specialist.md) - DevOps and infrastructure automation (planned)
+
+## References
+
+- **Skill Documentation:** [../../c-level-advisor/cto-advisor/SKILL.md](../../c-level-advisor/cto-advisor/SKILL.md)
+- **C-Level Domain Guide:** [../../c-level-advisor/CLAUDE.md](../../c-level-advisor/CLAUDE.md)
+- **Agent Development Guide:** [../CLAUDE.md](../CLAUDE.md)
+
+---
+
+**Last Updated:** November 5, 2025
+**Sprint:** sprint-11-05-2025 (Day 3)
+**Status:** Production Ready
+**Version:** 1.0
diff --git a/docs/agents/cs-demand-gen-specialist.md b/docs/agents/cs-demand-gen-specialist.md
new file mode 100644
index 0000000..e25c048
--- /dev/null
+++ b/docs/agents/cs-demand-gen-specialist.md
@@ -0,0 +1,293 @@
+---
+title: "Demand Generation Specialist Agent"
+description: "Demand Generation Specialist Agent - Claude Code agent for Marketing."
+---
+
+# Demand Generation Specialist Agent
+
+**Type:** Agent | **Domain:** Marketing | **Source:** [`agents/marketing/cs-demand-gen-specialist.md`](https://github.com/alirezarezvani/claude-skills/tree/main/agents/marketing/cs-demand-gen-specialist.md)
+
+---
+
+
+# Demand Generation Specialist Agent
+
+## Purpose
+
+The cs-demand-gen-specialist agent is a specialized marketing agent focused on demand generation, lead acquisition, and conversion optimization. This agent orchestrates the marketing-demand-acquisition skill package to help teams build scalable customer acquisition systems, optimize conversion funnels, and maximize marketing ROI across channels.
+
+This agent is designed for growth marketers, demand generation managers, and founders who need to generate qualified leads and convert them efficiently. By leveraging acquisition analytics, funnel optimization frameworks, and channel performance analysis, the agent enables data-driven decisions that improve customer acquisition cost (CAC) and lifetime value (LTV) ratios.
+
+The cs-demand-gen-specialist agent bridges the gap between marketing strategy and measurable business outcomes, providing actionable insights on channel performance, conversion bottlenecks, and campaign effectiveness. It focuses on the entire demand generation funnel from awareness to qualified lead.
+
+## Skill Integration
+
+**Skill Location:** `../../marketing-skill/marketing-demand-acquisition/`
+
+### Python Tools
+
+1. **CAC Calculator**
+   - **Purpose:** Calculates Customer Acquisition Cost (CAC) across channels and campaigns
+   - **Path:** `../../marketing-skill/marketing-demand-acquisition/scripts/calculate_cac.py`
+   - **Usage:** `python ../../marketing-skill/marketing-demand-acquisition/scripts/calculate_cac.py campaign-spend.csv customer-data.csv`
+   - **Features:** CAC calculation by channel, LTV:CAC ratio, payback period analysis, ROI metrics
+   - **Use Cases:** Budget allocation, channel performance evaluation, campaign ROI analysis
+
+**Note:** Additional tools (demand_gen_analyzer.py, funnel_optimizer.py) planned for future releases per marketing roadmap.
+
+### Knowledge Bases
+
+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. **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. **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
+
+No asset templates currently available — use campaign-templates.md reference for campaign structure guidance.
+
+## Workflows
+
+### Workflow 1: Multi-Channel Acquisition Campaign Launch
+
+**Goal:** Plan and launch demand generation campaign across multiple acquisition channels
+
+**Steps:**
+1. **Define Campaign Goals** - Set targets for leads, MQLs, SQLs, conversion rates
+2. **Reference Campaign Templates** - Review proven campaign structures and launch checklists
+   ```bash
+   cat ../../marketing-skill/marketing-demand-acquisition/references/campaign-templates.md
+   ```
+3. **Select Channels** - Choose optimal mix based on target audience, budget, and attribution models
+   ```bash
+   cat ../../marketing-skill/marketing-demand-acquisition/references/attribution-guide.md
+   ```
+4. **Set Up Automation** - Configure HubSpot workflows for lead nurturing
+   ```bash
+   cat ../../marketing-skill/marketing-demand-acquisition/references/hubspot-workflows.md
+   ```
+5. **Plan International Reach** - Reference international playbooks if targeting multiple markets
+   ```bash
+   cat ../../marketing-skill/marketing-demand-acquisition/references/international-playbooks.md
+   ```
+6. **Launch and Monitor** - Deploy campaigns, track metrics, collect data
+
+**Expected Output:** Structured campaign plan with channel strategy, budget allocation, success metrics
+
+**Time Estimate:** 4-6 hours for campaign planning and setup
+
+### Workflow 2: Conversion Funnel Analysis & Optimization
+
+**Goal:** Identify and fix conversion bottlenecks in acquisition funnel
+
+**Steps:**
+1. **Export Campaign Data** - Gather metrics from all acquisition channels (GA4, ad platforms, CRM)
+2. **Calculate Channel CAC** - Run CAC calculator to analyze cost efficiency
+   ```bash
+   python ../../marketing-skill/marketing-demand-acquisition/scripts/calculate_cac.py campaign-spend.csv conversions.csv
+   ```
+3. **Map Conversion Funnel** - Visualize drop-off points using campaign templates as structure guide
+   ```bash
+   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 Attribution Guide** - Review attribution models to identify problem areas
+   ```bash
+   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
+   ```bash
+   python ../../marketing-skill/marketing-demand-acquisition/scripts/calculate_cac.py post-optimization-spend.csv post-optimization-conversions.csv
+   ```
+
+**Expected Output:** 15-30% reduction in CAC and improved LTV:CAC ratio
+
+**Time Estimate:** 6-8 hours for analysis and optimization planning
+
+**Example:**
+```bash
+# Complete CAC analysis workflow
+python ../../marketing-skill/marketing-demand-acquisition/scripts/calculate_cac.py q3-spend.csv q3-conversions.csv > cac-report.txt
+cat cac-report.txt
+# Review metrics and optimize high-CAC channels
+```
+
+### Workflow 3: Channel Performance Benchmarking
+
+**Goal:** Evaluate and compare performance across acquisition channels to optimize budget allocation
+
+**Steps:**
+1. **Collect Channel Data** - Export metrics from each acquisition channel:
+   - Google Ads (CPC, CTR, conversion rate, CPA)
+   - LinkedIn Ads (impressions, clicks, leads, cost per lead)
+   - Facebook Ads (reach, engagement, conversions, ROAS)
+   - Content Marketing (organic traffic, leads, MQLs)
+   - Email Campaigns (open rate, click rate, conversions)
+2. **Run CAC Comparison** - Calculate and compare CAC across all channels
+   ```bash
+   python ../../marketing-skill/marketing-demand-acquisition/scripts/calculate_cac.py channel-spend.csv channel-conversions.csv
+   ```
+3. **Reference Attribution Guide** - Understand attribution models and benchmarks for each channel
+   ```bash
+   cat ../../marketing-skill/marketing-demand-acquisition/references/attribution-guide.md
+   ```
+4. **Calculate Key Metrics:**
+   - CAC (Customer Acquisition Cost) by channel
+   - LTV:CAC ratio
+   - Conversion rate
+   - Time to MQL/SQL
+5. **Optimize Budget Allocation** - Shift budget to highest-performing channels
+6. **Document Learnings** - Create playbook for future campaigns
+
+**Expected Output:** Data-driven budget reallocation plan with projected ROI improvement
+
+**Time Estimate:** 3-4 hours for comprehensive channel analysis
+
+### Workflow 4: Lead Magnet Campaign Development
+
+**Goal:** Create and launch lead magnet campaign to capture high-quality leads
+
+**Steps:**
+1. **Define Lead Magnet** - Choose format: ebook, webinar, template, assessment, free trial
+2. **Reference Campaign Templates** - Review lead capture and campaign structure best practices
+   ```bash
+   cat ../../marketing-skill/marketing-demand-acquisition/references/campaign-templates.md
+   ```
+3. **Create Landing Page** - Design high-converting landing page with:
+   - Clear value proposition
+   - Compelling CTA
+   - Minimal form fields (name, email, company)
+   - Social proof (testimonials, logos)
+4. **Set Up Campaign Tracking** - Configure analytics and attribution
+5. **Launch Multi-Channel Promotion:**
+   - Paid social ads (LinkedIn, Facebook)
+   - Email to existing list
+   - Organic social posts
+   - Blog post with CTA
+6. **Monitor and Optimize** - Track CAC and conversion metrics
+   ```bash
+   # Weekly CAC analysis
+   python ../../marketing-skill/marketing-demand-acquisition/scripts/calculate_cac.py lead-magnet-spend.csv lead-magnet-conversions.csv
+   ```
+
+**Expected Output:** Lead magnet campaign generating 100-500 leads with 25-40% conversion rate
+
+**Time Estimate:** 8-12 hours for development and launch
+
+## Integration Examples
+
+### Example 1: Automated Campaign Performance Dashboard
+
+```bash
+#!/bin/bash
+# campaign-dashboard.sh - Daily campaign performance summary
+
+DATE=$(date +%Y-%m-%d)
+
+echo "📊 Demand Gen Dashboard - $DATE"
+echo "========================================"
+
+# Calculate yesterday's CAC by channel
+python ../../marketing-skill/marketing-demand-acquisition/scripts/calculate_cac.py \
+  daily-spend.csv daily-conversions.csv
+
+echo ""
+echo "💰 Budget Status:"
+cat budget-tracking.txt
+
+echo ""
+echo "🎯 Today's Priorities:"
+cat optimization-priorities.txt
+```
+
+### Example 2: Weekly Channel Performance Report
+
+```bash
+# Generate weekly CAC report for stakeholders
+python ../../marketing-skill/marketing-demand-acquisition/scripts/calculate_cac.py \
+  weekly-spend.csv weekly-conversions.csv > weekly-cac-report.txt
+
+# Email to stakeholders
+echo "Weekly CAC analysis report attached." | \
+  mail -s "Weekly CAC Report" -a weekly-cac-report.txt stakeholders@company.com
+```
+
+### Example 3: Real-Time Funnel Monitoring
+
+```bash
+# Monitor CAC in real-time (run daily via cron)
+CAC_RESULT=$(python ../../marketing-skill/marketing-demand-acquisition/scripts/calculate_cac.py \
+  daily-spend.csv daily-conversions.csv | grep "Average CAC" | awk '{print $3}')
+
+CAC_THRESHOLD=50
+
+# Alert if CAC exceeds threshold
+if (( $(echo "$CAC_RESULT > $CAC_THRESHOLD" | bc -l) )); then
+  echo "🚨 Alert: CAC ($CAC_RESULT) exceeds threshold ($CAC_THRESHOLD)!" | \
+    mail -s "CAC Alert" demand-gen-team@company.com
+fi
+```
+
+## Success Metrics
+
+**Acquisition Metrics:**
+- **Lead Volume:** 20-30% month-over-month growth
+- **MQL Conversion Rate:** 15-25% of total leads qualify as MQLs
+- **CAC (Customer Acquisition Cost):** Decrease by 15-20% with optimization
+- **LTV:CAC Ratio:** Maintain 3:1 or higher ratio
+
+**Channel Performance:**
+- **Paid Search:** CTR 3-5%, conversion rate 5-10%
+- **Paid Social:** CTR 1-2%, CPL (cost per lead) benchmarked by industry
+- **Content Marketing:** 30-40% of organic traffic converts to leads
+- **Email Campaigns:** Open rate 20-30%, click rate 3-5%, conversion rate 2-5%
+
+**Funnel Optimization:**
+- **Landing Page Conversion:** 25-40% conversion rate on optimized pages
+- **Form Completion:** 60-80% of visitors who start form complete it
+- **Lead Quality:** 40-50% of MQLs convert to SQLs
+
+**Business Impact:**
+- **Pipeline Contribution:** Demand gen accounts for 50-70% of sales pipeline
+- **Revenue Attribution:** Track $X in closed-won revenue to demand gen campaigns
+- **Payback Period:** CAC recovered within 6-12 months
+
+## Related Agents
+
+- [cs-content-creator](cs-content-creator.md) - Content creation for demand gen campaigns
+- cs-product-marketing - Product positioning and messaging (planned)
+- cs-growth-marketer - Growth hacking and viral acquisition (planned)
+
+## References
+
+- **Skill Documentation:** [../../marketing-skill/marketing-demand-acquisition/SKILL.md](../../marketing-skill/marketing-demand-acquisition/SKILL.md)
+- **Marketing Domain Guide:** [../../marketing-skill/CLAUDE.md](../../marketing-skill/CLAUDE.md)
+- **Agent Development Guide:** [../CLAUDE.md](../CLAUDE.md)
+- **Marketing Roadmap:** [../../marketing-skill/marketing_skills_roadmap.md](../../marketing-skill/marketing_skills_roadmap.md)
+
+---
+
+**Last Updated:** November 5, 2025
+**Sprint:** sprint-11-05-2025 (Day 2)
+**Status:** Production Ready
+**Version:** 1.0
diff --git a/docs/agents/cs-engineering-lead.md b/docs/agents/cs-engineering-lead.md
new file mode 100644
index 0000000..78409a5
--- /dev/null
+++ b/docs/agents/cs-engineering-lead.md
@@ -0,0 +1,89 @@
+---
+title: "cs-engineering-lead"
+description: "cs-engineering-lead - Claude Code agent for Engineering - Core."
+---
+
+# cs-engineering-lead
+
+**Type:** Agent | **Domain:** Engineering - Core | **Source:** [`agents/engineering-team/cs-engineering-lead.md`](https://github.com/alirezarezvani/claude-skills/tree/main/agents/engineering-team/cs-engineering-lead.md)
+
+---
+
+
+# cs-engineering-lead
+
+## Role & Expertise
+
+Engineering team lead coordinating across specializations: frontend, backend, QA, security, data, ML, and DevOps. Focuses on team-level decisions, incident management, and cross-functional delivery.
+
+## Skill Integration
+
+### Development
+- `engineering-team/senior-frontend` — React/Next.js, design systems
+- `engineering-team/senior-backend` — APIs, databases, system design
+- `engineering-team/senior-fullstack` — End-to-end feature delivery
+
+### Quality & Security
+- `engineering-team/senior-qa` — Test strategy, automation
+- `engineering-team/playwright-pro` — E2E testing with Playwright
+- `engineering-team/tdd-guide` — Test-driven development
+- `engineering-team/senior-security` — Application security
+- `engineering-team/senior-secops` — Security operations, compliance
+
+### Data & ML
+- `engineering-team/senior-data-engineer` — Data pipelines, warehousing
+- `engineering-team/senior-data-scientist` — Analysis, modeling
+- `engineering-team/senior-ml-engineer` — ML systems, deployment
+
+### Operations
+- `engineering-team/senior-devops` — Infrastructure, CI/CD
+- `engineering-team/incident-commander` — Incident management
+- `engineering-team/aws-solution-architect` — Cloud architecture
+- `engineering-team/tech-stack-evaluator` — Technology evaluation
+
+## Core Workflows
+
+### 1. Incident Response
+1. Assess severity and impact via `incident-commander`
+2. Assemble response team by domain
+3. Run incident timeline and RCA
+4. Draft post-mortem with action items
+5. Create follow-up tickets and runbooks
+
+### 2. Tech Stack Evaluation
+1. Define requirements and constraints
+2. Run evaluation matrix via `tech-stack-evaluator`
+3. Score candidates across dimensions
+4. Prototype top 2 options
+5. Present recommendation with tradeoffs
+
+### 3. Cross-Team Feature Delivery
+1. Break feature into frontend/backend/data components
+2. Define API contracts between teams
+3. Set up test strategy (unit → integration → E2E)
+4. Coordinate deployment sequence
+5. Monitor rollout with feature flags
+
+### 4. Team Health Check
+1. Review code quality metrics
+2. Assess test coverage and CI pipeline health
+3. Check dependency freshness and security
+4. Evaluate deployment frequency and lead time
+5. Identify skill gaps and training needs
+
+## Output Standards
+- 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
diff --git a/docs/agents/cs-financial-analyst.md b/docs/agents/cs-financial-analyst.md
new file mode 100644
index 0000000..f97e82d
--- /dev/null
+++ b/docs/agents/cs-financial-analyst.md
@@ -0,0 +1,71 @@
+---
+title: "cs-financial-analyst"
+description: "cs-financial-analyst - Claude Code agent for Finance."
+---
+
+# cs-financial-analyst
+
+**Type:** Agent | **Domain:** Finance | **Source:** [`agents/finance/cs-financial-analyst.md`](https://github.com/alirezarezvani/claude-skills/tree/main/agents/finance/cs-financial-analyst.md)
+
+---
+
+
+# cs-financial-analyst
+
+## Role & Expertise
+
+Financial analyst covering valuation, ratio analysis, forecasting, and industry-specific financial modeling across SaaS, retail, manufacturing, healthcare, and financial services.
+
+## Skill Integration
+
+- `finance/financial-analyst` — DCF modeling, ratio analysis, forecasting, scenario planning
+  - 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_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_calculator.py`
+2. Assess liquidity (current, quick ratio)
+3. Assess profitability (gross margin, EBITDA margin, ROE)
+4. Assess leverage (debt/equity, interest coverage)
+5. Benchmark against industry standards
+
+### 3. Revenue Forecasting
+1. Analyze historical trends
+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
+
+### 4. Budget Planning
+1. Review prior year actuals
+2. Set revenue targets by segment
+3. Allocate costs by department
+4. Build monthly cash flow projection
+5. Define variance thresholds and review cadence
+
+## Output Standards
+- Valuations → range with methodology stated (DCF, comparables, precedent)
+- 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
diff --git a/docs/agents/cs-growth-strategist.md b/docs/agents/cs-growth-strategist.md
new file mode 100644
index 0000000..c6559ce
--- /dev/null
+++ b/docs/agents/cs-growth-strategist.md
@@ -0,0 +1,69 @@
+---
+title: "cs-growth-strategist"
+description: "cs-growth-strategist - Claude Code agent for Business & Growth."
+---
+
+# cs-growth-strategist
+
+**Type:** Agent | **Domain:** Business & Growth | **Source:** [`agents/business-growth/cs-growth-strategist.md`](https://github.com/alirezarezvani/claude-skills/tree/main/agents/business-growth/cs-growth-strategist.md)
+
+---
+
+
+# cs-growth-strategist
+
+## Role & Expertise
+
+Growth-focused operator covering the full revenue lifecycle: pipeline management, sales engineering, customer success, and commercial proposals.
+
+## Skill Integration
+
+- `business-growth/revenue-operations` — Pipeline analysis, forecast accuracy, GTM efficiency
+- `business-growth/sales-engineer` — POC planning, competitive positioning, technical demos
+- `business-growth/customer-success-manager` — Health scoring, churn risk, expansion opportunities
+- `business-growth/contract-and-proposal-writer` — Commercial proposals, SOWs, pricing structures
+
+## Core Workflows
+
+### 1. Pipeline Health Check
+1. Run `pipeline_analyzer.py` on deal data
+2. Assess coverage ratios, stage conversion, deal aging
+3. Flag concentration risks
+4. Generate forecast with `forecast_accuracy_tracker.py`
+5. Report GTM efficiency metrics (CAC, LTV, magic number)
+
+### 2. Churn Prevention
+1. Calculate health scores via `health_score_calculator.py`
+2. Run churn risk analysis via `churn_risk_analyzer.py`
+3. Identify at-risk accounts with behavioral signals
+4. Create intervention playbook (QBR, escalation, executive sponsor)
+5. Track save/loss outcomes
+
+### 3. Expansion Planning
+1. Score expansion opportunities via `expansion_opportunity_scorer.py`
+2. Map whitespace (products not adopted)
+3. Prioritize by effort-vs-impact
+4. Create expansion proposals via `contract-and-proposal-writer`
+
+### 4. Sales Engineering Support
+1. Build competitive matrix via `competitive_matrix_builder.py`
+2. Plan POC via `poc_planner.py`
+3. Prepare technical demo environment
+4. Document win/loss analysis
+
+## Output Standards
+- 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
diff --git a/docs/agents/cs-product-manager.md b/docs/agents/cs-product-manager.md
new file mode 100644
index 0000000..2cd376c
--- /dev/null
+++ b/docs/agents/cs-product-manager.md
@@ -0,0 +1,687 @@
+---
+title: "Product Manager Agent"
+description: "Product Manager Agent - Claude Code agent for Product."
+---
+
+# Product Manager Agent
+
+**Type:** Agent | **Domain:** Product | **Source:** [`agents/product/cs-product-manager.md`](https://github.com/alirezarezvani/claude-skills/tree/main/agents/product/cs-product-manager.md)
+
+---
+
+
+# Product Manager Agent
+
+## 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 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.
+
+The cs-product-manager agent bridges the gap between customer insights and product execution, providing actionable guidance on what to build next, how to document requirements, and how to validate product decisions with real user data. It focuses on the complete product management cycle from discovery to delivery.
+
+## Skill Integration
+
+**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
+
+1. **RICE Prioritizer**
+   - **Purpose:** RICE framework implementation for feature prioritization with portfolio analysis and capacity planning
+   - **Path:** `../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py`
+   - **Usage:** `python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py features.csv --capacity 20`
+   - **Formula:** RICE Score = (Reach × Impact × Confidence) / Effort
+   - **Features:** Portfolio analysis (quick wins vs big bets), quarterly roadmap generation, capacity planning, JSON/CSV export
+   - **Use Cases:** Feature prioritization, roadmap planning, stakeholder alignment, resource allocation
+
+2. **Customer Interview Analyzer**
+   - **Purpose:** NLP-based interview transcript analysis to extract pain points, feature requests, and themes
+   - **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, 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**
+   - **Location:** `../../product-team/product-manager-toolkit/references/prd_templates.md`
+   - **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
+
+**Goal:** Prioritize feature backlog using RICE framework and generate quarterly roadmap
+
+**Steps:**
+1. **Gather Feature Requests** - Collect from multiple sources:
+   - Customer feedback (support tickets, interviews)
+   - Sales team requests
+   - Technical debt items
+   - Strategic initiatives
+   - Competitive gaps
+
+2. **Create RICE Input CSV** - Structure features with RICE parameters:
+   ```csv
+   feature,reach,impact,confidence,effort
+   User Dashboard,500,3,0.8,5
+   API Rate Limiting,1000,2,0.9,3
+   Dark Mode,300,1,1.0,2
+   ```
+   - **Reach**: Number of users affected per quarter
+   - **Impact**: massive(3), high(2), medium(1.5), low(1), minimal(0.5)
+   - **Confidence**: high(1.0), medium(0.8), low(0.5)
+   - **Effort**: person-months (XL=6, L=3, M=1, S=0.5, XS=0.25)
+
+3. **Run RICE Prioritization** - Execute analysis with team capacity
+   ```bash
+   python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py features.csv --capacity 20
+   ```
+
+4. **Analyze Portfolio** - Review output for:
+   - **Quick Wins**: High RICE, low effort (ship first)
+   - **Big Bets**: High RICE, high effort (strategic investments)
+   - **Fill-Ins**: Medium RICE (capacity fillers)
+   - **Money Pits**: Low RICE, high effort (avoid or revisit)
+
+5. **Generate Quarterly Roadmap**:
+   - Q1: Top quick wins + 1-2 big bets
+   - Q2-Q4: Remaining prioritized features
+   - Buffer: 20% capacity for unknowns
+
+6. **Stakeholder Alignment** - Present roadmap with:
+   - RICE scores as justification
+   - Trade-off decisions explained
+   - Capacity constraints visible
+
+**Expected Output:** Data-driven quarterly roadmap with RICE-justified priorities and portfolio balance
+
+**Time Estimate:** 4-6 hours for complete prioritization cycle (20-30 features)
+
+**Example:**
+```bash
+# Complete prioritization workflow
+python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py q4-features.csv --capacity 20 > roadmap.txt
+cat roadmap.txt
+# Review quick wins, big bets, and generate quarterly plan
+```
+
+### Workflow 2: Customer Discovery & Interview Analysis
+
+**Goal:** Conduct customer interviews, extract insights, and identify high-priority problems
+
+**Steps:**
+1. **Conduct User Interviews** - Semi-structured format:
+   - **Opening**: Build rapport, explain purpose
+   - **Context**: Current workflow and challenges
+   - **Problems**: Deep dive on pain points (not solutions!)
+   - **Solutions**: Reaction to concepts (if applicable)
+   - **Closing**: Next steps, thank you
+   - **Duration**: 30-45 minutes per interview
+   - **Record**: With permission for analysis
+
+2. **Transcribe Interviews** - Convert audio to text:
+   - Use transcription service (Otter.ai, Rev, etc.)
+   - Clean up for clarity (remove filler words)
+   - Save as plain text file
+
+3. **Run Interview Analyzer** - Extract structured insights
+   ```bash
+   python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-001.txt
+   ```
+
+4. **Review Analysis Output** - Study extracted insights:
+   - **Pain Points**: Severity-scored problems
+   - **Feature Requests**: Priority-ranked asks
+   - **Jobs-to-be-Done**: User goals and motivations
+   - **Sentiment**: Overall satisfaction level
+   - **Themes**: Recurring topics across interviews
+   - **Key Quotes**: Direct user language
+
+5. **Synthesize Across Interviews** - Aggregate insights:
+   ```bash
+   # Analyze multiple interviews
+   python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-001.txt json > insights-001.json
+   python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-002.txt json > insights-002.json
+   python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-003.txt json > insights-003.json
+   # Aggregate JSON files to find patterns
+   ```
+
+6. **Prioritize Problems** - Identify which pain points to solve:
+   - Frequency: How many users mentioned it?
+   - Severity: How painful is the problem?
+   - Strategic fit: Aligns with company vision?
+   - Solvability: Can we build a solution?
+
+7. **Validate Solutions** - Test hypotheses before building:
+   - Create mockups or prototypes
+   - Show to users, observe reactions
+   - Measure willingness to pay/adopt
+
+**Expected Output:** Prioritized list of validated problems with user quotes and evidence
+
+**Time Estimate:** 2-3 weeks for complete discovery (10-15 interviews + analysis)
+
+### Workflow 3: PRD Development & Stakeholder Communication
+
+**Goal:** Document requirements professionally with clear scope, metrics, and acceptance criteria
+
+**Steps:**
+1. **Choose PRD Template** - Select based on complexity:
+   ```bash
+   cat ../../product-team/product-manager-toolkit/references/prd_templates.md
+   ```
+   - **Standard PRD**: Complex features (6-8 weeks dev)
+   - **One-Page PRD**: Simple features (2-4 weeks)
+   - **Feature Brief**: Exploration phase (1 week)
+   - **Agile Epic**: Sprint-based delivery
+
+2. **Document Problem** - Start with why (not how):
+   - User problem statement (jobs-to-be-done format)
+   - Evidence from interviews (quotes, data)
+   - Current workarounds and pain points
+   - Business impact (revenue, retention, efficiency)
+
+3. **Define Solution** - Describe what we'll build:
+   - High-level solution approach
+   - User flows and key interactions
+   - Technical architecture (if relevant)
+   - Design mockups or wireframes
+   - **Critically: What's OUT of scope**
+
+4. **Set Success Metrics** - Define how we'll measure success:
+   - **Leading indicators**: Usage, adoption, engagement
+   - **Lagging indicators**: Revenue, retention, NPS
+   - **Target values**: Specific, measurable goals
+   - **Timeframe**: When we expect to hit targets
+
+5. **Write Acceptance Criteria** - Clear definition of done:
+   - Given/When/Then format for each user story
+   - Edge cases and error states
+   - Performance requirements
+   - Accessibility standards
+
+6. **Collaborate with Stakeholders**:
+   - **Engineering**: Feasibility review, effort estimation
+   - **Design**: User experience validation
+   - **Sales/Marketing**: Go-to-market alignment
+   - **Support**: Operational readiness
+
+7. **Iterate Based on Feedback** - Incorporate input:
+   - Technical constraints → Adjust scope
+   - Design insights → Refine user flows
+   - Market feedback → Validate assumptions
+
+**Expected Output:** Complete PRD with problem, solution, metrics, acceptance criteria, and stakeholder sign-off
+
+**Time Estimate:** 1-2 weeks for comprehensive PRD (iterative process)
+
+### Workflow 4: Quarterly Planning & OKR Setting
+
+**Goal:** Plan quarterly product goals with prioritized initiatives and success metrics
+
+**Steps:**
+1. **Review Company OKRs** - Align product goals to business objectives:
+   - Review CEO/executive OKRs for quarter
+   - Identify product contribution areas
+   - Understand strategic priorities
+
+2. **Run Feature Prioritization** - Use RICE for candidate features
+   ```bash
+   python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py q4-candidates.csv --capacity 18
+   ```
+
+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
+
+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
+
+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
+
+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
+
+8. **Track Progress** - Weekly OKR check-ins:
+   - Update key result progress
+   - Adjust priorities if needed
+   - Communicate blockers early
+
+**Expected Output:** Quarterly OKRs with prioritized roadmap, capacity plan, and risk mitigation
+
+**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
+
+```bash
+#!/bin/bash
+# product-weekly-review.sh - Automated product metrics summary
+
+echo "📊 Weekly Product Review - $(date +%Y-%m-%d)"
+echo "=========================================="
+
+# Current roadmap status
+echo ""
+echo "🎯 Roadmap Priorities (RICE Sorted):"
+python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py current-roadmap.csv --capacity 20
+
+# Recent interview insights
+echo ""
+echo "💡 Latest Customer Insights:"
+if [ -f latest-interview.txt ]; then
+  python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py latest-interview.txt
+else
+  echo "No new interviews this week"
+fi
+
+# PRD templates available
+echo ""
+echo "📝 PRD Templates:"
+echo "Standard PRD, One-Page PRD, Feature Brief, Agile Epic"
+echo "Location: ../../product-team/product-manager-toolkit/references/prd_templates.md"
+```
+
+### Example 2: Discovery Sprint Workflow
+
+```bash
+# Complete discovery sprint (2 weeks)
+
+echo "🔍 Discovery Sprint - Week 1"
+echo "=============================="
+
+# Day 1-2: Conduct interviews
+echo "Conducting 5 customer interviews..."
+
+# Day 3-5: Analyze insights
+python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-001.txt > insights-001.txt
+python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-002.txt > insights-002.txt
+python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-003.txt > insights-003.txt
+python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-004.txt > insights-004.txt
+python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-005.txt > insights-005.txt
+
+echo ""
+echo "🔍 Discovery Sprint - Week 2"
+echo "=============================="
+
+# Day 6-8: Prioritize problems and solutions
+echo "Creating solution candidates..."
+
+# Day 9-10: RICE prioritization
+python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py solution-candidates.csv
+
+echo ""
+echo "✅ Discovery Complete - Ready for PRD creation"
+```
+
+### Example 3: Quarterly Planning Automation
+
+```bash
+# Quarterly planning automation script
+
+QUARTER="Q4-2025"
+CAPACITY=18  # person-months
+
+echo "📅 $QUARTER Planning"
+echo "===================="
+
+# Step 1: Prioritize backlog
+echo ""
+echo "1. Feature Prioritization:"
+python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py backlog.csv --capacity $CAPACITY > $QUARTER-roadmap.txt
+
+# Step 2: Extract quick wins
+echo ""
+echo "2. Quick Wins (Ship First):"
+grep "Quick Win" $QUARTER-roadmap.txt
+
+# Step 3: Identify big bets
+echo ""
+echo "3. Big Bets (Strategic Investments):"
+grep "Big Bet" $QUARTER-roadmap.txt
+
+# Step 4: Generate summary
+echo ""
+echo "4. Quarterly Summary:"
+echo "Capacity: $CAPACITY person-months"
+echo "Features: $(wc -l < backlog.csv)"
+echo "Report: $QUARTER-roadmap.txt"
+```
+
+## Success Metrics
+
+**Prioritization Effectiveness:**
+- **Decision Speed:** <2 days from backlog review to roadmap commitment
+- **Stakeholder Alignment:** >90% stakeholder agreement on priorities
+- **RICE Validation:** 80%+ of shipped features match predicted impact
+- **Portfolio Balance:** 40% quick wins, 40% big bets, 20% fill-ins
+
+**Discovery Quality:**
+- **Interview Volume:** 10-15 interviews per discovery sprint
+- **Insight Extraction:** 5-10 high-priority pain points identified
+- **Problem Validation:** 70%+ of prioritized problems validated before build
+- **Time to Insight:** <1 week from interviews to prioritized problem list
+
+**Requirements Quality:**
+- **PRD Completeness:** 100% of PRDs include problem, solution, metrics, acceptance criteria
+- **Stakeholder Review:** <3 days average PRD review cycle
+- **Engineering Clarity:** >90% of PRDs require no clarification during development
+- **Scope Accuracy:** >80% of features ship within original scope estimate
+
+**Business Impact:**
+- **Feature Adoption:** >60% of users adopt new features within 30 days
+- **Problem Resolution:** >70% reduction in pain point severity post-launch
+- **Revenue Impact:** Track revenue/retention lift from prioritized features
+- **Development Efficiency:** 30%+ reduction in rework due to clear requirements
+
+## Related Agents
+
+- [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
+
+- **Skill Documentation:** [../../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)
+
+---
+
+**Last Updated:** March 9, 2026
+**Status:** Production Ready
+**Version:** 2.0
diff --git a/docs/agents/cs-product-strategist.md b/docs/agents/cs-product-strategist.md
new file mode 100644
index 0000000..5e20de8
--- /dev/null
+++ b/docs/agents/cs-product-strategist.md
@@ -0,0 +1,490 @@
+---
+title: "Product Strategist Agent"
+description: "Product Strategist Agent - Claude Code agent for Product."
+---
+
+# Product Strategist Agent
+
+**Type:** Agent | **Domain:** Product | **Source:** [`agents/product/cs-product-strategist.md`](https://github.com/alirezarezvani/claude-skills/tree/main/agents/product/cs-product-strategist.md)
+
+---
+
+
+# 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
diff --git a/docs/agents/cs-project-manager.md b/docs/agents/cs-project-manager.md
new file mode 100644
index 0000000..42f0732
--- /dev/null
+++ b/docs/agents/cs-project-manager.md
@@ -0,0 +1,518 @@
+---
+title: "Project Manager Agent"
+description: "Project Manager Agent - Claude Code agent for Project Management."
+---
+
+# Project Manager Agent
+
+**Type:** Agent | **Domain:** Project Management | **Source:** [`agents/project-management/cs-project-manager.md`](https://github.com/alirezarezvani/claude-skills/tree/main/agents/project-management/cs-project-manager.md)
+
+---
+
+
+# Project Manager Agent
+
+## Purpose
+
+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
+
+### Senior PM
+
+**Skill Location:** `../../project-management/senior-pm/`
+
+**Python Tools:**
+
+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
+
+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
+
+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
+
+**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
diff --git a/docs/agents/cs-quality-regulatory.md b/docs/agents/cs-quality-regulatory.md
new file mode 100644
index 0000000..9a71425
--- /dev/null
+++ b/docs/agents/cs-quality-regulatory.md
@@ -0,0 +1,89 @@
+---
+title: "cs-quality-regulatory"
+description: "cs-quality-regulatory - Claude Code agent for Regulatory & Quality."
+---
+
+# cs-quality-regulatory
+
+**Type:** Agent | **Domain:** Regulatory & Quality | **Source:** [`agents/ra-qm-team/cs-quality-regulatory.md`](https://github.com/alirezarezvani/claude-skills/tree/main/agents/ra-qm-team/cs-quality-regulatory.md)
+
+---
+
+
+# cs-quality-regulatory
+
+## Role & Expertise
+
+Regulatory affairs and quality management specialist for medical device and healthcare companies. Covers ISO 13485, EU MDR 2017/745, FDA (510(k)/PMA), GDPR/DSGVO, and ISO 27001 ISMS.
+
+## Skill Integration
+
+### Quality Management
+- `ra-qm-team/quality-manager-qms-iso13485` — QMS implementation, process management
+- `ra-qm-team/quality-manager-qmr` — Management review, quality metrics
+- `ra-qm-team/quality-documentation-manager` — Document control, SOP management
+- `ra-qm-team/qms-audit-expert` — Internal/external audit preparation
+- `ra-qm-team/capa-officer` — Root cause analysis, corrective actions
+
+### Regulatory Affairs
+- `ra-qm-team/regulatory-affairs-head` — Regulatory strategy, submission planning
+- `ra-qm-team/mdr-745-specialist` — EU MDR classification, technical documentation
+- `ra-qm-team/fda-consultant-specialist` — 510(k)/PMA/De Novo pathway guidance
+- `ra-qm-team/risk-management-specialist` — ISO 14971 risk management
+
+### Information Security & Privacy
+- `ra-qm-team/information-security-manager-iso27001` — ISMS design, security controls
+- `ra-qm-team/isms-audit-expert` — ISO 27001 audit preparation
+- `ra-qm-team/gdpr-dsgvo-expert` — Privacy impact assessments, data subject rights
+
+## Core Workflows
+
+### 1. Audit Preparation
+1. Identify audit scope and standard (ISO 13485, ISO 27001, MDR)
+2. Run gap analysis via `qms-audit-expert` or `isms-audit-expert`
+3. Generate checklist with evidence requirements
+4. Review document control status via `quality-documentation-manager`
+5. Prepare CAPA status summary via `capa-officer`
+6. Mock audit with findings report
+
+### 2. MDR Technical Documentation
+1. Classify device via `mdr-745-specialist` (Annex VIII rules)
+2. Prepare Annex II/III technical file structure
+3. Plan clinical evaluation (Annex XIV)
+4. Conduct risk management per ISO 14971
+5. Generate GSPR checklist
+6. Review post-market surveillance plan
+
+### 3. CAPA Investigation
+1. Define problem statement and containment
+2. Root cause analysis (5-Why, Ishikawa) via `capa-officer`
+3. Define corrective actions with owners and deadlines
+4. Implement and verify effectiveness
+5. Update risk management file
+6. Close CAPA with evidence package
+
+### 4. GDPR Compliance Assessment
+1. Data mapping (processing activities inventory)
+2. Run DPIA via `gdpr-dsgvo-expert`
+3. Assess legal basis for each processing activity
+4. Review data subject rights procedures
+5. Check cross-border transfer mechanisms
+6. Generate compliance report
+
+## Output Standards
+- Audit reports → findings with severity, evidence, corrective action
+- 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
diff --git a/docs/agents/cs-senior-engineer.md b/docs/agents/cs-senior-engineer.md
new file mode 100644
index 0000000..e50b6f0
--- /dev/null
+++ b/docs/agents/cs-senior-engineer.md
@@ -0,0 +1,91 @@
+---
+title: "cs-senior-engineer"
+description: "cs-senior-engineer - Claude Code agent for Engineering - POWERFUL."
+---
+
+# cs-senior-engineer
+
+**Type:** Agent | **Domain:** Engineering - POWERFUL | **Source:** [`agents/engineering/cs-senior-engineer.md`](https://github.com/alirezarezvani/claude-skills/tree/main/agents/engineering/cs-senior-engineer.md)
+
+---
+
+
+# cs-senior-engineer
+
+## Role & Expertise
+
+Cross-cutting senior engineer covering architecture, backend, DevOps, security, and API design. Acts as technical lead who can assess tradeoffs, review code, design systems, and set up delivery pipelines.
+
+## Skill Integration
+
+### Architecture & Backend
+- `engineering/database-designer` — Schema design, query optimization, migrations
+- `engineering/api-design-reviewer` — REST/GraphQL API contract review
+- `engineering/migration-architect` — System migration planning
+- `engineering-team/senior-architect` — High-level architecture patterns
+- `engineering-team/senior-backend` — Backend implementation patterns
+
+### Code Quality & Review
+- `engineering/pr-review-expert` — Pull request review methodology
+- `engineering-team/code-reviewer` — Code quality analysis
+- `engineering-team/tdd-guide` — Test-driven development
+- `engineering-team/senior-qa` — Quality assurance strategy
+
+### DevOps & Delivery
+- `engineering/ci-cd-pipeline-builder` — Pipeline generation (GitHub Actions, GitLab CI)
+- `engineering/release-manager` — Release planning and execution
+- `engineering-team/senior-devops` — Infrastructure and deployment
+- `engineering/observability-designer` — Monitoring and alerting
+
+### Security
+- `engineering-team/senior-security` — Application security
+- `engineering-team/senior-secops` — Security operations
+- `engineering/dependency-auditor` — Supply chain security
+
+## Core Workflows
+
+### 1. System Architecture Design
+1. Gather requirements (scale, team size, constraints)
+2. Evaluate architecture patterns via `senior-architect`
+3. Design database schema via `database-designer`
+4. Define API contracts via `api-design-reviewer`
+5. Plan CI/CD pipeline via `ci-cd-pipeline-builder`
+6. Document ADRs
+
+### 2. Production Code Review
+1. Understand the change context (PR description, linked issues)
+2. Review code quality via `code-reviewer` + `pr-review-expert`
+3. Check test coverage via `tdd-guide`
+4. Assess security implications via `senior-security`
+5. Verify deployment safety via `senior-devops`
+
+### 3. CI/CD Pipeline Setup
+1. Detect stack and tooling via `ci-cd-pipeline-builder`
+2. Generate pipeline config (build, test, lint, deploy stages)
+3. Add security scanning via `dependency-auditor`
+4. Configure observability via `observability-designer`
+5. Set up release process via `release-manager`
+
+### 4. Technical Debt Assessment
+1. Scan codebase via `tech-debt-tracker`
+2. Score and prioritize debt items
+3. Create remediation plan with effort estimates
+4. Integrate into sprint backlog
+
+## Output Standards
+- Architecture decisions → ADR format (context, decision, consequences)
+- Code reviews → structured feedback (severity, file, line, suggestion)
+- 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-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
diff --git a/docs/agents/cs-ux-researcher.md b/docs/agents/cs-ux-researcher.md
new file mode 100644
index 0000000..3cd981e
--- /dev/null
+++ b/docs/agents/cs-ux-researcher.md
@@ -0,0 +1,534 @@
+---
+title: "UX Researcher Agent"
+description: "UX Researcher Agent - Claude Code agent for Product."
+---
+
+# UX Researcher Agent
+
+**Type:** Agent | **Domain:** Product | **Source:** [`agents/product/cs-ux-researcher.md`](https://github.com/alirezarezvani/claude-skills/tree/main/agents/product/cs-ux-researcher.md)
+
+---
+
+
+# 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
diff --git a/docs/agents/index.md b/docs/agents/index.md
new file mode 100644
index 0000000..3d81816
--- /dev/null
+++ b/docs/agents/index.md
@@ -0,0 +1,25 @@
+---
+title: "Agents"
+description: "All 14 Claude Code agents — multi-skill orchestrators across domains."
+---
+
+# Agents
+
+14 agents that orchestrate skills across domains.
+
+| Agent | Domain |
+|-------|--------|
+| [cs-growth-strategist](cs-growth-strategist.md) | Business & Growth |
+| [CEO Advisor Agent](cs-ceo-advisor.md) | C-Level Advisory |
+| [CTO Advisor Agent](cs-cto-advisor.md) | C-Level Advisory |
+| [cs-senior-engineer](cs-senior-engineer.md) | Engineering - POWERFUL |
+| [cs-engineering-lead](cs-engineering-lead.md) | Engineering - Core |
+| [cs-financial-analyst](cs-financial-analyst.md) | Finance |
+| [Content Creator Agent](cs-content-creator.md) | Marketing |
+| [Demand Generation Specialist Agent](cs-demand-gen-specialist.md) | Marketing |
+| [Agile Product Owner Agent](cs-agile-product-owner.md) | Product |
+| [Product Manager Agent](cs-product-manager.md) | Product |
+| [Product Strategist Agent](cs-product-strategist.md) | Product |
+| [UX Researcher Agent](cs-ux-researcher.md) | Product |
+| [Project Manager Agent](cs-project-manager.md) | Project Management |
+| [cs-quality-regulatory](cs-quality-regulatory.md) | Regulatory & Quality |
diff --git a/docs/commands/changelog.md b/docs/commands/changelog.md
new file mode 100644
index 0000000..ba8b77a
--- /dev/null
+++ b/docs/commands/changelog.md
@@ -0,0 +1,37 @@
+---
+title: "/changelog"
+description: "/changelog — Claude Code slash command."
+---
+
+# /changelog
+
+**Type:** Slash Command | **Source:** [`commands/changelog.md`](https://github.com/alirezarezvani/claude-skills/tree/main/commands/changelog.md)
+
+---
+
+
+# /changelog
+
+Generate Keep a Changelog entries from git history and validate commit message format.
+
+## Usage
+
+```
+/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-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 (`--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`
diff --git a/docs/commands/competitive-matrix.md b/docs/commands/competitive-matrix.md
new file mode 100644
index 0000000..7b68962
--- /dev/null
+++ b/docs/commands/competitive-matrix.md
@@ -0,0 +1,47 @@
+---
+title: "/competitive-matrix"
+description: "/competitive-matrix — Claude Code slash command."
+---
+
+# /competitive-matrix
+
+**Type:** Slash Command | **Source:** [`commands/competitive-matrix.md`](https://github.com/alirezarezvani/claude-skills/tree/main/commands/competitive-matrix.md)
+
+---
+
+
+# /competitive-matrix
+
+Build competitive matrices with weighted scoring, gap analysis, and market positioning insights.
+
+## Usage
+
+```
+/competitive-matrix analyze <competitors.json>                    Full analysis
+/competitive-matrix analyze <competitors.json> --weights pricing=2,ux=1.5    Custom weights
+```
+
+## Input Format
+
+```json
+{
+  "your_product": { "name": "MyApp", "scores": {"ux": 8, "pricing": 7, "features": 9} },
+  "competitors": [
+    { "name": "Competitor A", "scores": {"ux": 7, "pricing": 9, "features": 6} }
+  ],
+  "dimensions": ["ux", "pricing", "features"]
+}
+```
+
+## Examples
+
+```
+/competitive-matrix analyze competitors.json
+/competitive-matrix analyze competitors.json --format json --output matrix.json
+```
+
+## Scripts
+- `product-team/competitive-teardown/scripts/competitive_matrix_builder.py` — Matrix builder
+
+## Skill Reference
+→ `product-team/competitive-teardown/SKILL.md`
diff --git a/docs/commands/index.md b/docs/commands/index.md
new file mode 100644
index 0000000..1f1cbc3
--- /dev/null
+++ b/docs/commands/index.md
@@ -0,0 +1,23 @@
+---
+title: "Commands"
+description: "All 12 slash commands for quick access to common operations."
+---
+
+# Slash Commands
+
+12 commands for quick access to common operations.
+
+| Command | Description |
+|---------|-------------|
+| [`/changelog`](changelog.md) | Generate Keep a Changelog entries from git history and validate commit message format. |
+| [`/competitive-matrix`](competitive-matrix.md) | Build competitive matrices with weighted scoring, gap analysis, and market positioning insights. |
+| [`/okr`](okr.md) | Generate cascaded OKR frameworks from company-level strategy down to team-level key results. |
+| [`/persona`](persona.md) | Generate structured user personas with demographics, goals, pain points, and behavioral patterns. |
+| [`/pipeline`](pipeline.md) | Detect project stack and generate CI/CD pipeline configurations for GitHub Actions or GitLab CI. |
+| [`/project-health`](project-health.md) | Generate portfolio health dashboards and risk matrices for project oversight. |
+| [`/retro`](retro.md) | Analyze retrospective data for recurring themes, sentiment trends, and action item effectiveness. |
+| [`/rice`](rice.md) | Prioritize features using RICE scoring (Reach, Impact, Confidence, Effort) with optional capacity constraints. |
+| [`/sprint-health`](sprint-health.md) | Score sprint health across delivery, quality, and team metrics with velocity trend analysis. |
+| [`/tdd`](tdd.md) | Generate tests, analyze coverage, and validate test quality using the TDD Guide skill. |
+| [`/tech-debt`](tech-debt.md) | Scan codebases for technical debt, score severity, and generate prioritized remediation plans. |
+| [`/user-story`](user-story.md) | Generate structured user stories with acceptance criteria, story points, and sprint capacity planning. |
diff --git a/docs/commands/okr.md b/docs/commands/okr.md
new file mode 100644
index 0000000..2dfb663
--- /dev/null
+++ b/docs/commands/okr.md
@@ -0,0 +1,44 @@
+---
+title: "/okr"
+description: "/okr — Claude Code slash command."
+---
+
+# /okr
+
+**Type:** Slash Command | **Source:** [`commands/okr.md`](https://github.com/alirezarezvani/claude-skills/tree/main/commands/okr.md)
+
+---
+
+
+# /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`
diff --git a/docs/commands/persona.md b/docs/commands/persona.md
new file mode 100644
index 0000000..8fb4a9c
--- /dev/null
+++ b/docs/commands/persona.md
@@ -0,0 +1,47 @@
+---
+title: "/persona"
+description: "/persona — Claude Code slash command."
+---
+
+# /persona
+
+**Type:** Slash Command | **Source:** [`commands/persona.md`](https://github.com/alirezarezvani/claude-skills/tree/main/commands/persona.md)
+
+---
+
+
+# /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`
diff --git a/docs/commands/pipeline.md b/docs/commands/pipeline.md
new file mode 100644
index 0000000..c8bff52
--- /dev/null
+++ b/docs/commands/pipeline.md
@@ -0,0 +1,37 @@
+---
+title: "/pipeline"
+description: "/pipeline — Claude Code slash command."
+---
+
+# /pipeline
+
+**Type:** Slash Command | **Source:** [`commands/pipeline.md`](https://github.com/alirezarezvani/claude-skills/tree/main/commands/pipeline.md)
+
+---
+
+
+# /pipeline
+
+Detect project stack and generate CI/CD pipeline configurations for GitHub Actions or GitLab CI.
+
+## Usage
+
+```
+/pipeline detect [--repo <project-dir>]               Detect stack, tools, and services
+/pipeline generate --platform github|gitlab [--repo <project-dir>]  Generate pipeline YAML
+```
+
+## Examples
+
+```
+/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 (`--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`
diff --git a/docs/commands/project-health.md b/docs/commands/project-health.md
new file mode 100644
index 0000000..49ce5ab
--- /dev/null
+++ b/docs/commands/project-health.md
@@ -0,0 +1,50 @@
+---
+title: "/project-health"
+description: "/project-health — Claude Code slash command."
+---
+
+# /project-health
+
+**Type:** Slash Command | **Source:** [`commands/project-health.md`](https://github.com/alirezarezvani/claude-skills/tree/main/commands/project-health.md)
+
+---
+
+
+# /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`
diff --git a/docs/commands/retro.md b/docs/commands/retro.md
new file mode 100644
index 0000000..527f537
--- /dev/null
+++ b/docs/commands/retro.md
@@ -0,0 +1,49 @@
+---
+title: "/retro"
+description: "/retro — Claude Code slash command."
+---
+
+# /retro
+
+**Type:** Slash Command | **Source:** [`commands/retro.md`](https://github.com/alirezarezvani/claude-skills/tree/main/commands/retro.md)
+
+---
+
+
+# /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`
diff --git a/docs/commands/rice.md b/docs/commands/rice.md
new file mode 100644
index 0000000..e6136ba
--- /dev/null
+++ b/docs/commands/rice.md
@@ -0,0 +1,46 @@
+---
+title: "/rice"
+description: "/rice — Claude Code slash command."
+---
+
+# /rice
+
+**Type:** Slash Command | **Source:** [`commands/rice.md`](https://github.com/alirezarezvani/claude-skills/tree/main/commands/rice.md)
+
+---
+
+
+# /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`
diff --git a/docs/commands/sprint-health.md b/docs/commands/sprint-health.md
new file mode 100644
index 0000000..6d097aa
--- /dev/null
+++ b/docs/commands/sprint-health.md
@@ -0,0 +1,50 @@
+---
+title: "/sprint-health"
+description: "/sprint-health — Claude Code slash command."
+---
+
+# /sprint-health
+
+**Type:** Slash Command | **Source:** [`commands/sprint-health.md`](https://github.com/alirezarezvani/claude-skills/tree/main/commands/sprint-health.md)
+
+---
+
+
+# /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`
diff --git a/docs/commands/tdd.md b/docs/commands/tdd.md
new file mode 100644
index 0000000..d8ad88c
--- /dev/null
+++ b/docs/commands/tdd.md
@@ -0,0 +1,43 @@
+---
+title: "/tdd"
+description: "/tdd — Claude Code slash command."
+---
+
+# /tdd
+
+**Type:** Slash Command | **Source:** [`commands/tdd.md`](https://github.com/alirezarezvani/claude-skills/tree/main/commands/tdd.md)
+
+---
+
+
+# /tdd
+
+Generate tests, analyze coverage, and validate test quality using the TDD Guide skill.
+
+## Usage
+
+```
+/tdd generate <file-or-dir>     Generate tests for source files
+/tdd coverage <test-dir>        Analyze test coverage and gaps
+/tdd validate <test-file>       Validate test quality (assertions, edge cases)
+```
+
+## Examples
+
+```
+/tdd generate src/auth/login.ts
+/tdd coverage tests/ --threshold 80
+/tdd validate tests/auth.test.ts
+```
+
+## Scripts
+- `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`
diff --git a/docs/commands/tech-debt.md b/docs/commands/tech-debt.md
new file mode 100644
index 0000000..e8a714e
--- /dev/null
+++ b/docs/commands/tech-debt.md
@@ -0,0 +1,39 @@
+---
+title: "/tech-debt"
+description: "/tech-debt — Claude Code slash command."
+---
+
+# /tech-debt
+
+**Type:** Slash Command | **Source:** [`commands/tech-debt.md`](https://github.com/alirezarezvani/claude-skills/tree/main/commands/tech-debt.md)
+
+---
+
+
+# /tech-debt
+
+Scan codebases for technical debt, score severity, and generate prioritized remediation plans.
+
+## Usage
+
+```
+/tech-debt scan <project-dir>           Scan for debt indicators
+/tech-debt prioritize <inventory.json>  Prioritize debt backlog
+/tech-debt report <project-dir>         Full dashboard with trends
+```
+
+## Examples
+
+```
+/tech-debt scan ./src
+/tech-debt scan . --format json
+/tech-debt report . --format json --output debt-report.json
+```
+
+## Scripts
+- `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`
diff --git a/docs/commands/user-story.md b/docs/commands/user-story.md
new file mode 100644
index 0000000..76e5e41
--- /dev/null
+++ b/docs/commands/user-story.md
@@ -0,0 +1,50 @@
+---
+title: "/user-story"
+description: "/user-story — Claude Code slash command."
+---
+
+# /user-story
+
+**Type:** Slash Command | **Source:** [`commands/user-story.md`](https://github.com/alirezarezvani/claude-skills/tree/main/commands/user-story.md)
+
+---
+
+
+# /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`
diff --git a/docs/getting-started.md b/docs/getting-started.md
index ed36e60..ee439c4 100644
--- a/docs/getting-started.md
+++ b/docs/getting-started.md
@@ -1,6 +1,6 @@
 ---
 title: Getting Started
-description: "How to install and use Claude Code skills and plugins for Claude Code, OpenAI Codex, and OpenClaw."
+description: "How to install and use Claude Code skills and plugins for Claude Code, OpenAI Codex, Gemini CLI, and OpenClaw."
 ---
 
 # Getting Started
@@ -38,6 +38,19 @@ Choose your platform and follow the steps:
     ./scripts/codex-install.sh
     ```
 
+=== "Gemini CLI"
+
+    ```bash
+    git clone https://github.com/alirezarezvani/claude-skills.git
+    ./scripts/gemini-install.sh
+    ```
+
+    Or use the sync script to generate the skills index:
+
+    ```bash
+    python3 scripts/sync-gemini-skills.py
+    ```
+
 === "OpenClaw"
 
     ```bash
@@ -99,18 +112,21 @@ AI-augmented development. Optimize for SEO.
 
 ## Python Tools
 
-All 218+ tools use the standard library only — zero pip installs.
+All 237 tools use the standard library only — zero pip installs, all verified.
 
 ```bash
 # Security audit a skill before installing
 python3 engineering/skill-security-auditor/scripts/skill_security_auditor.py /path/to/skill/
 
 # Analyze brand voice
-python3 marketing-skill/content-creator/scripts/brand_voice_analyzer.py article.txt
+python3 marketing-skill/content-production/scripts/brand_voice_analyzer.py article.txt
 
 # RICE prioritization
 python3 product-team/product-manager-toolkit/scripts/rice_prioritizer.py features.csv
 
+# Generate landing page (TSX + Tailwind)
+python3 product-team/landing-page-generator/scripts/landing_page_scaffolder.py config.json --format tsx
+
 # Tech debt scoring
 python3 c-level-advisor/cto-advisor/scripts/tech_debt_analyzer.py /path/to/codebase
 ```
@@ -160,3 +176,9 @@ See the [Skills & Agents Factory](https://github.com/alirezarezvani/claude-code-
 
 ??? question "How do I update installed skills?"
     Re-run the install command. The plugin system fetches the latest version from the marketplace.
+
+??? question "Will upgrading to v2.1.2 break my setup?"
+    No. v2.1.2 is fully backward compatible. Existing SKILL.md files, scripts, and references are unchanged. New features (TSX output, brand voice integration) are opt-in additions.
+
+??? question "Does this work with Gemini CLI?"
+    Yes. Run `./scripts/gemini-install.sh` to set up skills for Gemini CLI. A sync script (`scripts/sync-gemini-skills.py`) generates the skills index automatically.
diff --git a/docs/index.md b/docs/index.md
index c22c0ff..ff3e399 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -1,6 +1,6 @@
 ---
 title: Claude Code Skills & Plugins
-description: "177 production-ready skills and plugins for Claude Code, OpenAI Codex, and OpenClaw. Reusable expertise bundles for engineering, product, marketing, compliance, and more."
+description: "170 production-ready skills, 14 agents, and 12 commands for Claude Code, OpenAI Codex, Gemini CLI, and OpenClaw."
 hide:
   - toc
   - edit
@@ -14,10 +14,10 @@ hide:
 
 # Claude Code Skills
 
-177 production-ready skills that transform AI coding agents into specialized professionals.
+170 production-ready skills that transform AI coding agents into specialized professionals.
 { .hero-subtitle }
 
-**Claude Code** | **OpenAI Codex** | **OpenClaw**
+**Claude Code** | **OpenAI Codex** | **Gemini CLI** | **OpenClaw**
 { .hero-platforms }
 
 [Get Started](getting-started.md){ .md-button .md-button--primary }
@@ -27,29 +27,29 @@ hide:
 
 <div class="grid cards" markdown>
 
--   :material-counter:{ .lg .middle } **177**
+-   :material-counter:{ .lg .middle } **170**
 
     ---
 
     Production-ready skills
 
--   :material-language-python:{ .lg .middle } **218+**
+-   :material-language-python:{ .lg .middle } **237**
 
     ---
 
-    Python CLI tools (stdlib-only)
+    Python CLI tools (stdlib-only, all verified)
 
--   :material-domain:{ .lg .middle } **9**
+-   :material-robot:{ .lg .middle } **14**
 
     ---
 
-    Professional domains
+    [Multi-skill agents](agents/)
 
--   :material-package-variant:{ .lg .middle } **0**
+-   :material-console:{ .lg .middle } **12**
 
     ---
 
-    External dependencies
+    [Slash commands](commands/)
 
 </div>
 
@@ -79,7 +79,7 @@ hide:
 
     ---
 
-    Product manager, agile PO, strategist, UX researcher, UI design system, landing pages, SaaS scaffolder
+    Product manager, agile PO, strategist, UX researcher, UI design system, landing pages (TSX + Tailwind), SaaS scaffolder
 
     [:octicons-arrow-right-24: 8 skills](skills/product-team/)
 
diff --git a/docs/skills/product-team/landing-page-generator.md b/docs/skills/product-team/landing-page-generator.md
index 13ff672..4671419 100644
--- a/docs/skills/product-team/landing-page-generator.md
+++ b/docs/skills/product-team/landing-page-generator.md
@@ -37,11 +37,16 @@ Generate high-converting landing pages from a product description. Output comple
 Follow these steps in order for every landing page request:
 
 1. **Gather inputs** — collect product name, tagline, audience, pain point, key benefit, pricing tiers, design style, and copy framework using the trigger format below. Ask only for missing fields.
-2. **Select design style** — map the user's choice (or infer from context) to one of the four Tailwind class sets in the Design Style Reference.
-3. **Apply copy framework** — write all headline and body copy using the chosen framework (PAS / AIDA / BAB) before generating components.
-4. **Generate sections in order** — Hero → Features → Pricing → FAQ → Testimonials → CTA → Footer. Skip sections not relevant to the product.
-5. **Validate against SEO checklist** — run through every item in the SEO Checklist before outputting final code. Fix any gaps inline.
-6. **Output final components** — deliver complete, copy-paste-ready TSX files with all Tailwind classes, SEO meta, and structured data included.
+2. **Analyze brand voice** (recommended) — if the user has existing brand content (website copy, blog posts, marketing materials), run it through `marketing-skill/content-production/scripts/brand_voice_analyzer.py` to get a voice profile (formality, tone, perspective). Use the profile to inform design style and copy framework selection:
+   - 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. **Select design style** — map the user's choice (or infer from brand voice analysis) to one of the four Tailwind class sets in the Design Style Reference.
+4. **Apply copy framework** — write all headline and body copy using the chosen framework (PAS / AIDA / BAB) before generating components. Match the voice profile's formality and tone throughout.
+5. **Generate sections in order** — Hero → Features → Pricing → FAQ → Testimonials → CTA → Footer. Skip sections not relevant to the product.
+6. **Validate against SEO checklist** — run through every item in the SEO Checklist before outputting final code. Fix any gaps inline.
+7. **Output final components** — deliver complete, copy-paste-ready TSX files with all Tailwind classes, SEO meta, and structured data included.
 
 ---
 
@@ -190,3 +195,11 @@ Inject `FAQPage` JSON-LD via `<script type="application/ld+json" dangerouslySetI
 - CTA copy too vague — "Get started" beats "Learn more"; "Start free trial" beats "Sign up"
 - Pricing page missing trust signals — add money-back guarantee and testimonials near CTA
 - No above-the-fold CTA on mobile — ensure button is visible without scrolling on 375px viewport
+
+---
+
+## Related Skills
+
+- **Brand Voice Analyzer** (`marketing-skill/content-production/scripts/brand_voice_analyzer.py`) — Run before generation to establish voice profile and ensure copy consistency
+- **UI Design System** (`product-team/ui-design-system/`) — Generate design tokens from brand color before building the page
+- **Competitive Teardown** (`product-team/competitive-teardown/`) — Competitive positioning informs landing page messaging and differentiation
diff --git a/mkdocs.yml b/mkdocs.yml
index a755acf..f758c64 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -1,6 +1,6 @@
 site_name: Claude Code Skills & Plugins
 site_url: https://alirezarezvani.github.io/claude-skills
-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_description: "170 production-ready skills, 14 agents, and 12 commands for Claude Code, OpenAI Codex, Gemini CLI, and OpenClaw. Reusable expertise for engineering, product, marketing, compliance, and more."
 site_author: Alireza Rezvani
 repo_url: https://github.com/alirezarezvani/claude-skills
 repo_name: alirezarezvani/claude-skills
@@ -309,3 +309,33 @@ nav:
     - Finance:
       - Overview: skills/finance/index.md
       - "Financial Analyst": skills/finance/financial-analyst.md
+  - Agents:
+    - Overview: agents/index.md
+    - "CS Agile Product Owner": agents/cs-agile-product-owner.md
+    - "CS CEO Advisor": agents/cs-ceo-advisor.md
+    - "CS Content Creator": agents/cs-content-creator.md
+    - "CS CTO Advisor": agents/cs-cto-advisor.md
+    - "CS Demand Gen Specialist": agents/cs-demand-gen-specialist.md
+    - "CS Engineering Lead": agents/cs-engineering-lead.md
+    - "CS Financial Analyst": agents/cs-financial-analyst.md
+    - "CS Growth Strategist": agents/cs-growth-strategist.md
+    - "CS Product Manager": agents/cs-product-manager.md
+    - "CS Product Strategist": agents/cs-product-strategist.md
+    - "CS Project Manager": agents/cs-project-manager.md
+    - "CS Quality & Regulatory": agents/cs-quality-regulatory.md
+    - "CS Senior Engineer": agents/cs-senior-engineer.md
+    - "CS UX Researcher": agents/cs-ux-researcher.md
+  - Commands:
+    - Overview: commands/index.md
+    - "/changelog": commands/changelog.md
+    - "/competitive-matrix": commands/competitive-matrix.md
+    - "/okr": commands/okr.md
+    - "/persona": commands/persona.md
+    - "/pipeline": commands/pipeline.md
+    - "/project-health": commands/project-health.md
+    - "/retro": commands/retro.md
+    - "/rice": commands/rice.md
+    - "/sprint-health": commands/sprint-health.md
+    - "/tdd": commands/tdd.md
+    - "/tech-debt": commands/tech-debt.md
+    - "/user-story": commands/user-story.md
diff --git a/scripts/generate-docs.py b/scripts/generate-docs.py
index 58100e4..e526aa1 100644
--- a/scripts/generate-docs.py
+++ b/scripts/generate-docs.py
@@ -1,5 +1,5 @@
 #!/usr/bin/env python3
-"""Generate MkDocs documentation pages from all SKILL.md files in the repository."""
+"""Generate MkDocs documentation pages from SKILL.md files, agents, and commands."""
 
 import os
 import re
@@ -80,6 +80,30 @@ def extract_title(filepath):
     return None
 
 
+def extract_subtitle(filepath):
+    """Extract the first non-empty line after the first H1 heading."""
+    try:
+        with open(filepath, "r", encoding="utf-8") as f:
+            found_h1 = False
+            in_frontmatter = False
+            for line in f:
+                stripped = line.strip()
+                if stripped == "---" and not in_frontmatter:
+                    in_frontmatter = True
+                    for line2 in f:
+                        if line2.strip() == "---":
+                            break
+                    continue
+                if stripped.startswith("# ") and not found_h1:
+                    found_h1 = True
+                    continue
+                if found_h1 and stripped and not stripped.startswith("#"):
+                    return stripped
+    except Exception:
+        pass
+    return None
+
+
 def slugify(name):
     """Convert a skill name to a URL-friendly slug."""
     return re.sub(r"[^a-z0-9-]", "-", name.lower()).strip("-")
@@ -226,10 +250,152 @@ description: "All {domain_name} skills for Claude Code, OpenAI Codex, and OpenCl
         with open(index_path, "w", encoding="utf-8") as f:
             f.write(index_content)
 
-    # Print nav YAML for mkdocs.yml
+    # Generate agent pages
+    agents_dir = os.path.join(REPO_ROOT, "agents")
+    agents_docs_dir = os.path.join(DOCS_DIR, "agents")
+    os.makedirs(agents_docs_dir, exist_ok=True)
+    agent_count = 0
+    agent_entries = []
+
+    # Agent domain mapping for display
+    AGENT_DOMAINS = {
+        "business-growth": "Business & Growth",
+        "c-level": "C-Level Advisory",
+        "engineering-team": "Engineering - Core",
+        "engineering": "Engineering - POWERFUL",
+        "finance": "Finance",
+        "marketing": "Marketing",
+        "product": "Product",
+        "project-management": "Project Management",
+        "ra-qm-team": "Regulatory & Quality",
+    }
+
+    if os.path.isdir(agents_dir):
+        for domain_folder in sorted(os.listdir(agents_dir)):
+            domain_path = os.path.join(agents_dir, domain_folder)
+            if not os.path.isdir(domain_path):
+                continue
+            domain_label = AGENT_DOMAINS.get(domain_folder, prettify(domain_folder))
+            for agent_file in sorted(os.listdir(domain_path)):
+                if not agent_file.endswith(".md"):
+                    continue
+                agent_name = agent_file.replace(".md", "")
+                agent_path = os.path.join(domain_path, agent_file)
+                rel = os.path.relpath(agent_path, REPO_ROOT)
+                title = extract_title(agent_path) or prettify(agent_name)
+                title = re.sub(r"[*_`]", "", title)
+
+                with open(agent_path, "r", encoding="utf-8") as f:
+                    content = f.read()
+
+                content_clean = re.sub(r"^---\n.*?---\n", "", content, flags=re.DOTALL)
+                content_clean = re.sub(r"^#\s+.+\n", "", content_clean, count=1)
+
+                page = f"""---
+title: "{title}"
+description: "{title} - Claude Code agent for {domain_label}."
+---
+
+# {title}
+
+**Type:** Agent | **Domain:** {domain_label} | **Source:** [`{rel}`](https://github.com/alirezarezvani/claude-skills/tree/main/{rel})
+
+---
+
+{content_clean}"""
+                slug = slugify(agent_name)
+                out_path = os.path.join(agents_docs_dir, f"{slug}.md")
+                with open(out_path, "w", encoding="utf-8") as f:
+                    f.write(page)
+                agent_count += 1
+                agent_entries.append((title, slug, domain_label))
+
+    # Generate agents index
+    if agent_entries:
+        idx = f"""---
+title: "Agents"
+description: "All {agent_count} Claude Code agents — multi-skill orchestrators across domains."
+---
+
+# Agents
+
+{agent_count} agents that orchestrate skills across domains.
+
+| Agent | Domain |
+|-------|--------|
+"""
+        for title, slug, domain in agent_entries:
+            idx += f"| [{title}]({slug}.md) | {domain} |\n"
+        with open(os.path.join(agents_docs_dir, "index.md"), "w", encoding="utf-8") as f:
+            f.write(idx)
+
+    # Generate command pages
+    commands_dir = os.path.join(REPO_ROOT, "commands")
+    commands_docs_dir = os.path.join(DOCS_DIR, "commands")
+    os.makedirs(commands_docs_dir, exist_ok=True)
+    cmd_count = 0
+    cmd_entries = []
+
+    if os.path.isdir(commands_dir):
+        for cmd_file in sorted(os.listdir(commands_dir)):
+            if not cmd_file.endswith(".md") or cmd_file == "CLAUDE.md":
+                continue
+            cmd_name = cmd_file.replace(".md", "")
+            cmd_path = os.path.join(commands_dir, cmd_file)
+            rel = os.path.relpath(cmd_path, REPO_ROOT)
+            title = extract_title(cmd_path) or prettify(cmd_name)
+            title = re.sub(r"[*_`]", "", title)
+
+            with open(cmd_path, "r", encoding="utf-8") as f:
+                content = f.read()
+
+            content_clean = re.sub(r"^---\n.*?---\n", "", content, flags=re.DOTALL)
+            content_clean = re.sub(r"^#\s+.+\n", "", content_clean, count=1)
+
+            page = f"""---
+title: "/{cmd_name}"
+description: "/{cmd_name} — Claude Code slash command."
+---
+
+# /{cmd_name}
+
+**Type:** Slash Command | **Source:** [`{rel}`](https://github.com/alirezarezvani/claude-skills/tree/main/{rel})
+
+---
+
+{content_clean}"""
+            slug = slugify(cmd_name)
+            out_path = os.path.join(commands_docs_dir, f"{slug}.md")
+            with open(out_path, "w", encoding="utf-8") as f:
+                f.write(page)
+            cmd_count += 1
+            desc = extract_subtitle(cmd_path) or title
+            cmd_entries.append((cmd_name, slug, title, desc))
+
+    # Generate commands index
+    if cmd_entries:
+        idx = f"""---
+title: "Commands"
+description: "All {cmd_count} slash commands for quick access to common operations."
+---
+
+# Slash Commands
+
+{cmd_count} commands for quick access to common operations.
+
+| Command | Description |
+|---------|-------------|
+"""
+        for name, slug, title, desc in cmd_entries:
+            idx += f"| [`/{name}`]({slug}.md) | {desc} |\n"
+        with open(os.path.join(commands_docs_dir, "index.md"), "w", encoding="utf-8") as f:
+            f.write(idx)
+
+    # Print summary
     print(f"Generated {total} skill pages across {len(skills_by_domain)} domains.")
-    print("\nNav structure for mkdocs.yml:\n")
-    print(generate_nav_entry(skills_by_domain))
+    print(f"Generated {agent_count} agent pages.")
+    print(f"Generated {cmd_count} command pages.")
+    print(f"Total: {total + agent_count + cmd_count} pages.")
 
 
 if __name__ == "__main__":