NewAI Content Creation is now live in Early Access
Turning Point Training Instituteby Training Center
Skip to content
0%
Module 9 · Deliver and transferLesson 1 of 2
Video lesson

L17 · Hand over a project someone can inspect

IntermediateVideo lesson
6 min readIntermediate
Downloads & resources
Download this lesson's materials, ready to use.

Skill packs and prompts are provided in English so they work best with the AI tools. Use them as-is.

Hand over a project someone can inspect

Learning time: about 23.7–35.2 active minutes. Choose ONE presentation: the text (about 5.2 minutes, estimated) OR the lesson video (3:43, 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.

Example prompt

Where you are: Module 9, lesson 1 of 2. You have built, tested and repaired the Workshop Launch Kit. Now prepare the exact version another person will receive.

What you will do

Package the project with instructions, actual test evidence and honest limitations. Verify the recipient copy rather than relying on the working folder. Outcomes O3, O7 and O8.

Teaching

Your working folder may contain useful output mixed with experiments, caches, private notes and superseded versions. The recipient needs the actual project plus enough context to use and evaluate it. A good handover starts with one clear file and separates user instructions from internal evidence.

Create a delivery index that names the purpose, version, included files, entry point, prerequisites, expected behavior and known limits. Explain how to open the calculator using the route you actually tested. If it needs a local server, provide that exact tested procedure and how to stop it. If direct file opening works, state which environment you checked. Never invent a public URL or claim a deployed service when the project exists only on the laptop.

Preserve the source files and tests needed for maintenance, but do not include credentials, private chats, employer information or unrelated files. The teaching project's interest data remains fictional. Put that label in the recipient's starting instructions and any report discussing interest. A reader who misses the course videos should still understand the limits.

A release candidate is a specific proposed delivery version. Identify it by a commit or package version and a file manifest. A manifest lists included paths; checksums can help detect changed bytes. Neither a checksum nor a clean Git status proves the content is correct. They identify what the review applies to. Actual behavior checks still matter.

Use a short readiness statement with separate categories: verified in the tested environment, produced but not tested, known issue, and decision required. “Everything complete” hides useful distinctions. A calculator may have passed local arithmetic and keyboard checks while the cross-agent handoff or target browser remains untested. State that directly without treating one missing test as proof the whole project failed.

Worked example

A recipient receives calculator.html with no instructions. They open it successfully, enter a number and see a surplus. They cannot tell whether figures include taxes or whether twelve seats are a venue limit. The technical file exists, but its use is ambiguous.

A better package starts with START-HERE.md: fictional workshop, USD assumptions, tested opening instructions, capacity policy and the location of its test record. It says no booking, demand validation or publication occurred. Its change note records the last repaired issue and the tests repeated afterward. The recipient can judge the proposed use without reading an entire agent conversation.

Do it yourself

Prepare a new delivery folder from an explicit list of intended project files. Do not edit the baseline while copying. Ask the agent for an inventory first:

text
Audit the current fictional Workshop Launch Kit for handover. Read the brief and actual project records. Do not modify, zip, upload, publish, send or delete anything. Propose an explicit inclusion list for a local delivery copy: runnable artifact, required source/input files, start instructions, tests/results and limitations. Identify secrets, unrelated files, missing dependencies and assessor answers that must stay out. Distinguish actual executed checks from suggested or unrun checks. Report the exact version and any uncommitted changes. Do not claim release approval or market demand.

After reviewing the list, authorize creation of the local copy only. Open the copy in a fresh folder using its own instructions. Repeat a valid calculation, one invalid-input test and keyboard navigation. Check that local links resolve without referring to a private authoring path. Save actual results and environment details. If a test cannot run, record why and leave it pending.

Write a short recipient message naming the file to open, the purpose, exact version, two important limits and the decision you need. Preparing this message does not send it. Give the recipient the working artifact and evidence, not a promise that they can reconstruct it from the chat.

Feedback and retry

Pause here. The package should be understandable from its index, and the checked copy should match the version under review. A “passed” row must name the test and actual result. Any later repair requires affected rechecks and an updated version record; do not keep an old pass attached to changed output.

For the retry, imagine the recipient sees “file not found” because a link points to your private authoring folder. Find the broken dependency in the delivery copy, repair its relative link or include the permitted missing file, then reopen the package from a different disposable location. Record the failure and retest. Do not grant the recipient access to your entire laptop as a workaround.

Check your understanding

Choose an answer and write one sentence explaining why before you read the answers.

  1. Does a matching checksum establish that a calculation is correct?
    • A. Yes.
    • B. Only for spreadsheet files.
    • C. No: it establishes byte identity.
  2. Can the working folder's successful test stand in for opening the delivery copy?
    • A. No: packaging can introduce missing files or broken paths.
    • B. Yes: the files are the same.
    • C. Yes, if the archive was created by an agent.
  3. Does preparing a review message authorise sending it?
    • A. Yes, once it is written.
    • B. No: send only within an explicit authorised action.
    • C. Yes, if it goes to a colleague.

Answers

  1. C. No. It establishes byte identity, not correctness.
  2. A. No. Packaging can introduce missing files or broken paths.
  3. B. No. Send only within an explicit authorised action.

Summary

Deliver one identifiable version with an obvious starting point. Record what works, what remains untested and what decision the recipient is being asked to make.

Sources

GitHub, GitHub flow, reviewed 8 November 2026, supports explicit review and versioned changes. The package manifest, readiness categories and recipient-copy test are original course practices. They do not constitute CPD accreditation, expert approval or authorization to publish.