opencode-foremanlisted

# Delegating implementation to OpenCode You keep the plan and the review. OpenCode's executor model does the typing. Work lands only after you have read the diff. Delegate when the task is **mechanical and self-contained**: a scripted transformation, tests for an existing module, a bounded refactor, bulk classification, boilerplate. Do it yourself when the task needs cross-file reasoning, novel architecture, or touches anything irreversible. ## Preflight ```bash foreman up # idempotent; prints the running version ``` If `foreman` is missing, say so and stop — do not fall back to editing the files yourself without telling the user. ## The loop **1. Write a self-contained prompt.** The executor gets none of this conversation. State the file paths, the expected behaviour, and how it can verify itself. Vague prompts are the main cause of unusable output. **2. Dispatch.** Always isolate, always deny by default: ```bash foreman dispatch --worktree --deny '<paths that must not change>' \ --profile pro "<the full task>" ``` - `--profile pro` for implementation, `--profile flash` for search, classification, or high-volume mechanical passes. - `--allow-bash` only when the task genuinely needs to run tests or tooling. It is off by default. - Add `--deny` for every path where a wrong edit would be expensive. The rule is enforced by the server, and `dispatch` prints the ruleset actually in force — read that line back and confirm it covers what you intended. *