setup-agent-docslisted

# Setup Agent Docs Run this setup once per repository when the user wants explicit paths for artifacts written by the project skills in this collection. It may be invoked directly or as the delegated final documentation step of `setup-project`, and it must remain safe to run again. Keep this skill model-invocable because `setup-project` calls it through the agent's skill tool. The already explicit parent setup request authorizes this narrow documentation step; it does not authorize any broader project mutation. Scope: only project skills produce repository artifacts. Personal-use skills such as `disk-cleaner` and `grey-market` operate on the user's machine, not on a repository, never configure paths, conventions, or guidance for them. ## Workflow 1. Inspect existing guidance and conventions before proposing anything: - `AGENTS.md` - `CLAUDE.md` - `.gemini/rules/agents.md` - `CONTRIBUTING.md` - existing architecture and documentation directories - existing glossary, ADR, research, handoff, and prototype paths 2. Reuse established paths where they are clear. Ask only which still-unconfigured artifact types the user actually wants. 3. Suggested defaults when no convention exists: - domain glossary: `CONTEXT.md` - ADRs: `docs/adr/` - research: `docs/research/` - handoffs: `.scratch/handoffs/` - prototypes: `.scratch/prototypes/` 4. Show the short configuration block before writing it. 5. Record only selected conventions in existing repository