bootstrap-projectlisted

# Bootstrap a project A worker can only be as good as the project it lands in. A fresh project has no `AGENTS.md`, no conventions, and none of the skills the work needs — so the worker guesses, the review has nothing to hold it to, and the result is generic. Fix that *before* delegating: give the project its context and its skills. ## When to use - Before the first delegation into a project, or any time a project has no `AGENTS.md`. - When the work needs a capability the project does not have — web design, framework specifics, testing, deployment, and so on. - When a worker's output was weak and the cause was a thin project context, rather than the worker. ## When not to use - The project already has a solid `AGENTS.md` and the skills this work needs. - A trivial, well-specified change in an established project. ## Inputs - The resolved project root (`multi-project-context`). - The work to be done, so you know which domain and stack matter. - Any existing `AGENTS.md`, `CONTEXT.md`, and project skills (`load-project-context`). ## Procedure 1. **Resolve and read.** Pin the project root, then read what already exists: `AGENTS.md`, `CONTEXT.md`, local skills, and the commands. Never overwrite the developer's context; merge into it. Record a durable allow rule for the project boundary (OpenCode applies it from the next session, so do this before the primary needs to read or write the project): ```bash python3 scripts/tm.py permissions allow --cw