Resources / Prompt of the week

Team & workflowAgentic

The Agent Blueprint Builder

Suggested tool: Claude

The scenario

You have a repetitive communications workflow — something you or your team does weekly, sometimes daily — that eats time you'd rather spend on strategy. Before you build anything, you need a clear design. This prompt turns your workflow description into a structured agent blueprint you can hand off, build from, or pitch to your tech team.

The prompt

You are an AI workflow designer helping a communications professional build their first agent. Based on the workflow I've described, create a structured Agent Blueprint with the following sections:Trigger: What starts the workflow?Task: What discrete steps does the agent take? List each step in plain language. Maximum 5 steps.Output: What does the agent produce, in what format, delivered where?Escalation: What should the agent flag for human review?Data sources needed: What inputs does the agent need access to?Risk check: What could go wrong, and what guardrail prevents it?Keep the language simple. Assume the person building this has no coding background. Format each section with a bold header and 2–3 bullet points maximum.

How to use it

  1. Open Claude and start a new conversation.
  1. Describe your target workflow in plain language — what triggers it, what you do, and what you produce. One paragraph is enough.
  1. Paste the following prompt:
  1. Review the blueprint. Push back — simplify a step, add a guardrail, adjust the output format.
  1. Save the final blueprint. This is your build spec. Bring it to a cohort session, share with a collaborator, or start building it yourself.

Why it works

  • It removes the biggest blocker — most people don't build agents because they don't know where to start. A blueprint gives you a concrete starting point in under 15 minutes.
  • It works for any workflow — media monitoring, inbox triage, issues briefings, client reporting, executive prep. The prompt adapts to whatever's eating your time.
  • It makes the build conversation easier — whether you're working with a tech partner, a VA, or building it yourself, a clean blueprint is the difference between a yes and a blank stare.

This prompt first ran in TIC. Read the original issue →

Be the one in the room who saw it coming.

One issue a week. One AI development that matters for comms, broken down into what it means for your budget, your team, and your next board conversation.

A free, weekly, unsubscribe anytime.