feat: add file resolution context for IDE agents

- Added file resolution section to SM agent explaining path patterns
- Created reusable file-resolution-context.md utility
- Documents how agents resolve tasks/templates/checklists to file paths
- Provides natural language to command mapping examples
- Helps IDE agents understand file system structure

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

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Brian Madison
2025-06-19 13:02:17 -05:00
parent aea7f3cc86
commit 74d9bb4b2b
2 changed files with 126 additions and 0 deletions

View File

@@ -46,4 +46,43 @@ 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