From devpace
Recommends highest-priority next action by scanning .devpace signals from CRs, risks, iterations, releases, epics, and metrics. Triggered by '下一步做什么', 'pace-next', or priority queries.
How this skill is triggered — by the user, by Claude, or both
Slash command
/devpace:pace-nexthaikuThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
跨域全局导航:综合 CR、迭代、Release、度量、风险、Epic/Opportunity 等多维信号,推荐当前最该做的 1 件事。
跨域全局导航:综合 CR、迭代、Release、度量、风险、Epic/Opportunity 等多维信号,推荐当前最该做的 1 件事。
$ARGUMENTS:
detail → 展开候选列表(≤ 8 行,含 top-3 建议)why → 展开推理链(2-5 行,信号扫描 + 优先级对比 + 角色影响 + 备选)journey [模板名] → 展示完整工作流路径:从当前状态到目标的分步引导
new-feature(默认)、iteration、hotfix、release、onboarding重要:根据 $ARGUMENTS 值,仅读取对应的输出规程文件,不加载全部规程。所有模式先加载 skills/pace-next/next-procedures.md(核心决策逻辑)。
| 参数 | 加载文件 |
|---|---|
| (空) | skills/pace-next/next-procedures.md + skills/pace-next/next-procedures-output-default.md |
detail | skills/pace-next/next-procedures.md + skills/pace-next/next-procedures-output-detail.md |
why | skills/pace-next/next-procedures.md + skills/pace-next/next-procedures-output-why.md |
journey | skills/pace-next/next-procedures.md + skills/pace-next/next-procedures-journey.md |
.devpace/state.md读取 .devpace/ 下的数据源(目录/文件不存在时静默跳过):
| 数据源 | 读取内容 |
|---|---|
backlog/*.md | CR 状态、类型 |
state.md | 当前工作摘要 |
releases/*.md | Release 状态 |
risks/*.md | 风险严重度 |
iterations/current.md | PF 完成率、周期 |
metrics/dashboard.md | 最近更新日期 |
project.md | MoS、PF/BR/OBJ 映射 |
integrations/sync-mapping.md | 同步状态(存在时) |
epics/*.md | Epic 状态、BR 列表 |
opportunities.md | Opportunity 状态 |
提取关键状态字段(不全量读取)。额外采集 CR→PF→BR→Epic→OPP 价值链映射。
从高到低遍历信号分组,取首个命中(判断细节见 skills/pace-next/next-procedures.md):
| 组 | 信号 |
|---|---|
| Blocking | S1 审批阻塞(in_review > 0)· S2 高风险阻塞(High 且 open) |
| In Progress | S3 继续开发(developing CR)· S4 恢复暂停(paused 阻塞解除) |
| Delivery | S5 Release 待验证 · S6 风险积压(open > 3)· S7 迭代紧迫(< 2 天且 < 50%)· S8 迭代接近完成(> 80%) |
| Strategic | S9 回顾提醒(> 7 天 + merged)· S10 缺陷占比(> 30%)· S11 同步滞后(> 24h)· S12 MoS 达成(> 80%) |
| Growth | S13 功能未开始 · S14 规划新迭代 · S15 全部完成 · S16 Epic 需分解 · S17 未评估机会 · S18 功能树稀疏 · S19 范围未定义 · S21 依赖阻塞 · S22 技术债积压 · S24 首次循环引导 |
| Idle | S20 无信号 |
journey 模式跳过 Step 3 的信号优先级决策,改为按旅程模板生成分步路径。详见 skills/pace-next/next-procedures-journey.md。
匹配历史经验 pattern(.devpace/metrics/insights.md,如存在),在建议中附加 ≤1 行经验参考。
根据当前角色(Dev/PM/Biz/Tester/Ops)调整建议措辞维度和信号组内排序。
按路由表加载的输出规程文件格式化输出。
≤ 3 行(默认)或 ≤ 8 行(detail)或 2-5 行推理链(why)。自然语言为主,不暴露 ID。建议体现价值链上下文。
npx claudepluginhub arch-team/devpace --plugin devpaceReads project state and recommends the single next sensible step, anchored to concrete tasks and open questions. Read-only advisory output.
Analyzes project state to suggest next actions based on pipeline status, artifacts, and context. Helps developers decide what to do next.
Scores and recommends the next highest-impact unblocked roadmap item, then assigns it and transitions to the appropriate next skill.