# PRODUCT.md

> The open standard for describing a product in one Markdown file — who it is for, how it speaks, and what it costs — readable by humans, coding agents, and buying agents. The same file lives at `./PRODUCT.md` at build time and at `https://yourdomain/product.md` at sell time.

A repo has three readers now: the engineer reads the README, the coding agent reads AGENTS.md, and the buying agent arrives with a job and a budget and — until PRODUCT.md — had nothing written for it. Headings are the schema; there are zero required fields. A fenced `json product.md#pricing` block is a machine island: typed pricing an agent-commerce flow can quote instead of guessing from a screenshot.

## The standard

- [Specification (one page)](https://product.md/): layers, canonical sections, machine islands, and the three conformance levels — the whole spec on a single page.
- [PRODUCT.md, published](https://product.md/product.md): this site's own PRODUCT.md — the file the standard describes, served as Markdown.
- [Capability card](https://product.md/.well-known/agents.json): what this surface is and how to consume it.
- [Reader classification](https://product.md/icp.json): who PRODUCT.md is for, so an agent can self-classify.

## Get the file

- `npx productmd init` — interview-driven bootstrap, then `npx productmd check` to verify Level 2.
- `/impeccable init` — impeccable has written this file since v1; if you use it, yours already exists.

## Related standards

- [AGENTS.md](https://agents.md): build conventions for coding agents; PRODUCT.md sits beside it at the repo root.
- [llms.txt](https://llmstxt.org): the convention this file follows.
- [MDXLD](https://mdxld.org): the optional linked-data frontmatter layer (`$id`, `$type`, `$context`).