aigroup-workflow 1.0.1 → 1.1.0

package/skills/jarvis/engineering-team/docs/agents/cs-senior-engineer.md

@@ -1,91 +0,0 @@
----
-title: "Senior Engineer — AI Coding Agent & Codex Skill"
-description: "Senior Engineer agent for architecture decisions, code review, DevOps, and API design. Orchestrates engineering and engineering-team skills for. Agent-native orchestrator for Claude Code, Codex, Gemini CLI."
----
-
-# Senior Engineer
-
-<div class="page-meta" markdown>
-<span class="meta-badge">:material-robot: Agent</span>
-<span class="meta-badge">:material-rocket-launch: Engineering - POWERFUL</span>
-<span class="meta-badge">:material-github: <a href="https://github.com/alirezarezvani/claude-skills/tree/main/agents/engineering/cs-senior-engineer.md">Source</a></span>
-</div>
-
-
-## 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](https://github.com/alirezarezvani/claude-skills/tree/main/agents/engineering-team/cs-engineering-lead.md) -- Team coordination, incident response, and cross-functional delivery
-- [cs-product-manager](https://github.com/alirezarezvani/claude-skills/tree/main/agents/product/cs-product-manager.md) -- Feature prioritization and requirements context

package/skills/jarvis/engineering-team/docs/agents/cs-ux-researcher.md

@@ -1,534 +0,0 @@
----
-title: "UX Researcher Agent — AI Coding Agent & Codex Skill"
-description: "UX research agent for research planning, persona generation, journey mapping, and usability test analysis. Agent-native orchestrator for Claude Code, Codex, Gemini CLI."
----
-
-# UX Researcher Agent
-
-<div class="page-meta" markdown>
-<span class="meta-badge">:material-robot: Agent</span>
-<span class="meta-badge">:material-lightbulb-outline: Product</span>
-<span class="meta-badge">:material-github: <a href="https://github.com/alirezarezvani/claude-skills/tree/main/agents/product/cs-ux-researcher.md">Source</a></span>
-</div>
-
-
-## 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`](https://github.com/alirezarezvani/claude-skills/tree/main/product-team/ux-researcher-designer)
-
-### All Orchestrated Skills
-
-| # | Skill | Location | Primary Tool |
-|---|-------|----------|-------------|
-| 1 | UX Researcher & Designer | [`product-team/ux-researcher-designer`](https://github.com/alirezarezvani/claude-skills/tree/main/product-team/ux-researcher-designer) | persona_generator.py |
-| 2 | Product Manager Toolkit | [`product-team/product-manager-toolkit`](https://github.com/alirezarezvani/claude-skills/tree/main/product-team/product-manager-toolkit) | customer_interview_analyzer.py |
-| 3 | UI Design System | [`product-team/ui-design-system`](https://github.com/alirezarezvani/claude-skills/tree/main/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:** [`scripts/persona_generator.py`](https://github.com/alirezarezvani/claude-skills/tree/main/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:** [`scripts/customer_interview_analyzer.py`](https://github.com/alirezarezvani/claude-skills/tree/main/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:** [`scripts/design_token_generator.py`](https://github.com/alirezarezvani/claude-skills/tree/main/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:** [`references/persona-methodology.md`](https://github.com/alirezarezvani/claude-skills/tree/main/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:** [`references/example-personas.md`](https://github.com/alirezarezvani/claude-skills/tree/main/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:** [`references/journey-mapping-guide.md`](https://github.com/alirezarezvani/claude-skills/tree/main/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:** [`references/usability-testing-frameworks.md`](https://github.com/alirezarezvani/claude-skills/tree/main/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:** [`references/component-architecture.md`](https://github.com/alirezarezvani/claude-skills/tree/main/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:** [`references/developer-handoff.md`](https://github.com/alirezarezvani/claude-skills/tree/main/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:** [`assets/research_plan_template.md`](https://github.com/alirezarezvani/claude-skills/tree/main/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:** [`assets/design_system_doc_template.md`](https://github.com/alirezarezvani/claude-skills/tree/main/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`](https://github.com/alirezarezvani/claude-skills/tree/main/product-team/ui-design-system))
-
-## References
-
-- **Primary Skill:** [../../product-team/ux-researcher-designer/SKILL.md](https://github.com/alirezarezvani/claude-skills/tree/main/product-team/ux-researcher-designer/SKILL.md)
-- **Interview Analyzer:** [../../product-team/product-manager-toolkit/SKILL.md](https://github.com/alirezarezvani/claude-skills/tree/main/product-team/product-manager-toolkit/SKILL.md)
-- **Persona Methodology:** [../../product-team/ux-researcher-designer/references/persona-methodology.md](https://github.com/alirezarezvani/claude-skills/tree/main/product-team/ux-researcher-designer/references/persona-methodology.md)
-- **Journey Mapping Guide:** [../../product-team/ux-researcher-designer/references/journey-mapping-guide.md](https://github.com/alirezarezvani/claude-skills/tree/main/product-team/ux-researcher-designer/references/journey-mapping-guide.md)
-- **Usability Testing:** [../../product-team/ux-researcher-designer/references/usability-testing-frameworks.md](https://github.com/alirezarezvani/claude-skills/tree/main/product-team/ux-researcher-designer/references/usability-testing-frameworks.md)
-- **Design System:** [../../product-team/ui-design-system/SKILL.md](https://github.com/alirezarezvani/claude-skills/tree/main/product-team/ui-design-system/SKILL.md)
-- **Product Domain Guide:** [../../product-team/CLAUDE.md](https://github.com/alirezarezvani/claude-skills/tree/main/product-team/CLAUDE.md)
-- **Agent Development Guide:** [../CLAUDE.md](https://github.com/alirezarezvani/claude-skills/tree/main/agents/CLAUDE.md)
-
----
-
-**Last Updated:** March 9, 2026
-**Status:** Production Ready
-**Version:** 1.0