atelier-setuplisted

# Atelier Setup Set up repository guidance that Atelier skills need without taking ownership of the developer's installation, harness configuration, or project structure. Explore first, present every proposed edit exactly, and write only after the developer approves it. ## 1. Explore Read the repository before proposing any change: - Root `AGENTS.md` and `CLAUDE.md`, if present. Note whether either already has an `## Agent skills` heading. - Root `CONTEXT.md` and `CONTEXT-MAP.md`. - `docs/adr/` and any context-local `docs/adr/` directories. - `docs/agents/`, including existing `issue-tracker.md` and `domain.md`. - Existing issue-tracker conventions: remotes, issue links in documentation, local issue directories, and project guidance. - Genuine monorepo signals: a workspace manifest, or multiple independently deployable packages with their own source directories. Do not create, install, configure, or modify anything during exploration. ## 2. Present Findings Summarize what exists and recommend a domain-document layout: - **Single-context** is the default: domain language belongs in root `CONTEXT.md`; architectural decisions belong in root `docs/adr/`. - **Multi-context** is appropriate only when the repository has genuinely separate bounded contexts. `CONTEXT-MAP.md` belongs at the root and points to each context's `CONTEXT.md` and `docs/adr/` directory. Explain that domain documents remain lazy: do not create `CONTEXT.md`, `CONTEXT-MAP.md`, or an ADR dire