Pro Software Engineer Prompt Pack: Everyday Work

1. 1.Write a design doc that gets a reply

   You are an experienced software engineer. Write a design doc to [RECIPIENT_NAME] about [TOPIC]. Lead with the ask, keep it under [WORD_LIMIT] words, and end with one clear next step.

2. 2.Rewrite a rough pull request description

   Rewrite this rough pull request description so it is clear and warm without losing the main point. Audience: [AUDIENCE]. Tone: [TONE]. Draft: [PASTE_DRAFT]

3. 3.Explain a decision to a teammate

   Draft a short message to a teammate explaining why we decided [DECISION]. Cover the reason, the trade-off we accepted, and what happens next. Avoid jargon.

4. 4.Say no politely to a product manager

   Write a respectful message declining a request from a product manager about [REQUEST]. Offer one alternative, keep the door open, and stay under [WORD_LIMIT] words.

5. 5.Chase an overdue reply

   Write three follow-up messages to a reviewer who has not answered my note about [TOPIC]. Space them [DAYS_APART] days apart and change the angle each time without sounding pushy.

6. 6.Deliver bad news to a teammate

   Help me tell a teammate that [BAD_NEWS]. Give me an opening line, the facts in plain words, what we are doing about it, and a closing that keeps trust.

7. 7.Turn notes into a code review comment

   Turn these notes into a clean code review comment with a one-line summary at the top, then decisions, owners and dates. Notes: [PASTE_NOTES]

8. 8.Write a short update on lead time

   Write a five-sentence update for [AUDIENCE] on lead time: where we are, what changed since [LAST_UPDATE_DATE], what is at risk, and what I need from them.

9. 9.Introduce two people

   Write a warm introduction email connecting [PERSON_A] and [PERSON_B] because [REASON]. Say what each gains and make the first step easy.

10. 10.Prepare for a hard conversation with a product manager

    I need to talk to a product manager about [DIFFICULT_TOPIC]. Give me a calm opening, three questions that invite their view, and two phrases to use if the conversation gets tense.

11. 11.Shorten a long message

    Cut this message to half its length. Keep every decision and date, drop the filler, and keep my voice. Message: [PASTE_MESSAGE]

12. 12.Make a design doc friendlier

    Rewrite this design doc so it sounds friendly and human, still professional, and does not use any corporate clichés. Text: [PASTE_TEXT]

13. 13.Write a thank-you that is specific

    Write a short thank-you to [PERSON_NAME] for [SPECIFIC_ACTION]. Name the concrete impact it had on [IMPACT_AREA] and avoid generic praise.

14. 14.Reply to a frustrated teammate

    A teammate wrote this frustrated message. Draft a reply that acknowledges the problem, takes ownership where it is ours, and proposes a fix with a date. Their message: [PASTE_MESSAGE]

15. 15.Announce a change

    Write an announcement about [CHANGE] for [AUDIENCE]. Explain what changes, what stays the same, when it starts, and where to ask questions.

16. 16.Write a subject line set

    Give me ten subject lines for a design doc about [TOPIC]. Mix curiosity, benefit and plain description, and flag the two you would test first.

17. 17.Clarify an unclear request

    An on-call engineer sent this vague request. List the questions I should ask so I can do it right the first time, ordered by importance. Request: [PASTE_REQUEST]

49 more prompts in the full pack