diagram-reports-generator

Diagram and MicroSim reporting automation scans chapter markdown files to extract visual element metadata, then generates comprehensive reports tracking implementation status, Bloom's Taxonomy levels, UI element counts, and estimated difficulty. This skill parses chapters and produces table and detailed markdown views registered in MkDocs, eliminating manual tracking across large projects.

Automated diagram audits track element type, implementation status, learning objectives, Bloom's Taxonomy classification, UI element count, and estimated difficulty. The skill extracts these metrics from chapter markdown and compiles them into both summary tables and detailed reports for comprehensive visibility.

Yes. The skill generates both markdown table and detailed markdown reports by default, with support for CSV and HTML output formats. All reports are produced from a single scan of chapter files and automatically registered in MkDocs navigation.

Diagram reports integrate by parsing chapter markdown files directly, outputting reports to docs/learning-graph, and registering navigation entries in MkDocs. This keeps visual element tracking synchronized with course structure and makes reports discoverable within existing documentation.

Chapter markdown files must follow a structure where diagrams and MicroSims include Type, Status, Learning Objectives, Bloom's Taxonomy level, and UI element metadata. The skill parses these fields to populate reports, so consistent markdown formatting across chapters ensures accurate auditing.

Automated tracking becomes essential when manually monitoring diagrams and MicroSims across multiple chapters becomes error-prone and time-consuming. It's particularly valuable for projects managing dozens of interactive elements where status, complexity, and pedagogical alignment must stay current for project oversight.