Plan your app and give your agent a clear brief

Your outcome

Write a brief another person can implement and test. Our example is a solo maker who needs to save a task and find it after refreshing the same browser. It starts without accounts, a database server, or deployment.

Start here

Have a project folder and a coding agent with access to its files. A text editor is optional if you want to review or adjust the brief manually. If you need setup, choose an agent. Download the task tracker and planning materials, extract it, and read examples/task-tracker/brief.md. The blank files are in learning/resources/app-delivery/ inside the same archive.

Use App and workspace blueprint for the brief and acceptance record. Plan an app guides the decision-making; it does not choose a stack on your behalf.

1. Name the user and complete journey

Write: "A solo maker adds a task and finds it again after refresh." The journey is empty list -> enter title -> Add task -> see saved task -> refresh -> see that same task once. A list that only looks populated is not the completed journey.

The first screen needs an input, Add button, list, empty message, success status, and failure message. The record has a unique id and a trimmed title of 1-120 characters. Browser localStorage is sufficient for this exercise's same-browser requirement; it does not synchronize accounts or devices.

2. Bound the first increment

The filled brief separates the first create-and-refresh slice from later editing and deletion. Do not add notifications, billing, teams, or AI generation to explain saving a task. The supplied example also includes the later edit/delete increment so the can verify it explicitly.