[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6D7PFD5DHHDN557YQV92W7A":3,"skill-same:01M6D7PFD5DHHDN557YQV92W7A":129},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6D7PFD5DHHDN557YQV92W7A","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.","oabdelmaksoud\u002FSuperClaw","oabdelmaksoud","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F50699149?v=4","01M6D5CVVN778ZCDP1WHS816SP","Omar Abdelmaksoud","01M6D5CW1RHNSKCJR85GJACBFT",2,"MIT","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fproject-management\u002Fscrum-master\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"master","scrum","Scrum Master","data-analysis","retrospective","project","coaching","velocity","scoring","frameworks","sprint health","project-management","team","health","analysis","Safety","data","agile","teams","development","2026-11-10 10:12:30",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":49,"description":7},{"author":50,"domain":51,"updated":52,"version":53,"category":35,"tech-stack":54,"python-tools":55},"Alireza Rezvani","agile-development",1771113600000,"2.0.0","scrum, agile-coaching, team-dynamics, data-analysis","velocity_analyzer.py, sprint_health_scorer.py, retrospective_analyzer.py","main","7b610356e36623652299fa2acb477ff821b1d920","upstream-sync\u002Fwork\u002Fclaude-skills\u002Fproject-management\u002Fscrum-master",0,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fo-abdelmaksoud\u002F","Full-Stack Engineer | AI Systems Architect | Building autonomous multi-agent systems","2026-03-08 21:12:53",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add oabdelmaksoud\u002FSuperClaw --skill scrum-master",{"tool":71,"command":72},"bunx","bunx skills add oabdelmaksoud\u002FSuperClaw --skill scrum-master",{"tool":74,"command":75},"pnpm","pnpm dlx skills add oabdelmaksoud\u002FSuperClaw --skill scrum-master","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fproject-management\u002Fscrum-master\u002FSKILL.md",true,[79,85,89,93,97,101,107,111,115,121,125],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"assets\u002Fexpected_output.json","ASSET","资产文件",3710,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fproject-management\u002Fscrum-master\u002Fassets\u002Fexpected_output.json",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"assets\u002Fexpected_velocity_output.json",2077,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fproject-management\u002Fscrum-master\u002Fassets\u002Fexpected_velocity_output.json",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"assets\u002Fsample_sprint_data.json",24611,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fproject-management\u002Fscrum-master\u002Fassets\u002Fsample_sprint_data.json",{"path":94,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":95,"sourceHtmlUrl":96},"assets\u002Fsprint_report_template.md",7496,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fproject-management\u002Fscrum-master\u002Fassets\u002Fsprint_report_template.md",{"path":98,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":99,"sourceHtmlUrl":100},"assets\u002Fteam_health_check_template.md",9965,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fproject-management\u002Fscrum-master\u002Fassets\u002Fteam_health_check_template.md",{"path":102,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fretro-formats.md","REFERENCE","参考文档",8163,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fproject-management\u002Fscrum-master\u002Freferences\u002Fretro-formats.md",{"path":108,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fteam-dynamics-framework.md",24621,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fproject-management\u002Fscrum-master\u002Freferences\u002Fteam-dynamics-framework.md",{"path":112,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":113,"sourceHtmlUrl":114},"references\u002Fvelocity-forecasting-guide.md",13346,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fproject-management\u002Fscrum-master\u002Freferences\u002Fvelocity-forecasting-guide.md",{"path":116,"resourceType":117,"resourceTypeDesc":118,"sizeBytes":119,"sourceHtmlUrl":120},"scripts\u002Fretrospective_analyzer.py","SCRIPT","脚本",36183,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fproject-management\u002Fscrum-master\u002Fscripts\u002Fretrospective_analyzer.py",{"path":122,"resourceType":117,"resourceTypeDesc":118,"sizeBytes":123,"sourceHtmlUrl":124},"scripts\u002Fsprint_health_scorer.py",28751,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fproject-management\u002Fscrum-master\u002Fscripts\u002Fsprint_health_scorer.py",{"path":126,"resourceType":117,"resourceTypeDesc":118,"sizeBytes":127,"sourceHtmlUrl":128},"scripts\u002Fvelocity_analyzer.py",21963,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fclaude-skills\u002Fproject-management\u002Fscrum-master\u002Fscripts\u002Fvelocity_analyzer.py",[130,151,165,193,219,238],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":141,"publishedAt":44},"01M6D88QCPTBZVCRED0NZ1Y8K8","visa-doc-translate","Translate visa application documents (images) to English and create a bilingual PDF with original and translation","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fvisa-doc-translate\u002FSKILL.md",[136],{"categoryNo":137,"categoryName":138,"taxonomyType":139,"taxonomyTypeDesc":140},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",[142,143,144,145,146,147,148,149,150],"translate","doc","visa doc translate","translation","application","create","images","PDF","documents",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":44},"01M6D88NBM95T3TFM50CYYAP65","verification-loop","A comprehensive verification system for Claude Code sessions.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[158,159,160,161,162,163,164],"verification","loop","verification loop","sessions","code","claude code sessions","system",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":180,"publishedAt":44},"01M6D88JFZ2P996GVRHJNSZSTM","tdd-workflow","Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Ftdd-workflow\u002FSKILL.md",[171,174,177],{"categoryNo":172,"categoryName":173,"taxonomyType":139,"taxonomyTypeDesc":140},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":175,"categoryName":176,"taxonomyType":139,"taxonomyTypeDesc":140},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":178,"categoryName":179,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师",[181,182,183,184,185,186,162,43,187,188,189,190,191,192],"tdd","workflow","tdd workflow","e2e tests","e2e","integration","use","test","refactoring","coverage","tests","writing",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":199,"publishedAt":44},"01M6D88FTHRRSVJMXF2G7MQAK3","swiftui-patterns","SwiftUI architecture patterns, state management with @Observable, view composition, navigation, performance optimization, and modern iOS\u002FmacOS UI best practices.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fswiftui-patterns\u002FSKILL.md",[],[200,201,202,203,204,205,206,207,208,209,210,211,212,213,214,215,216,217,218],"patterns","swiftui","swiftui patterns","architecture","macos","performance","state management","best practices","state","ui","Optimization","ios","architecture patterns","Composition","performance optimization","view","management","swiftui architecture","navigation",{"skillNo":220,"name":221,"nameZh":6,"description":222,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":223,"categories":224,"keywords":226,"publishedAt":44},"01M6D88D527QTQT9DKHTRFN6EA","swift-protocol-di-testing","Protocol-based dependency injection for testable Swift code — mock file system, network, and external APIs using focused protocols and Swift Testing.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fswift-protocol-di-testing\u002FSKILL.md",[225],{"categoryNo":172,"categoryName":173,"taxonomyType":139,"taxonomyTypeDesc":140},[227,228,229,230,162,231,232,233,234,164,235,236,237],"swift protocol di testing","protocol","swift","testing","protocols","file","network","injection","dependency","swift testing","dependency injection",{"skillNo":239,"name":240,"nameZh":6,"description":241,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":242,"categories":243,"keywords":244,"publishedAt":44},"01M6D88AJW8H2QNWSW5ZY82R43","swift-concurrency-6-2","Swift 6.2 Approachable Concurrency — single-threaded by default, @concurrent for explicit background offloading, isolated conformances for main actor types.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fswift-concurrency-6-2\u002FSKILL.md",[],[245,246,229,247,248,56],"concurrency","swift concurrency","swift concurrency 6 2","default"]