pace-plan

An iteration-planning workflow for Devpace, where an iteration is a planned period of development work. It manages the end of one iteration and the scope of the next.

In plain words
What is it for?
It is for planning the next iteration, closing the current one, adjusting its scope, and checking iteration health.
Why use it?
It helps teams decide whether to continue, close, or adjust the current set of planned work.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/arch-team/devpace/pace-plan
Any agent
npx skills add arch-team/devpace --skill pace-plan
Clone the repo
git clone --depth 1 https://github.com/arch-team/devpace

Made for: Claude Code, Codex.

Per session 84 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 834 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00084 $0.00834
Opus 5 $0.00042 $0.00417
Sonnet 5 $0.00017 $0.00167
Haiku 4.5 $0.00008 $0.00083

Measured yesterday against content hash 68a5a533c2d1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pace-plan scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/pace-plan/SKILL.md · 62 lines

What it actually says

/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 skills/pace-plan/plan-procedures.md Step 1 → Step 3 → Step 4
close skills/pace-plan/close-procedures.md Step 1 → Step 2
adjust skills/pace-plan/adjust-procedures.md Step 2.5
health skills/pace-plan/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:规划新迭代

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

Step 4:确认与输出

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

输出

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

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 62 lines · 84 tokens per session scan A 68a5a533c2d1

Subscribe to this mod's changes

pace-plan is a skill published in the GitHub repository arch-team/devpace (73 stars, last pushed 4mo ago), licensed MIT. It adds 84 tokens to every session and 834 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories