Plugin

devpace

Name: devpace
Author: arch-team

Manage end-to-end BizDevOps workflows in Claude Code projects via .devpace directories: capture business opportunities and decompose them into epics, features, and code changes; automate change request advancement with quality gates, testing, and autonomous coding; track iterations, releases, risks, and metrics; sync to GitHub Issues; generate role-specific reports and retrospectives.

Component Overview

Commands

pace-analyst, pace-engineer +1

Agents

/pace-biz — 业务规划域统一入口, /pace-change — 需求变更管理 +18

Skills

Stop, PreCompact +10

Hooks

MCP Servers

LSP Servers

devpace-bizdevops

Output Styles

Themes

Monitors

Install

npx claudepluginhub arch-team/devpace --plugin devpace

Component Details

Agents (3)

pace-analyst

/pace-analyst

Analyst perspective agent for devpace. Handles metrics collection, retrospectives, and trend analysis. Data analysis with write capability for dashboards and insights.

pace-engineer

/pace-engineer

Engineer perspective agent for devpace. Handles CR implementation, quality gates, and code changes. Full file access for development work.

pace-pm

/pace-pm

Product manager perspective agent for devpace. Handles iteration planning, change management, and business alignment. Analysis with write capability for planning and change execution.

Skills (20)

/pace-biz — 业务规划域统一入口

/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.

/pace-change — 需求变更管理

/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 (/pace-dev) or project init (/pace-init).

/pace-dev — 推进变更请求

/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 (/pace-change), code review (/pace-review), tests (/pace-test), or production issues (/pace-feedback).

/pace-feedback — 反馈收集与事件处理

/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 /pace-dev). NOT for requirement changes (use /pace-change).

/pace-guard — 风险预判与管理

/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 gate), NOT for /pace-test (testing).

/pace-help — 使用帮助

/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 recommendation (use /pace-next). NOT for code implementation (use /pace-dev).

/pace-init — 初始化项目开发节奏管理

/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 /pace-dev).

/pace-learn — 经验积累与知识管理

/pace-learn

Use when user says "/pace-learn", "经验", "知识库", "pattern", "lessons learned", "学到了什么", or auto-invoked after CR merge, gate failure recovery, or human rejection. NOT for iteration retrospectives or metrics (use /pace-retro). NOT for concept explanations (use /pace-theory).

/pace-next — 下一步导航

/pace-next

Use when user asks "下一步做什么", "接下来做什么", "该做什么", "什么最重要", "应该先做哪个", "最紧急", "优先级", "推荐做什么", "为什么推荐这个", "pace-next", or wants a recommendation for the most important next action across all domains. NOT for current progress overview (use /pace-status).

/pace-plan — 迭代规划

/pace-plan

Use when user says "规划迭代", "下个迭代做什么", "迭代规划", "计划", "排期", "安排", "sprint", "pace-plan", "调整迭代范围", "迭代调整", "迭代健康", or at iteration boundary when planning next iteration scope. NOT for PF-level requirement changes (use /pace-change).

pace-pulse — 节奏心跳检查

/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).

/pace-release — 发布管理

/pace-release

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).

/pace-retro — 迭代回顾与度量

/pace-retro

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 /pace-status).

/pace-review — 生成 Review 摘要

/pace-review

Use when user says "review", "审核", "帮我看看", "代码审查", "提交审核", "Gate 2", "提交审批", "pace-review", or when a change request reaches in_review state. NOT for running tests or acceptance verification (use /pace-test).

/pace-role — 角色视角切换

/pace-role

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).

/pace-status — 查看项目状态

/pace-status

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).

/pace-sync — 外部工具同步

/pace-sync

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).

/pace-test — BizDevOps 感知的测试策略与验证

/pace-test

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).

/pace-theory — 设计理论指南

/pace-theory

Use when user asks "为什么", "怎么理解", "概念", "理论", "方法论", "BizDevOps", "原理", "什么是 BR", "什么是 PF", "CR 是什么意思", "价值链", "状态机原理", "追溯", "闭环", "度量", "MoS", "成效指标", "设计决策", "pace-theory", or wants to understand devpace concepts, behavior rationale, or methodology. NOT for specific CR decision audit trail (use /pace-trace). NOT for code implementation (use /pace-dev).

/pace-trace — 决策轨迹查询

/pace-trace

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 retrospective analysis (use /pace-retro).

Hooks (1)

Review workflow modifications before installing

Event Hooks

File writes

12 hooks across 9 events

Output Styles (1)

devpace-bizdevops

keeps coding instructions

BizDevOps development rhythm communication style — traces business intent through product features to code changes

README

🌐 中文版 | English

devpace

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.

version

Why devpace

When using Claude Code for product development:

Problem	Without devpace	With devpace
Requirements change = chaos	"Add a feature" triggers cascading confusion, nobody knows the blast radius	Impact analysis + orderly adjustment, Claude won't change the plan on its own
Inconsistent quality	Claude sometimes skips tests, forgets checks	Auto-checks + human approval, quality gates cannot be bypassed
Work drifts from goals	Technical work disconnects from business goals, lots done but unclear value	Goal-to-code traceability at all times
Re-explain everything each session	Manual approach needs 8 user corrections (3 interruption test)	Auto-restores context, 0 corrections

See full walkthrough: from init to done

30-Second Experience

/pace-init                 ← Initialize (once)
"Help me implement user auth" ← Claude auto-tracks tasks, writes code, runs tests, checks quality
"approve" or "reject"      ← You decide whether to merge
"add an export feature"    ← Claude analyzes impact, adjusts plan, waits for your confirmation
"pause auth for now"       ← Impact analysis → pause (preserving work) → adjust plan

Next session, Claude reports: "Last time we stopped at auth module, continue?" — zero manual re-explanation.

Full Development Lifecycle

Opportunity ──→ Epic ──→ Requirements ──→ Features ──→ Code Changes ──→ Quality ──→ Ship
        │          │           │              │              │              │           │
     pace-biz   pace-biz   pace-biz       pace-plan      pace-dev     pace-review  pace-release
                                          pace-change                              pace-feedback

Requirements can change anytime — /pace-change auto-analyzes impact, adjusts the plan, and waits for your confirmation.

After each cycle, /pace-retro shows quality metrics and improvement trends.

How It Works

devpace builds a goal-to-code traceability chain in your project:

Goal alignment — Every code change links back to a business goal. No work without purpose.
Auto quality gates — Claude auto-checks code quality and requirement consistency, self-repairs on failure. Human approval cannot be skipped.
Change is normal — Requirements changed? Auto impact analysis, orderly adjustment, existing work preserved.
Interrupt-proof — Session broke? Auto-resume next time. All state in .devpace/ as plain Markdown.

Under the hood: a Claude Code Plugin using Rules (behavioral guidelines) + Skills (/pace-* commands) + Hooks (auto-triggers at critical moments).

Installation

Prerequisite: Claude Code CLI must be installed.

Marketplace Install (Recommended)

# Step 1: Register marketplace (one-time)
/plugin marketplace add arch-team/devpace-marketplace

# Step 2: Install
/plugin install devpace@devpace

From Source

git clone https://github.com/arch-team/devpace.git
claude --plugin-dir /path/to/devpace

Verify Installation

After installing, type /pace- in Claude Code. If devpace is loaded, you'll see auto-complete suggestions for /pace-init, /pace-dev, /pace-status, etc.

Commands

Most of the time you don't need commands — saying "help me implement X" equals /pace-dev, "where are we" equals /pace-status.

Start Here (5 commands cover 90% of daily work)

Command	Purpose
`/pace-init`	First-time setup (once)
`/pace-dev`	Start coding — or just say "help me implement X"
`/pace-status`	Check progress — or say "where are we"
`/pace-review`	Approve changes
`/pace-next`	Not sure what's next? Get AI recommendations

More Commands

As your project grows, devpace offers change management, iteration planning, business alignment, release orchestration, and more. See User Guide for all 19 commands.

Quick reference: /pace-change (requirements changed) · /pace-plan (plan iterations) · /pace-retro (review metrics) · /pace-biz (business planning) · /pace-release (ship it)

Core Capabilities

Change Management (Core Differentiator)

View full README on GitHub

Similar Plugins

dotnet-skills

Comprehensive .NET development skills for modern C#, ASP.NET, MAUI, Blazor, Aspire, EF Core, Native AOT, testing, security, performance optimization, CI/CD, and cloud-native applications

Stats

Version1.7.0

Stars57

Forks6

MaintenanceExcellent

LicenseMIT

Last CommitApr 20, 2026

AddedMar 25, 2026

Actions

View on GitHub View README Plugin Marketplace JSON

Available In

devpace57

Safety Signals

Caution

Modifies files

Hook triggers on file write and edit operations

Uses power tools

Uses Bash, Write, or Edit tools

devpace

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.

version

Why devpace

When using Claude Code for product development:

