add-datasource

1> **Plugin check**: Run `node "${PLUGIN_ROOT}/scripts/check-version.js"` - if it outputs a message, show it to the user before proceeding.
2 
3**📋 Shared instructions: [shared-instructions.md](${PLUGIN_ROOT}/shared/shared-instructions.md)** — read first.
4 
5# Add Data Source
6 
7**Entry routing:** use the shared [App feature entry points](../../shared/shared-instructions.md#app-feature-entry-points)
8preflight before the workflow below.
9 
10**Invocation scope:** follow [Data-source invocation scope](../../shared/shared-instructions.md#data-source-invocation-scope)
11before any project read or the workflow below. Resolve the absolute app root
12before reading memory-bank. Routing selects a data workflow, not implementation
13approval or a full-app integration workflow.
14 
15Router skill that understands the user's goal and connects them to the right data source — without requiring them to know Power Platform terminology.
16 
17## Workflow
18 
19### Check Memory Bank
20 
21Check for `memory-bank.md` per [shared-instructions.md](${PLUGIN_ROOT}/shared/shared-instructions.md).
22 
23### Understand the Goal
24 
251. **If `$ARGUMENTS` is provided or the caller already specified what's needed**, use it directly and skip the question below.
262. Otherwise, ask the user **what they want their app to do** — not which connector to use. Focus on the end goal. Example questions:
27   - "What kind of data does your app need to work with?"
28   - "What should your app be able to do? (e.g., search company info, manage tasks, send messages)"
29…