Like AGENTS.md or CLAUDE.md, but for production
What is PROD.md?
Files like AGENTS.md or CLAUDE.md tell your AI how to work on code. PROD.md tells it what your product needs in production. Prodwise generates it from your repo, commits it, and keeps it up to date. It is read before changes are made, so your pro-based adaptive software can make safe updates with full context.
Written by Prodwise
We inspect your repo, ask the right questions at setup, and generate the file. You never have to write it from scratch.
Lives in your repo
It sits alongside your code like any other file. Your AI tools read it before making changes, you can read it, and it travels wherever your repo goes.
Adaptive by default
It captures goals, guardrails, and priorities so your software adapts to your real business context, not just code context.
What it looks like
This sample shows the context your adaptive software should use before any change: purpose, priorities, guardrails, and safe change rules.
PROD.md
committed to your repo by Prodwise
The other half of your project context
Files like AGENTS.md and CLAUDE.md give your tools context for code: how to run tests, what patterns to follow, what files to leave alone. When the project goes live, that context stops. There is nothing in your repo that describes the production side.
PROD.md fills that gap. It is the file your AI tools reach for when they need to understand not just your code, but your product context in production. What outcome matters right now, which flows are critical, and what tradeoffs are acceptable. It gets read before changes are made, so your assistant starts from real context instead of guessing.
Think of it alongside AGENTS.md or CLAUDE.md. One file tells your tools how to work on your code. The other tells them how your project runs. Together, they power adaptive software that can change safely as your project and users evolve.
The format is open for the same reason package.json is open. Prodwise writes and maintains it, but we do not own it. Any tool that supports the standard can read your PROD.md and use the same context.
What goes in it
Prodwise captures the context your pro-based adaptive software needs before it changes production behavior. We document your setup; we do not host your project.
Product purpose
What this project does and who it is for.
Help founders launch and run their product with less maintenance work
Current priorities
What matters most right now so changes target the right outcomes.
Improve activation, reduce drop-off in onboarding
Key user journeys
Flows that must keep working after every change.
Signup, onboarding, checkout, settings
Guardrails
Hard rules your adaptive software must not violate.
Do not break billing, auth, or existing URLs
Success signals
The metrics used to decide whether a change helped.
Activation rate, conversion, error rate
Change policy
How updates are applied safely in production.
Small batches, reversible changes, rollback triggers
Critical dependencies
External systems the project relies on in production.
Postgres, Stripe, email provider, auth provider
Secrets needed
The names of the environment variables your project requires. Values are stored separately and never committed.
- STRIPE_SECRET_KEY
Connect your repo and we will write it for you
Sign in with GitHub, choose your repo, and join early access. Prodwise generates your PROD.md during onboarding so your production context is documented from day one.
Join early access