https://github.com/arch-team/devpace
BizDevOps rhythm manager for Claude Code β trace business goals to code changes with 18 skills
https://github.com/arch-team/devpace
ai-coding ai-development bizdevops change-management claude-code claude-code-plugin devops plugin project-management quality-gates
Last synced: 25 days ago
JSON representation
BizDevOps rhythm manager for Claude Code β trace business goals to code changes with 18 skills
- Host: GitHub
- URL: https://github.com/arch-team/devpace
- Owner: arch-team
- License: mit
- Created: 2026-02-20T13:35:09.000Z (2 months ago)
- Default Branch: main
- Last Pushed: 2026-03-22T16:53:22.000Z (about 1 month ago)
- Last Synced: 2026-03-22T23:51:32.228Z (about 1 month ago)
- Topics: ai-coding, ai-development, bizdevops, change-management, claude-code, claude-code-plugin, devops, plugin, project-management, quality-gates
- Language: Python
- Size: 3.09 MB
- Stars: 42
- Watchers: 0
- Forks: 2
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
- Codeowners: .github/CODEOWNERS
- Security: SECURITY.md
Awesome Lists containing this project
README
π [δΈζη](README_zh.md) | 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.
  
## 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](examples/todo-app-walkthrough.md)
## 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:
1. **Goal alignment** β Every code change links back to a business goal. No work without purpose.
2. **Auto quality gates** β Claude auto-checks code quality and requirement consistency, self-repairs on failure. Human approval cannot be skipped.
3. **Change is normal** β Requirements changed? Auto impact analysis, orderly adjustment, existing work preserved.
4. **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](https://claude.ai/code) must be installed.
### Marketplace Install (Recommended)
```bash
# Step 1: Register marketplace (one-time)
/plugin marketplace add arch-team/devpace-marketplace
# Step 2: Install
/plugin install devpace@devpace
```
### From Source
```bash
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](docs/user-guide.md) 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)
| Capability | Description |
|-----------|-------------|
| Requirement changes | Add features, pause, change scope β auto impact analysis, orderly adjustment, Claude won't change the plan unilaterally |
| Complexity awareness | Auto-assesses task complexity, small changes fast-track, large changes full process, complexity drift auto-detected |
| Technical debt management | `tech-debt` CR type + iteration capacity reservation + trend tracking |
| Architecture decisions | `/pace-trace arch` manages cross-CR Architecture Decision Records (ADR) |
### Quality & Traceability
| Capability | Description |
|-----------|-------------|
| Quality gates | Code quality + requirement consistency auto-check + adversarial review, human approval cannot be skipped |
| Goal traceability | From business goals to code changes, always traceable |
| Test verification | Requirements-driven β strategy generation, coverage analysis, AI acceptance verification, change impact regression |
| Semantic drift detection | Continuous monitoring of code-requirement alignment during development, Review includes semantic consistency score |
### Development Rhythm
| Capability | Description |
|-----------|-------------|
| Cross-session restore | Session interrupted? Auto-resume, zero re-explanation, experience persists across sessions |
| Iteration management | Plan β Execute β Review full cycle, auto-recommends next step |
| Progressive autonomy | Assisted / Standard / Autonomous β more guidance for new users, less for experienced ones |
| DORA proxy metrics | Deploy frequency / Lead time / Failure rate / MTTR proxy values, Elite~Low benchmarks + trend comparison |
| CI/CD awareness | Auto-detects CI tool type, Gate 4 auto-queries CI status, zero config |
| Risk fabric | OWASP-aware security scanning + Pre-flight 5-dimension risk scan + Runtime monitoring + Graduated autonomous response (High requires human confirmation) |
| Delivery prediction | AI-powered iteration delivery probability forecasting, bottleneck identification, and risk early warning |
| Cross-project insights | High-confidence insights exportable/importable to other projects, reducing redundant learning |
## Workflow
### Two Modes
- **Explore mode** (default): Freely read code, analyze problems, discuss approaches. No process triggered.
- **Advance mode** (when changing code): Auto-creates tasks, tracks progress, checks quality. Small changes fast-track, large changes full process.
When unsure, Claude asks: "Ready to start coding, or just exploring?"
### Workflow
```
Normal flow:
Start βββ In Progress βββ Pending Review βββ Done
β β
Auto quality check You approve Auto merge + status update
(Claude handles) (you decide)
Anytime:
Requirements changed βββ Impact analysis βββ Adjust plan βββ Continue
Session interrupted βββ Next session auto-resumes from where you left off
Full cycle (optional):
Plan (pace-plan) β Build (pace-dev) β Review (pace-retro) β Next cycle
```
## Design Principles
| Principle | Meaning |
|-----------|---------|
| Zero friction | Natural language works, no jargon to learn |
| Progressive disclosure | Default 1-line output, details on demand |
| Byproducts not prerequisites | Structured data is auto-produced from work, not a required input |
| Interruption tolerance | Interrupt at any point, seamless resume next time |
## vs Alternatives
| Dimension | GitHub Issues / Manual | devpace |
|-----------|----------------------|---------|
| Core model | Task list | Goal β Feature β Code Change traceability |
| Requirement changes | Manual impact assessment | Auto impact analysis + orderly adjustment |
| Claude's role | Executor (you direct each step) | Autonomous collaborator (auto-advances, self-checks, waits for your decisions) |
| Traceability | Task β Code | Business Goal β Feature β Change β Code |
| Metrics | Completion count | Quality pass rate + value alignment + DORA proxies |
## What devpace is NOT
- **Not a CI/CD pipeline** β it works alongside your existing tools (GitHub Actions, Jenkins, etc.)
- **Not a project management platform** β no web dashboard, no team features, pure CLI
- **Not a replacement for git** β it creates Markdown state files in `.devpace/`, your code stays in git
## Feedback
Tried devpace? [Tell us what you think](https://github.com/arch-team/devpace/issues/3) β one word or a full report, everything helps.
## Learn More
- [User Guide](docs/user-guide.md) β Full command reference, modes, state machine details ([δΈζ](docs/user-guide_zh.md))
- [Walkthrough](examples/todo-app-walkthrough.md) β Complete example from init to finish ([δΈζ](examples/todo-app-walkthrough_zh.md))
- [Contributing](CONTRIBUTING.md) β Dev environment, testing, PR process
- [Changelog](CHANGELOG.md) β Version history ([English summaries on GitHub Releases](https://github.com/arch-team/devpace/releases))
- [Troubleshooting](https://github.com/arch-team/devpace/issues?q=label%3Abug) β Search known issues or open a new one
---
MIT