返回资讯中心
外部精选
软件工程
#开发者实时流

Pdd-kit – Product-Driven Development for coding agents

Product-Driven Development for coding agents (OSS)

Hacker News 最新Itai-gendler2026/10/20 · 26 天前13 分钟阅读

以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。

Product-Driven Development for coding agents (OSS)

The definition of your product already exists, just unstructured, incomplete and scattered across docs, code, tickets, chats and people.

Every coding agent reconstructs it from scratch, and differently each time.

PDD gives agents and humans a shared product model that is git-tracked, reviewable, and verifiable.

The problem · The Product Model · Where it fits · Example · Get started · Development loop · FAQ

The definition of your product already exists, just unstructured, incomplete and scattered across docs, code, tickets, chats and people. Every coding agent reconstructs it from scratch, and differently each time (AI is writing code for products it doesn't understand).

Spec-driven development (SDD) tools such as OpenSpec, spec-kit and Kiro describe each change, with the product mixed into its design, plan and tasks and spread across feature folders (SDD describes the change, not the product).

Product-Driven Development (PDD) keeps the product in one place, apart from how it's built: a shared product model for agents and humans that is git-tracked, reviewable and verifiable (Introducing pdd-kit).

product-model/, a Product Model: one definition of what the product does, as plain Markdown next to the code. It is made of:

Bring knowledge from docs, designs, code, and people into one product model. Fill gaps, clarify uncertainty, and make every source leaner and more focused.

Each information source’s purpose, supported by a shared product model

Agents write code faster than anyone can explain to them what the product is. They fill the gaps by guessing, and the guesses ship.

To show what a Product Model answers, here is one for a kanban board: a conceptual product where a small team plans its work on shared boards of columns and cards, and an AI agent proposes the next cards. It is the Kanban Board Blueprint, a model with no code behind it. Every answer below is read from the model.

npx pdd-toolkit blueprint pull kanban-board npx pdd-toolkit view

  1. Entities, and which capabilities change them

All 9 entities in the kanban model: what the product keeps, and who acts on it.

Which capabilities create, change or remove each entity, filtered to the four capabilities around a proposed card:

All 23 capabilities in the kanban model: what the product lets someone do.

Which interfaces offer each capability, filtered to six card capabilities:

All 32 business rules in the kanban model: what must always hold, and who may do what.

Where each business rule is attached, filtered to the five attached to the Proposed card entity:

The Proposed card entity, one of the 9, and the information kept about it:

How it moves through its states, and the capability behind every move:

The 4 scenarios of the Card proposals capability:

One shared definition of what the product does helps everyone who works on it:

Dogfooded: pdd-kit is developed with pdd-kit. Its own Product Model lives in this repository's product-model/ folder; open it with npx pdd-toolkit view itai-gendler/pdd-kit.

🤖 Agent skills: map, ideate and verify for Claude Code, Codex, Cursor, Gemini CLI and GitHub Copilot

📝 Markdown-native: every resource is a plain .md file in your repo, reviewed in pull requests

✅ Lint and verify: npx pdd-toolkit lint checks the files; pdd-verify checks the code against them

🔁 Fits your workflow: implement with plan mode, an SDD tool or freestyle; check the code against the model when you choose

🖥️ Local report: npx pdd-toolkit view opens the model in your browser and follows your edits

📦 Blueprints: start from a reviewed model for a common product instead of a blank page

🔒 Local-first: no account, no hosted service; the skills read your code and never run it

npx pdd-toolkit install

The npm package is pdd-toolkit; it installs the pdd-kit command, so after npm install --global pdd-toolkit you can run pdd-kit install instead.

This adds the skills to the coding agents it detects (Claude Code, Codex, Cursor, Gemini CLI or GitHub Copilot), or to Claude Code and Codex when it detects none; you can change the selection. Then start from where you are, inside your agent (Codex uses $ instead of /):

/pdd-map

It reads the code without running it, asks what the code can't answer, and writes product-model/ once you approve. Then open the report:

No code yet? Describe the product you want:

/pdd-ideate I want to build a booking app for dog walkers

You pick from a few product shapes, then approve the model. From an idea

A familiar kind of product? List the reviewed models and pull one:

npx pdd-toolkit blueprint list npx pdd-toolkit blueprint pull <name>

Browse the Blueprints · From a Blueprint

Optionally, let pdd-kit orchestrate the implementation and verification loop: verify plans the work in phases, your agent implements each phase, and verify checks it before the next. Turn it on with npx pdd-toolkit install --orchestrate=on or one sentence in your AGENTS.md; see Implement with verify.

install, update, lint, view and the blueprint commands. Every command and option: CLI reference, or npx pdd-toolkit --help.

Read the frequently asked questions about adopting pdd-kit, what the Product Model covers, and getting help.

pdd-kit is released under the MIT License: do anything, just give credit. See LICENSE.

正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。

打开原文
去社区讨论 →