Change Bill Proposals to Be More Like Engineer Project Proposals with Requirements of Data, Metrics, Feedback, and Analysis

When politicians propose policies and bills, there often is a lack of evidence, data, and even common sense. The idea for this policy is when bills are proposed to the Congress or House of Representatives, politicians need to address, propose, and present the bills/policies with all forms of data much like an engineer would for an engineering project.
A long example can be: what is the mission, what is the intended outcome, what are consequences, what will it improve, what is the research, 5Ws (Who, what, where, when, why, and how), how can they make it happen, what is the feedback, what are the disagreements, how much will it cost, what is the cost break-down, what is the project break-down, what is the time scale, what is the projected timeline and estimated date of delivery, what is the swot (strength, weakness, opportunity, threat) analysis, what metrics can they use for testing and review, what are the hurdles and obstacles, what are the requirements and tools, who is on the team, who is associated with the idea and why, what are the legal challenges, how can security/bug testing be done (what are ways people manipulate or take advantage of imperfections and how to keep important areas secure), What are the testing timeframes for quality assurance, what are the logistics, how to conduct the test iterations (there should also be initial test iteration to present when pitching the proposal), and all the other data which is required to get the policy made and implemented with precision with its desired outcomes.
Overall, if we want better bill proposals for things with better impact to improve the United States, I believe this is the way to do it. With cold hard data, metrics, evidence, and complete research, explanations, and analysis.