Prompts

How to write clear instructions Haruno can act on.

What makes a good prompt

A good prompt tells Haruno what you want, why you want it, and how the result should look. The clearer your instruction, the less back-and-forth is needed. Think of it like briefing a teammate: include the goal, any relevant background, and the format you expect back.

      Use a simple structure

      You do not need to follow a strict template, but prompts that include these four parts tend to get the best results:

      • Goal — what you want Haruno to do. Example: 'Draft a monthly management report.'
      • Context — background Haruno needs. Example: 'Use the figures in Q2-Operations.xlsx and compare them to Q1.'
      • Constraints — limits or rules. Example: 'Keep it under two pages and use the board deck template.'
      • Output format — how the result should look. Example: 'Return a Word document with charts and a short executive summary.'

        Example prompts

        • 'Summarize the last 20 support tickets from HubSpot. Group them by issue type and highlight the top three recurring problems.'
        • 'Build a Q3 sales presentation from the data in Salesforce. Use the same slide layout as Q2-Sales-Review.pptx.'
        • 'Research three competitors' pricing pages and create a comparison table in Excel with plan names, prices, and key limits.'
        • 'Draft a follow-up email to the vendor in a polite but firm tone. Mention the delayed delivery and ask for a revised timeline.'

          Common mistakes

          • Being too vague: 'Do something with the sales data' gives Haruno little to work with.
          • Asking for too much at once: break large jobs into smaller tasks so each result is reviewable.
          • Forgetting the output format: say whether you want a document, email, table, or bullet list.
          • Leaving out sources: point Haruno to the files, folders, or apps it should use.

            Iterate and refine

            Your first prompt does not have to be perfect. Start with a clear goal, review Haruno's draft, and then ask for changes. For example: 'Make this more concise,' 'Add a chart,' or 'Rewrite this section for a non-technical audience.' Each round gets you closer to the final result.

                Next steps

                Put prompts into practice by creating your first task or browsing example tasks.