Browser extension PRD template

Browser extensions have a shape most PRD templates don't account for at all: no single screen, a background script that runs independently of any page, a content script that injects into whatever site the user's on, and a permissions model that determines what the browser will even let you do. Skip specifying that up front and your AI coding tool has to guess at a manifest structure it's never seen your actual use case for.

Draftlytic asks about the extension's shape directly — which browser APIs it needs, whether it injects UI into pages or runs from a popup/side panel, what data it stores locally vs. syncs — then generates a structured, editable spec with a typed data model, a feature list, and an explicit non-goals list ready for Claude Code, Cursor, or any AI coding tool.

An extension isn't one app — it's up to three surfaces working together: a background service worker, a content script running in the context of a web page, and a popup or side-panel UI the user actually clicks on. Draftlytic's spec separates these out so your AI coding tool knows which logic belongs where, instead of collapsing everything into one flat feature list.

Permissions matter more here than in almost any other app category: which browser APIs does the extension need (storage, tabs, cookies, host permissions for specific sites), and what's the minimum set that still does the job? Draftlytic captures the requested permissions as an explicit constraint, which doubles as documentation for the store-listing review most extension platforms require.

Describe your extension idea — what it does, which sites or pages it needs to interact with, and whether it needs to store data locally or sync across a user's browsers. Draftlytic's follow-up questions cover the trigger model (does it run automatically on page load, or only when the user clicks the toolbar icon), auth if it talks to a backend, and monetisation if it's not fully free.

The generated spec includes a prioritized feature list with acceptance criteria at Detailed depth, a typed data model for anything you're storing, and a non-goals list — useful for keeping a first version to 'the core content-script behaviour' instead of an AI coding tool adding a full account system you don't need yet. Export as Markdown, PDF, or Word doc, or push straight to a connected GitHub repo, and run an AI Scan to catch gaps like a feature that implies a permission you haven't listed.