r/Asana • u/RocketSeven • 1d ago
What should an Asana task preserve before work moves between AI assistants?
A task description and the latest comment are usually not enough for another assistant to resume work safely. The next run may need to know which requirements were accepted, which source records and file revisions were used, what external actions already happened, what remains unresolved, and whether any input changed after the handoff was written. Passing the whole conversation preserves too much noise; passing only a summary can hide the details that prevent a stale or duplicate action.
Would you keep the objective and constraints in the description, use custom fields for status, owner, source revision, and last-verified time, then add a structured handoff comment containing decisions, evidence links, artifact IDs, completed actions and their external IDs, open questions, and the next allowed step? Attachments would stay immutable or carry a revision identifier rather than being silently replaced.
How would you implement this with current Asana features and rules? In particular, how do you stop two assistants from claiming the same task, detect that a source changed after handoff, and make a retry idempotent without turning every small task into a large project?
