DevPace Iteration Planning

VerifiedSafe

Manages iteration close and new iteration planning. When called with 'next', 'close', 'adjust', or 'health' arguments, it performs specific actions like starting new sprint planning, closing current iteration with lightweight retrospective, adjusting scope mid-iteration, or showing health metrics. Helps teams complete the plan-execute-review cycle.

Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude Code
#sprint-planning#iteration-management#agile#project-management

Recommended for

Automated summary

Helps manage iteration cycles: close current sprint, plan next sprint, adjust scope, or check iteration health.

Strengths

  • Structured process for iteration planning and closing
  • Integration with other pace commands (pace-biz, pace-dev)
  • Provides iteration health metrics
  • Supports mid-iteration scope adjustments

Limitations

  • Requires specific file structure (.devpace/)
  • Does not handle PF-level requirement changes (use /pace-change)
  • May be overly structured for non-agile workflows
When to use it

Use this command when planning the next iteration, closing the current one, or adjusting scope mid-sprint.

When not to use it

Do not use for high-level requirement changes at the PF level; use /pace-change instead.

Security analysis

Safe
Quality score90/100

The skill only uses safe tools (AskUserQuestion, Write, Read, Edit, Glob) for planning and project management. It does not invoke any shell commands, network requests, or destructive operations.

No concerns found

How this analysis is made

Examples

Plan next iteration
Plan the next iteration based on the current backlog.
Close current iteration
Close the current iteration and archive it.
Check iteration health
Show the health status of the current iteration.

description: Use when user says "规划迭代", "下个迭代做什么", "迭代规划", "计划", "排期", "安排", "sprint", "pace-plan", "调整迭代范围", "迭代调整", "迭代健康", or at iteration boundary when planning next iteration scope. NOT for PF-level requirement changes (use /pace-change). allowed-tools: AskUserQuestion, Write, Read, Edit, Glob argument-hint: "[next|close|adjust|health]" context: fork agent: pace-pm

/pace-plan — 迭代规划

管理迭代的关闭和新迭代的规划,补齐产品闭环中的"规划→执行→回顾"循环。

与相关命令的关系

  • /pace-change:PF/BR/Epic 级需求变更(add/pause/resume/modify)
  • /pace-biz:业务规划域(Opportunity→Epic→BR 的创建和分解)
  • /pace-plan adjust:迭代范围级调整(本迭代纳入/移出哪些 PF)
  • 典型协同:/pace-biz decompose 分解出 BR/PF → /pace-plan next 纳入迭代 → /pace-dev 开始开发

输入

$ARGUMENTS:

  • (空)→ 评估当前迭代状态,建议下一步操作(关闭 or 继续)
  • next → 直接进入新迭代规划流程
  • close → 关闭当前迭代(自动轻量回顾 + 归档,不启动新迭代)
  • adjust → 迭代中途范围调整(增加/移除 PF、调整优先级)
  • health → 展示当前迭代健康度指标

执行路由

重要:根据 $ARGUMENTS 值,仅读取对应的 procedures 文件,不加载其他 procedures。

| 参数 | 加载文件 | 执行路径 | |------|---------|---------| | (空) | 无外部文件 | Step 1 评估 → 建议下一步 | | next | plan-procedures.md | Step 1 → Step 3 → Step 4 | | close | close-procedures.md | Step 1 → Step 2 | | adjust | adjust-procedures.md | Step 2.5 | | health | health-procedures.md | Step 5 |

流程

Step 1:评估当前迭代状态

  1. 读取 .devpace/iterations/current.md(不存在则跳到 Step 3)
  2. 读取 .devpace/project.md 的价值功能树(有 Epic 时按 Epic 分组展示)
  3. 汇总:PF 完成率(✅ 数 / 总数)、未完成 PF 列表及 CR 状态、变更记录条数、Epic 完成度(如有)
  4. 用 1-2 句话告知用户当前迭代进展

Step 3:规划新迭代

$ARGUMENTS 为 next 时执行。读取 plan-procedures.md 完成候选 PF 列出、范围估算、Plan Proposal 生成、迭代文件创建。

Step 4:确认与输出

展示新迭代规划摘要(目标 + PF 列表 + 周期 + 工作量估算),引导衔接 /pace-dev。

输出

迭代规划摘要(3-5 行):目标、纳入的 PF 数量、周期。

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/devpace-iteration-planning-mmlj2nz8/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/devpace-iteration-planning-mmlj2nz8' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/devpace-iteration-planning-mmlj2nz8/download' --output '.skill-downloads/devpace-iteration-planning-mmlj2nz8/SKILL.md.part' && mv '.skill-downloads/devpace-iteration-planning-mmlj2nz8/SKILL.md.part' '.skill-downloads/devpace-iteration-planning-mmlj2nz8/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): AskUserQuestion, Write, Read, Edit, Glob

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/devpace-iteration-planning-mmlj2nz8/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills