Welcome to our final unit! You've done the heavy lifting by defining and documenting your ideal super-specialist. Now what? How do you turn that blueprint into a working, impactful agent?
In this lesson, you'll learn how to translate all your workshop outcomes into actionable next steps for agent configuration and essential follow-up activities. We're moving from design to delivery!
Mapping the workshop output to the configuration
Recall the three key artifacts that you created in the workshop: the Job Profile, the Tools and Data Template, and the Task Instructions? How do you think these documents relate to building the agent?
To build an agent in a low-code environment, like the Agent Builder in Joule Studio, you need to define two main components: the system prompt (instructions) and the tools the agent needs to act. Your workshop output includes both.
Although this course does not cover how to build agents in Joule Studio, this lesson provides some guidance on how to use the information from the workshop to create a first iteration of instructions for the defined agent.
For more information about the Agent Builder in Joule Studio, you can check the resources linked as material for this lesson.
When configuring your agent, you'll encounter a form requesting information to "brief" your super-specialist.
Here's how the information you gathered maps directly to the sections of this form: 
Let’s check each section of the form one by one.
Agent Name
The agent name is the one that you gave to your agent in the Job Title section of the Job Profile Template. The name should provide a clear, function-based identity. Make sure that the name is based on the agent’s expertise and gives an idea of what it does. For example, instead of own names like "Eliza" or "Robocop", write something that shows what the agent does like "Travel Optimizer" or "Travel Booking Assistant".
Expertise and Instructions
This section is where you include most of the information defined in the workshop. Here is where you instruct the agent as if it were its first day on the job.
You can use the following prompt template structure to ensure you include all the vital, context-rich information from your workshop:
| Expertise | Instructions | Context |
|---|---|---|
| Your job is to [main responsibilities] | ## Role You are a world-class [Job Title] with in-depth knowledge of [experience / knowledge]. | ## Job Context You will be needed when [job context] |
# Standard operating procedure When [trigger] It's crucial that you think step by step through the following process to ensure the best result First, [step in the flow + tools used + example]. | ## Considerations and rules It’s crucial that [list of considerations] ## Impact This job is vital because [impact] |
Here is an example of each section
Expertise
Start with "Your job is…." and then add a summary of the main responsibilities.
For example:
"Your job is to [generate itinerary adjustments during travel disruptions, modify bookings requested by the customers and clarify customer requests when information is not sufficient]"
Instructions
Most of the instructions go here. You can start with an introduction of the role and then continue with the instruction template step by step.
| Prompt Section | Source & Content | Example for "Travel Optimizer" |
|---|---|---|
| ## Role | Job Title (2) and Experience and Knowledge (3)from the Job Profile. | You are a world-class [Travel Optimizer] with in-depth knowledge of [managing travel bookings modifications using booking systems, airline and hotel industry rules, travel requirements and restrictions worldwide]. (etc). |
| Prompt Section | Source & Content | Example for "Travel Optimizer" |
|---|---|---|
| ## Standard Operating Procedure | The Trigger (4) and Steps (5) from the Instructions template. This is the step-by-step SOP. | When [a customer requests an urgent flight rebooking via the online chat interface of the Travel Agency customer service website, or you detect a travel disruption from online news sources], It's crucial that you think step by step through the following process to ensure the best result
|
Context
This is additional information about the job the agent will do. You can include the following sections:
| Prompt Section | Source & Content | Example for "Travel Optimizer" |
|---|---|---|
| ## Job Context | The Job Context (6) section of the Job Profile. | You will be needed when [customers face unexpected travel disruptions, need urgent assistance with their bookings, or require itinerary adjustments]. |
| ## Considerations and Rules | The Considerations (7) section of the Job Profile. | It’s crucial that you consider the following when handling a request:
|
| ## Impact | The Impact (8) part of the Job Context. | This service is vital for the company / team / department because it aims to: [address urgent rebooking cases... reduce number of calls to customer service... reduce negative reviews…] |
Remember, you aren't writing a rigid flowchart in the instructions. You are defining the outcome and sequence of major steps, and the agent's reasoning capabilities will handle the specific "how". This system prompt is the starting point and will need iteration as you test your agent.
The implementation team can also use the Tools and Data template as a reference for the tools the agent needs to be connected to.
Beyond Configuration: Essential Follow-Up Activities
The configuration of the agent is a first next step, but successful projects need alignment across different stakeholders: business, technical, and executive. Here are two follow-up activities that you can facilitate:
1. Create a Solution Concept Diagram
This technical diagram shows the different technical building blocks needed to build your agent and how your new agent fits within the company’s existing tech landscape.
- Who needs it: The implementation team and IT stakeholders.
- What it does: It documents the agent's architectural requirements (data sources, APIs, connected systems, etc.) identified in the Tools and Data Template.
- Example:
Check how to create a Solution Concept Diagram here
2. Design a Vision Storyboard (Pitch)
A storyboard illustrates how a future user might collaborate with the agent(s) to achieve objectives and improve outcomes.
- Who needs it: Executives, sponsors, and end-users.
- What it does: You can use this storyboard as a compelling pitch to demonstrate the value and user experience (AX/UX) of your final solution, ensuring executive buy-in and validation of your design.
- Example
Check how to create a Vision Storyboard here
Key Takeaways
- The two main components for agent configuration are the System Prompt (instructions) and the Tools it needs to act.
- The Job Profile, Tools and Data Template, and Task Instructions are the core artifacts used to populate the agent's instructions in the agent builder.
- The System Prompt should include the Role and Knowledge, Step-by-step instructions and Tools, Context, Considerations and Rules, and the overall Impact to guide the agent's intelligent decision-making.
- Follow-up activities like creating a Solution Concept Diagram (technical document) and a Vision Storyboard (stakeholder pitch) to support the project documentation and successful implementation.
By learning how to translate the human-centered insights from the workshop into the technical blueprint for the agent, you transform from a facilitator into a strategic partner, ensuring that your organization builds purposeful, impactful, and trusted agentic solutions.