Start from a Blueprint

Use this door when your product is a familiar kind (a webshop, a booking app, a help desk) and you would rather adapt a reviewed model than write one from nothing.

What a Blueprint is

A Blueprint is a reviewed Product Model for a common kind of product, published in the pdd-kit repository, that you pull instead of starting blank. It holds only product meaning: no code, no file paths, nothing tied to the repository it came from.

Its life in one line: someone exports a model and contributes it, merging its pull request publishes it, and you pull it by name, or open a Blueprint file you were given.

Steps

1. Find one with npx @itai-gendler/pdd-kit blueprint list, or browse blueprints/ on GitHub. Create the project, install the skills into it, and pull the Blueprint by name:

   mkdir my-product && cd my-product
   git init
   npx @itai-gendler/pdd-kit install
   npx @itai-gendler/pdd-kit blueprint pull kanban-board
   

   
   It writes only product-model/; nothing else in the repo changes.
2. Read the Product (product-model/product/product.md, or product.md when the Blueprint has no logo), then skim the rest with:

   npx @itai-gendler/pdd-kit view
   

3. If you want something more or different, ask your agent for the change, such as "add guest checkout to the product", and approve it first.
4. Ask your agent to implement it: "implement our PDD". Verify plans the work in phases: your agent implements each phase your usual way, and verify checks it before the next. Say "in one go" to skip phases, or "one slice at a time" to go slower; see Choose the pace. Ask your agent to check the code against the model whenever you want to be sure, or run /pdd-verify by name.