In order to stabilize automated UI tests without halting development on new features, developers can build a test skeleton into their current framework. This approach avoids creating a manual test suite and instead focuses on defining test plans, unit testing, and UI testing while still manually running through tests during the sprint. Automated UI tests are temporarily disabled with a comment describing the goal of the test, allowing teams to identify which tests need to be executed manually. The test skeletons can be easily identified and refined as needed, and once stabilization is achieved, the automated tests can be enabled and converted from manual tests, minimizing overhead and conversion costs.