Look at your organization and scope one idea for Week 3
What is my organization still missing, and which one team-sized idea do I bring into Week 3?
- Source
- Current Internal package, pages/anw-w2-close.html (Internal b518c35b; src/hunter-week2/SOURCE.md). Original handoff: Internal PR #125.
- Copy
- Exact Internal source package, vendored without editing its lesson or prompt bytes.
- Prompts
- Prompts are rendered from the current vendored Internal package named in Source. Historical publication: student 50ab8c5c from Internal 0e2885b5; that receipt does not qualify later Outlook changes.
- Checked in the app
- Historical baseline QA: bounded integrated checks passed for fresh preparation, upgrade, supported-model native routing and tracing. This receipt does not qualify later Outlook changes. Ordinary-student and Windows qualification remain unverified.
- Open to students
- Yes.
- Other view
- one scroll (Wade chose one part at a time; one scroll is kept to compare)
This is the short close of Week 2. You look at what your organization has now, ask your Chief of Staff what it is missing for the need you just approved, and choose one idea sized for a team to bring into Week 3.
Nothing is built, hired, filed or changed in this lesson. The Chief of Staff reads and answers; you decide.
One short, dated note in your own words: the idea you bring into Week 3, what your organization is missing for it, and the first thing you want to try.
You choose the idea and how big it is. The Chief of Staff points out gaps, and you decide what to do with them.
Start or resume this lesson
Use the native aibl-chief-of-staff agent to start Week 2 Module 4 Lesson 3. Read course/workforce/week2/prompts/anw-w2-close.txt and course/workforce/week2/lessons/anw-w2-close.md. Stay read-only and save nothing before my yes to the exact note. If the named agent is unavailable, pause and ask Gigawatt to check the installation.
Look at what you have
Open three things you built or used this week:
- Your roster:
workforce/shed/registry.yaml, the agents in your organization and each one's job. - Your library:
library/knowledge/INDEX.md, the index of what the Knowledge Librarian (Sallee) has filed. - Your approved SOP: the version you approved in Module 3, Lesson 3.
Before you ask anyone, guess: which stage of your workstream has nobody and nothing behind it yet?
Do this now: make your guess
Write your guess in one line. You will compare it with the Chief of Staff's answer.
Ask your Chief of Staff what is missing
Copy the start prompt at the top of this page. It asks the Chief of Staff to read your roster, your library index, your approved SOP and the Week 3 section you approved in Lesson 2 (in context/handoff.md), then tell you what your organization is missing for that need. It reads only; it changes nothing.
A good answer:
- Names specific gaps: a stage of your workstream that no agent's job covers, knowledge your library doesn't hold yet, or a stage with no approved SOP.
- Points each gap to something you can open: a roster row, an index line, or a phrase in your need.
- Marks anything it couldn't open as not checked.
- Leaves the choice to you. It doesn't pick your idea, design agents or start any work.
For the fictional client-kickoff example, one good line might be: “Confirming the first payment: no agent's job covers it, and the library holds no payment records.” That is a synthetic example, not a claim about your organization.
A weak answer is a general list, such as “you need more agents”, or an offer to build something now. Ask the Chief of Staff to point each gap to a file.
Do this now: compare the answer
Compare the answer with your guess from Part 1. Where do they differ?
Scope one idea and save your note
Choose one idea sized for a team of about five agents: a piece of your workstream they could share, from what starts it to who receives the result. It is usually the need you wrote in Lesson 2, perhaps trimmed to what you could try in a week. One check or one step is too small. Your whole business is too big.
Write your note in three short lines, in your own words:
- The idea: what starts it, what finishes it, and who receives the result.
- What is missing: the gaps from Part 2 you agree with. Name what is missing, not which agent to build; Week 3 decides that.
- First try: the first thing you want to try in Week 3.
The Chief of Staff shows you the exact note and waits for your yes. After your yes, The Professor appends it, with today's date and the heading “End of Week 2”, to your course progress note, work/course/staff/progress.md. Nothing else changes: context/handoff.md keeps the need you approved in Lesson 2.
Do this now: check your note
Open work/course/staff/progress.md and check that the note reads the way you wrote it.
If you get stuck
| What you notice | What to try |
|---|---|
| The Chief of Staff offers to build or hire something. | Say no for now. This lesson only names what is missing; Week 3 decides what to build. |
| The answer lists gaps you can't find in any file. | Ask which file each gap comes from. Keep only the gaps you can open. |
| Your idea is one step, such as a single check. | Ask what starts the work before it and who receives the result after it. Write the whole piece. |
| You have no approved SOP or no Week 3 section yet. | Finish Lesson 2 first, or save “not checked” beside that item and keep going. |
Next: Week 3, where you build a team of about five agents for one workstream in your business, on top of what you set up this week, starting from your need and the idea you just scoped. Bring your evidence record, your need sentence and your end-of-Week-2 note.