atlas-projectlisted

# Make or change a project Tools: `atlas`, `project` on the atlas MCP server. A project is a folder `atlas/<name>/` inside the user's work, a repository or a folder of documents. The folder takes the project's name. It holds the project's identity, its threads, its phases, and an inbox for notes. It has no git of its own: when the work is a repository, the repository tracks `atlas/` like any other folder. It uses one knowledge base. Call `atlas` first: the knowledge bases and their scopes, and the projects that exist. ## Make one Ask one question at a time. Offer the default; accept a yes. 1. **Where.** The current folder, when the session is in the work. Otherwise the path the user names. Never a folder inside a knowledge base or inside another project. 2. **Name.** Default: the folder's name. 3. **Description.** One sentence saying what the project is. Draft it from the folder's README or CLAUDE.md when there is one, and read it back. 4. **Knowledge base.** Read each scope from `atlas` and suggest the one that fits. None is a valid answer; the thread skills work without one, and `link` adds one later. State the whole change in one line. When the folder is in no git repository, init makes it one, with no commit; say so in the line: > Make `~/code/webapp` the project `webapp`, "The customer-facing web application for the fire-detection product", using `product-x`? On yes: `project` with `action: init`, `work`, `name`, `description`, and `knowledge`; add