Nav2 BT Condition Nodes

Source: ros2-copilot-skills BT condition nodes skill

Why This Matters

Condition nodes decide how the tree branches under real robot state, and bad condition design can make a tree feel unstable or opaque. In Nav2, conditions are where state observation turns into control-flow choice.

Distilled Takeaways

• Condition nodes should reflect meaningful robot state, not accidental implementation details.
• They are critical for recovery gating, goal progress, path validity, and environment-aware branching.
• Poorly chosen conditions can cause oscillation between branches or premature recovery.
• The behavior tree becomes easier to reason about when conditions are explicit and semantically narrow.

Practical Guidance

• Use condition nodes to make tree decisions readable and debuggable.
• Prefer a few clear state checks over complicated implicit logic in action nodes.
• Watch for repeated branch flipping as a sign of weak condition design.
• Treat conditions as part of the autonomy contract, not just tree plumbing.

Corroborating References

• Nav2 behavior tree docs
• BehaviorTree.CPP docs

When to Read the Original Source

Go to the original skill when you want the built-in Nav2 condition-node inventory and practical reminders about where each condition fits in real trees.