Problem	Without devpace	With devpace
Requirements change = chaos	"Add a feature" triggers cascading confusion, nobody knows the blast radius	Impact analysis + orderly adjustment, Claude won't change the plan on its own
Inconsistent quality	Claude sometimes skips tests, forgets checks	Auto-checks + human approval, quality gates cannot be bypassed
Work drifts from goals	Technical work disconnects from business goals, lots done but unclear value	Goal-to-code traceability at all times
Re-explain everything each session	Manual approach needs 8 user corrections (3 interruption test)	Auto-restores context, 0 corrections

See full walkthrough: from init to done

30-Second Experience

/pace-init                 ← Initialize (once)
"Help me implement user auth" ← Claude auto-tracks tasks, writes code, runs tests, checks quality
"approve" or "reject"      ← You decide whether to merge
"add an export feature"    ← Claude analyzes impact, adjusts plan, waits for your confirmation
"pause auth for now"       ← Impact analysis → pause (preserving work) → adjust plan

Next session, Claude reports: "Last time we stopped at auth module, continue?" — zero manual re-explanation.

Full Development Lifecycle

Opportunity ──→ Epic ──→ Requirements ──→ Features ──→ Code Changes ──→ Quality ──→ Ship
        │          │           │              │              │              │           │
     pace-biz   pace-biz   pace-biz       pace-plan      pace-dev     pace-review  pace-release
                                          pace-change                              pace-feedback

Requirements can change anytime — /pace-change auto-analyzes impact, adjusts the plan, and waits for your confirmation.

After each cycle, /pace-retro shows quality metrics and improvement trends.

How It Works

devpace builds a goal-to-code traceability chain in your project:

Goal alignment — Every code change links back to a business goal. No work without purpose.
Auto quality gates — Claude auto-checks code quality and requirement consistency, self-repairs on failure. Human approval cannot be skipped.
Change is normal — Requirements changed? Auto impact analysis, orderly adjustment, existing work preserved.
Interrupt-proof — Session broke? Auto-resume next time. All state in .devpace/ as plain Markdown.

Under the hood: a Claude Code Plugin using Rules (behavioral guidelines) + Skills (/pace-* commands) + Hooks (auto-triggers at critical moments).

Installation

Prerequisite: Claude Code CLI must be installed.

Marketplace Install (Recommended)

# Step 1: Register marketplace (one-time)
/plugin marketplace add arch-team/devpace-marketplace

# Step 2: Install
/plugin install devpace@devpace

From Source

git clone https://github.com/arch-team/devpace.git
claude --plugin-dir /path/to/devpace

Verify Installation

After installing, type /pace- in Claude Code. If devpace is loaded, you'll see auto-complete suggestions for /pace-init, /pace-dev, /pace-status, etc.

Commands

Most of the time you don't need commands — saying "help me implement X" equals /pace-dev, "where are we" equals /pace-status.

Start Here (5 commands cover 90% of daily work)

Command	Purpose
`/pace-init`	First-time setup (once)
`/pace-dev`	Start coding — or just say "help me implement X"
`/pace-status`	Check progress — or say "where are we"
`/pace-review`	Approve changes
`/pace-next`	Not sure what's next? Get AI recommendations

More Commands

As your project grows, devpace offers change management, iteration planning, business alignment, release orchestration, and more. See User Guide for all 19 commands.

Quick reference: /pace-change (requirements changed) · /pace-plan (plan iterations) · /pace-retro (review metrics) · /pace-biz (business planning) · /pace-release (ship it)

devpace

Component Overview

Install

Component Details

Agents (3)

Skills (20)

Hooks (1)

Output Styles (1)

README

devpace

Why devpace

30-Second Experience

Full Development Lifecycle

How It Works

Installation

Marketplace Install (Recommended)

From Source

Verify Installation

Commands

Start Here (5 commands cover 90% of daily work)

More Commands

Core Capabilities

Change Management (Core Differentiator)

Similar Plugins

dotnet-skills

devpace

Component Overview

Install

Component Details

Agents (3)

Skills (20)

Hooks (1)

Output Styles (1)

README

devpace

Why devpace

30-Second Experience

Full Development Lifecycle

How It Works

Installation

Marketplace Install (Recommended)

From Source

Verify Installation

Commands

Start Here (5 commands cover 90% of daily work)

More Commands

Core Capabilities

Change Management (Core Differentiator)

Similar Plugins

dotnet-skills

claude-code-toolkit

everything-claude-code

fullstack-dev-skills

prompts.chat

agent-teams