- First-pass output rarely lands perfectly; iteration is the normal path to a good result.; The chairman saw the output and now knows what to ask for more precisely.; A small detail was wrong and a redo is faster than editing the deliverable by hand.

1. Open the task and use the "Redo" button in the task header — this keeps the original brief and full context in the same thread, so the teammate doesn't start from scratch. 2. In the redo prompt, say only what should change: "Same thing, but shorter." "Same thing, but more skeptical." "Same thing,

How to redo a task

What's happening A task finished but the chairman wants another pass — a fix, a different angle, or a sharper version of the same deliverable.

Why it happens

First-pass output rarely lands perfectly; iteration is the normal path to a good result.
The chairman saw the output and now knows what to ask for more precisely.
A small detail was wrong and a redo is faster than editing the deliverable by hand.

What to do

Open the task and use the "Redo" button in the task header — this keeps the original brief and full context in the same thread, so the teammate doesn't start from scratch.
In the redo prompt, say only what should change: "Same thing, but shorter." "Same thing, but more skeptical." "Same thing, but use the Q3 numbers instead of Q2."
If the chairman wants the original kept as a reference, ask for it: "Save the first version as a comparison." The teammate will keep both.
If the second pass should go to a different specialist (a writer instead of a researcher, for example), say so: "Hand this to Casey for a rewrite." Astra will reroute.
If none of this works, message Astra and she'll loop in support.