Repository navigation
pdd 0.1.12: new command names, like the tools of a programming language. pdd test runs your Stories, pdd lint checks your files, and pdd simulate opens the PDD Simulator.
Install or update
Update pdd and the skills together. The skills now tell your agent to use pdd test and pdd workflow start, and pdd 0.1.11 and older do not know these names.
npm install -g github:promptdriven/pdd
npx skills add promptdriven/pdd#alpha -g
pdd --version # prints 0.1.12; warns when your skills are older
cd your-repo
pdd setup # updates the PDD block in AGENTS.md or CLAUDE.md one timeImportant
Do not run npm install -g pdd or npm update -g. The npm registry has a different package with the name pdd, and npm replaces this pdd with it (#2715). To update pdd, run the install line above again.
After you update, start a new agent chat, so that it loads the new skills. If you have the older Python pdd, read section 3 of docs/USAGE.md.
New names
| You want to | New command | Old command |
|---|---|---|
| run the tests of your Stories, like pytest | pdd test [STORY...] |
pdd check |
| check your prompts, Stories and tests before a real check, like a linter | pdd lint [STORY...] |
pdd check --lint |
| use your program by hand in the browser | pdd simulate STORY (short: pdd sim) |
pdd try |
| start a workflow on a GitHub issue | pdd workflow start NAME ISSUE |
pdd workflow run |
- The old commands still work. They do the same thing and print one line on stderr, for example
pdd check is now pdd test.The line never goes to stdout, so--jsonoutput andpdd mcpstay clean (#2701). - pdd now says "PDD interpreter" for the service that runs your prompts, and "PDD Simulator" for the page where you use your program. The docs say "PDD compiler" for the step where your agent writes the code. Names that programs read stay the same:
PDD_RUNTIME_URL,~/.pdd/runtime, theRuntime interfaceblock and theRuntime checkline. pdd --helpand shell completion show only the new names.- The README, the docs, the help and the error lines no longer call the product "v2" or "Alpha". The product is pdd, and the version is 0.1.12 (#2700).
Known limits
- Some lines still say "Try", for example "Try ready for …" and "This Try has ended", and the agent tools are still named
try_*. Workflow step names (check,try?) also stay. Some hints and error lines still show an old command, for examplepdd check and pdd try work in a Git repository. The old command works and prints the notice. - The older Python pdd also has a
pdd testcommand. If it comes first on your PATH,pdd testruns the Python one.pdd setupwarns when twopddcommands are on your PATH. pdd main.prompt.md(run your whole program, likepython main.py) is not in this release (#2708).
Checks
- Full test suite on the runner VM, on the release tree: 2645 of 2645 pass, 0 fail, 0 skipped, with Chrome. The GitHub check (auto-heal) passed.
- A fresh independent review of the whole release diff approved it. It ran every old command next to its new command: the output and exit codes are the same, and the old command adds only the one notice line on stderr. Every
pdd …command in the skills and docs parses with this pdd. - Fresh install from GitHub on the runner VM, in a new user home:
npm install -g github:promptdriven/pddfrom main, thenpdd --versionprints 0.1.12.npx skills add promptdriven/pdd#alpha -ginstalls the six skills at 0.1.12 (12 files). In a small sample repo:pdd setupwrites the block withpdd workflow start;pdd lintpasses with 0 AI calls;pdd testwith no Story name passes 1 of 1 Story on the PDD interpreter (2 AI calls);pdd simulateprints a Simulator link; the oldpdd try,pdd check --lintandpdd checkprint their one-line notice on stderr;pdd workflow listshows the four workflows. 12 of 12 items pass.