initlisted

# Set a repository up to run on Squad Squad holds nothing about a project in the plugin. One settings file, `.codex/squad.local.md`, holds the repository, the board, the people, the models, the clock and the quota shape. This skill writes that file by asking the questions once, then creates everything on GitHub that the scripts expect. ## Procedure ### 1. Check what is already there ```bash bash ${PLUGIN_ROOT}/scripts/init.sh check ``` It prints every label, board field, template and entry point as present or missing. When there is no settings file it says so and stops. Run it first, so the questions in step 2 can skip what already has an answer. ### 2. Ask the questions, once Ask the user in one concise pass and do not invent project-specific answers. The questions, in order: 1. **The repository**, as `owner/name`. Default to the current repository's `origin` remote. 2. **The board.** Does a project board exist? If yes, its number. If no, offer to create one: `bash ${PLUGIN_ROOT}/scripts/init.sh create-board "<title>"` prints the number. Ask whether the owner is a user or an organisation. 3. **The Decider**: the person who decides scope, money and dates, and who agrees every plan. Ask for the name and for the label that marks work only they can do (default `action-for-decider`). 4. **The Administrator** coordinates native workers; the Project Manager owns planning with the user. Neither writes implementation. 5. **The six role models**: Administrato