A workflow for adding new behavior to a project that uses prompt-driven development. It plans the story, writes the prompt and tests first, and then builds the code in a separate step if requested.

Use it to plan a feature, write its prompt, story, and test cases, optionally design a page or screen, and then implement and verify the approved work.

It separates agreement on behavior from implementation and asks for approval at defined gates. This reduces the chance of building an unwanted feature or allowing the implementation to define the requirements.

pdd-feature — Skill for Claude Code and Codex by promptdriven/pdd

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add promptdriven/pdd --skill pdd-feature

Clone the repo

git clone --depth 1 https://github.com/promptdriven/pdd

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/promptdriven/pdd/pdd-feature/github.svg)](https://agentmods.dev/skills/promptdriven/pdd/pdd-feature)

Your own site

<a href="https://agentmods.dev/skills/promptdriven/pdd/pdd-feature"><img src="https://agentmods.dev/badge/skills/promptdriven/pdd/pdd-feature/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/promptdriven/pdd/pdd-feature"><img src="https://agentmods.dev/badge/skills/promptdriven/pdd/pdd-feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 801 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00050	$0.00801
Opus 5.5	$0.00020	$0.00320
Sonnet 5.5	$0.00010	$0.00160
Haiku 4.5	$0.00005	$0.00080

Measured today against content hash 8a7656bad8b3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pdd-feature scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/pdd-feature/SKILL.md · 31 lines

How it starts

The opening of the file, as written. The whole thing — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PDD feature

Each area is one main chat. Step briefs are in steps/. ? = optional.

story: understand, visual?, prompt-story → gate: approve
prompt-pr: check, try? → approve, then gate: pr (PR 1: prompt, Story, tests), then ask
code: build, verify, formal → gate: pr (PR 2)

Rules

The main chat coordinates and talks with the person. It does not write code.
Run each step in a new subagent, never reused, so verify never checks its own code. Give it its full brief at once: the step file and file paths, not the chat history. Then wait for it with one long time-out. Do not send small follow-up messages or use short waits.
At a gate, show the result, ask the person, and stop. For changes, revise here and ask again.
Write each link as its full URL (https://…), never as a linked word.
Before an optional step, ask the person and wait for the answer: "Do you want a visual design step? yes/no". In a run, run <pdd> workflow ask first. For a page or a screen, recommend visual: it makes the app map.
At the story gate, give the full paths of the Story files and the plan, and show the plan list. The person can say "make it one Story", "split part 5" or "change Story 5: …". A change request names a Story: redo only that Story and its test file. If a new prompt covers only this issue, say that a bigger "adopt PDD for this module" step can come later. You may offer: "You can also open it now with pdd try <story> before the check." If visual made an app map, tell the person to run pdd try <story> --new. End with: "Reply 'I approve' here or run pdd workflow approve N, or tell me what to change."
Before PR 1, show one Runtime check line per Story with its report link, and the Try links, if any. Ask the person to try it and approve, or ask for changes. pdd opens PR 1 only after the approval. Then show the PR 1 link and ask: "Do you want the code PR now, or stop here and merge PR 1 first? To make the code PR later, run pdd workflow approve N." The code area starts only when the person asks.
If verify or formal finds a failing case, go back to build in a new subagent, at most 2 times. If it still fails, PR 2 opens anyway with "✗ N vectors fail" on top. Say so at the gate.
A person decides expected values. Never change a test to make it pass.
Never push, open a PR or merge.

Read the full file on GitHub · 31 lines

Files

What ships with it

9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

today First seen · 31 lines · 50 tokens per session scan A 8a7656bad8b3

Subscribe to this mod's changes

pdd-feature is a skill published in the GitHub repository promptdriven/pdd (920 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 801 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-28.

Building agents Planning ai cli code developer-tools development methodology

pdd-feature

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

PDD feature

Rules

What ships with it

What this file has done since we first saw it

Other skills, from other repositories

sparc-methodology

logic-lens

knowledge-extension-ecosystem-lsp-code-intelligence

code-runner

github-explorer

code-review