What happens in the room, in sequence. This is a working session. The output is a project brief your cohort actually owns.
Before anything else, confirm that everyone can access the Claude Teams environment. If anyone is blocked, get them in before moving to the project work. A participant who cannot access the shared workspace cannot meaningfully participate in the build.
Your access email is firstname@jayfontanini.com. If you have not yet set up that account, go to accounts.google.com, sign in with that address, set a new password, and accept the Claude Teams invitation from your inbox.
Once you are in, you should see a shared team project in the left sidebar. That is where the cohort's work will live through Modules 7 and 8.
Your cohort should arrive with a project direction already forming from the email thread. This block is not a fresh pitch session - it is a chance to confirm the direction out loud, make sure everyone is aligned, and surface any reservations before the group commits and starts building.
One person states the direction in two sentences. The group confirms or adjusts. If there is still genuine disagreement about which project to pursue, spend five minutes on it and make a decision. The session cannot produce a useful project brief if the first half is spent relitigating project selection.
With the project selected, the group defines the scope together. This is the most important part of the session. A well-scoped project produces a working demo in two weeks. A poorly scoped one produces a frustrating partial build.
The scope question to press hardest: if you only had two working sessions to build this, what is the one thing the system must do to be worth presenting? That is your scope.
With scope defined, the group designs the approach. Use the patterns from Module 6 as the vocabulary. Which pattern fits this problem? Where does the human stay in the loop? What does a working prototype actually need to include?
Refer to the Advisor OS: Agentic Email Processing page as a reference model. It shows what a fully designed system looks like - config file, worker agents, human checkpoint, build sequence. Your system does not need to be that complex. But that page illustrates the design decisions you are working through right now.
Every project needs owners, not participants. The group assigns roles before the session ends. Roles do not need to be permanent - people will naturally shift as the build evolves - but someone needs to own each piece going into Module 8.
One person can hold more than one role in a small group. What matters is that every role is claimed and every person knows what they own going into Module 8.
Open Claude Teams and start the project brief in the shared project. Use the session you just had as the input. The goal is not a finished document - it is a working draft that captures what the group agreed on so that the asynchronous work between now and Module 8 has a foundation.
Ask Claude to help you draft it. Give it the decisions you made in this session and ask it to produce a project brief in a format the group could share and iterate on. Then edit it together until it sounds like your cohort, not like an AI summary.
Three things need to be true before you end the session. The group has selected a project and defined the scope. Every role is assigned. The project brief draft is in Claude Teams and everyone can see it.
If those three things are done, Module 8 can be a build session. If they are not, Module 8 becomes another planning session, and there will not be enough time to present something working at the capstone.