Mode d’emploi
- Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
- Consultez le document original pour les outils, identifiants et environnements requis.
- Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/promptdriven/pdd --skill pdd-setupAvant de commencer
- L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
- Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.
PDD setup
Add one short PDD block to the file that this repo's agents read, and keep .pdd/ out of Git. This skill installs nothing: if you can read it, the PDD skills are already installed. The pdd setup command checks for a ready agent, does the same in the current folder, installs missing skills and updates eligible marked copies, then previews MCP changes for approval.
The bundled skills also include pdd-product, pdd-graph and pdd-setup. Bundled workflow names also include product.
- Pick the file:
CLAUDE.mdif it exists, elseAGENTS.md. If neither exists, createAGENTS.md. Use the repo root. - Write this block exactly. Leave out the RUNBOOK.md line if the pdd-prompting skill has no RUNBOOK.md.
- If the file already has a
<!-- pdd:start -->…<!-- pdd:end -->block, replace only that block. Otherwise add the block at the end, after one empty line. Keep all other text. - If the block is already the same, change nothing. If only one marker is there, stop and ask the person.
- In a Git repo, add the line
.pdd/at the end of the root.gitignoreif no line there is.pdd,.pdd/,/.pddor/.pdd/(no space at the start). Create the file if needed. Keep all other bytes. If the last such line starts with!, or there is no such line but a line starts with!.pddor!/.pdd(for example!.pdd/config.json), change nothing and tell the person.pdd testkeeps its local cache in.pdd/.
<!-- pdd:start -->
## PDD
This project uses PDD. Change the prompt that owns a file before the file. New code starts with its prompt. Files that no prompt owns change directly, with a test when behavior changes.
Skills: pdd-prompting (the Prompting guide), pdd-feature, pdd-bug, pdd-small-change, pdd-product, pdd-setup and pdd-graph. Call one with `$pdd-feature` in Codex or `/pdd-feature` in Claude Code, or just ask for it by name.
Full run with PRs: `pdd workflow run NAME ISSUE` (NAME: feature, bug, small-change, product or your own workflow).
Before you write prompts or tests, read RUNBOOK.md in the pdd-prompting skill.
<!-- pdd:end -->Never paste the guide or a workflow into the file. Show the person the diff.