flow-setuplisted

# Setup Install the Coding Flow project scaffold into the current repository, so the `/flow-plan` and `/flow-run` skills have rules, docs, and a harness to act on. This is the one-context alternative to running `init` yourself in a terminal: `/plugin install` then `/flow-setup`. ## When To Use - Right after installing the plugin, the first time you open a repo that does not yet have Coding Flow (`RULES.md`, `epics/`, `.coding-flow/`). - To re-check or repair an existing install. ## Steps 1. Confirm the working directory is the project root (the git repo root, or where `package.json` lives if there is one). Stop and ask if it is not. 2. Run the scaffold: ```bash npx @landry_pouth/coding-flow init ``` - `init` is **non-destructive by default**: it never overwrites your files. An existing file is left untouched, so re-running is safe. - If the project has no `package.json`, a minimal private one is created so the `flow:*` scripts work. 3. Read what `init` reports about the repo. It scans for an existing codebase on its own and says whether it found one — relay that verdict, and if it is brownfield, be explicit that the project docs are still empty: the scan is mechanical and does not document anything. `/flow-plan` (its Brownfield Bootstrap section) is what fills them. 4. Verify the install: ```bash npx @landry_pouth/coding-flow doctor ``` 5. Report what was created, then point to the next step: `/flow-plan` to turn an