L02 · Agree what finished means
Skill packs and prompts are provided in English so they work best with the AI tools. Use them as-is.
Agree what finished means
Learning time: about 23.9–35.3 active minutes. Choose ONE presentation: the text (about 5.3 minutes, estimated) OR the lesson video (3:54, measured). Then 20–30 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 1, lesson 2 of 2. You have a project intent. Now turn it into an assignment that can be checked.
What you will do
Write a project contract with inputs, permitted actions, observable acceptance tests and stop conditions. You will separate course assumptions from facts about a real business. Outcome O1.
Teaching
A project contract is a short agreement about the work, not a legal document in this course. It answers what the agent should create, where it may work, what it may use and what evidence the owner needs before accepting the result.
For the Workshop Launch Kit, the main output is a local calculator with a short explanation and test record. Use the supplied USD inputs: fixed cost 180, variable cost 8 per attendee, price 30 and capacity 12. Define attendance as a whole number from zero through capacity. The budget is a synthetic teaching model. It excludes taxes, discounts, refunds, venue availability and other costs that the case does not supply. Those exclusions must remain visible.
Write the calculation in ordinary language before asking for code. Revenue is price multiplied by attendees. Total cost is fixed cost plus variable cost multiplied by attendees. Surplus is revenue minus total cost. A negative surplus is a loss; do not hide its sign. A break-even result needs a stated rule for whole attendees. The later calculation lesson develops and tests that rule.
Acceptance should describe both useful behavior and failure behavior. “Looks professional” is too subjective on its own. “The page states USD beside the financial result” can be checked. “An attendance entry above capacity is rejected with an explanation” specifies a failure response. Include at least one condition in which the correct action is to stop rather than invent an input.
Keep the input source intact. If a requester changes capacity later, record that as a new requirement, preserve the earlier version and rerun affected tests. Do not quietly change the original brief because a new answer looks more attractive. A change in requirements can invalidate earlier results even when the project still opens.
Authority belongs in the contract too. Creating local teaching files does not authorize buying a domain or sending invitations. A tool's ability to perform an action is separate from your permission to use it. Ask for approval only when a real boundary is reached; within the approved local task, routine drafting and repairs can proceed.
Worked example
Weak criterion: “The calculator should be accurate and user friendly.”
Checkable replacement: “Given whole-number attendance within capacity, the page shows revenue, total cost and surplus in USD. It states the assumptions. It rejects an attendance value above 12 without displaying that value as a valid plan. A reviewer can reach the inputs and calculate action using a keyboard.”
This replacement still needs concrete test cases and expected results. A reviewer should also ask how the page handles blank entries. Silently treating a blank field as a confirmed zero could produce a plausible budget from information the user never supplied. Make that policy explicit instead of letting the builder choose unnoticed.
Do it yourself
Create PROJECT-BRIEF.md with these headings: user and decision; artifact; source inputs and exclusions; permitted workspace/actions; acceptance tests; stops; completion evidence. Include at least five tests covering arithmetic, missing input, capacity, visible assumptions and usable interaction.
Use this complete review prompt:
Review my proposed Workshop Launch Kit contract. This is an English learning project using fictional inputs: USD 180 fixed cost, USD 8 variable cost per attendee, USD 30 ticket price and capacity 12. We are building a local calculator, an explanation and a test record. No public deployment, payment, booking, messages, real personal data or claim of market demand is authorized.
For each acceptance criterion, state whether a person could observe pass or fail. Identify missing inputs, unit ambiguity, unhandled invalid values and authority overreach. Do not edit files or build the calculator. Do not invent a test result. Suggest a minimal revision only where needed.
CONTRACT:
[Paste the full contract, including its tests and stops.]
Record which suggestions you accept. Save the revised contract with a version note. Label title changes separately from behavior changes.
Feedback and retry
Pause here. Your contract should allow the owner to reject a beautiful but incorrect result and accept a plain but usable one. Each test needs an input or condition, expected behavior and evidence route. “The AI says it passed” is not an evidence route.
For the retry, a fictional coordinator says, “If interest is high, change the capacity to 20 and assume all interested people will pay.” Write a response that preserves progress. Explain that interest is not bookings, capacity changes need a revised approved input, and a scenario can be labelled hypothetical without replacing the baseline. Then identify the tests that a capacity change would affect. No source can establish the fictional interest as real demand.
Check your understanding
Choose an answer and write one sentence explaining why before you read the answers.
- A tool can publish the project. Is publishing included in a contract that permits local creation only?
- A. No.
- B. Yes, because the tool is available.
- C. Yes, if publishing is quick to undo.
- A new capacity is approved. Can the old test evidence prove the updated version works?
- A. Yes: the formula has not changed.
- B. Yes, if the old tests all passed.
- C. No: rerun the affected checks and identify the version.
- Is a deliberate, specific stop always a failed project?
- A. Yes: a finished project never stops.
- B. No: stopping on an invalid input can be correct behaviour.
- C. Yes, unless the owner asked for it in advance.
Answers
- A. No. Availability of a tool does not widen the agreed scope.
- C. No. Rerun the affected checks and identify the version they cover.
- B. No. Stopping on an invalid input can be correct behaviour.
Summary
Save the contract before building. It gives the builder direction and the reviewer an observable basis for judging the actual result.
Sources
Anthropic, permissions, and OpenAI, permissions, reviewed 8 November 2026. Their enforcement differs; confirm the actual environment. The project contract and examples are original course methods, not a vendor or CPD-prescribed template.
