← Back to Subagent Architecture

Pipeline Agent Prompts

The complete prompt templates for pipeline and file agents, variable substitution, and quality instructions — annotated and explained

On this page

01Complete Pipeline Agent Prompt 02Complete File Agent Prompt 03Variable Substitution 04Quality Instructions in the Prompt

01

Complete Pipeline Agent Prompt

The pipeline agent receives a complete context from the orchestrator about the audience variant to generate. Here is the full template with annotations.

// ============================================
// PIPELINE AGENT PROMPT TEMPLATE
// ============================================

You are a pipeline agent for the Stakeholder
Content Generator. Your task: Generate all HTML
files for ONE audience variant.

AUDIENCE:
  Name:       {{audience_name}}
  Emoji:      {{audience_emoji}}
  Suffix:     {{audience_suffix}}
  max_level:  {{max_level}}

HS_THRESHOLDS:
  L1: {{threshold_l1}}
  L2: {{threshold_l2}}   // null if max_level < 2
  L3: {{threshold_l3}}   // null if max_level < 3

INTEGRATION_MODE: {{mode}}
  // "standalone": with header/footer
  // "embedded": without header/footer

OUTPUT_DIR:      {{output_dir}}
NAMING_PATTERN:  [slug]{{suffix}}_{{lang}}.html

CURRICULUM:
  // Pre-computed tree from orchestrator
  // Only topics relevant for THIS audience
  [
    {
      theme: "Authentication",
      slug:  "authentifizierung",
      hs:    10,
      planned_levels: ["L0", "L1", "L2", "L3"],
      sub_themes: [...]
    },
    ...
  ]

LANGUAGE:       {{lang}}
LANG_PARTNER:   {{partner_lang}}

For each topic in the curriculum, generate the
planned levels as separate HTML files.
For each file: Start a File Agent (subagent)
with the File Agent Prompt.
            

The pipeline agent prompt contains everything needed to generate a complete audience variant: audience context (name, emoji, suffix, max depth), HS thresholds per level, integration mode, output directory, naming pattern, the pre-computed curriculum tree (only topics relevant for this audience), and language settings. The pipeline agent does not need to compute HS scores — that was done by the orchestrator.

02

Complete File Agent Prompt

The file agent generates one single HTML file. Its prompt contains everything relevant for exactly that page — from filename to quality gates.

// ============================================
// FILE AGENT PROMPT TEMPLATE
// ============================================

You generate ONE HTML file.

FILENAME:     {{filename}}
PATH:         {{output_dir}}/{{level_dir}}/{{filename}}
AUDIENCE:     {{audience_name}} {{audience_emoji}}
LANGUAGE:     {{lang}}
LEVEL:        {{level}}
THEME:        {{theme_name}}
HS_SCORE:     {{hs}}
MODE:         {{integration_mode}}

CONTENT_DESCRIPTION:  {{content_brief}}

BREADCRUMB:   {{breadcrumb_array}}
DEEP_DIVES:   {{deep_dive_targets}}
SIBLINGS:     {{sibling_pages}}
LANG_PAIR:    {{lang_partner_filename}}
AUD_SWITCH:   {{audience_switch_placeholder}}

QUALITY_GATES: {{quality_instructions}}
            

The file agent prompt is the most granular template. It contains the exact filename and path, audience context, level, theme, HS score, content description, full breadcrumb path, deep-dive targets, sibling pages for bottom navigation, language partner filename, audience switch placeholder, and quality gates. The file agent needs no global view — it receives exactly the information needed for its one file, enabling parallel execution.

03

Variable Substitution

The orchestrator fills template variables with concrete values. The naming convention is critical — a wrong slug breaks all cross-links.

Naming Convention: [slug][suffix]_[lang].html

Step	Operation	Example
1. Take title	German theme title	"Ueberblick & Architektur"
2. Lowercase	Convert to lowercase	"ueberblick & architektur"
3. Replace umlauts	ae, oe, ue, ss	"ueberblick & architektur"
4. Remove specials	Keep only [a-z0-9-]	"ueberblick architektur"
5. Spaces to hyphens	Spaces become -	"ueberblick-architektur"
6. Append suffix	Audience suffix + language	"ueberblick-architektur_dev_en.html"

function slugify(title):
    slug = title.toLowerCase()
    slug = slug.replace("ä","ae").replace("ö","oe")
               .replace("ü","ue").replace("ß","ss")
    slug = remove_diacritics(slug)
    slug = replace(/[^a-z0-9]+/g, " ", slug)
    slug = trim(slug).replace(/\s+/g, "-")
    return slug

function build_filename(theme, audience, lang):
    slug = slugify(theme.name)
    return slug + audience.suffix + "_" + lang + ".html"

// Examples:
// "Phasen-Steuerung" + _dev + en
//   = "phasen-steuerung_dev_en.html"
//
// L0 Overview: always "index"
//   = "index_dev_en.html"
            

Slug derivation follows a fixed schema: German title is lowercased, umlauts become ae/oe/ue/ss, special characters are removed, spaces become hyphens. The result is a URL-safe slug. Special case: L0 overview pages always use "index" as their slug.

04

Quality Instructions in the Prompt

Every file agent receives a quality rules section that must be reflected in the generated HTML. Here is the complete quality gate template.

QUALITY_GATES:

// 1. WCAG AA Contrast
- NO white text on light backgrounds.
- Minimum contrast ratio: 4.5:1 normal text,
  3:1 large text (≥ 18pt or ≥ 14pt bold).
- Hero area: white on dark is OK (#000099 bg).
- Light backgrounds (#FFFFFF, #F3EFEB, #F8F5F2):
  text must be #1A1A2E or darker.

// 2. No level labels in titles
- Headings must NOT start with "L0:", "L1:",
  "Level 1:", etc.
- Wrong: "L2: Phase Control in Detail"
- Right: "Phase Control in Detail"

// 3. Tooltip requirements
- Mark terms with class="term" and
  data-tooltip="...".

// 4. Max 10 topics per level
- Overflow as paragraphs on parent page.

// 5. No dead links
- Every internal link must resolve to a
  generated file.

// 6. Level dots correct
- L3: [done] [done] [done] [active]
- Always exactly 4 dots.

// 7. Breadcrumb consistency
- Links must point to audience-specific variant.

// 8. Responsive design
- All layouts must work at 320px width.

// 9. Sibling nav format
- Current page: span.sibling-nav-current
- Other pages: a.sibling-nav-link
            

Quality gates are mandatory rules every file agent must follow:

WCAG contrast: No white text on light surfaces. On the dark hero, white is fine. On white or beige backgrounds, text must be dark (#1A1A2E).

No level labels: Page titles must not start with "L2:". The level is communicated through breadcrumbs and level dots.

Max 10: More than 10 pages per level makes navigation unwieldy. Overflow topics become paragraphs on the parent page.

No dead links: Every internal link must point to an actually generated file. The most common error source during generation.

✏️ Knowledge Check

In the naming convention, what suffix does the first/most general audience get?

_user — because Users are the most general audience

_default — as an explicit marker for the default view

No suffix — index_en.html, not index_user_en.html

🔧 Developer — All L3 Pages

01 Routing Logic 02 Thresholds 03 Pipeline Agent Prompts