Progressive Change-Driven Development
Ship with AI agents.Without losingthe plot.
PCDD gives every change just enough process: a spec when it matters, a record that outlives the session, and a finish line you approve.
$ curl -fsSL https://pcdd.dev/install.sh | shor uv tool install pcdd · pipx install pcdd · Python 3.9+, zero dependencies
$ pcdd init ›_ pcdd · each change, just enough. PCDD is ready. Create .pcdd/core.md Create AGENTS.md Create CLAUDE.md Your own content is preserved. $ pcdd new rate-limit Change created: pcdd/changes/rate-limit.md Define specs before implementing. $ pcdd time status rate-limit 2/3 tasks completed · 2880 s recorded
Other agents that read AGENTS.md can follow the core — not tested yet.
The problem
AI coding fails in two opposite ways.
Most teams swing between them. One fix gets a ten-page spec; the next risky migration gets a prompt and a prayer.
Fast today. Lost tomorrow.
- A new session forgets what was decided and why.
- “Done” means it compiled, not that it works.
- Risky changes get the same treatment as typos.
Safe on paper. Skipped in practice.
- A full spec for a one-line fix.
- Ceremony burns context, tokens and patience.
- So people stop following it — even when it matters.
Process proportional to risk.
- Small, clear work goes straight through.
- Substantial work gets approved specs and a record.
- Risky work gets independent review before commit.
Why it matters
Thursday morning.
New session.
You started a feature on Monday. Same request, same agent — the only difference is what it can read.
You re-explain. You find the bug later.
make ready). It’s done when you accept it — here’s how to check.It reads the record. You decide when it’s done.
How it works
Pick a change. Watch the process fit.
The agent assesses risk on its own terms, not by line count. Size alone never decides.
- Read context
- Approved specs (skipped)
- Tasks (skipped)
- Implement
- Checks
- Evidence (skipped)
- Independent review (skipped)
- Your acceptance
Fix a typo in the docs: Straight through.
Well-understood and bounded. The agent reads just enough context, makes the change and runs the checks. The diff is the record — no change document, no ceremony.
- Read context
- Approved specs
- Tasks
- Implement
- Checks
- Evidence
- Independent review (skipped)
- Your acceptance
Add rate limiting to login: Define, then build.
The agent proposes verifiable specs and waits for your approval. Tasks, test results and the next step are written to pcdd/changes/rate-limit.md, so any session can pick it up.
- Read context
- Approved specs
- Tasks
- Implement
- Checks
- Evidence
- Independent review
- Your acceptance
Migrate auth to a new provider: Review before commit.
Irreversible effects and security on the line. After the gate passes, an independent review verifies the work, and you approve from a summary you can actually understand.
Continuity
Close the laptop.
Keep the context.
Every substantial change lives in one Markdown file in your repo: specs, tasks, evidence and the exact next step. A fresh session — or a different agent — reads that, not your entire history.
Small starting context. Skills load only when needed. No external memory service.
## Specs S1 — Limit login attempts per IP. Approved. ## Tasks - [x] T1 (S1) Write the failing test - [x] T2 (S1) Implement the limiter - [ ] T3 (S1) Verify and accept ## Continuation Next step: user tests lockout after 5 attempts.
Get started
Three steps.
Nothing new to learn.
No new app, no account, no config to write. You keep using your agent the way you already do.
- 1
Install once
$ curl -fsSL https://pcdd.dev/install.sh | shOne line. Installs uv if it’s missing. Python 3.9+, zero runtime dependencies.
- 2
Add it to your project
$ pcdd initPreview first with
--dry-run. Your own content is preserved, andpcdd rollbackundoes it. - 3
Just describe the change
“Add rate limiting to the login endpoint.”Open Codex, Claude Code or Antigravity. The agent picks the right amount of process and asks only what it needs.
You stay in charge
The agent proposes.
You decide.
You approve the specs
Verifiable criteria, with your words quoted, before any code is written.
Evidence, not vibes
Test-first when the result is clear; otherwise the record says what remains unverified.
No surprise commits
Commits, pushes and publishing need your explicit go-ahead. No AI attribution added.
Yours, locally
Plain Markdown in your repo. Preview, update and roll back installs. No service, no lock-in.
Compare
Not the lightest.
The one that fits.
Same change, three approaches. See how much process each one asks for.
Fix a typo in the docs
- Spec
- Plan
- Implement
- Checks
- Implement
- Checks
- Implement
- Checks
- Your acceptance
Spec-first workflows pay full ceremony for a one-line change. PCDD goes straight through — and you still check the result.
Shapes follow each approach’s organizing idea; real implementations vary. We haven’t measured time or tokens yet — when we do, we’ll publish the method with the numbers.
Add rate limiting to login
- Spec
- Plan
- Tasks
- Implement
- Checks
- Context notes
- Implement
- Checks
- Approved specs
- Tasks
- Implement
- Checks
- Change record
- Your acceptance
Here PCDD looks like SDD — plus a change record any session or agent can resume, and your sign-off at the end.
Shapes follow each approach’s organizing idea; real implementations vary. We haven’t measured time or tokens yet — when we do, we’ll publish the method with the numbers.
Migrate auth to a new provider
- Spec
- Plan
- Tasks
- Implement
- Checks
- Context notes
- Implement
- Checks
- Approved specs
- Tasks
- Implement
- Checks
- Change record
- Independent review
- Your acceptance
When security and irreversible effects are on the line, PCDD adds an independent review after the gate, before anything is committed.
Shapes follow each approach’s organizing idea; real implementations vary. We haven’t measured time or tokens yet — when we do, we’ll publish the method with the numbers.
Each change,
just enough process.
Install in one line. Try it on your next change.
$ curl -fsSL https://pcdd.dev/install.sh | sh