← 返回
未分类 中文

Sprint Plan

Use when the user asks to create, rewrite, or structure a concise one-week sprint plan, engineering sprint plan, focused project plan, or alignment doc with...
用于用户请求创建、重写或构建简洁的一周冲刺计划、工程冲刺计划、重点项目计划或对齐文档...
patrick-erichsen-2
未分类 clawhub v1.0.0 1 版本 100000 Key: 无需
★ 0
Stars
📥 181
下载
💾 1
安装
1
版本
#latest

概述

Sprint Plan

Use this skill to produce a concise sprint planning document for engineering or product alignment.

Workflow

  1. Identify the sprint outcome in one sentence.
  2. Add a concise bullet summary beneath the goal.
  3. State why this work matters now, using one concrete example if available.
  4. Separate current gaps from proposed work.
  5. Keep scope explicit: In Scope and Out Of Scope.
  6. Break work into 4-8 workstreams.
  7. For each workstream, include Goal, Deliverables, and Done when.
  8. Add decision principles only when they clarify tradeoffs.
  9. End with definition of done, success metrics, and risks/open questions.

Avoid day-by-day plans unless the user explicitly asks for scheduling.

Template

# <Sprint Name>

## Sprint Goal

<One clear sentence describing the outcome.>

## Summary

- <Most important outcome or user-visible change.>
- <Main internal/process improvement.>
- <Key automation, quality, or measurement improvement.>

## Context

<Why this matters now. Include a canonical example if useful.>

## Current Gaps

- <What is broken or missing today.>

## In Scope

- <What this sprint will attempt to ship.>

## Out Of Scope

- <What this sprint will intentionally avoid.>

## Workstreams

### 1. <Workstream>

Goal: <Short outcome.>

Deliverables:

- <Concrete deliverable.>

Done when: <Observable completion criteria.>

### 2. <Workstream>

Goal: <Short outcome.>

Deliverables:

- <Concrete deliverable.>

Done when: <Observable completion criteria.>

## Decision Principles

- <Tradeoff or rule that should guide implementation decisions.>

## Definition Of Done

- <Sprint-level completion checklist.>

## Success Metrics

- <Observable outcome or metric.>

## Risks / Open Questions

- <Unresolved assumption, dependency, or risk.>

Style

  • Be direct and readable.
  • Prefer concise bullets over long paragraphs.
  • Keep the doc focused on alignment, not exhaustive execution detail.
  • Avoid grand strategy unless the sprint depends on it.
  • Preserve user-provided language when it is clearer than generic planning jargon.

版本历史

共 1 个版本

  • v1.0.0 当前
    2026-06-01 12:53

安全检测

腾讯云安全 (Keen)

队列中

腾讯云安全 (Sanbu)

队列中

🔗 相关推荐

Test skill

patrick-erichsen-2
在 macOS 上使用 memo CLI 创建、查看、编辑、删除、搜索、移动或导出 AppleNotes。
★ 0 📥 314

Chronicle

patrick-erichsen-2
Allows you to view the user's screen as well as several hours of history. Use when the user makes a reference to their r
★ 0 📥 215

Yeet

patrick-erichsen-2
仅在用户明确要求一次性使用 GitHub CLI(gh)完成暂存、提交、推送并打开 GitHub Pull Request 时使用。
★ 0 📥 226