setup-context-system: offer Atlassian MCP setup in Phase 2.5

skills/setup-context-system/SKILL.md

@@ -200,11 +200,33 @@ For each domain the user has real content for, draft a small focused file. Show
 
 Offer this only after Phase 2 (imported content needs a home). Skippable.
 
-### Step 2.5.1 — Detect
+### Step 2.5.1 — Detect, and offer to set up the MCP
 
 Check whether Atlassian MCP tools are available in this session.
-- **Not available** → explain: "Connecting an Atlassian (Confluence/Jira) integration lets me pull your existing docs straight into context files. You can connect it and re-run this step later." Mark as deferred; continue.
+- **Available** → proceed to Step 2.5.2.
-- **Available** → proceed.
+- **Not available** → offer to set it up: "Connecting an Atlassian (Confluence/Jira) integration lets me pull your existing docs straight into context files. Want to set it up now?"
+
+If the user wants to set it up, give the install method for the **detected platform** (verify the current method against the platform's MCP docs — methods change; do not hardcode from memory). The Atlassian remote MCP endpoint is `https://mcp.atlassian.com/v1/mcp`.
+
+- **OpenCode** — add to the user's `opencode.json` under `mcp`, then authenticate:
+  ```json
+  {
+    "mcp": {
+      "atlassian": { "type": "remote", "url": "https://mcp.atlassian.com/v1/mcp" }
+    }
+  }
+  ```
+  Then run `opencode mcp auth atlassian` to complete the OAuth flow. (Source: https://opencode.ai/docs/mcp-servers)
+- **Claude Code** — run:
+  ```bash
+  claude mcp add --transport http atlassian https://mcp.atlassian.com/v1/mcp
+  ```
+  Then run `/mcp` and follow the browser login to complete OAuth. (Source: https://docs.claude.com/en/docs/claude-code/mcp)
+- **Other platforms** — point the user to that platform's MCP-server docs; the endpoint is the same.
+
+Present the config/command and let the user run it — do not edit their MCP config or run auth silently. OAuth requires a browser step the user must complete. After setup, the Atlassian tools load on the next session (or after re-auth); if they aren't available in the current session yet, mark this step as deferred and tell the user to re-run Phase 2.5 once connected.
+
+If the user declines setup, mark as deferred and continue.
 
 ### Step 2.5.2 — Scope the pull