/pace-guard
Use when user wants to assess risks before development, check current risk status, analyze risk trends, or says "风险/预检/预分析/guard/risk/隐患/安全检查". Also auto-invoked during advance mode intent checkpoint for L/XL CRs. NOT for /pace-dev (implementation), NOT for /pace-review (quality
$ npx -y skills add arch-team/devpace --skill pace-guard --agent claude-codeHow 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-guard
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when user wants to assess risks before development, check current risk status, analyze risk trends, or says "风险/预检/预分析/guard/risk/隐患/安全检查". Also auto-invoked during advance mode intent checkpoint for L/XL CRs. NOT for /pace-dev (implementation), NOT for /pace-review (quality
SKILL.md
pace-guard.SKILL.mddescription: Use when user wants to assess risks before development, check current risk status, analyze risk trends, or says "风险/预检/预分析/guard/risk/隐患/安全检查". Also auto-invoked during advance mode intent checkpoint for L/XL CRs. NOT for /pace-dev (implementation), NOT for /pace-review (quality gate), NOT for /pace-test (testing).
allowed-tools: Read, Write, Edit, Glob, Grep, Bash
model: sonnet
argument-hint: "[scan|monitor|trends|report|resolve] [CR编号] [--full|--brief|--detail|--batch]"
context: fork
agent: pace-analyst
/pace-guard — 风险预判与管理
统一管理开发全生命周期的风险:从编码前的 Pre-flight 扫描,到开发中的实时监控,再到跨迭代的趋势分析——让风险可见、可追踪、可解决。风险评估覆盖 Epic 级别(Epic 范围风险影响其下所有 BR/PF/CR)。
推荐使用流程
编码前预检: scan(L/XL CR 意图检查点自动触发)
开发中监控: monitor(pace-pulse 周期性触发)
问题解决: resolve RISK-xxx mitigated
迭代回顾: trends → report
子命令
| 子命令 | 用途 | 输入 | 自动触发 | |--------|------|------|---------| | `scan` | Pre-flight 风险扫描 | CR 编号或当前 CR | L/XL 意图检查点 | | `monitor` | 实时风险汇总 | 当前 CR | pace-pulse 第 8 信号 | | `trends` | 跨 CR 趋势分析 | 迭代 ID(可选) | pace-retro 报告 | | `report` | 风险全局视图 | — | 用户显式调用 | | `resolve` | 更新风险状态 | RISK 编号 + 目标状态 | Gate 通过后自动提议 |
输入
$ARGUMENTS:
- `scan [CR编号] [--full|--detail]` → 对指定 CR(或当前活跃 CR)执行 Pre-flight 风险扫描。`--full` 强制完整 5 维扫描,`--detail` 展示全维度矩阵
- `monitor [CR编号] [--detail|--brief]` → 汇总当前 CR 的实时风险状态。默认简要输出,`--detail` 展开完整表格
- `trends [迭代ID] [--detail]` → 分析跨 CR 的风险趋势(默认当前迭代)。默认摘要,`--detail` 展示完整趋势报告
- `report [--brief|--detail]` → 生成项目级风险全局视图
- `resolve <RISK编号> <目标状态>` → 更新指定风险的状态(mitigated / accepted / resolved)
- `resolve --batch [严重度]` → 批量处理同等级的 open 风险
- (空)→ 等同于 `scan`,对当前 CR 执行风险扫描
流程
Step 1:上下文加载
1. 检查 `.devpace/` 是否存在:
- **存在** → 读取 `state.md` 确定当前 CR 和项目状态,继续 Step 2
- **不存在(降级模式)** → 基于代码库直接分析(无 CR 级风险追踪,仅提供即时风险评估)
2. 如果指定了 CR 编号 → 定位对应 CR 文件 3. 如果未指定 → 读取 state.md 当前活跃 CR
Step 2:路由到子命令
根据 $ARGUMENTS 第一个参数路由(**仅读取匹配子命令的规程文件**):
| 参数 | 流程 | 加载文件 | |------|------|---------| | (空)/ `scan` | Pre-flight 风险扫描 | `skills/pace-guard/guard-procedures-common.md` + `skills/pace-guard/guard-procedures-scan.md` | | `monitor` | 实时风险汇总 | `skills/pace-guard/guard-procedures-common.md` + `skills/pace-guard/guard-procedures-monitor.md` | | `trends` | 跨 CR 趋势分析 | `skills/pace-guard/guard-procedures-trends.md`(自包含) | | `report` | 风险全局视图 | `skills/pace-guard/guard-procedures-report.md`(自包含) | | `resolve` | 更新风险状态 | `skills/pace-guard/guard-procedures-common.md` + `skills/pace-guard/guard-procedures-resolve.md` |
Step 3:执行并报告
1. 按子命令流程执行 2. 将风险发现写入 CR 文件"风险预评估"section(scan/monitor 产出) 3. 更新 state.md(如有状态变化) 4. **智能推荐**:风险评估类报告末尾根据风险等级推荐下一步操作(详见各子命令规程文件)
输出
各子命令均支持 `--brief`/`--detail` 分层输出,具体格式和降级模式见对应 procedures 文件。
Read more
description: Use when user wants to assess risks before development, check current risk status, analyze risk trends, or says "风险/预检/预分析/guard/risk/隐患/安全检查". Also auto-invoked during advance mode intent checkpoint for L/XL CRs. NOT for /pace-dev (implementation), NOT for /pace-review (quality gate), NOT for /pace-test (testing). allowed-tools: Read, Write, Edit, Glob, Grep, Bash model: sonnet argument-hint: "[scan|monitor|trends|report|resolve] [CR编号] [--full|--brief|--detail|--batch]" context: fork agent: pace-analyst
/pace-guard — 风险预判与管理
统一管理开发全生命周期的风险:从编码前的 Pre-flight 扫描,到开发中的实时监控,再到跨迭代的趋势分析——让风险可见、可追踪、可解决。风险评估覆盖 Epic 级别(Epic 范围风险影响其下所有 BR/PF/CR)。
推荐使用流程
编码前预检: scan(L/XL CR 意图检查点自动触发) 开发中监控: monitor(pace-pulse 周期性触发) 问题解决: resolve RISK-xxx mitigated 迭代回顾: trends → report
子命令
| 子命令 | 用途 | 输入 | 自动触发 | |--------|------|------|---------| | `scan` | Pre-flight 风险扫描 | CR 编号或当前 CR | L/XL 意图检查点 | | `monitor` | 实时风险汇总 | 当前 CR | pace-pulse 第 8 信号 | | `trends` | 跨 CR 趋势分析 | 迭代 ID(可选) | pace-retro 报告 | | `report` | 风险全局视图 | — | 用户显式调用 | | `resolve` | 更新风险状态 | RISK 编号 + 目标状态 | Gate 通过后自动提议 |
输入
$ARGUMENTS:
- `scan [CR编号] [--full|--detail]` → 对指定 CR(或当前活跃 CR)执行 Pre-flight 风险扫描。`--full` 强制完整 5 维扫描,`--detail` 展示全维度矩阵
- `monitor [CR编号] [--detail|--brief]` → 汇总当前 CR 的实时风险状态。默认简要输出,`--detail` 展开完整表格
- `trends [迭代ID] [--detail]` → 分析跨 CR 的风险趋势(默认当前迭代)。默认摘要,`--detail` 展示完整趋势报告
- `report [--brief|--detail]` → 生成项目级风险全局视图
- `resolve <RISK编号> <目标状态>` → 更新指定风险的状态(mitigated / accepted / resolved)
- `resolve --batch [严重度]` → 批量处理同等级的 open 风险
- (空)→ 等同于 `scan`,对当前 CR 执行风险扫描
流程
Step 1:上下文加载
1. 检查 `.devpace/` 是否存在:
- **存在** → 读取 `state.md` 确定当前 CR 和项目状态,继续 Step 2
- **不存在(降级模式)** → 基于代码库直接分析(无 CR 级风险追踪,仅提供即时风险评估)
2. 如果指定了 CR 编号 → 定位对应 CR 文件 3. 如果未指定 → 读取 state.md 当前活跃 CR
Step 2:路由到子命令
根据 $ARGUMENTS 第一个参数路由(**仅读取匹配子命令的规程文件**):
| 参数 | 流程 | 加载文件 | |------|------|---------| | (空)/ `scan` | Pre-flight 风险扫描 | `skills/pace-guard/guard-procedures-common.md` + `skills/pace-guard/guard-procedures-scan.md` | | `monitor` | 实时风险汇总 | `skills/pace-guard/guard-procedures-common.md` + `skills/pace-guard/guard-procedures-monitor.md` | | `trends` | 跨 CR 趋势分析 | `skills/pace-guard/guard-procedures-trends.md`(自包含) | | `report` | 风险全局视图 | `skills/pace-guard/guard-procedures-report.md`(自包含) | | `resolve` | 更新风险状态 | `skills/pace-guard/guard-procedures-common.md` + `skills/pace-guard/guard-procedures-resolve.md` |
Step 3:执行并报告
1. 按子命令流程执行 2. 将风险发现写入 CR 文件"风险预评估"section(scan/monitor 产出) 3. 更新 state.md(如有状态变化) 4. **智能推荐**:风险评估类报告末尾根据风险等级推荐下一步操作(详见各子命令规程文件)
输出
各子命令均支持 `--brief`/`--detail` 分层输出,具体格式和降级模式见对应 procedures 文件。
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.
Repo: arch-team/devpace
Other skills on devpace.
- /pace-biz
Use when user says "业务机会/OPP", "专题/Epic", "分解需求/decompose", "精炼/refine", "战略对齐/align", "业务全景/view", "需求发现/brainstorm/discover", "导入/import", "技术债务/infer", "pace-biz", or wants to plan requirements. NOT for /pace-dev, -change, -plan, -init.
Open skill - /pace-change
Use when user says "不做了", "搁置", "停掉", "加一个", "加需求", "追加", "改需求", "需求变了", "范围变了", "优先级调", "延后", "提前", "砍掉", "先做这个", "排到前面", "恢复", "捡回来", "pace-change", or wants to add, pause, resume, reprioritize, modify, undo, batch change, or query change history. NOT for code implementation
Open skill - /pace-dev
Use when user says "开始做", "帮我改", "实现", "修复", "继续推进", "编码", "写代码", "开发", "重构", "做个", "coding", "implement", "fix", "refactor", "build", /pace-dev, or explicitly requests to start/continue/resume coding work. "帮我改" only when target is code/UI/config. NOT for requirement changes
Open skill - /pace-feedback
Use when user reports issues, shares feedback, or receives production alerts — "用户反馈", "线上问题", "生产问题", "告警", "改进建议", "新需求", "体验问题", "功能请求", "线上bug", "运维", "事件", "incident", "故障", "P0", "P1", "严重故障", "postmortem", "事后复盘". NOT for code implementation or development (use
Open skill - /pace-help
Use when user says "帮助", "help", "怎么用", "使用说明", "用法", "有哪些命令", "能做什么", "命令列表", "怎么入门", "quickstart", "FAQ", "常见问题", "pace-help", or wants help with how to use devpace commands and features. NOT for concept deep dive or methodology (use /pace-theory). NOT for next-step
Open skill - /pace-init
Use when user says "初始化", "pace-init", "开始追踪", "初始化研发管理", "新项目", "项目管理", "set up devpace", "健康检查 devpace", "重置 devpace", "预览初始化", or wants to set up, verify, or reset project development tracking. NOT for current progress overview (use /pace-status) or starting development (use
Open skill

