business-sprint-plan

Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing

SKILL.md

GitHub

App 执行约定

先读取本技能正文及任务所需的本地参考资源。使用中文;工作目录由任务提供,仅读取用户提供、当前任务授权的资料。正文中的 $ARGUMENTS 及斜杠命令表示用户任务输入,不调用 Claude 专用命令。AskUserQuestion/提问通过 App ask_user;本地文件通过 read_file,成果使用 write_file 后 register_artifact,或 write_artifact。相对资源路径以本 SKILL.md 所在目录为起点。若技能读取结果含目录,按该目录构建资源绝对路径。

正文中 Search/WebFetch、Figma、CRM、广告平台及其它连接名称仅为可选来源;只使用 App 实际提供且已授权的工具。没有连接时从上传材料完成流程,把缺少的外部验证列出,不安装运行时插件或扫描用户全局配置。默认输出 Markdown/CSV 草稿;Office、图表、HTML、PNG 或图像生成只在对应工具和运行库可用时执行。不得擅自发送邮件、发表内容、签约、创建发票、修改线上商品或花费广告预算。

Sprint Planning

Plan a sprint by estimating team capacity, selecting and sequencing stories, and identifying risks.

Context

You are helping plan a sprint for $ARGUMENTS.

If the user provides files (backlogs, velocity data, team rosters, or previous sprint reports), read them first.

Instructions

  1. Estimate team capacity:

    • Number of team members and their availability (PTO, meetings, on-call)
    • Historical velocity (average story points per sprint from last 3 sprints)
    • Capacity buffer: reserve 15-20% for unexpected work, bugs, and tech debt
    • Calculate available capacity in story points or ideal hours
  2. Review and select stories:

    • Pull from the prioritized backlog (highest priority first)
    • Verify each story meets the Definition of Ready (clear AC, estimated, no blockers)
    • Flag stories that need refinement before committing
    • Stop adding stories when capacity is reached
  3. Map dependencies:

    • Identify stories that depend on other stories or external teams
    • Sequence dependent stories appropriately
    • Flag external dependencies and owners
    • Identify the critical path
  4. Identify risks and mitigations:

    • Stories with high uncertainty or complexity
    • External dependencies that could slip
    • Knowledge concentration (only one person can do it)
    • Suggest mitigations for each risk
  5. Create the sprint plan summary:

    Sprint Goal: [One sentence describing what success looks like]
    Duration: [2 weeks / 1 week / etc.]
    Team Capacity: [X story points]
    Committed Stories: [Y story points across Z stories]
    Buffer: [remaining capacity]
    
    Stories:
    1. [Story title] — [points] — [owner] — [dependencies]
    ...
    
    Risks:
    - [Risk] → [Mitigation]
    
  6. Define the sprint goal: A single, clear sentence that captures the sprint's primary value delivery.

Think step by step. Save as markdown.


Further Reading