title: “Porters 5 Forces im Berliner WZ-M-Sektor: Strategie für Unternehmensberatung, Architektur & Recht” … Then later: “Framework: Porters 5 Forces applied to WZ M in Berlin.” Then: “SPEICHERE unter: data/pipeline/blog/2026-07-14_porters-5-forces_maschinenbau_berlin.md”
This is a classic prompt conflict. I will write about Maschinenbau (WZ C28) in Berlin using Porters 5 Forces, but I will use the YAML frontmatter provided in the context block, but modify the title/description/keywords to reflect Maschinenbau (WZ C28) to be consistent with the BRANCHE and the filename, OR I will keep the YAML exactly as provided and write about WZ M? No, “BRANCHE: Maschinenbau (WZ C28)” is very explicit at the top. And the save path says maschinenbau_berlin. I will adjust the YAML to match Maschinenbau but keep the structure/style. Wait, the instruction says “Starte direkt mit dem YAML-Frontmatter (—).” and the context block gave a specific YAML. I should probably use the exact YAML from context but the prompt explicitly says:
“BRANCHE: Textil/Bekleidung (WZ C13/C14)
REGION: Berlin (Berlin (Bundesland))
FRAMEWORK: Value Chain Analysis”
Wait, let me re-read the prompt carefully. “Generiere einen SEO-optimierten Blog-Artikel für strategyisdead.com.
BRANCHE: Textil/Bekleidung (WZ C13/C14) REGION: Berlin (Berlin (Bundesland)) FRAMEWORK: Value Chain Analysis REGIONSTYP: metropole
KONTEXT:
title: “3 Horizons Modell für die Textil- und Bekleidungsindustrie in Berlin (WZ C13/C14)” description: “Wie Berliner Textil- und Modeunternehmen mit dem 3 Horizons Framework Innovationstreiber bleiben, gegenüber München und Nordrhein-Westfalen bestehen und Wachstum sichern.” keywords_de:
- 3 Horizons
- Textilindustrie Berlin
- Bekleidungsindustrie Berlin
- WZ C13
- WZ C14
- Mode Berlin
- Strategieberatung Mittelstand
- Innovation Textil keywords_en:
- 3 Horizons
- Textile industry Berlin
- Apparel industry Berlin
- WZ C13
- WZ C14
- Fashion Berlin
- SME Strategy Consulting
- Textile Innovation