You discussed candidate problems in this session. Now do the preparation work that turns a good idea into a project your cohort can actually execute.
Module 7 is a working session. Your cohort will select one project, produce a project brief, and assign roles. The quality of that hour depends entirely on the preparation you do this week. Show up ready to work, not ready to brainstorm.
You surfaced candidate problems during this session. Between now and Module 7, refine yours. Write it as one clear sentence: the problem, who it affects, and why it matters. If your idea shifted during the group discussion, follow the better version.
Test it against this filter: is the problem specific enough to scope in two sessions, but general enough that the solution would transfer beyond your organization? If yes, it is ready to pitch. If not, narrow or broaden until it passes.
Do not build anything yet. But think through the architecture on paper or in your head. Which of the five multi-agent patterns fits this problem? A relay for sequential steps? A supervisor for task decomposition? A debate loop for quality assurance? The pattern choice shapes the entire build.
Identify the key design decisions. Where does the human stay in the loop? What inputs does the system need? What does the output look like? Where would the system break first? These are the questions Module 7 will answer as a group, but having your own draft answers makes the conversation faster.
The agentic email processing example is your model for how to think through these design decisions. Study how the config file structures trust levels per contact, how the system refuses to act on unknown inputs, and how each phase adds one capability without breaking what came before.
A project brief is not complete until the work is divided. Think about what your cohort members bring to the table and how the work could be split. Consider roles like: problem definer (who owns the scope), architect (who designs the system), builder (who prompts and iterates), tester (who runs the verification pass), and presenter (who prepares the capstone walkthrough).
You do not need to assign these before Module 7. But arriving with a point of view on how the work divides will help the group move from discussion to delegation in a single session.
Your cohort should leave Module 7 with a written project brief that answers four questions: what are we building, which pattern are we using, who owns which piece, and what does the deliverable look like for the capstone? Everything you do this week feeds that outcome.
You have already read these for Module 6. Revisit them with your project in mind. The question is no longer "what are the patterns" but "which pattern fits the problem we are going to solve."
Review with fresh eyes. Which pattern matches the project candidates your cohort discussed? More than one may apply. Come ready to argue for the one you think fits best.
15 minThis time, read it as a design template rather than as a case study. Pay attention to the build sequence: how each phase adds one capability, how the config file centralizes decisions, and how the human checkpoint is positioned. Your project brief will need the same kind of phased thinking.
20 min