Help CenterSituationsI want to take over an old project, and have a session read the code and report back first
I want to take over an old project, and have a session read the code and report back first
Situations

I want to take over an old project, and have a session read the code and report back first

Each situation has three parts: what to tell Q, what happens, and what you need to do. The wording is only an example; say it in your own words.

What to tell Q

What to say

"I've just taken over this project. Don't change any code yet. Read through it and tell me: what it does, how to get it running, what its main parts are, and where it's messiest."

What happens

  • Q creates a research only task: no code changes; it reads in the project's original folder and hands in a written conclusion.
  • The session reads it, writes the conclusion, and hands it to you.

What you need to do

  1. Read the conclusion, and keep asking about anything unclear.
  2. Have the session register "how to get it running" as the dev build command; it'll come in handy from then on.
  3. For conventions worth keeping, have Q note them down (like "this project always uses dayjs for dates"), and sessions will take them along when they start. You can also write them into the repo's AGENTS.md (see Memory).