# A PRD is not enough anymore: what an AI coding agent actually needs to build your app > Source: > Published: 2026-11-15 04:39:08+00:00 A product requirements document used to be the end of the specification. You wrote what the app should do, handed it to a developer, and the developer filled in the rest — the tables, the endpoints, the edge cases — with judgement. An AI coding agent does not fill in the rest with judgement. It fills it in with guesses. And guesses, repeated across a whole codebase, are how you end up with a database that does not match the document, an API payload that changes shape twice in one week, and no security rules anywhere. That is not a complaint about the agent. The agent did exactly what it was told. The document never actually decided those things. When a human reads "users belong to organisations", they know what that means for the database, the API, and the permissions. When an agent reads it, it has to invent a table name, a foreign key, a query pattern, and an authorisation check — and it will invent a different one in each file if nothing pins it down. This is why I stopped treating the PRD as the deliverable and started treating it as one part of a suite. The tool I built, Web Dev Mehedi, takes one product idea and generates four files that agree with each other, in under 60 seconds: Nothing in that list is exotic. It is just the set of decisions a senior engineer would have made anyway — written down before the code exists, instead of discovered afterwards. **Multi-tenancy has to be in the schema on day one.** If the RLS policy is written in the same step as the table, the agent never gets a chance to build an unprotected version first and bolt security on later. Security that arrives later arrives incomplete. **Agents follow rigid rules surprisingly well.** Most of the "hallucinations" I saw were vagueness failures, not capability failures. The spec never actually decided the thing the agent got wrong — so the agent decided it, plausibly, and wrongly. **Specification is the new bottleneck.** Writing code got cheap. Deciding exactly what to build — tables, payloads, permissions, states — is now the expensive part, and it is the part most teams still do in prose. Web Dev Mehedi is built in Bangladesh and priced in Taka — from ৳99/month, paid with bKash or Nagad, with 50 free credits on signup and no card required. That is a deliberate choice: the developers and founders I am building for pay for everything with mobile money, and they get skipped by almost every tool in this category, which assumes a dollar card. If you build with AI coding agents, try generating the full suite for your next idea and hand the agent all four files instead of just the PRD: [https://webdevmehedi.com/ai-prd-generator](https://webdevmehedi.com/ai-prd-generator) The free template behind the format is on GitHub if you want to use the structure without the generator: [https://github.com/web-dev-mehedi/ai-prd-template](https://github.com/web-dev-mehedi/ai-prd-template) What do you hand your coding agent before a build — and what does it still get wrong?