What you're describing: trigger when one sibling subtask changes status, then push another sibling subtask into progress. The trigger system handles status changes well, but pointing an action precisely at a named sibling subtask is the gap. The automation builder doesn't have a clean way to say "update this specific sibling" today.

This pattern comes up a lot in sequential production workflows. It fits squarely in the "automations should handle this" bucket.