Verwendung
- Installationsbefehl kopieren und das Quellpaket vor der Installation in der eigenen Agentenumgebung prüfen.
- Benötigte Werkzeuge, Zugangsdaten und Hosts im Original prüfen.
- Eingabe und gewünschtes Ergebnis beschreiben und die Ausgabe mit den Quellen abgleichen.
npx skills add https://github.com/promptdriven/pdd --skill pdd-productVor dem Start
- Die Installation umfasst weder Modellabo noch API-Kontingent oder Dateizugriffsrechte.
- Sterne und Installationen zeigen Aktivität, keine unabhängige Qualitäts- oder Sicherheitsprüfung.
Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.
PDD product
Start with the person's product request. Find or make its product issue, for example gh issue create --title "Product: coffee pickup" --body "<the request>", then run pdd workflow run product ISSUE. This workflow makes and tracks the plan. Normal feature runs build the parts.
- map: steps/understand.md, steps/map.md → gate: approve
- plan: steps/parts.md, steps/contracts.md, steps/plan.md → gate: pr
Rules
- Read pdd-prompting before writing Stories or contracts (
1Story per cohesive standalone user loop). Keep one coupled slice in 1 session (0 authoring subagents) and checkpdd files+pdd lint --local; across independent decoupled modules, lock shared contracts first and parallelize independent workers. - The person approves the map, then reviews the plan PR. Never decide their open questions or approve for them. Never merge.
- Size the plan by architecture boundaries rather than fixed Story counts: for a single cohesive part, keep
product/map.mdonly and run one feature run; for multiple decoupled parts, define parts, shared contracts and planned runs; for broad cross-part rollouts, also define vertical slices where slice 1 is one thin end-to-end journey through the parts. The person can change the path. - Keep the plan in repo files. Use the file formats. A product piece is a part; an area is a workflow phase.
- Keep each planned run scoped to one cohesive part or contract boundary; warn without refusing when a planned run mixes unrelated parts.
- Parts share contracts, not code. Feature tests use the other parts as fakes from those contracts. Contract changes go through a plan PR.
- Parallel runs are optional. After the plan PR, show
pdd product nextand let the person start runs in parallel or in order. - In a run, use
pdd workflow done STEP --summary "one line"andpdd workflow ask "question". Write notes in the run folder. Keep receipts and logs outside the repo.