Priya's Thursday, two ways

Priya, a software architect at a payments company.

Priya starts Thursday with a decision that has been sitting for two weeks: whether to keep the old billing service or split it out. She opens ChatGPT and pastes the prompt from the decision record lesson, adding the constraints she knows by heart: three teams, a July deadline, and a database nobody wants to touch. The draft comes back with three options and the consequences of each. She rewrites two paragraphs, deletes a claim she cannot support, and sends it to the review meeting.

At lunch she uses the technical spec prompt in Claude for a small internal API. She gives it the requirement in plain words and asks for acceptance criteria. The first pass is close, so she fixes the error cases and adds a note about the rate limit. An engineer replies an hour later with one question instead of ten.

In the afternoon, a pull request lands that touches a shared module. She runs the code quality review prompt in Gemini, pasting the diff and asking where coupling has crept in. It flags two places she would have found eventually. She leaves comments and moves on.

Before she logs off, she uses the team guidance prompt to write a short note explaining the billing decision to the support team. She reads it once, softens a sentence, and sends it. The time she would have spent writing three documents after dinner goes to a walk with her dog and an early start on Friday's design review.