What problem does it solve? Creating a new gz-sim system plugin requires boilerplate across many files — a header, source file, local CMakeLists, parent CMake registration, plugin alias, integration test, example world, and changelog entries. Missing any step produces a plugin that fails to load or is invisible to users. ## Core Features & Use Cases - Complete plugin scaffolding: Generates the header and source templates implementing ISystemConfigure, ISystemPreUpdate, and ISystemPostUpdate with PIMPL via GZ_UTILS_UNIQUE_IMPL_PTR. - Build system integration: Provides the gz_add_system CMake snippet and the add_subdirectory registration in src/systems/CMakeLists.txt. - Testing and documentation: Includes a minimal TestFixture-based integration test, an example SDF world, and reminders for Migration.md and Changelog.md updates. - Use Case: When adding a new controller like a wheel-slip system to the simulator, follow the steps to produce src/systems/wheel_slip/WheelSlip.{hh,cc}, register it in CMake, and verify it loads with a TestFixture test. ## Quick Start Ask the assistant to create a new gz-sim system plugin named fancy_drive and it will generate the header, source, CMake glue, and test stub following this guide.
