What you’ll take away
01Start with the result02Choose the right unit of work03Keep the context small and useful01 / Start with the result
Write down the specific deliverable before you open more threads. “Prepare a release brief with sources and unresolved questions” is easier to review than “research everything about AI.” Name the person who will check the result and the format they need.
02 / Choose the right unit of work
A project coordinates ongoing work across separate threads. A subagent carries out a bounded assignment inside a parent session. Decide whether you need a conversation you can return to, or a focused piece of assistance for the task already in progress.
03 / Keep the context small and useful
Provide the relevant files, instructions and source links. Explain what the task may change, what requires review and what evidence must be returned. A short, precise brief is more useful than a folder of material with no stated purpose.
04 / Review access before the first assignment
Check which repository and working environment the thread will use. Start with a task you can inspect. Treat account availability, permissions and usage as things to verify in your own account, not assumptions to inherit from a video.
05 / Read the blocker before retrying
A thread waiting for access or an approval needs that specific issue resolved. Read the request in the thread that made it. Repeating the same instruction can create more work without removing the cause.
06 / Close with a clear handover
Ask for the deliverable, the evidence, the unresolved items and the next decision. Keep those four pieces together. A status label is useful; the actual files and checks are what let you decide whether the job is complete.
Source material
Use the original documentation for changing product capabilities and account availability.
Claude Projects documentation Projects announcement