By arch-team
Manage BizDevOps workflows with multi-role collaboration, change impact analysis, quality gates, goal-to-code traceability, and cross-session continuity for .devpace projects.
Analyst perspective agent for devpace. Handles metrics collection, retrospectives, and trend analysis. Data analysis with write capability for dashboards and insights.
Engineer perspective agent for devpace. Handles CR implementation, quality gates, and code changes. Full file access for development work.
Product manager perspective agent for devpace. Handles iteration planning, change management, and business alignment. Analysis with write capability for planning and change execution.
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.
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).
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).
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).
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).
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
🌐 中文版 | English
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.
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 |
/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.
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.
devpace builds a goal-to-code traceability chain in your project:
.devpace/ as plain Markdown.Under the hood: a Claude Code Plugin using Rules (behavioral guidelines) + Skills (/pace-* commands) + Hooks (auto-triggers at critical moments).
Prerequisite: Claude Code CLI must be installed.
# Step 1: Register marketplace (one-time)
/plugin marketplace add arch-team/devpace-marketplace
# Step 2: Install
/plugin install devpace@devpace
git clone https://github.com/arch-team/devpace.git
claude --plugin-dir /path/to/devpace
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.
Most of the time you don't need commands — saying "help me implement X" equals /pace-dev, "where are we" equals /pace-status.
| 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 |
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)
npx claudepluginhub arch-team/devpace --plugin devpaceImplementation planning, execution, and PR creation workflows with multi-agent collaboration
PRD-driven AI dev team control plane for Claude Code — agents, skills, and a GitHub-first sprint workflow.
Context-Driven Development plugin that transforms Claude Code into a project management tool with structured workflow: Context → Spec & Plan → Implement
Use Claude Code As Is - native plugin leveraging built-in architecture
Corca Workflow Framework — consolidated hooks and skill orchestration for structured development sessions
Autonomous development methodology: PRD interviews → agent execution → automated review