Clanker CloudAn AI project assistant helps prepare the work around a project: organizing the brief, checking updates, identifying open decisions, and producing the next document. It is most useful when it can work from a clear set of current sources rather than a fragment of yesterday's conversation.
Clanker Cloud Projects keep related files, instructions, and Sessions together. An Agent can apply the same method to different tasks, while each Project carries its own context. This is particularly useful for consultants, agencies, and office teams moving between several initiatives.
Give each project a clear starting point
Imagine a fictional agency with two clients, Northstar and Elm. Northstar is launching a website; Elm needs a research brief. Both need progress updates, but their dates, source material, and commitments are different.
Create a separate Project for each engagement. In each, identify the approved brief, current working files, decision notes, and expected outputs. Add an instruction that tells the assistant which document governs when sources conflict.
The reporting Agent can know how to write an update without containing either client's private facts. Check the actual files and capabilities available to the Agent for each Session; project organization should not be treated as proof that every connected tool has been scoped correctly.
Make changes to the brief visible
Projects rarely stand still. A new email might request extra work, while the last approved document still describes the original scope.
Ask the assistant to compare the new material with the current brief and return three categories: confirmed changes, proposed changes, and unresolved conflicts. Include a source for each item. You can then decide which proposals become part of the working brief.
The document comparison guide provides a practical method for reviewing versions. Give files meaningful dates or version names so “latest” is not something the assistant has to infer from a filename such as final-final.
Prepare updates from the reporting window
For a weekly update, provide a start and end date and tell the assistant which sources cover that period. Ask for progress, blockers, decisions, and next actions. Require it to mark missing ownership or timing instead of filling the gap with a plausible answer.
For example:
Prepare Northstar's internal update for September 21–25 from the current brief and this week's notes. Separate completed work from planned work. Keep new client requests in a decisions-needed section. For every deadline, show the supporting file. Do not reuse Elm's material.
This is an illustrative prompt, not a record of a customer run. Review the result against the files and then save the approved version. The client report template can help establish the format.
Hand over the project, not just the last answer
When a colleague takes over, a recent chat summary may leave out the information needed to continue. Ask for a handoff containing the current objective, authoritative files, decisions made, unresolved questions, and the next few actions.
The project handoff template includes fictional material for practicing this. Open every important referenced file and confirm that the intended recipient can access what they need through the actual sharing controls. Mentioning someone in a document does not grant access.
Reuse the method on the next engagement
Save the reporting structure and review checklist in a custom Agent. Keep changing client facts in their Projects. If work must recur automatically, configure and test a Loop or Schedule separately; a saved Project does not schedule its own updates.
A good project assistant makes the next decision easier because the evidence, open questions, and finished files are together. Start by organizing one active project well enough that another person could pick it up without a long explanation.
Sources
Give your assistant one useful job
Keep your briefs, related Sessions, instructions, and deliverables in a Project, then reuse an Agent for the next task.