Calendar: 'Priya — Alderwood Relaunch'\nWeek 6\n\nMonday: Final QA begins. Marcus full time on this, no other commitments booked.\nTuesday: QA continues. Sales team walkthrough of the new site scheduled 2pm.\nWednesday: Final sign-off deadline, end of day. Priya travels to RevCon 4pm.\nThursday: RevCon.\n\nAuto-detected: Only Monday and Tuesday are real working days before the Wednesday sign-off deadline. No time has been allocated for anything not already in progress.

Draft created in the lab's draft area.\n\nTo: marcus@alderwood.com, tom@alderwood.com\nSubject: One Thing to Confirm Today\n\nHey both,\n\nQuick flag as we head into final QA: the ROI calculator card has been sitting with no owner and no timeline since it was added two weeks ago. With sign-off Wednesday, I need to know today whether this is realistic to include or whether we're launching without it and adding it after RevCon.\n\nMarcus, can you give me a straight answer by end of day on whether this fits in the QA window without risking the core site?\n\nThanks,\nPriya

Page: 'Alderwood Relaunch — Task Board'\nWeek 6, 3 days before RevCon\n\nIn Progress:\n- Final QA pass (Marcus) — started this morning, no blockers reported yet.\n- Case study template (Fieldstone/Jess) — final version delivered yesterday, on time per revised timeline.\n- ROI calculator widget (Marcus) — still marked 'not started', no owner confirmed, no timeline set since it was added 2 weeks ago.\n- Blog redesign scope (unassigned) — still no owner, no updates in 26 days total.\n\nDone:\n- Homepage copy, pricing page dev, design handoff, stock photography, both case study interviews.\n\nAuto-detected: Everything on the critical path is done or in final QA except the ROI calculator, which has never been assigned an owner or a timeline despite being added 2 weeks ago. Blog redesign remains untouched and is not currently blocking anything time-sensitive.

Summary  
This chapter covers how to build and configure a multi-tool AI agent by defining a system prompt, connecting specific tools (task board, calendar, email draft), and orchestrating them to answer complex queries and execute actions.  

General domain of usage  
Project management

You're Priya, three days before you travel to RevCon. Everything you've done across this course — the plan, the budget, the blocker hunt, the vendor chase, the tracker — now has to come together at once. And the one task that's been quietly unowned this whole time is about to become today's problem.
 
In this final lab, you build the assistant yourself. Instead of a pre-configured helper, you'll create an agent, give it a role, connect its tools, and put it to work coordinating the last three days.

Three sample sources are already connected for your agent — a task board (behind Notion Page), the project calendar (behind Calendar Events), and a draft area (behind Email Draft). You don't need any real accounts. The two project files (`project-brief-raw.txt` and `alderwood-relaunch-budget.csv`) are also in the file tree if your agent needs to look back at the original ask or the budget.

Note

>### System Prompt
>
><b>You are Priya's project coordination assistant for the Alderwood website relaunch. You have three tools: notion_page (the team's task board), calendar_events (the project calendar), and email_draft (drafting messages to the team or stakeholders). You can also read two reference files if relevant: project-brief-raw.txt (the original brief) and alderwood-relaunch-budget.csv (the budget).
>
>Use notion_page when the question is about task status, ownership, or what's blocked. Use calendar_events when the question is about timing, availability, or what's booked. Use email_draft when the user asks you to write or send something. If a question touches more than one area, use more than one tool before answering.
>
>Keep answers direct and specific: name owners, name dates, name the actual next action. Do not pad with generic project management advice.
>
>Always answer the user's question directly. Do not refuse or redirect simply because a question is not about code. If the question is unrelated to software engineering, answer it briefly and naturally instead of saying it is outside your scope. Never explain what kinds of questions you can or cannot answer unless the user explicitly asks.

>### Task
 >
>Build your agent, then put it to work. Follow these steps:
 >
>1. Click **Create Agent** on the right.
>2. Agent name → type `Sprint Coordinator`.
>3. System prompt → paste the block above exactly as written.
>4. Choose tools → check **Notion Page**, **Calendar Events**, and **Email Draft**.
>5. Click **Save Agent**.
>6. Click the saved agent card to activate it for this chapter.
>7. Send this message:
>><b>Check the task board and the calendar. With 3 days left before I travel to RevCon, what's the single biggest risk to the launch, and who needs to hear about it today?
 >
>**Then send a follow-up in the same conversation:**
 >
>><b>Draft a message to the team flagging that risk and asking for a same-day response.
 >
>**What you're aiming for:** on the first message, the agent should pull from both the task board and the calendar to name one specific risk — most likely the ROI calculator sitting with no owner and no timeline against a 3-day buffer — rather than a generic list of worries. On the follow-up, it should draft a team message about that exact risk, reusing what it just found instead of asking you to start over. When you've watched your own agent connect two sources into one clear recommendation and then act on it, you've finished the course.

Discover how to keep a real project from falling apart: turn a messy brief into an actual plan, catch budget and schedule problems before they bite, push back on scope creep, and keep your team coordinated under a hard deadline. You'll practice it all through a live website relaunch, with Claude helping you plan, defend, and coordinate the work end to end.

Get hands-on experience turning a scattered project brief into a task list, then checking that plan against a real calendar and a real budget before you commit to a deadline.
 

Discover how to defend a deadline against scope creep, find the task that's quietly stuck, and chase down a vendor who's gone quiet — before any of it becomes a crisis.

Master the skills needed to research the competitive landscape, update stakeholders clearly, track the whole team's progress in one place, and coordinate a final sprint under pressure.