Skip to content

/pace-pulse

Auto-invoked during advance mode after extended work on same CR, at session start/end, or when rhythm anomalies are detected. NOT for metrics reports or retrospectives (use /pace-retro). NOT for project status overview (use /pace-status).

From plugin
7320 skills3 agents9 hooks
shell
$ npx -y skills add arch-team/devpace --skill pace-pulse --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/pace-pulse
How auto-invocation works

Context preview

The summary Claude sees to decide when to auto-load this skill.

Auto-invoked during advance mode after extended work on same CR, at session start/end, or when rhythm anomalies are detected. NOT for metrics reports or retrospectives (use /pace-retro). NOT for project status overview (use /pace-status).

SKILL.md

pace-pulse.SKILL.md
description: Auto-invoked during advance mode after extended work on same CR, at session start/end, or when rhythm anomalies are detected. NOT for metrics reports or retrospectives (use /pace-retro). NOT for project status overview (use /pace-status).
user-invocable: false
allowed-tools: Read, Write, Glob
model: haiku
context: fork
agent: pace-analyst

pace-pulse — 节奏心跳检查

Claude 自动调用的健康度检查 Skill,不暴露给用户。在推进模式中周期性执行,检测研发节奏异常并输出非打断式建议。

触发条件

由 `rules/devpace-rules.md` §10 和 §6 定义触发时机:

  • 推进模式中每完成 5 个 checkpoint 后(脉搏检查)
  • 会话中超过 30 分钟未切换 CR
  • 会话开始时(§1 分层摘要)
  • 会话结束时(§6 节奏摘要)
  • 提醒配额:标准 ≤3 条/会话(长会话 >2h 放宽至 ≤5 条),正向反馈和会话结束摘要不计配额

执行路由

**重要**:根据触发场景,仅读取路由表中对应的 procedures 文件,不加载其他 procedures。

| 触发场景 | 加载文件 | |---------|---------| | 脉搏检查(§10,每 5 checkpoint) | `skills/pace-pulse/pulse-procedures-core.md` | | 会话开始(§1) | `skills/pace-pulse/pulse-procedures-session-start.md` + `skills/pace-pulse/pulse-procedures-snooze.md` + `skills/pace-pulse/pulse-procedures-gc.md` | | 会话结束(§6) | `skills/pace-pulse/pulse-procedures-session-end.md` | | CR merged 后 Snooze 检测(§11) | `skills/pace-pulse/pulse-procedures-snooze.md` |

流程

Step 1:采集信号

1. 读取 `.devpace/state.md`:当前工作状态 2. 读取 `.devpace/iterations/current.md`(如存在):PF 完成率、迭代阶段 3. 扫描 `.devpace/backlog/` 所有 CR 文件:状态分布 4. 读取 `.devpace/metrics/dashboard.md`(如存在):最近更新日期 5. 读取 `.devpace/risks/`(如存在):风险积压状态

Step 2:按路由表加载对应文件执行评估

根据触发场景加载对应 procedures 文件,执行信号评估和建议输出。

Step 3:记录执行时间戳

将当前时间戳(`Date.now()` 毫秒值)写入 `.devpace/.pulse-last-run`,供 pulse-counter Hook 协调避免双重提醒。

角色感知

脉搏信号检测逻辑不变,仅调整输出措辞按当前角色关注点框架化:

| 信号示例 | Dev 框架(默认) | PM 框架 | Biz 框架 | |---------|----------------|---------|---------| | CR 滞留 >3 天 | "检查是否遇到技术阻塞" | "可能影响迭代进度,建议评估" | "交付延迟可能影响目标达成" | | Gate 失败率高 | "质量检查频繁失败,建议审视实现" | "质量问题可能拖慢交付节奏" | "质量风险可能影响产品可靠性" | | 风险积压 >3 | "有未解决的技术风险待处理" | "风险积压影响迭代健康度" | "累积风险可能影响业务目标" |

规则:适配通用原则见 `knowledge/role-adaptations.md`(权威源)。Dev 角色不改变现有措辞。信号严重度升级规则不受角色影响。

输出

  • **脉搏检查**:0-2 行 `💡` 建议,含可操作命令。严重度升级用 `⚠️`
  • **正向反馈**:`✓` 前缀,≤1 次/会话
  • **会话结束**:`📊` 前缀,1-2 行节奏总结
  • **会话开始**:分层摘要(最高 1 条完整建议 + 精简列表),≤3 行
Read more
Read it on GitHub ↗
Ships withdevpace

Give your Claude Code projects a steady development pace — requirements change, rhythm stays. A development harness for Claude Code — rules, schemas, gates, and feedback loops that keep AI-assisted development traceable and measurable.

Get the whole plugin, auto-invoked
Stats
73
Stars
0
Views
6
Forks
Maintained
Maintenance
Python
Language
MIT
License
3mo ago
Last commit
5mo ago
Created

Repo: arch-team/devpace

Other skills on devpace.