Generate a ROS 2 design contract with node specs, interfaces, and PlantUML diagrams.
npx skills add https://github.com/robotics-playground/skills --skill ros2-design
Please help me install this Agent Skill. Skill: ros2-design Source: https://github.com/robotics-playground/skills/tree/main/skills/ros2-design Command: npx skills add https://github.com/robotics-playground/skills --skill ros2-design
ROS 2 design teams often struggle to align on a single, implementable contract before coding. This skill provides a structured blueprint by generating a designs/ tree containing per-node specs, custom interfaces, a package-structure document, and PlantUML diagrams that communicate architecture and data flows for a robotics project.
Provide the PRD, architecture, and hardware docs to generate the full ROS 2 design tree under designs/ with node specs, interfaces, package structure, and PlantUML diagrams.
High-intent search queries and answers about installing and using this skill.
To generate a ROS 2 design contract, provide your PRD, architecture, and hardware docs. The tool outputs a designs/ tree containing node specs, custom interfaces, and a package structure ready for downstream implementation.
Visualizing ROS 2 node architecture uses PlantUML diagrams embedded as SVGs. The generation process creates node-map and data-flow diagrams directly within the design files to communicate architecture effectively.
Traceability from functional requirements to ROS 2 packages is ensured by mapping FRs directly within the generated design tree. This structured blueprint links each requirement to its corresponding package and node design files.
Yes, you can automatically generate a complete ROS 2 package structure. By processing your architecture and hardware documents, the tool produces a structured package-layout document within a designs/ subtree.
You do not need to provide custom interfaces upfront. The skill generates custom interfaces definitions alongside node designs by analyzing the provided PRD, architecture, and hardware documentation.
PlantUML diagrams for ROS 2 architecture are limited to static node-map and data-flow visualizations embedded as SVGs. They communicate structure effectively but do not simulate runtime behavior or dynamic message routing.
sandraschiDesign ROS 2 architectures, integrate sensors, and implement navigation stacks.
DevHammad0Generate ROS 2 Python node templates with publisher/subscriber patterns.
cloud-native-toolsGenerate UML and specialty diagrams from PlantUML syntax.
ayeshakhalid192007-devGenerate ROS 2 .msg and .srv interface definitions with package structure.
