When should I send a follow-up instead of a new task?

Use a follow-up to revise a completed deliverable within the same goal. Use a new task for a different objective so unrelated context does not obscure the requested result.

Before you begin

Task status describes execution, not whether the result is factually correct or ready to publish. Keep the original input and inspect the actual output file. Task details, results and execution events provide different evidence; use them together when deciding whether to accept, revise or retry work.

Steps

1. Open the original task.
2. Identify the file and precise correction.
3. Send the revision through its follow-up box.
4. Compare the revised artifact with the prior version.

Example

In outputs/recap.md, split the Decisions section from Open questions and retain the existing source references. Save recap-v2.md for comparison.

Check the result

Confirm that the requested change happened and that previously correct sections were preserved.

Limits and troubleshooting

Session continuation depends on the selected tool and saved session. Include essential filenames and constraints even when continuing a conversation.