The group-travel team of Nordlicht Reisen GmbH has seven roles (M-03), so seven prompts. They must agree in tone, carry the same house rules and hand each other results in a format the next agent can read. At the same time, what an agent needs to know changes with every run: the customer's language, the group size, the sources. The lesson asks how to build seven prompts from building blocks, how foreign data gets in without becoming instructions, and how a change goes live.
Prior knowledge. Structure of a system prompt, separating instructions and data, filling placeholders safely: "AI track, lesson T3.1". Examples as message pairs, good and bad examples: "T3.2". Prompts as files and versions: "T3.3". Stable first, changing last for the prompt cache: "T3.4". Hard rules in code: "T6.4". The path of an agent version: "AI-103, lesson 1.2". None of that is repeated; new is what connects several prompts.
New in this lesson. (1) Every prompt lives as a file under prompts/<agent>/ in the repository gruppenreisen and consists of hausregeln.md (the same for all), rolle.md and beispiele.json. (2) Every agent that hands something to another answers with a JSON object whose field uebergabe is weiter or mensch. (3) For every run the orchestrator provides language and group size as context (session state, keys sprache and personen). (4) A prompt change is a release like any other.
The requirement
All numbers are assumptions of the task.
| No. | Requirement | Type | Measure | Weight | Source |
|---|---|---|---|---|---|
| 2.1-01 | All seven prompts carry the same block of house rules. | R | 1 file, 7 uses | Must | Quality |
| 2.1-02 | Foreign text (attachment, supplier reply, form field) is never read as an instruction. | R | 10 of 10 malicious cases (M-12) without consequence | Must | Security |
| 2.1-03 | Legal questions leave recht as a handoff to a person. |
R | 100 % in the test set | Must | Legal (M-03) |
| 2.1-04 | A prompt change goes live only after the test set has passed it. | R | 0 changes without a run | Must | Operations |
| 2.1-05 | Every trace names the agent version. | F | 100 % of calls | Should | Troubleshooting |
Cost frame. Cost driver: tokens per call. House rules and examples appear in every call and grow with every role; examples are the most expensive line (T3.2). Prices: the pricing page of Foundry.