Ask for work clearly
A useful request gives a teammate enough context to act and a clear way to recognize completion.
Include four things
| Include | Example |
|---|---|
| Outcome | A two-page launch brief for the product team |
| Sources | The attached notes and this project folder |
| Constraints | Keep the current dates; flag missing owners |
| Finish | Attach the brief and summarize the decisions I need to make |
Name the app account, repository, folder, or teammate when there could be more than one. Replace “check the latest changes” with the branch, date, or previous review that defines the comparison.
Describe the action boundary
Say whether you want a draft, an edit, a sent message, or a published change. A useful instruction is “Prepare the customer reply here for review.” For cloud coding, remember that a completed job publishes a task branch; requesting no pull request still permits that branch publication.
Correct the existing task
Quote the relevant message and explain the correction. “Use the second option and keep the original deadline” gives more direction than “wrong.” Ask for a saved profile, memory, or skill change when the correction should apply later.
Compare these two proposals for our onboarding project. Use cost, implementation effort, and maintenance as the criteria. Recommend one, cite the supplied evidence, and list the assumptions that could change your choice.