L07 · Delegate a bounded build
Skill packs and prompts are provided in English so they work best with the AI tools. Use them as-is.
Delegate a bounded build
Learning time: about 28.5–45.5 active minutes. Choose ONE presentation: the text (about 5.5 minutes, estimated) OR the lesson video (3:30, measured). Then 25–40 minutes of practice and checking (estimated). Do not count both presentations. Setup delays and optional extra study are separate; learner timing has not yet been piloted.
Where you are: Module 4, lesson 7. Your project has a brief, a recoverable starting point and a handoff record. You will now give one agent a small build task.
What you will do
Write a complete build instruction, inspect the agent's plan, and compare its changed files with your acceptance checks. Save your instruction and a short decision in your project record. This practises outcome O4.
Teaching
“Build me a workshop business” leaves important decisions to the agent. It could choose prices, invent demand or add a payment service. Your first task should produce something small enough that you can inspect it yourself. Our Workshop Launch Kit needs a local budget calculator using fictional workshop figures. This lesson delegates its written calculation specification before anyone edits the calculator.
A useful instruction gives the worker a job, the facts it may use, its permitted changes, and a way to show completion. Ask it to inspect the current project before changing anything, because yesterday's starting point may have changed.
The product's permission controls and your written brief do different jobs. The brief describes the task; the controls limit available actions. Check both. A sentence saying “do not publish” does not remove a connected publishing tool. Keep this first exercise local, and decline permissions unrelated to the job.
Use one builder at a time in this working folder. You can choose Claude Code or Codex. Record which surface and version you used. The second agent will review the result in lesson 8. GitHub holds your files and change history; it does not automatically deliver your chat to the other agent.
Worked example
This is an original simulated teaching example, not a transcript of a tested AI run. A coordinator needs a calculation note for a fictional workshop. Fixed cost is USD 180, variable cost is USD 8 per attendee, ticket price is USD 30, and capacity is 12. Interest responses are fictional, not bookings.
The coordinator gives the following complete instruction in the project folder:
Act as the builder for my fictional Workshop Launch Kit. First identify
the current folder, branch or detached checkout, starting commit and
uncommitted files. Read the existing brief and project instructions.
If the recorded facts conflict with the facts below, report the conflict
before editing. Do not overwrite other people's work.
Create only build-notes/budget-spec.md. Do not edit the calculator yet.
Use fixed cost USD180, variable cost USD8 per attendee, ticket price USD30,
and capacity 12. State the revenue, total-cost and surplus formulas.
Calculate the smallest whole attendee count that covers cost; show the
calculation and check its result. Include results for 8 and 12 attendees.
Describe how a later calculator should handle invalid attendee input.
Keep this fictional and local. No payments, bookings, outside messages,
new services, dependencies, deployment or Git push. Plan briefly first.
After I accept the plan, create the note and report the exact changed
file, calculations checked, any unchecked claim, and remaining questions.
Stop after that report. Do not declare the whole project complete.
The expected specification uses revenue = 30 × attendees and cost = 180 + 8 × attendees. Each attendee contributes USD 22 toward fixed costs. Nine attendees cover cost; eight produce a USD 4 loss, and twelve produce a USD 84 surplus. These calculations do not predict purchases.
The coordinator can accept a plan to write the note. A plan to add a payment button needs correction before execution. A completion report needs the file and checks.
Do it yourself
Use a separate practice note with these new fictional facts: fixed cost USD 96, variable cost USD 6, price USD 18, capacity 10. Write a complete builder instruction for build-notes/practice-budget-spec.md. Require the break-even count and results at 7 and 10 attendees. Include the allowed file, a conflict stop, the required completion evidence and the same local-only boundary.
If your AI account is available, run the task after inspecting its plan. Otherwise write the instruction and specification yourself and label the execution “not run.” Both routes practise the calculations; only the first provides evidence of delegating to a live agent. Save the plan, the actual file and your decision.
Feedback and retry
Pause here before reading the feedback.
Your instruction succeeds if it preserves all four facts, restricts the changed file, requests evidence and separates calculation from demand. Contribution is USD 12 per attendee; break-even is 8. At 7 attendees the loss is USD 12; at 10 the surplus is USD 24. Check the actual file, even if the agent's report gives these answers.
Retry with fixed cost USD 70, variable cost USD 5, price USD 15 and capacity 6. Ask for feasibility within capacity. The smallest break-even count is 7, so this workshop cannot cover its fixed cost at the stated capacity; at 6 it loses USD 10. A good worker reports that constraint and asks about options. It must not silently increase capacity or price.
Check your understanding
Choose an answer and write one sentence explaining why before you read the answers.
- The builder says the task is finished but changed three extra files. What should you do?
- A. Accept because it may have improved the project.
- B. Inspect the extra changes against the brief and resolve them before accepting.
- C. Ask a second agent whether the first sounds confident.
Answers
- B. Extra files may be justified, harmless or harmful. Their contents and purpose need review. Neither confidence nor another model's agreement supplies that evidence.
Summary
Your completed record contains a bounded instruction, a plan, the actual result and your acceptance decision. Keep these together for the independent review in lesson 8.
Sources
- Anthropic, Common workflows, planning and isolated-work sections, checked 8 November 2026.
- Anthropic, Configure permissions, permission modes and rules.
- GitHub, GitHub flow. The exercise, prompt and financial cases are original course material.
