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).
Use when user says "发布", "部署", "上线", "release", "pace-release", or wants to create, deploy, or close a release. NOT for CI/CD pipeline management (use /pace-sync). NOT for code implementation (use /pace-dev).
Use when user says "回顾", "复盘", "度量", "retro", "总结", "数据分析", "DORA", "质量报告", "交付效率", "度量报告", "趋势", "中期检查", "对比", "预测", "forecast", "能按时交付吗", "交付概率", "瓶颈", "pace-retro", or at iteration end when reviewing progress and metrics. NOT for next-step recommendations (use /pace-next). NOT for current status overview (use…
Use when user says "review", "审核", "帮我看看", "代码审查", "提交审核", "Gate 2", "提交审批", "pace-review", or when a change request reaches inreview state. NOT for running tests or acceptance verification (use /pace-test).
Use when user wants to switch output perspective (视角切换), says "切换角色/视角", "以XX视角", "pace-role", "作为产品经理", "作为运维", "换个角度看", or wants to view project from a different role perspective. NOT for project status overview (use /pace-status). NOT for understanding devpace concepts (use /pace-theory).
Use when user asks "进度怎样", "做到哪了", "项目状态", "当前状态", "进展", "看看进度", "总览", "dashboard", "pace-status", or wants to see project development progress and current state overview. NOT for next-step recommendations (use /pace-next).
Use when user says "同步/sync/同步到GitHub/关联Issue/unlink/Gate同步/sub-issue/全量同步/增量同步" or /pace-sync. Syncs Epic/BR/PF/CR to GitHub Issues. NOT for internal state (use /pace-dev).
Use when user says "跑测试", "测试覆盖", "验证一下", "验收", "回归", "影响分析", "test", "verify", "accept", "coverage", "测试策略", /pace-test, or when test results, coverage gaps, or acceptance readiness are discussed. NOT for code implementation (use /pace-dev). NOT for code review or approval (use /pace-review).
A guide to the ideas and working methods behind Devpace, including its development model, project objects, value chain, decisions, metrics, and change process.
Use when user asks "why did devpace decide X", "追溯", "为什么这样做", "决策记录", "决策原因", "架构决策", "ADR", "技术选型", wants to see AI decision trail or manage architecture decisions, or says /pace-trace [CR] [gate/decision/arch]. NOT for concept explanations or methodology questions (use /pace-theory). NOT for metrics or…