BT Subtrees for Reusable Autonomy

Source: ros2-copilot-skills subtree composition skill

Why This Matters

Behavior trees scale poorly if every behavior lives in one file. Subtrees are how autonomy starts to become modular: reusable patrol logic, recovery bundles, shared task sequences, and clearer ownership of behavior pieces.

Distilled Takeaways

• Subtrees are the main structural tool for keeping large BT systems understandable.
• Reuse matters not just for convenience but for consistency across behaviors.
• Blackboard naming and interface discipline become more important as subtrees proliferate.
• Good subtree boundaries often follow robot tasks or reusable decision patterns.

Practical Guidance

• Extract repeated patterns into named subtrees early.
• Keep subtree interfaces narrow and explicit.
• Use subtrees to express autonomy architecture, not just to split a long file.
• Watch for hidden blackboard coupling between subtrees.

Corroborating References

• BehaviorTree.CPP docs
• Nav2 behavior tree docs

When to Read the Original Source

Go to the original skill when you want the subtree composition patterns and practical blackboard-remapping guidance for larger Nav2 behavior-tree systems.