pdd-kit install
Install the three pdd-* agent skills into your AI harnesses, once per
project or once for your user, before you map, ideate or verify.
npx @itai-gendler/pdd-kit install [--providers <list>] [--scope project|global] [--yes] [--force]
Options
| Option | Meaning |
|---|---|
--providers <list> | Comma-separated harnesses: claude,codex,cursor,gemini,github |
--scope project|global | Install into the current project or your user configuration |
--yes | Take the defaults for anything not given: detected harnesses (Claude Code and Codex when none are detected) and project scope |
--force | Replace a colliding pdd-* skill directory that pdd-kit does not own |
Without a terminal (in CI, for example), pass --providers and --scope, or
--yes to take the defaults:
npx @itai-gendler/pdd-kit install --providers claude,codex --scope project
See Installation for each harness's directories and how to choose a scope.
What it does
- Detects which harnesses you use. Interactively, you keep that selection or customize it, then choose project or global scope.
- Checks every selected skills directory before writing to any of them.
- Writes the three skills, removing any
pdd-*skill an earlier install recorded that this release no longer ships. - Writes
.pdd-kit-install.jsonin each skills directory, recording the harness, scope, version and skill names, soupdatecan find it later.
It installs skills only: no product-model/, no hooks, no account.
Safety
The marker is the only proof of ownership. A pdd-* directory the
marker does not list is someone else's, so it stops the run unless you pass
--force.
A refusal changes nothing. Every harness is checked before any is written, and the message names the directory that blocked the run.
Exits 0 when the skills are installed, 1 when a collision, a missing terminal or a cancelled prompt stops it, and 2 for an unknown harness, scope or option.
Next
pdd-mapfor established code,pdd-ideatefor a new product, orpdd-verifyfor an existing model.updateafter upgrading the package.