Skip to content

Lesson 4.3 · 3:59

The project brief file

Goal: Put who the app is for, what it does and what "done" means in one file that every session can read.

Try it

  1. In your Module 3 app folder, create PROJECT-BRIEF.md. You can ask OpenCode to create the empty file with the headings above, but you fill in the answers.
  2. Fill in user, problem, outcome and main action.
  3. Paste in your three checks from 4.2.
  4. Write at least one "out of scope" and one "don't change".
  5. Open a new OpenCode session and type: "Read PROJECT-BRIEF.md and tell me in two sentences what this app is for and what I must not change."

You're done when the fresh session's two-sentence summary matches what you meant. If it doesn't, fix the brief (not the prompt) and ask again. Make a save point.

Recap

  • New sessions start blank. The brief is the memory that lives in a file.
  • Keep it to half a page: user, problem, outcome, checks, boundaries.
  • Start prompts with "Read PROJECT-BRIEF.md first", and update the brief when you decide something new.

Next lesson (4.4): what to do when a session's desk fills up: handoffs.