sprint-planning
敏捷迭代规划指南，帮助团队有效组织和执行冲刺计划，AI Agent Skill，提升工作效率和自动化能力
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill sprint-planningBefore / After 效果对比
1 组在没有 `sprint-planning` 技能时，团队需要手动进行冲刺规划。这通常涉及召开长时间的会议来定义冲刺目标、讨论并手动估算团队容量（需逐一核对成员的请假和会议安排）。产品待办事项需要从项目追踪器中手动拉取，然后进行优先级排序和范围界定。识别依赖项和潜在风险也依赖于人工讨论和记录。最终，团队成员需要花费大量时间手动创建和格式化冲刺计划文档，并手动通过邮件或聊天工具分享给团队，整个过程耗时且易出错。
使用 `sprint-planning` 技能后，冲刺规划流程得到显著简化和自动化。AI Agent 能够根据用户提供的团队信息、冲刺时长、待办事项和依赖项，自动定义冲刺目标和成功标准。通过连接项目追踪器和日历工具，技能可以自动拉取待办事项、精确估算团队容量（自动考虑请假和会议），并识别依赖项。它能即时生成结构清晰的冲刺计划文档，并可直接通过聊天工具分享给团队。这大大减少了会议时间、手动数据整理和文档创建的工作量，确保规划的准确性和效率。
sprint-planning
/sprint-planning
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Plan a sprint by scoping work, estimating capacity, and setting clear goals.
Usage
/sprint-planning $ARGUMENTS
How It Works
┌─────────────────────────────────────────────────────────────────┐
│ SPRINT PLANNING │
├─────────────────────────────────────────────────────────────────┤
│ STANDALONE (always works) │
│ ✓ Define sprint goals and success criteria │
│ ✓ Estimate team capacity (accounting for PTO, meetings) │
│ ✓ Scope and prioritize backlog items │
│ ✓ Identify dependencies and risks │
│ ✓ Generate sprint plan document │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + Project tracker: Pull backlog, create sprint, assign items │
│ + Calendar: Account for PTO and meetings in capacity │
│ + Chat: Share sprint plan with the team │
└─────────────────────────────────────────────────────────────────┘
What I Need From You
-
Team: Who's on the team and their availability this sprint?
-
Sprint length: How many days/weeks?
-
Backlog: What's prioritized? (Pull from tracker, paste, or describe)
-
Carryover: Anything unfinished from last sprint?
-
Dependencies: Anything blocked on other teams?
Output
## Sprint Plan: [Sprint Name]
**Dates:** [Start] — [End] | **Team:** [X] engineers
**Sprint Goal:** [One clear sentence about what success looks like]
### Capacity
| Person | Available Days | Allocation | Notes |
|--------|---------------|------------|-------|
| [Name] | [X] of [Y] | [X] points/hours | [PTO, on-call, etc.] |
| **Total** | **[X]** | **[X] points** | |
### Sprint Backlog
| Priority | Item | Estimate | Owner | Dependencies |
|----------|------|----------|-------|--------------|
| P0 | [Must ship] | [X] pts | [Person] | [None / Blocked by X] |
| P1 | [Should ship] | [X] pts | [Person] | [None] |
| P2 | [Stretch] | [X] pts | [Person] | [None] |
### Planned Capacity: [X] points | Sprint Load: [X] points ([X]% of capacity)
### Risks
| Risk | Impact | Mitigation |
|------|--------|------------|
| [Risk] | [What happens] | [What to do] |
### Definition of Done
- [ ] Code reviewed and merged
- [ ] Tests passing
- [ ] Documentation updated (if applicable)
- [ ] Product sign-off
### Key Dates
| Date | Event |
|------|-------|
| [Date] | Sprint start |
| [Date] | Mid-sprint check-in |
| [Date] | Sprint end / Demo |
| [Date] | Retro |
Tips
-
Leave buffer — Plan to 70-80% capacity. You will get interrupts.
-
One clear sprint goal — If you can't state it in one sentence, the sprint is unfocused.
-
Identify stretch items — Know what to cut if things take longer than expected.
-
Carry over honestly — If something didn't ship, understand why before re-committing.
Weekly Installs295Repositoryanthropics/know…-pluginsGitHub Stars10.5KFirst SeenMar 13, 2026Security AuditsGen Agent Trust HubPassSocketPassSnykPassInstalled oncodex283gemini-cli281opencode280cursor280github-copilot279amp279
用户评价 (0)
发表评价
暂无评价
统计数据
用户评分
为此 Skill 评分