# K-04 — Explore → Plan → Code → Verify → Commit
# Category: KEY
# Kapitel: 01 §1.5 / 15
# Anker: Philosophie Explore–Plan–Code–Verify
# Orientierung: 16:9 landscape
# Didaktik: Phasengrenzen als Fehlerbremse; Plan Mode stoppt vor dem großen Diff.
# Caption (DE): Phasengrenzen sind billige Sicherungspunkte — Plan Mode stoppt vor dem Diff.
# Language: English (Gemini / Imagen)
# Usage: paste entire prompt body below into Gemini

--- PROMPT START ---
Create a clean educational technical illustration, 16:9 landscape.

GLOBAL STYLE:
- flat vector + soft 3D depth; night navy (#0B1B2B), cyan (#2EC4FF), soft violet (#8B7CFF), off-white panels, slate grays
- minimal English labels (2–6 words); no brand logos; no photoreal UI; no watermarks; generous print margins; high contrast
- book context: Grok Build practice guide (agentic coding harness); never Claude Code titles

Title concept: "Explore → Plan → Code → Verify → Commit".

Composition:
- Horizontal main flow of five rounded stage nodes with icons:
  Explore (map), Plan (blueprint / plan file), Code (wrench / diff), Verify (checkmark / test flask), Commit (git commit node).
- Soft cyan progress arrow left-to-right.
- Plan node highlighted with “read-only except plan file” badge.
- From Code and Verify, a dashed violet return arc labeled “on fail: step back” looping back toward Explore/Plan.
- Under each stage, short outcome labels: “map”, “approval”, “narrow diff”, “green tests”, “human ownership”.

Print-ready workflow figure for a technical practice book.

--- PROMPT END ---
