refactor: simplify file resolution to concise activation instructions

- Added two concise activation instructions to SM agent
- IDE-FILE-RESOLUTION: One-line explanation of file path mapping
- REQUEST-RESOLUTION: One-line instruction for flexible request matching
- Simplified file-resolution-context.md to be a quick reference
- Removed verbose documentation in favor of clear, actionable instructions

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

bmad-core/agents/sm.md

@@ -8,6 +8,8 @@ activation-instructions:
   - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
   - The customization field ALWAYS takes precedence over any conflicting instructions
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+  - IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}.md where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
+  - REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task), or ask for clarification if ambiguous.
 agent:
   name: Bob
   id: sm
@@ -46,43 +48,4 @@ dependencies:
     - story-draft-checklist
   utils:
     - template-format
-    - file-resolution-context
 ```
-
-## File Resolution Context (IDE Integration)
-
-When working in an IDE environment, understand these file resolution patterns:
-
-### Base Path
-
-- The `root` field (line 6) defines the base path: `.bmad-core`
-- All file references are relative to this root directory
-
-### Dependency Resolution
-
-All items under `dependencies` follow a folder/file hierarchy pattern:
-
-- **Tasks**: `{root}/tasks/{task-name}.md`
-  - Example: `create-next-story` → `.bmad-core/tasks/create-next-story.md`
-- **Templates**: `{root}/templates/{template-name}.md`
-  - Example: `story-tmpl` → `.bmad-core/templates/story-tmpl.md`
-- **Checklists**: `{root}/checklists/{checklist-name}.md`
-  - Example: `story-draft-checklist` → `.bmad-core/checklists/story-draft-checklist.md`
-- **Utils**: `{root}/utils/{util-name}.md`
-  - Example: `template-format` → `.bmad-core/utils/template-format.md`
-
-### Command Mapping
-
-When users request actions, understand these equivalences:
-
-- "draft the next story" = `*draft` = `*create` = execute task at `.bmad-core/tasks/create-next-story.md`
-- "show story checklist" = `*checklist story-draft-checklist` = display `.bmad-core/checklists/story-draft-checklist.md`
-
-### Working with Files
-
-When executing tasks or accessing dependencies:
-
-1. Always resolve the full path from the dependency name
-2. Read the file content from the resolved path
-3. Execute the instructions contained within
-4. Reference templates using their full resolved paths