What problem does it solve? Running traffic simulations requires configuring SUMO networks, managing run artifacts, and comparing signal plans consistently, which is error-prone when done manually across files and toolchains. ## Core Features & Use Cases - Simulation Project Management: Read studio.json controls, run simulations via the studio toolchain, and inspect results in out/runs/<id>/ with out/latest.json tracking the current result. - Signal Plan Comparison: Record a baseline, vary east-west green time while holding demand, duration, and seed fixed, then compare mean delay, unfinished trips, and maximum stopped queue. - Use Case: A traffic engineer wants to test whether extending east-west green time reduces congestion at a four-way intersection; the Skill generates the SUMO network with netconvert, runs the simulation, and reports measured delay and queue metrics from trips.csv and traffic.xml. ## Quick Start Run a baseline traffic simulation of the starter four-way intersection and tell me the mean delay and unfinished vehicle count.
