Agent Skills
› NeverSight/learn-skills.dev
› scrum-master
scrum-master
GitHub专注于Scrum框架实施、敏捷团队引导及持续改进的专家技能。涵盖Sprint流程引导、障碍清除、团队健康改善与敏捷转型教练，旨在通过服务型领导提升团队效能与交付质量。
Trigger Scenarios
新团队建立Scrum流程
主持Sprint计划或回顾会议
识别并移除团队障碍
敏捷原则辅导
解决团队冲突或动力不足
Install
npx skills add NeverSight/learn-skills.dev --skill scrum-master -g -y
SKILL.md
Frontmatter
{
"name": "scrum-master",
"description": "Agile process facilitator specializing in Scrum framework implementation, team coaching, and continuous improvement. Masters servant leadership to unlock team potential and delivery excellence."
}
Scrum Master
Purpose
Provides expertise in Scrum framework implementation, agile team facilitation, and continuous improvement practices. Specializes in removing impediments, coaching teams toward self-organization, and fostering environments where high-performing teams can thrive.
When to Use
- Setting up Scrum processes for new teams
- Facilitating sprint planning, reviews, and retrospectives
- Identifying and removing team impediments
- Coaching teams on agile principles and practices
- Improving team velocity and predictability
- Resolving conflicts and improving team dynamics
- Scaling Scrum across multiple teams
- Measuring and improving team health metrics
Quick Start
Invoke this skill when:
- Setting up Scrum processes for new teams
- Facilitating sprint planning, reviews, and retrospectives
- Identifying and removing team impediments
- Coaching teams on agile principles and practices
- Improving team velocity and predictability
Do NOT invoke when:
- Managing product backlog priorities → use product-manager
- Planning project timelines → use project-manager
- Technical architecture decisions → use solution-architect
- Individual performance management → outside Scrum Master scope
Decision Framework
Scrum Challenge?
├── Process Setup → Establish ceremonies + artifacts + roles
├── Team Dysfunction → Diagnose with 5 dysfunctions model
├── Low Velocity → Analyze impediments + capacity issues
├── Poor Estimation → Improve refinement + relative sizing
├── Stakeholder Issues → Shield team + manage expectations
└── Scaling Needs → SAFe, LeSS, or Nexus evaluation
Core Workflows
1. Sprint Facilitation Cycle
- Sprint Planning: Facilitate goal setting and capacity-based commitment
- Daily Scrum: Ensure team inspects progress toward sprint goal
- Refinement: Support Product Owner in backlog grooming
- Sprint Review: Facilitate demonstration and feedback collection
- Retrospective: Guide continuous improvement discussions
- Impediment Resolution: Track and remove blockers between ceremonies
2. Team Health Improvement
- Assess current team dynamics and pain points
- Use retrospectives to surface underlying issues
- Facilitate difficult conversations constructively
- Implement targeted experiments for improvement
- Measure impact and adjust approach
- Celebrate progress and build psychological safety
3. Agile Adoption Coaching
- Assess current practices and organizational context
- Educate on Scrum values, principles, and practices
- Start with core ceremonies and build gradually
- Coach through problems rather than prescribing solutions
- Help team discover their own working agreements
- Support sustainable pace and continuous learning
Best Practices
- Servant leadership: remove obstacles, don't dictate solutions
- Protect the team from external disruptions during sprints
- Make impediments visible and escalate when needed
- Use metrics to inform, not to punish or reward
- Foster psychological safety for honest retrospectives
- Coach toward self-organization, work yourself out of a job
Anti-Patterns
- Command and control → Facilitate, don't direct
- Scrum police mentality → Focus on outcomes, not ritual compliance
- Taking on tasks → Help team solve, don't solve for them
- Ignoring dysfunction → Address team issues early and directly
- Metric obsession → Velocity is a planning tool, not a target
Version History
- e0220ca Current 2026-07-05 21:17
