The 7-phase execution model of the skill — from bootstrap to transparency report
The orchestrator controls the entire generation process through seven sequential phases. Each phase has clearly defined inputs, outputs, and abort conditions. No phase may be skipped — the skill enforces the order.
Design decision: Phases 0–3 run strictly sequentially. Phase 4 contains parallel sub-pipelines per audience. Phases 5–6 are post-processing steps that operate on the complete output of all pipelines.
The preparation phases run strictly sequentially. Each phase must complete fully before the next begins. By the end of Phase 2, the complete curriculum for all audiences is ready.
git clone is executed.Deep codebase understanding: the skill reads all relevant files, traces data flows, and identifies the "main characters" of the software — core modules, API endpoints, configuration files, and their relationships.
A separate curriculum is created for each audience. Every module receives a Helpfulness Score (HS) that determines whether a drill-down page is built.
Helpfulness Score (HS): Each topic is scored individually for each audience. The formula weighs four factors: relevance to the role, topic complexity, number of dependencies, and source code depth. Developer topics weigh complexity and dependencies more heavily; decision-maker topics weigh relevance and source depth more. A score of 7 or above triggers the creation of a dedicated drill-down page.
The CSS/JS foundation is created once and then embedded into every HTML file. The self-contained principle: every file is fully standalone — no external stylesheets, no bundlers, no build step.
:root. Changes in one place propagate globally.transform.Self-Contained Principle: Phase 3 produces a complete CSS/JS foundation with 18 color variables, 3 font stacks, 10 size steps, 12 spacing values, and all component classes (modules, cards, visualizations, quizzes, navigation). Plus four JavaScript systems: scroll animations, quiz engine, tooltips, and progress bar. This entire package is copied into the <style> and <script> block of every single HTML file.
Order constraint: Phase 3 must complete before any HTML generation. The orchestrator checks this explicitly — if the foundation does not exist, Phase 4 will not start.
The key innovation of the skill: each audience gets its own independent pipeline. Pipelines can run in parallel (in practice often sequential, as LLM context is limited). Within a pipeline, levels are built one at a time.
Pipeline Overview: Audiences × Depth Levels
Pipeline logic: Each audience progresses through its levels sequentially (L0 must be complete before L1 begins). Within a level, themes and language versions can be built in parallel. Pipelines of different audiences are fully independent — the Developer pipeline can already be at L2 while the Decision-Maker pipeline is still generating L0.
Can the Developer pipeline build L2 while the Decision-Maker pipeline is still on L0?
The final two phases operate on the complete output of all pipelines. Phase 5 ensures consistency, Phase 6 produces the transparency report.
tiefenkarte.html
Depth Map: The transparency report lists for each audience which topics were built at which levels, which were skipped, and why. Each topic includes its HS score and the specific stop reason (e.g., "threshold not met" or "maximum depth reached").