pdd-kit agent skills
pdd-kit installs exactly three skills:
| Skill | Use it when | Writes |
|---|---|---|
pdd-map | Existing behavior needs an initial model, scoped remap, or coverage expansion | Approved model meaning inside product-model/ |
pdd-ideate | You are deciding what the product should do | Approved model meaning inside product-model/ |
pdd-verify | You ask to implement the model, or need branch, named, or current-state model/code alignment | Nothing during classification; approved resolution and optional Reference bookkeeping. Code is written by your agent |
Map and ideate answer opposite questions: “what already exists?” and “what should exist?” Verify owns the loop between those authorities after code moves.
You don't have to name a skill: ask your agent to change the product or to implement it, and it picks the right one. The three installed skills are self-contained, and none of them writes code: when you ask to implement, verify has your own agent implement the work in phases, your usual way, and checks each part. See the development loop.
Blueprint contribution is a deterministic CLI workflow:
npx @itai-gendler/pdd-kit blueprint contribute
Claude Code uses /pdd-map; Codex commonly uses $pdd-map.
See Installation for provider paths.