Split a big goal into briefs for separate chats
Breaks a project too large for one conversation into self-contained work packages, each written so you can paste it into a fresh chat.
You get: A dependency map, the order to run things in, where pieces will clash, and a checklist for joining the results.
I have a goal that is too big for one chat: [describe the goal, the deadline and what done looks like]. Act as a project lead. First ask me up to 5 questions about anything unclear. Then: 1. Split the work into 4 to 8 packages that can each be finished in one separate chat. 2. Draw a simple dependency map: which packages must come first, which can run side by side. 3. Point out where two packages are likely to collide, such as shared names, files, numbers or assumptions, and say how to keep them consistent. 4. For each package, write a brief I can paste into a new chat: the goal, the context it needs, the inputs, the exact output format and how to check it is right. 5. End with a short checklist for stitching the results together.