pdd
starsforks
How to install pdd?
promptdriven/pdd
$git clone https://github.com/promptdriven/pddPDD (Prompt-Driven Development) is a prompt-native programming system. .prompt files are the human-authored source language; Python, TypeScript, Go, and other traditional languages are generated artifacts.
README.md
| 1 | # PDD: The Last Programming Language™ |
| 2 | |
| 3 |  [](https://discord.gg/Yp4RTh8bG7) |
| 4 | |
| 5 | ## Introduction |
| 6 | |
| 7 | PDD (Prompt-Driven Development) is a prompt-native programming system. `.prompt` |
| 8 | files are the human-authored source language; Python, TypeScript, Go, and other |
| 9 | traditional languages are generated artifacts. |
| 10 | |
| 11 | PDD is the last programming language in this specific sense: developers author |
| 12 | durable intent, constraints, examples, and tests, then compile that source into |
| 13 | whatever implementation language the project needs. Code remains real and |
| 14 | reviewable, but it is no longer the primary source of truth. |
| 15 | |
| 16 | **Getting started is simple:** |
| 17 | |
| 18 | ```bash |
| 19 | # Install and run |
| 20 | uv tool install pdd-cli |
| 21 | pdd setup |
| 22 | pdd connect |
| 23 | ``` |
| 24 | |
| 25 | This launches a web interface at `localhost:9876` where you can: |
| 26 | - Implement GitHub issues automatically |
| 27 | - Generate and test code from prompts |
| 28 | - Manage your PDD projects visually |
| 29 | |
| 30 | <p align="center"> |
| 31 | <img src="docs/videos/handpaint_demo.gif" alt="PDD Handpaint Demo" /> |
| 32 | </p> |
| 33 | |
| 34 | For CLI users, PDD also offers powerful **agentic commands** that implement GitHub issues automatically: |
| 35 | - `pdd change <issue-url>` - Implement feature requests (13-step workflow) |
| 36 | - `pdd bug <issue-url>` - Create failing tests for bugs |
| 37 | - `pdd fix <issue-url>` - Fix the failing tests |
| 38 | - `pdd split <target-file>` - Diagnose and split large dev units (15-step workflow with intent classification, diagnosis, phase extraction, per-child verify gate, and repair) |
| 39 | - `pdd generate <issue-url>` - Generate architecture.json from a PRD issue (11-step workflow) |
| 40 | - `pdd test <issue-url>` - Generate UI tests from issue descriptions (18-step workflow with exploratory testing, contract validation, accessibility audits) |
| 41 | |
| 42 | Choose `pdd bug` before `pdd change` when an issue reports a current runtime |
| 43 | symptom, even if it says the prompt or spec should be updated. Stack traces, |
| 44 | failing commands, wrong CLI/API/UI output, regressions, crashes, and incorrect |
| 45 | generated behavior should run through `pdd bug <issue-url>` followed by |
| 46 | `pdd fix <issue-url>` (`bug → fix`) so the failure is reproduced and covered by |
| 47 | a behavioral test. Use `pdd change` for explicit source-truth/spec/product |
| 48 | changes with no current runtime failure to reproduce (`change → sync` after |
| 49 | the source-truth change lands). |
| 50 | |
| 51 | For prompt-based workflows, the **`sync`** command automates the complete development cycle with intelligent decision-making, real-time visual feedback, and sophisticated state management. |
| 52 | |
| 53 | ## Whitepaper |
| 54 | |
| 55 | For the positioning essay behind this shift, read [The Last Programming Language](docs/the-last-programming-language.md). |
| 56 | |
| 57 | For a detailed explanation of the concepts, architecture, and benefits of Prompt-Driven Development, please refer to our full whitepaper. This document provides an in-depth look at the PDD philosophy, its advantages over traditional development, and includes benchmarks and case studies. |
| 58 | |
| 59 | [Read the Full Whitepaper with Benchmarks](docs/whitepaper_with_benchmarks/whitepaper_w_benchmarks.md) |
| 60 | |
| 61 | For a case study on specification drift in AI-assisted coding workflows, read [Why AI Code Falls Apart](docs/whitepaper_specification_drift/whitepaper.md). |
| 62 | |
| 63 | Also see the Prompt‑Driven Development Doctrine for core principles and practices: [docs/prompt-driven-development-doctrine.md](docs/prompt-driven-development-doctrine.md) |
| 64 | |
| 65 | For a step-by-step methodology on turning a GitHub issue into a durable, human-verified user story, see [docs/generating_user_stories.md](docs/generating_user_stories.md). |
| 66 | |
| 67 | For pre-merge prompt and user-story quality (vague terms, vocabulary, optional LLM review), see [docs/prompt_lint.md](docs/prompt_lint.md). |
| 68 | |
| 69 | For deterministic contract-section lint (`<contract_rules>`, `<coverage>`, waivers, story `## Covers`), see [docs/contract_check.md](docs/contract_check.md). |
| 70 | |
| 71 | For a rule-to-story/test coverage matrix (`pdd checkup co |
People who liked this also viewed
6 picksType
- components-helperBased on the docs to provide code prompt files for vue component libraryPromptsNov 2023
- VibeCode-Protocol-SuiteA comprehensive suite of protocols, meta-prompts, and orchestration tools designed to streamline software development workflows, project management, and team collaboration. Includes the VibeCode Protocol Suite with web interface, user manuals, and reusable templates for efficient development processes.PromptsJul 2026
- Promptable-web-sdkWeb SDK for Promptable Website.PromptsDec 2022
- LLMFlexA python package for developing AI applications with local LLMs.PromptsJan 2025
- cli-repo-to-promptexport any codebase to a single LLM-ready markdown promptPromptsJul 2026
- Files2PromptVS Code extension to copy files for an LLM promptPromptsApr 2025
