TACTIXBegin with the outcome
Explain the problem and the result you need before prescribing a button, color or technical solution.
Include the essential context
State the user, current situation, expected behavior, scope, owner, due date and acceptance criteria.
Make completion testable
Replace vague requests with observable outcomes and say what must not change.
Keep the request, discussion, files and acceptance criteria connected to the relevant topic instead of scattering them across separate tools.