Task revisions
Ask a Character for revisions in the same Asana task, follow its progress and keep normal teammate discussion separate.
Explore this guide
Address the Character explicitly
Use the configured Growthub: @alias prefix for each new request and revision. The same task keeps its existing Character conversation.
Growthub: @studio Revise the second concept: show the product in use, reduce the headline and keep the approved palette. Keep the earlier version and return the new draft links in this task.
Address the Character explicitly
Use the configured Growthub: @alias prefix for each new request and revision. The same task keeps its existing Character conversation.
Ordinary comments, acknowledgements and @mentions of human teammates remain normal team discussion. They do not request Character work.
Growthub: @studio Revise the second concept: show the product in use, reduce the headline and keep the approved palette. Keep the earlier version and return the new draft links in this task.
Follow one reply as it updates
The reply identifies Growthub AI, the Character and its current state. Received means the request is saved. Working reflects the native turn actually starting. Response ready includes the saved result.
Selected teammates get the same progress presentation as the owner. Each request has its own reply; a revision does not overwrite an earlier accepted result.
Answer a question or inspect the work
A genuine input request can show a question in the task. Use Open work to answer through the existing Growthub controls, especially for private values or approvals.
An ordinary Asana comment does not answer a paused input control. Keep confidential answers in the secure work controls.
Review before the next action
- Open the returned document, file or destination record.
- Check the requested revision and confirm earlier accepted work remains.
- Request the next bounded change with the Character prefix.
- Give a clear separate instruction when you want a send, schedule or publication.