Sprint Planning

作者 anthropicsae1513ea94dc無授權條款27K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫今天更新

Plan a sprint — scope work, estimate capacity, set goals, and draft a sprint plan. Use when kicking off a new sprint, sizing a backlog against team availability (accounting for PTO and meetings), deciding what's P0 vs. stretch, or handling carryover from the last sprint.

精選僅含說明Productivity & Workflow
AI 產生的概覽

透過界定工作範圍、估算團隊產能、設定目標並起草衝刺計畫來規劃一個衝刺。

功能
引導代理完成衝刺規劃:定義衝刺目標和成功標準,在考量休假和會議的情況下估算團隊產能,界定並排定待辦事項優先順序,以及識別相依性和風險。它會產出一份衝刺計畫文件,包含產能、待辦事項、風險、完成定義和關鍵日期。當連接了專案追蹤、行事曆和聊天工具時,還可以選擇拉取待辦事項、建立衝刺並分享計畫。
適用情境
適用於啟動新衝刺、根據團隊可用性評估待辦事項規模、決定哪些是 P0 哪些是彈性事項,或處理上一衝刺遺留事項的情境。
執行需求
僅為說明文件,不含指令碼。可獨立使用,但也可選擇使用已連接的專案追蹤、行事曆和聊天工具來拉取待辦事項、建立衝刺並分享計畫。

/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

markdown
## 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

  1. Leave buffer — Plan to 70-80% capacity. You will get interrupts.
  2. One clear sprint goal — If you can't state it in one sentence, the sprint is unfocused.
  3. Identify stretch items — Know what to cut if things take longer than expected.
  4. Carry over honestly — If something didn't ship, understand why before re-committing.

來源與署名

來源:anthropics/knowledge-work-plugins位於product-management/skills/sprint-planning提交ae1513e

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架

更多來自 anthropics/knowledge-work-plugins 的技能

Ticket Deflector

anthropics

精選

Reads a forwarded customer email or ticket, pulls order and refund status from a payments connector (PayPal, Square, or Stripe) or Shopify, account history from the CRM, and open tickets from a support desk (Zoho Desk), drafts a tone-matched reply in the owner's writing voice, and can issue a refund through the payments connector with explicit owner approval. With Shopify connected it also runs a proactive order-triage mode that surfaces orders needing attention — unfulfilled past the promised window, payment problems, pending refunds, stuck shipments — and drafts the next action for each before the customer has to ask. Use when the user says "draft a response," "answer this customer," "where's my order," "I want a refund," "check my orders," or "anything about to blow up."

待分類27K今天更新

Tax Season Organizer

anthropics

精選

Prepares tax-season materials for the owner's accountant, not tax advice. US federal tax; a non-US business gets its closed-books packet instead. Two modes: (1) quarterly estimated tax from YTD net income in the ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books); (2) year-end 1099 prep, scanning the ledger, PayPal, and Stripe for contractors paid over USD 600 into a 1099-NEC list with missing W-9 flags. Any tax request routes first to /tax-prep, which confirms the books are closed and reconciled before running this skill. Use this skill directly only when the owner says the period's books are already closed: "books are closed, now do the 1099s," "run the quarterly estimate off the closed numbers," or "just the contractor W-9 list."

待分類27K今天更新

Tax Prep

anthropics

精選

根據已結帳的帳目準備稅務資料:季度預估繳稅明細,或年終 1099-NEC 清單與會計師資料包。

Business & Finance27K今天更新

Smb Onboard

anthropics

精選

引導小型企業主完成首次設定:連接工具、執行一次展現價值的配方、記錄業務背景並設定每週檢查節奏。

Productivity & Workflow27K今天更新

Smb Router

anthropics

精選

將小型企業主的需求轉接到合適的外掛技能或指令,並說明可用功能。

Productivity & Workflow27K今天更新

Month End Prep

anthropics

精選

Reconciles the accounting ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books) against PayPal, Shopify, Square, and Stripe settlements, flags transactions that need attention, suspicious duplicates, and missing receipts, then writes a plain-English P&L narrative and exports a close packet (xlsx + one-page PDF). This is the first link of the /close-month command; a request to close the month or the books routes there, and the command runs this skill before refreshing the forecast and distributing the packet. Use this skill directly only when the owner wants the reconciliation alone, with no forecast refresh and no distribution: "just reconcile, no packet," "what's missing from the books," "flag the duplicates and missing receipts," or "write the P&L narrative for this month."

待分類27K今天更新