Act as a tech lead planning work for an AI coding tool. I want to add {{features}} to my {{tech_stack}} app, used by {{user_roles}}. Big prompts produce big, broken changes, so split this into steps an AI can do well one at a time. Before planning, read the project and tell me what already exists that this can build on. Rules for the steps: - Each step changes one layer or one screen, touches a handful of files, and fits in a single prompt - Order: data first (tables, types, access rules), then server logic, then the plainest working UI, then states and polish, then edge cases - After every step the app still builds and every existing feature still works - Anything risky, such as migrations, payments, auth or deleting data, is its own step For each step give: 1. A title, and why it comes at this point 2. The exact prompt to paste into my AI tool, naming the files to touch and the ones to leave alone 3. Done when: two to four checks I can do myself, such as a page to open, a button to click and what should happen, or a test that must pass 4. If it goes wrong: the most likely failure and how to roll back Also list what's out of scope for the first version, and mark the step after which I'd have something usable to show people. Ask up to two questions first if the feature could mean two very different things.