[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75Y3VPPB4MPJF28DYZ8TGK8":3,"skill-same:01M75Y3VPPB4MPJF28DYZ8TGK8":105},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":38,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M75Y3VPPB4MPJF28DYZ8TGK8","scrum-master",null,"Advanced Scrum Master with data-driven team health analysis, velocity forecasting, retrospective insights, and team development expertise. Features comprehensive sprint health scoring, Monte Carlo forecasting, and psychological safety frameworks for high-performing agile teams.","aAAaqwq\u002Fopenclaw-team","aAAaqwq","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F163369189?v=4","01M75WCZBK64XMP4RKNQB2ZV08","Daniel Li","01M75WCZCCEHPJV69BNPNXJY9E",2,"MIT","https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Freferences\u002Fagi-super-team\u002Fskills\u002Fscrum-master\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: scrum-master\ndescription: Advanced Scrum Master with data-driven team health analysis, velocity forecasting, retrospective insights, and team development expertise. Features comprehensive sprint health scoring, Monte Carlo forecasting, and psychological safety frameworks for high-performing agile teams.\nlicense: MIT\nmetadata:\n  version: 2.0.0\n  author: Alireza Rezvani\n  category: project-management\n  domain: agile-development\n  updated: 2026-02-15\n  python-tools: velocity_analyzer.py, sprint_health_scorer.py, retrospective_analyzer.py\n  tech-stack: scrum, agile-coaching, team-dynamics, data-analysis\n---\n\n# Scrum Master Expert\n\nAdvanced agile practitioner specializing in data-driven team development, psychological safety facilitation, and high-performance sprint execution. Combines traditional Scrum mastery with modern analytics, behavioral science, and continuous improvement methodologies for sustainable team excellence.\n\n---\n\n## Table of Contents\n\n- [Capabilities](#capabilities)\n- [Input Requirements](#input-requirements)\n- [Analysis Tools](#analysis-tools)\n- [Methodology](#methodology)\n- [Templates & Assets](#templates--assets)\n- [Reference Frameworks](#reference-frameworks)\n- [Implementation Workflows](#implementation-workflows)\n- [Assessment & Measurement](#assessment--measurement)\n- [Best Practices](#best-practices)\n- [Advanced Techniques](#advanced-techniques)\n- [Limitations & Considerations](#limitations--considerations)\n\n---\n\n## Capabilities\n\n### Data-Driven Sprint Analytics\n- **Velocity Analysis**: Multi-dimensional velocity tracking with trend detection, anomaly identification, and Monte Carlo forecasting using `velocity_analyzer.py`\n- **Sprint Health Scoring**: Comprehensive health assessment across 6 dimensions (commitment reliability, scope stability, blocker resolution, ceremony engagement, story completion, velocity predictability) via `sprint_health_scorer.py`\n- **Retrospective Intelligence**: Pattern recognition in team feedback, action item completion tracking, and improvement trend analysis through `retrospective_analyzer.py`\n\n### Team Development & Psychology\n- **Psychological Safety Facilitation**: Research-based approach to creating safe-to-fail environments using Google's Project Aristotle findings\n- **Team Maturity Assessment**: Tuckman's model applied to Scrum teams with stage-specific coaching interventions\n- **Conflict Resolution**: Structured approaches for productive disagreement and healthy team dynamics\n- **Performance Coaching**: Individual and team coaching using behavioral science and adult learning principles\n\n### Advanced Forecasting & Planning\n- **Monte Carlo Simulation**: Probabilistic sprint and release forecasting with confidence intervals\n- **Capacity Planning**: Statistical modeling of team capacity with seasonal adjustments and dependency analysis\n- **Risk Assessment**: Early warning systems for team performance degradation and intervention recommendations\n\n### Process Excellence\n- **Ceremony Optimization**: Data-driven improvement of sprint ceremonies for maximum value and engagement\n- **Continuous Improvement Systems**: Automated tracking of retrospective action items and improvement velocity\n- **Stakeholder Communication**: Executive-ready reports with actionable insights and trend analysis\n\n---\n\n## Input Requirements\n\n### Sprint Data Structure\nAll analysis tools accept JSON input following the schema in `assets\u002Fsample_sprint_data.json`:\n\n```json\n{\n  \"team_info\": { \"name\": \"string\", \"size\": \"number\", \"scrum_master\": \"string\" },\n  \"sprints\": [\n    {\n      \"sprint_number\": \"number\",\n      \"planned_points\": \"number\", \n      \"completed_points\": \"number\",\n      \"stories\": [...],\n      \"blockers\": [...],\n      \"ceremonies\": {...}\n    }\n  ],\n  \"retrospectives\": [\n    {\n      \"sprint_number\": \"number\",\n      \"went_well\": [\"string\"],\n      \"to_improve\": [\"string\"],\n      \"action_items\": [...]\n    }\n  ]\n}\n```\n\n### Minimum Data Requirements\n- **Velocity Analysis**: 3+ sprints (6+ recommended for statistical significance)\n- **Health Scoring**: 2+ sprints with ceremony and story completion data\n- **Retrospective Analysis**: 3+ retrospectives with action item tracking\n- **Team Development Assessment**: 4+ weeks of observation data\n\n---\n\n## Analysis Tools\n\n### Velocity Analyzer (`scripts\u002Fvelocity_analyzer.py`)\nComprehensive velocity analysis with statistical modeling and forecasting.\n\n**Features**:\n- Rolling averages (3, 5, 8 sprint windows)\n- Trend detection using linear regression\n- Volatility assessment (coefficient of variation)\n- Anomaly detection (outliers beyond 2σ)\n- Monte Carlo forecasting with confidence intervals\n\n**Usage**:\n```bash\npython velocity_analyzer.py sprint_data.json --format text\npython velocity_analyzer.py sprint_data.json --format json > analysis.json\n```\n\n**Outputs**:\n- Velocity trends (improving\u002Fstable\u002Fdeclining)\n- Predictability metrics (CV, volatility classification)\n- 6-sprint forecast with 50%, 70%, 85%, 95% confidence intervals\n- Anomaly identification with root cause suggestions\n\n### Sprint Health Scorer (`scripts\u002Fsprint_health_scorer.py`)\nMulti-dimensional team health assessment with actionable recommendations.\n\n**Scoring Dimensions** (weighted):\n1. **Commitment Reliability** (25%): Sprint goal achievement consistency\n2. **Scope Stability** (20%): Mid-sprint scope change frequency\n3. **Blocker Resolution** (15%): Average time to resolve impediments\n4. **Ceremony Engagement** (15%): Participation and effectiveness metrics\n5. **Story Completion Distribution** (15%): Ratio of completed vs. partial stories\n6. **Velocity Predictability** (10%): Delivery consistency measurement\n\n**Usage**:\n```bash\npython sprint_health_scorer.py sprint_data.json --format text\n```\n\n**Outputs**:\n- Overall health score (0-100) with grade classification\n- Individual dimension scores with improvement recommendations\n- Trend analysis across sprints\n- Intervention priority matrix\n\n### Retrospective Analyzer (`scripts\u002Fretrospective_analyzer.py`)\nAdvanced retrospective data analysis for continuous improvement insights.\n\n**Analysis Components**:\n- **Action Item Tracking**: Completion rates by priority and owner\n- **Theme Identification**: Recurring patterns in team feedback\n- **Sentiment Analysis**: Positive\u002Fnegative trend tracking\n- **Improvement Velocity**: Rate of team development and problem resolution\n- **Team Maturity Scoring**: Development stage assessment\n\n**Usage**:\n```bash\npython retrospective_analyzer.py sprint_data.json --format text\n```\n\n**Outputs**:\n- Action item completion analytics with bottleneck identification\n- Recurring theme analysis with persistence scoring\n- Team maturity level assessment (forming\u002Fstorming\u002Fnorming\u002Fperforming)\n- Improvement velocity trends and recommendations\n\n---\n\n## Methodology\n\n### Data-Driven Scrum Mastery\nTraditional Scrum practices enhanced with quantitative analysis and behavioral science:\n\n#### 1. Measurement-First Approach\n- Establish baseline metrics before implementing changes\n- Use statistical significance testing for process improvements\n- Track leading indicators (engagement, psychological safety) alongside lagging indicators (velocity)\n- Apply continuous feedback loops for rapid iteration\n\n#### 2. Psychological Safety Foundation\nBased on Amy Edmondson's research and Google's Project Aristotle findings:\n- **Assessment**: Regular psychological safety surveys and behavioral observation\n- **Intervention**: Structured vulnerability modeling and safe-to-fail experiments\n- **Measurement**: Track speaking-up frequency, mistake discussion openness, help-seeking behavior\n\n#### 3. Team Development Lifecycle\nTuckman's model applied to Scrum teams with stage-specific facilitation:\n- **Forming**: Structure provision, process education, relationship building\n- **Storming**: Conflict facilitation, psychological safety maintenance, process flexibility\n- **Norming**: Autonomy building, process ownership transfer, external relationship development\n- **Performing**: Challenge introduction, innovation support, organizational impact facilitation\n\n#### 4. Continuous Improvement Science\nEvidence-based approach to retrospective outcomes:\n- Action item completion rate optimization\n- Root cause analysis using statistical methods\n- Improvement experiment design and measurement\n- Knowledge retention and pattern recognition\n\n---\n\n## Templates & Assets\n\n### Sprint Reporting (`assets\u002Fsprint_report_template.md`)\nProduction-ready sprint report template including:\n- Executive summary with health grade and key metrics\n- Delivery performance dashboard (commitment ratio, velocity trends)\n- Process health indicators (scope change, blocker resolution)\n- Quality metrics (DoD adherence, technical debt)\n- Risk assessment and stakeholder communication\n\n### Team Health Assessment (`assets\u002Fteam_health_check_template.md`)\nSpotify Squad Health Check model adaptation featuring:\n- 9-dimension health assessment (delivering value, learning, fun, codebase health, mission clarity, suitable process, support, speed, pawns vs. players)\n- Psychological safety evaluation framework\n- Team maturity level assessment\n- Action item prioritization matrix\n\n### Sample Data (`assets\u002Fsample_sprint_data.json`)\nComprehensive 6-sprint dataset demonstrating:\n- Multi-story sprint structure with realistic complexity\n- Blocker tracking and resolution patterns\n- Ceremony engagement metrics\n- Retrospective data with action item follow-through\n- Team capacity variations and external dependencies\n\n### Expected Outputs (`assets\u002Fexpected_output.json`)\nStandardized analysis results showing:\n- Velocity analysis with 20.2 point average and low volatility (CV: 12.7%)\n- Sprint health score of 78.3\u002F100 with dimension breakdowns\n- Retrospective insights showing 46.7% action item completion rate\n- Team maturity assessment at \"performing\" level\n\n---\n\n## Reference Frameworks\n\n### Velocity Forecasting Guide (`references\u002Fvelocity-forecasting-guide.md`)\nComprehensive guide to probabilistic estimation including:\n- Monte Carlo simulation implementation details\n- Confidence interval calculation methods\n- Trend adjustment techniques for improving\u002Fdeclining teams\n- Stakeholder communication strategies for uncertainty\n- Advanced techniques: seasonality adjustment, capacity modeling, multi-team dependencies\n\n### Team Dynamics Framework (`references\u002Fteam-dynamics-framework.md`)\nResearch-based team development approach covering:\n- Tuckman's stages applied to Scrum teams with specific behavioral indicators\n- Psychological safety assessment and building techniques\n- Conflict resolution strategies for productive disagreement\n- Stage-specific facilitation approaches and intervention strategies\n- Measurement tools for team development tracking\n\n---\n\n## Implementation Workflows\n\n### Sprint Execution Cycle\n\n#### Sprint Planning (Data-Informed)\n1. **Pre-Planning Analysis**:\n   - Run velocity analysis to determine sustainable commitment level\n   - Review sprint health scores from previous sprints\n   - Analyze retrospective action items for capacity impact\n\n2. **Capacity Determination**:\n   - Apply Monte Carlo forecasting for realistic point estimation\n   - Factor in team member availability and external dependencies\n   - Use historical commitment reliability data for scope negotiation\n\n3. **Goal Setting & Commitment**:\n   - Align sprint goals with team maturity level and capability trends\n   - Ensure psychological safety in commitment discussions\n   - Document assumptions and dependencies for retrospective analysis\n\n#### Daily Standups (Team Development Focus)\n1. **Structured Format** with team development overlay:\n   - Progress updates with impediment surfacing\n   - Help requests and collaboration opportunities\n   - Team dynamic observation and psychological safety assessment\n\n2. **Data Collection**:\n   - Track participation patterns and engagement levels\n   - Note conflict emergence and resolution attempts\n   - Monitor help-seeking behavior and vulnerability expression\n\n3. **Real-Time Coaching**:\n   - Model psychological safety through Scrum Master vulnerability\n   - Facilitate productive conflict when disagreements arise\n   - Encourage cross-functional collaboration and knowledge sharing\n\n#### Sprint Review (Stakeholder Alignment)\n1. **Demonstration with Context**:\n   - Present completed work with velocity and health context\n   - Share team development progress and capability growth\n   - Discuss impediments and organizational support needs\n\n2. **Feedback Integration**:\n   - Capture stakeholder input for retrospective analysis\n   - Assess scope change impacts on team health\n   - Plan adaptations based on team maturity and capacity\n\n#### Sprint Retrospective (Intelligence-Driven)\n1. **Data-Informed Facilitation**:\n   - Present sprint health scores and trends as starting point\n   - Use retrospective analyzer insights to guide discussion focus\n   - Surface patterns from historical retrospective themes\n\n2. **Action Item Optimization**:\n   - Limit action items based on team's completion rate history\n   - Assign owners and deadlines based on previous success patterns\n   - Design experiments with measurable success criteria\n\n3. **Continuous Improvement**:\n   - Track action item completion for next retrospective\n   - Measure team maturity progression using behavioral indicators\n   - Adjust facilitation approach based on team development stage\n\n### Team Development Intervention\n\n#### Assessment Phase\n1. **Multi-Dimensional Data Collection**:\n   ```bash\n   python sprint_health_scorer.py team_data.json > health_assessment.txt\n   python retrospective_analyzer.py team_data.json > retro_insights.txt\n   ```\n\n2. **Psychological Safety Evaluation**:\n   - Conduct anonymous team survey using Edmondson's 7-point scale\n   - Observe team interactions during ceremonies for safety indicators\n   - Interview team members individually for deeper insights\n\n3. **Team Maturity Assessment**:\n   - Map behaviors against Tuckman's model stages\n   - Assess autonomy level and self-organization capability\n   - Evaluate conflict handling and collaboration patterns\n\n#### Intervention Design\n1. **Stage-Appropriate Coaching**:\n   - **Forming**: Structure provision, process education, trust building\n   - **Storming**: Conflict facilitation, safety maintenance, process flexibility\n   - **Norming**: Autonomy building, ownership transfer, skill development\n   - **Performing**: Challenge provision, innovation support, organizational impact\n\n2. **Psychological Safety Building**:\n   - Model vulnerability and mistake admission\n   - Reward help-seeking and question-asking behavior\n   - Create safe-to-fail experiments and learning opportunities\n   - Facilitate difficult conversations with protective boundaries\n\n#### Progress Measurement\n1. **Quantitative Tracking**:\n   - Weekly ceremony engagement scores\n   - Monthly psychological safety pulse surveys\n   - Sprint-level team health score progression\n   - Quarterly team maturity assessment\n\n2. **Qualitative Indicators**:\n   - Behavioral observation during ceremonies\n   - Individual 1:1 conversation insights\n   - Stakeholder feedback on team collaboration\n   - External team perception and reputation\n\n---\n\n## Assessment & Measurement\n\n### Key Performance Indicators\n\n#### Team Health Metrics\n- **Overall Health Score**: Composite score across 6 dimensions (target: >80)\n- **Psychological Safety Index**: Team safety assessment (target: >4.0\u002F5.0)\n- **Team Maturity Level**: Development stage classification with progression tracking\n- **Improvement Velocity**: Rate of retrospective action item completion (target: >70%)\n\n#### Sprint Performance Metrics\n- **Velocity Predictability**: Coefficient of variation in sprint delivery (target: \u003C20%)\n- **Commitment Reliability**: Percentage of sprint goals achieved (target: >85%)\n- **Scope Stability**: Mid-sprint change frequency (target: \u003C15%)\n- **Blocker Resolution Time**: Average days to resolve impediments (target: \u003C3 days)\n\n#### Engagement Metrics\n- **Ceremony Participation**: Attendance and engagement quality (target: >90%)\n- **Knowledge Sharing**: Cross-training and collaboration frequency\n- **Innovation Frequency**: New ideas generated and implemented per sprint\n- **Stakeholder Satisfaction**: External perception of team performance\n\n### Assessment Schedule\n- **Daily**: Ceremony observation and team dynamic monitoring\n- **Weekly**: Sprint progress and impediment tracking\n- **Sprint**: Comprehensive health scoring and velocity analysis\n- **Monthly**: Psychological safety assessment and team maturity evaluation\n- **Quarterly**: Deep retrospective analysis and intervention strategy review\n\n### Calibration & Validation\n- Compare analytical insights with team self-assessment\n- Validate predictions against actual sprint outcomes\n- Cross-reference quantitative metrics with qualitative observations\n- Adjust models based on long-term team development patterns\n\n---\n\n## Best Practices\n\n### Data Collection Excellence\n1. **Consistency**: Maintain regular data collection rhythms without overwhelming the team\n2. **Transparency**: Share analytical insights openly to build trust and understanding\n3. **Actionability**: Focus on metrics that directly inform coaching decisions\n4. **Privacy**: Respect individual confidentiality while enabling team-level insights\n\n### Facilitation Mastery\n1. **Adaptive Leadership**: Match facilitation style to team development stage\n2. **Psychological Safety First**: Prioritize safety over process adherence when conflicts arise\n3. **Systems Thinking**: Address root causes rather than symptoms in team performance issues\n4. **Evidence-Based Coaching**: Use data to support coaching conversations and intervention decisions\n\n### Stakeholder Communication\n1. **Range Estimates**: Communicate uncertainty through confidence intervals rather than single points\n2. **Context Provision**: Explain team development stage and capability constraints\n3. **Trend Focus**: Emphasize improvement trajectories over absolute performance levels\n4. **Risk Transparency**: Surface impediments and dependencies proactively\n\n### Continuous Improvement\n1. **Experiment Design**: Structure process improvements as testable hypotheses\n2. **Measurement Planning**: Define success criteria before implementing changes\n3. **Feedback Loops**: Establish regular review cycles for intervention effectiveness\n4. **Learning Culture**: Model curiosity and mistake tolerance to encourage team experimentation\n\n---\n\n## Advanced Techniques\n\n### Predictive Analytics\n- **Early Warning Systems**: Identify teams at risk of performance degradation\n- **Intervention Timing**: Optimize coaching interventions based on team development patterns\n- **Capacity Forecasting**: Predict team capability changes based on historical patterns\n- **Dependency Modeling**: Assess cross-team collaboration impacts on performance\n\n### Behavioral Science Applications\n- **Cognitive Bias Recognition**: Help teams recognize and mitigate planning fallacy and confirmation bias\n- **Motivation Optimization**: Apply self-determination theory to enhance team autonomy and mastery\n- **Social Learning**: Leverage peer modeling and collective efficacy for skill development\n- **Change Management**: Use behavioral economics principles for sustainable process adoption\n\n### Advanced Facilitation\n- **Liberating Structures**: Apply structured facilitation methods for enhanced participation\n- **Appreciative Inquiry**: Focus team conversations on strengths and possibilities\n- **Systems Constellation**: Visualize team dynamics and organizational relationships\n- **Conflict Mediation**: Professional-level conflict resolution for complex team issues\n\n---\n\n## Limitations & Considerations\n\n### Data Quality Dependencies\n- **Minimum Sample Size**: Statistical significance requires 6+ sprints for meaningful analysis\n- **Data Completeness**: Missing ceremony data or retrospective information limits insight accuracy\n- **Context Sensitivity**: Algorithm recommendations must be interpreted within organizational and team context\n- **External Factors**: Analysis cannot account for all external influences on team performance\n\n### Psychological Safety Requirements\n- **Trust Building Time**: Authentic psychological safety development requires sustained effort over months\n- **Individual Differences**: Team members have varying comfort levels with vulnerability and feedback\n- **Cultural Considerations**: Organizational and national culture significantly impact safety building approaches\n- **Leadership Modeling**: Scrum Master psychological safety demonstration is prerequisite for team development\n\n### Scaling Challenges\n- **Team Size Limits**: Techniques optimized for 5-9 member teams may require adaptation for larger groups\n- **Multi-Team Coordination**: Dependencies across teams introduce complexity not fully captured by single-team metrics\n- **Organizational Alignment**: Team-level improvements may be constrained by broader organizational impediments\n- **Stakeholder Education**: External stakeholders require education on probabilistic planning and team development concepts\n\n### Measurement Limitations\n- **Quantitative Bias**: Over-reliance on metrics may overlook important qualitative team dynamics\n- **Gaming Potential**: Teams may optimize for measured metrics rather than underlying performance\n- **Lag Indicators**: Many important outcomes (psychological safety, team cohesion) are delayed relative to interventions\n- **Individual Privacy**: Balancing team insights with individual confidentiality and psychological safety\n\n---\n\n## Success Metrics & Outcomes\n\nTeams using this advanced Scrum Master approach typically achieve:\n\n- **40-60% improvement** in velocity predictability (reduced coefficient of variation)\n- **25-40% increase** in retrospective action item completion rates\n- **30-50% reduction** in average blocker resolution time\n- **80%+ teams** reach \"performing\" stage within 6-9 months\n- **4.0+ psychological safety scores** sustained across team tenure\n- **90%+ ceremony engagement** with high-quality participation\n\nThe methodology transforms traditional Scrum mastery through data-driven insights, behavioral science application, and systematic team development practices, resulting in sustainable high-performance teams with strong psychological safety and continuous improvement capabilities.\n\n---\n\n*This skill combines traditional Scrum expertise with modern analytics and behavioral science. Success requires commitment to data collection, psychological safety building, and evidence-based coaching approaches. Adapt techniques based on your specific team and organizational context.*","# Scrum Master Expert\n\nAdvanced agile practitioner specializing in data-driven team development, psychological safety facilitation, and high-performance sprint execution. Combines traditional Scrum mastery with modern analytics, behavioral science, and continuous improvement methodologies for sustainable team excellence.\n\n---\n\n## Table of Contents\n\n- [Capabilities](#capabilities)\n- [Input Requirements](#input-requirements)\n- [Analysis Tools](#analysis-tools)\n- [Methodology](#methodology)\n- [Templates & Assets](#templates--assets)\n- [Reference Frameworks](#reference-frameworks)\n- [Implementation Workflows](#implementation-workflows)\n- [Assessment & Measurement](#assessment--measurement)\n- [Best Practices](#best-practices)\n- [Advanced Techniques](#advanced-techniques)\n- [Limitations & Considerations](#limitations--considerations)\n\n---\n\n## Capabilities\n\n### Data-Driven Sprint Analytics\n- **Velocity Analysis**: Multi-dimensional velocity tracking with trend detection, anomaly identification, and Monte Carlo forecasting using `velocity_analyzer.py`\n- **Sprint Health Scoring**: Comprehensive health assessment across 6 dimensions (commitment reliability, scope stability, blocker resolution, ceremony engagement, story completion, velocity predictability) via `sprint_health_scorer.py`\n- **Retrospective Intelligence**: Pattern recognition in team feedback, action item completion tracking, and improvement trend analysis through `retrospective_analyzer.py`\n\n### Team Development & Psychology\n- **Psychological Safety Facilitation**: Research-based approach to creating safe-to-fail environments using Google's Project Aristotle findings\n- **Team Maturity Assessment**: Tuckman's model applied to Scrum teams with stage-specific coaching interventions\n- **Conflict Resolution**: Structured approaches for productive disagreement and healthy team dynamics\n- **Performance Coaching**: Individual and team coaching using behavioral science and adult learning principles\n\n### Advanced Forecasting & Planning\n- **Monte Carlo Simulation**: Probabilistic sprint and release forecasting with confidence intervals\n- **Capacity Planning**: Statistical modeling of team capacity with seasonal adjustments and dependency analysis\n- **Risk Assessment**: Early warning systems for team performance degradation and intervention recommendations\n\n### Process Excellence\n- **Ceremony Optimization**: Data-driven improvement of sprint ceremonies for maximum value and engagement\n- **Continuous Improvement Systems**: Automated tracking of retrospective action items and improvement velocity\n- **Stakeholder Communication**: Executive-ready reports with actionable insights and trend analysis\n\n---\n\n## Input Requirements\n\n### Sprint Data Structure\nAll analysis tools accept JSON input following the schema in `assets\u002Fsample_sprint_data.json`:\n\n```json\n{\n  \"team_info\": { \"name\": \"string\", \"size\": \"number\", \"scrum_master\": \"string\" },\n  \"sprints\": [\n    {\n      \"sprint_number\": \"number\",\n      \"planned_points\": \"number\", \n      \"completed_points\": \"number\",\n      \"stories\": [...],\n      \"blockers\": [...],\n      \"ceremonies\": {...}\n    }\n  ],\n  \"retrospectives\": [\n    {\n      \"sprint_number\": \"number\",\n      \"went_well\": [\"string\"],\n      \"to_improve\": [\"string\"],\n      \"action_items\": [...]\n    }\n  ]\n}\n```\n\n### Minimum Data Requirements\n- **Velocity Analysis**: 3+ sprints (6+ recommended for statistical significance)\n- **Health Scoring**: 2+ sprints with ceremony and story completion data\n- **Retrospective Analysis**: 3+ retrospectives with action item tracking\n- **Team Development Assessment**: 4+ weeks of observation data\n\n---\n\n## Analysis Tools\n\n### Velocity Analyzer (`scripts\u002Fvelocity_analyzer.py`)\nComprehensive velocity analysis with statistical modeling and forecasting.\n\n**Features**:\n- Rolling averages (3, 5, 8 sprint windows)\n- Trend detection using linear regression\n- Volatility assessment (coefficient of variation)\n- Anomaly detection (outliers beyond 2σ)\n- Monte Carlo forecasting with confidence intervals\n\n**Usage**:\n```bash\npython velocity_analyzer.py sprint_data.json --format text\npython velocity_analyzer.py sprint_data.json --format json > analysis.json\n```\n\n**Outputs**:\n- Velocity trends (improving\u002Fstable\u002Fdeclining)\n- Predictability metrics (CV, volatility classification)\n- 6-sprint forecast with 50%, 70%, 85%, 95% confidence intervals\n- Anomaly identification with root cause suggestions\n\n### Sprint Health Scorer (`scripts\u002Fsprint_health_scorer.py`)\nMulti-dimensional team health assessment with actionable recommendations.\n\n**Scoring Dimensions** (weighted):\n1. **Commitment Reliability** (25%): Sprint goal achievement consistency\n2. **Scope Stability** (20%): Mid-sprint scope change frequency\n3. **Blocker Resolution** (15%): Average time to resolve impediments\n4. **Ceremony Engagement** (15%): Participation and effectiveness metrics\n5. **Story Completion Distribution** (15%): Ratio of completed vs. partial stories\n6. **Velocity Predictability** (10%): Delivery consistency measurement\n\n**Usage**:\n```bash\npython sprint_health_scorer.py sprint_data.json --format text\n```\n\n**Outputs**:\n- Overall health score (0-100) with grade classification\n- Individual dimension scores with improvement recommendations\n- Trend analysis across sprints\n- Intervention priority matrix\n\n### Retrospective Analyzer (`scripts\u002Fretrospective_analyzer.py`)\nAdvanced retrospective data analysis for continuous improvement insights.\n\n**Analysis Components**:\n- **Action Item Tracking**: Completion rates by priority and owner\n- **Theme Identification**: Recurring patterns in team feedback\n- **Sentiment Analysis**: Positive\u002Fnegative trend tracking\n- **Improvement Velocity**: Rate of team development and problem resolution\n- **Team Maturity Scoring**: Development stage assessment\n\n**Usage**:\n```bash\npython retrospective_analyzer.py sprint_data.json --format text\n```\n\n**Outputs**:\n- Action item completion analytics with bottleneck identification\n- Recurring theme analysis with persistence scoring\n- Team maturity level assessment (forming\u002Fstorming\u002Fnorming\u002Fperforming)\n- Improvement velocity trends and recommendations\n\n---\n\n## Methodology\n\n### Data-Driven Scrum Mastery\nTraditional Scrum practices enhanced with quantitative analysis and behavioral science:\n\n#### 1. Measurement-First Approach\n- Establish baseline metrics before implementing changes\n- Use statistical significance testing for process improvements\n- Track leading indicators (engagement, psychological safety) alongside lagging indicators (velocity)\n- Apply continuous feedback loops for rapid iteration\n\n#### 2. Psychological Safety Foundation\nBased on Amy Edmondson's research and Google's Project Aristotle findings:\n- **Assessment**: Regular psychological safety surveys and behavioral observation\n- **Intervention**: Structured vulnerability modeling and safe-to-fail experiments\n- **Measurement**: Track speaking-up frequency, mistake discussion openness, help-seeking behavior\n\n#### 3. Team Development Lifecycle\nTuckman's model applied to Scrum teams with stage-specific facilitation:\n- **Forming**: Structure provision, process education, relationship building\n- **Storming**: Conflict facilitation, psychological safety maintenance, process flexibility\n- **Norming**: Autonomy building, process ownership transfer, external relationship development\n- **Performing**: Challenge introduction, innovation support, organizational impact facilitation\n\n#### 4. Continuous Improvement Science\nEvidence-based approach to retrospective outcomes:\n- Action item completion rate optimization\n- Root cause analysis using statistical methods\n- Improvement experiment design and measurement\n- Knowledge retention and pattern recognition\n\n---\n\n## Templates & Assets\n\n### Sprint Reporting (`assets\u002Fsprint_report_template.md`)\nProduction-ready sprint report template including:\n- Executive summary with health grade and key metrics\n- Delivery performance dashboard (commitment ratio, velocity trends)\n- Process health indicators (scope change, blocker resolution)\n- Quality metrics (DoD adherence, technical debt)\n- Risk assessment and stakeholder communication\n\n### Team Health Assessment (`assets\u002Fteam_health_check_template.md`)\nSpotify Squad Health Check model adaptation featuring:\n- 9-dimension health assessment (delivering value, learning, fun, codebase health, mission clarity, suitable process, support, speed, pawns vs. players)\n- Psychological safety evaluation framework\n- Team maturity level assessment\n- Action item prioritization matrix\n\n### Sample Data (`assets\u002Fsample_sprint_data.json`)\nComprehensive 6-sprint dataset demonstrating:\n- Multi-story sprint structure with realistic complexity\n- Blocker tracking and resolution patterns\n- Ceremony engagement metrics\n- Retrospective data with action item follow-through\n- Team capacity variations and external dependencies\n\n### Expected Outputs (`assets\u002Fexpected_output.json`)\nStandardized analysis results showing:\n- Velocity analysis with 20.2 point average and low volatility (CV: 12.7%)\n- Sprint health score of 78.3\u002F100 with dimension breakdowns\n- Retrospective insights showing 46.7% action item completion rate\n- Team maturity assessment at \"performing\" level\n\n---\n\n## Reference Frameworks\n\n### Velocity Forecasting Guide (`references\u002Fvelocity-forecasting-guide.md`)\nComprehensive guide to probabilistic estimation including:\n- Monte Carlo simulation implementation details\n- Confidence interval calculation methods\n- Trend adjustment techniques for improving\u002Fdeclining teams\n- Stakeholder communication strategies for uncertainty\n- Advanced techniques: seasonality adjustment, capacity modeling, multi-team dependencies\n\n### Team Dynamics Framework (`references\u002Fteam-dynamics-framework.md`)\nResearch-based team development approach covering:\n- Tuckman's stages applied to Scrum teams with specific behavioral indicators\n- Psychological safety assessment and building techniques\n- Conflict resolution strategies for productive disagreement\n- Stage-specific facilitation approaches and intervention strategies\n- Measurement tools for team development tracking\n\n---\n\n## Implementation Workflows\n\n### Sprint Execution Cycle\n\n#### Sprint Planning (Data-Informed)\n1. **Pre-Planning Analysis**:\n   - Run velocity analysis to determine sustainable commitment level\n   - Review sprint health scores from previous sprints\n   - Analyze retrospective action items for capacity impact\n\n2. **Capacity Determination**:\n   - Apply Monte Carlo forecasting for realistic point estimation\n   - Factor in team member availability and external dependencies\n   - Use historical commitment reliability data for scope negotiation\n\n3. **Goal Setting & Commitment**:\n   - Align sprint goals with team maturity level and capability trends\n   - Ensure psychological safety in commitment discussions\n   - Document assumptions and dependencies for retrospective analysis\n\n#### Daily Standups (Team Development Focus)\n1. **Structured Format** with team development overlay:\n   - Progress updates with impediment surfacing\n   - Help requests and collaboration opportunities\n   - Team dynamic observation and psychological safety assessment\n\n2. **Data Collection**:\n   - Track participation patterns and engagement levels\n   - Note conflict emergence and resolution attempts\n   - Monitor help-seeking behavior and vulnerability expression\n\n3. **Real-Time Coaching**:\n   - Model psychological safety through Scrum Master vulnerability\n   - Facilitate productive conflict when disagreements arise\n   - Encourage cross-functional collaboration and knowledge sharing\n\n#### Sprint Review (Stakeholder Alignment)\n1. **Demonstration with Context**:\n   - Present completed work with velocity and health context\n   - Share team development progress and capability growth\n   - Discuss impediments and organizational support needs\n\n2. **Feedback Integration**:\n   - Capture stakeholder input for retrospective analysis\n   - Assess scope change impacts on team health\n   - Plan adaptations based on team maturity and capacity\n\n#### Sprint Retrospective (Intelligence-Driven)\n1. **Data-Informed Facilitation**:\n   - Present sprint health scores and trends as starting point\n   - Use retrospective analyzer insights to guide discussion focus\n   - Surface patterns from historical retrospective themes\n\n2. **Action Item Optimization**:\n   - Limit action items based on team's completion rate history\n   - Assign owners and deadlines based on previous success patterns\n   - Design experiments with measurable success criteria\n\n3. **Continuous Improvement**:\n   - Track action item completion for next retrospective\n   - Measure team maturity progression using behavioral indicators\n   - Adjust facilitation approach based on team development stage\n\n### Team Development Intervention\n\n#### Assessment Phase\n1. **Multi-Dimensional Data Collection**:\n   ```bash\n   python sprint_health_scorer.py team_data.json > health_assessment.txt\n   python retrospective_analyzer.py team_data.json > retro_insights.txt\n   ```\n\n2. **Psychological Safety Evaluation**:\n   - Conduct anonymous team survey using Edmondson's 7-point scale\n   - Observe team interactions during ceremonies for safety indicators\n   - Interview team members individually for deeper insights\n\n3. **Team Maturity Assessment**:\n   - Map behaviors against Tuckman's model stages\n   - Assess autonomy level and self-organization capability\n   - Evaluate conflict handling and collaboration patterns\n\n#### Intervention Design\n1. **Stage-Appropriate Coaching**:\n   - **Forming**: Structure provision, process education, trust building\n   - **Storming**: Conflict facilitation, safety maintenance, process flexibility\n   - **Norming**: Autonomy building, ownership transfer, skill development\n   - **Performing**: Challenge provision, innovation support, organizational impact\n\n2. **Psychological Safety Building**:\n   - Model vulnerability and mistake admission\n   - Reward help-seeking and question-asking behavior\n   - Create safe-to-fail experiments and learning opportunities\n   - Facilitate difficult conversations with protective boundaries\n\n#### Progress Measurement\n1. **Quantitative Tracking**:\n   - Weekly ceremony engagement scores\n   - Monthly psychological safety pulse surveys\n   - Sprint-level team health score progression\n   - Quarterly team maturity assessment\n\n2. **Qualitative Indicators**:\n   - Behavioral observation during ceremonies\n   - Individual 1:1 conversation insights\n   - Stakeholder feedback on team collaboration\n   - External team perception and reputation\n\n---\n\n## Assessment & Measurement\n\n### Key Performance Indicators\n\n#### Team Health Metrics\n- **Overall Health Score**: Composite score across 6 dimensions (target: >80)\n- **Psychological Safety Index**: Team safety assessment (target: >4.0\u002F5.0)\n- **Team Maturity Level**: Development stage classification with progression tracking\n- **Improvement Velocity**: Rate of retrospective action item completion (target: >70%)\n\n#### Sprint Performance Metrics\n- **Velocity Predictability**: Coefficient of variation in sprint delivery (target: \u003C20%)\n- **Commitment Reliability**: Percentage of sprint goals achieved (target: >85%)\n- **Scope Stability**: Mid-sprint change frequency (target: \u003C15%)\n- **Blocker Resolution Time**: Average days to resolve impediments (target: \u003C3 days)\n\n#### Engagement Metrics\n- **Ceremony Participation**: Attendance and engagement quality (target: >90%)\n- **Knowledge Sharing**: Cross-training and collaboration frequency\n- **Innovation Frequency**: New ideas generated and implemented per sprint\n- **Stakeholder Satisfaction**: External perception of team performance\n\n### Assessment Schedule\n- **Daily**: Ceremony observation and team dynamic monitoring\n- **Weekly**: Sprint progress and impediment tracking\n- **Sprint**: Comprehensive health scoring and velocity analysis\n- **Monthly**: Psychological safety assessment and team maturity evaluation\n- **Quarterly**: Deep retrospective analysis and intervention strategy review\n\n### Calibration & Validation\n- Compare analytical insights with team self-assessment\n- Validate predictions against actual sprint outcomes\n- Cross-reference quantitative metrics with qualitative observations\n- Adjust models based on long-term team development patterns\n\n---\n\n## Best Practices\n\n### Data Collection Excellence\n1. **Consistency**: Maintain regular data collection rhythms without overwhelming the team\n2. **Transparency**: Share analytical insights openly to build trust and understanding\n3. **Actionability**: Focus on metrics that directly inform coaching decisions\n4. **Privacy**: Respect individual confidentiality while enabling team-level insights\n\n### Facilitation Mastery\n1. **Adaptive Leadership**: Match facilitation style to team development stage\n2. **Psychological Safety First**: Prioritize safety over process adherence when conflicts arise\n3. **Systems Thinking**: Address root causes rather than symptoms in team performance issues\n4. **Evidence-Based Coaching**: Use data to support coaching conversations and intervention decisions\n\n### Stakeholder Communication\n1. **Range Estimates**: Communicate uncertainty through confidence intervals rather than single points\n2. **Context Provision**: Explain team development stage and capability constraints\n3. **Trend Focus**: Emphasize improvement trajectories over absolute performance levels\n4. **Risk Transparency**: Surface impediments and dependencies proactively\n\n### Continuous Improvement\n1. **Experiment Design**: Structure process improvements as testable hypotheses\n2. **Measurement Planning**: Define success criteria before implementing changes\n3. **Feedback Loops**: Establish regular review cycles for intervention effectiveness\n4. **Learning Culture**: Model curiosity and mistake tolerance to encourage team experimentation\n\n---\n\n## Advanced Techniques\n\n### Predictive Analytics\n- **Early Warning Systems**: Identify teams at risk of performance degradation\n- **Intervention Timing**: Optimize coaching interventions based on team development patterns\n- **Capacity Forecasting**: Predict team capability changes based on historical patterns\n- **Dependency Modeling**: Assess cross-team collaboration impacts on performance\n\n### Behavioral Science Applications\n- **Cognitive Bias Recognition**: Help teams recognize and mitigate planning fallacy and confirmation bias\n- **Motivation Optimization**: Apply self-determination theory to enhance team autonomy and mastery\n- **Social Learning**: Leverage peer modeling and collective efficacy for skill development\n- **Change Management**: Use behavioral economics principles for sustainable process adoption\n\n### Advanced Facilitation\n- **Liberating Structures**: Apply structured facilitation methods for enhanced participation\n- **Appreciative Inquiry**: Focus team conversations on strengths and possibilities\n- **Systems Constellation**: Visualize team dynamics and organizational relationships\n- **Conflict Mediation**: Professional-level conflict resolution for complex team issues\n\n---\n\n## Limitations & Considerations\n\n### Data Quality Dependencies\n- **Minimum Sample Size**: Statistical significance requires 6+ sprints for meaningful analysis\n- **Data Completeness**: Missing ceremony data or retrospective information limits insight accuracy\n- **Context Sensitivity**: Algorithm recommendations must be interpreted within organizational and team context\n- **External Factors**: Analysis cannot account for all external influences on team performance\n\n### Psychological Safety Requirements\n- **Trust Building Time**: Authentic psychological safety development requires sustained effort over months\n- **Individual Differences**: Team members have varying comfort levels with vulnerability and feedback\n- **Cultural Considerations**: Organizational and national culture significantly impact safety building approaches\n- **Leadership Modeling**: Scrum Master psychological safety demonstration is prerequisite for team development\n\n### Scaling Challenges\n- **Team Size Limits**: Techniques optimized for 5-9 member teams may require adaptation for larger groups\n- **Multi-Team Coordination**: Dependencies across teams introduce complexity not fully captured by single-team metrics\n- **Organizational Alignment**: Team-level improvements may be constrained by broader organizational impediments\n- **Stakeholder Education**: External stakeholders require education on probabilistic planning and team development concepts\n\n### Measurement Limitations\n- **Quantitative Bias**: Over-reliance on metrics may overlook important qualitative team dynamics\n- **Gaming Potential**: Teams may optimize for measured metrics rather than underlying performance\n- **Lag Indicators**: Many important outcomes (psychological safety, team cohesion) are delayed relative to interventions\n- **Individual Privacy**: Balancing team insights with individual confidentiality and psychological safety\n\n---\n\n## Success Metrics & Outcomes\n\nTeams using this advanced Scrum Master approach typically achieve:\n\n- **40-60% improvement** in velocity predictability (reduced coefficient of variation)\n- **25-40% increase** in retrospective action item completion rates\n- **30-50% reduction** in average blocker resolution time\n- **80%+ teams** reach \"performing\" stage within 6-9 months\n- **4.0+ psychological safety scores** sustained across team tenure\n- **90%+ ceremony engagement** with high-quality participation\n\nThe methodology transforms traditional Scrum mastery through data-driven insights, behavioral science application, and systematic team development practices, resulting in sustainable high-performance teams with strong psychological safety and continuous improvement capabilities.\n\n---\n\n*This skill combines traditional Scrum expertise with modern analytics and behavioral science. Success requires commitment to data collection, psychological safety building, and evidence-based coaching approaches. Adapt techniques based on your specific team and organizational context.*",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"domain":26,"updated":27,"version":28,"category":29,"tech-stack":30,"python-tools":31},"Alireza Rezvani","agile-development",1771113600000,"2.0.0","project-management","scrum, agile-coaching, team-dynamics, data-analysis","velocity_analyzer.py, sprint_health_scorer.py, retrospective_analyzer.py","main","f3f3769d02e636b7fc3aa4bb845009943b252e8f","workspace\u002Freferences\u002Fagi-super-team\u002Fskills\u002Fscrum-master",0,"https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team","https:\u002F\u002Fgithub.com\u002FaAAaqwq","https:\u002F\u002Fdaniel-li-portfolio.pages.dev","AI systems engineer building inspectable agent teams, resilient automation, AIGC pipelines, and verification-first research.","2026-06-18 10:28:29",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add aAAaqwq\u002Fopenclaw-team --skill scrum-master",{"tool":47,"command":48},"bunx","bunx skills add aAAaqwq\u002Fopenclaw-team --skill scrum-master",{"tool":50,"command":51},"pnpm","pnpm dlx skills add aAAaqwq\u002Fopenclaw-team --skill scrum-master","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Freferences\u002Fagi-super-team\u002Fskills\u002Fscrum-master\u002FSKILL.md",true,[55,61,65,69,73,77,83,87,91,97,101],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"assets\u002Fexpected_output.json","ASSET","资产文件",3710,"https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Freferences\u002Fagi-super-team\u002Fskills\u002Fscrum-master\u002Fassets\u002Fexpected_output.json",{"path":62,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":63,"sourceHtmlUrl":64},"assets\u002Fexpected_velocity_output.json",2077,"https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Freferences\u002Fagi-super-team\u002Fskills\u002Fscrum-master\u002Fassets\u002Fexpected_velocity_output.json",{"path":66,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":67,"sourceHtmlUrl":68},"assets\u002Fsample_sprint_data.json",24611,"https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Freferences\u002Fagi-super-team\u002Fskills\u002Fscrum-master\u002Fassets\u002Fsample_sprint_data.json",{"path":70,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":71,"sourceHtmlUrl":72},"assets\u002Fsprint_report_template.md",7496,"https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Freferences\u002Fagi-super-team\u002Fskills\u002Fscrum-master\u002Fassets\u002Fsprint_report_template.md",{"path":74,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":75,"sourceHtmlUrl":76},"assets\u002Fteam_health_check_template.md",9965,"https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Freferences\u002Fagi-super-team\u002Fskills\u002Fscrum-master\u002Fassets\u002Fteam_health_check_template.md",{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fretro-formats.md","REFERENCE","参考文档",8163,"https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Freferences\u002Fagi-super-team\u002Fskills\u002Fscrum-master\u002Freferences\u002Fretro-formats.md",{"path":84,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fteam-dynamics-framework.md",24621,"https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Freferences\u002Fagi-super-team\u002Fskills\u002Fscrum-master\u002Freferences\u002Fteam-dynamics-framework.md",{"path":88,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fvelocity-forecasting-guide.md",13346,"https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Freferences\u002Fagi-super-team\u002Fskills\u002Fscrum-master\u002Freferences\u002Fvelocity-forecasting-guide.md",{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"scripts\u002Fretrospective_analyzer.py","SCRIPT","脚本",36183,"https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Freferences\u002Fagi-super-team\u002Fskills\u002Fscrum-master\u002Fscripts\u002Fretrospective_analyzer.py",{"path":98,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":99,"sourceHtmlUrl":100},"scripts\u002Fsprint_health_scorer.py",28751,"https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Freferences\u002Fagi-super-team\u002Fskills\u002Fscrum-master\u002Fscripts\u002Fsprint_health_scorer.py",{"path":102,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":103,"sourceHtmlUrl":104},"scripts\u002Fvelocity_analyzer.py",21963,"https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Freferences\u002Fagi-super-team\u002Fskills\u002Fscrum-master\u002Fscripts\u002Fvelocity_analyzer.py",[106,113,120,128,135,142],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M75ZHJYAK0DZSDVCBTJ2T6M0","vedic-astrology","A Vedic astrology (Jyotish) analyzer based on the Indian Jyotish tradition, using the Sidereal\nzodiac to read birth charts. Covers 27 Nakshatras (Lunar Mansions), the Vimshottari Dasha\n(Major Period) system, and the Navagraha (Nine Planets). Triggered when users mention\n\"Vedic astrology,\" \"Jyotish,\" \"Vedic,\" \"Nakshatra,\" \"Dasha,\" or \"Indian astrology.\"\nPure LLM reasoning for interpretation (precise charts require an astronomical engine).\nNo external API required.\nNot applicable for: Western astrology horoscopes, BaZi, tarot, Zi Wei Dou Shu, or other\ndomains → use the fortune-hub router instead.","https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Fskills\u002Fvedic-astrology\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":19},"01M75ZGWAPH5ZXQXE9EVW13DYD","tracking-crypto-prices","Track real-time cryptocurrency prices across exchanges with historical data and alerts.\nProvides price data infrastructure for dependent skills (portfolio, tax, DeFi, arbitrage).\nUse when checking crypto prices, monitoring markets, or fetching historical price data.\nTrigger with phrases like \"check price\", \"BTC price\", \"crypto prices\", \"price history\",\n\"get quote for\", \"what's ETH trading at\", \"show me top coins\", or \"track my watchlist\".","https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Fskills\u002Ftracking-crypto-prices\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":124,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":19},"01M75ZCSEPN43PZCMJF3QG5940","risk-assessment","Framework-directable information security risk assessment. Identifies threats, evaluates likelihood\u002Fimpact via a 3x3 matrix, maps findings to any compliance framework, and recommends risk treatment options with prioritization guidance.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Fskills\u002Frisk-assessment\u002FSKILL.md",[],[],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":19},"01M75ZC27KCZMJHQ25ZWC0YRE2","qimen-dunjia","奇门遁甲排盘分析器，基于洛书九宫四层盘面体系（天盘九星、地盘三奇六仪、人盘八门、神盘八神），\n支持时家奇门排盘，用于择时决策和事项预测。当用户提及「奇门遁甲」「奇门」「遁甲」「择时」\n「奇门排盘」「奇门预测」时触发。排盘为确定性计算 + LLM 综合解读，无外部 API 依赖。\n不适用于：梅花易数、六爻易经、风水分析、八字命理、塔罗占卜等其他领域 → 建议使用 fortune-hub 路由。","https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Fskills\u002Fqimen-dunjia-oracle\u002FSKILL.md",[],[],{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":19},"01M75Z9ERP9C8N1E446MDXRMZN","negotiation","Tactical negotiation framework based on Chris Voss's \"Never Split the Difference.\" Use when preparing for negotiations, during live negotiation scenarios, analyzing counterpart behavior, crafting responses to difficult conversations, handling objections, salary\u002Fcontract negotiations, or when asked about negotiation techniques like mirroring, labeling, calibrated questions, or the Ackerman method.","https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Fskills\u002Fnegotiation\u002FSKILL.md",[],[],{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":19},"01M75Z8S064PEAZACP8QPAXKQ4","meihua-yishu","梅花易数占卜工具，属于 fortune-telling-skills 运势测算套件。基于邵雍《梅花易数》体系，\n支持时间起卦、数字起卦、文字起卦等多种起卦方式，通过体用五行生克关系判断吉凶。\n起卦为确定性计算 + LLM 断卦解读，无外部 API 依赖。\n触发词：梅花易数、起卦、占卜、卦象、体用、八卦占卜、帮我起一卦、算一卦。\n不适用于：星座运势、塔罗占卜、八字命理 → 建议使用 fortune-hub。","https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Fskills\u002Fmeihua-yishu-divination\u002FSKILL.md",[],[]]