Written reply & bug report

The async exercise is where two audiences collide. The same incident becomes a warm reply to a furious user and a cold, precise report for an engineer who has never seen the ticket. Both come from one prompt and you write them fast.

Take a messy, angry ticket - the kind with caps lock, three unrelated complaints and no version number - and produce both artifacts. The reply ships to the customer. The report goes to Eng. Grading is partly volume done well under time pressure, so set a clock.