Problem:
I often need to design with the future in mind, I need to be considering the product several releases ahead of dev. When it is time to share designs with the dev team we often spend a good portion of our conversation going over what the requirements are for the current release. Developers need to make sure what is required of them for the next release and it seems there is no way around this conversation except to spend time just removing things from the designs which I never do because, well, time.

Example:
1. My designs might include an extra filter or sort option that is not yet ready to be hooked up by dev. I still want it in the design but there is no need for it to be presented to devs yet.

1. The product has a feature that doesn't come until a couple releases later. Devs would need to see it to plan ahead but when sharing designs for their current work it would be nice to switch it off easily.

I know this is a challenging one and could be solved in a variety of different ways (simply tagging layers with ability to show/hide entire tag with one click, OR being smart by adapting the designs when an entire feature is hidden, or allowing designers to reuse features from previous releases but with ability to create new release branch of sorts while maintaining sync throughout each release branch to allow the ability for the designer to work ahead).

Thanks for receiving this request, I think it could really change the way designers work and help focus the conversations that us the valuable time of the team.