Plan a one-command local development setup

Plans a local development setup a new teammate can start with one command, in numbered steps with a check after each one.

Task: Plan how to get my project to start on a new machine with one command, in numbered steps. Context: The project is [language and framework] with the services [database, queue, other services]. Today a new teammate needs [number of manual steps] manual steps and about [hours] hours. The team uses [macOS, Windows or Linux]. Rules: - Start from the manual steps I list and turn each one into a script, a container or a check. - Add a check after every step that shows whether it worked. - Keep real secrets out of the repository. Use an example env file with fake values and say where each real value comes from. - Ask for no keys or passwords in the chat. - Mark any step that deletes data, such as resetting the local database, and say what it removes. Result: A numbered list of at most 8 steps, each with the action, the check and the one thing most likely to go wrong. End with the single command a new teammate runs. Material: [list the manual setup steps you do today]

Updated