Octopus Deploy does not currently enforce the completion of all steps in all environments. This leads to at least two scenarios that may not represent the desired workflow:

1. Steps skipped in previous environments are not necessarily skipped in later environments
   e.g. a database script was not applied in Integration but was applied in User Acceptance Testing, when the intention was for User Acceptance Testing to have skipped the same steps that were skipped in Integration to ensure both environments are the same.

2. Promotions can take place when steps have been skipped in previous environments
   e.g. a database script was not applied in Integration and the deployment was promoted to User Acceptance Testing with the database script applied, when the intention was for all steps to be completed in a previous environment before a promotion could occur.

This idea is to provide some means to enforce that either the same steps are skipped in all environments, or all steps are completed before a promotion can take place to the next environment.