executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
searchSearch vault content by keyword using Grep. Zero dependencies — works in any vault without indexes or plugins. Groups results by directory for easy scanning.
Independent GitHub snapshot · Automated classification · Original documentation governs
Fast keyword search across all vault markdown files using the Grep tool. No indexes, no plugins, no setup — just structured search with directory grouping.
/search <term>
Examples:
/search project planning/search weekly review/search TODOWhen the user invokes /search <term>:
Use the Grep tool to search all .md files for the term:
Grep:
pattern: <search term>
glob: "*.md"
output_mode: content
-n: true
-C: 1
Exclude hidden directories (.claude/, .obsidian/) and templates:
Grep:
pattern: <search term>
glob: "*.md"
path: .
output_mode: content
-n: true
-C: 1
Filter out results from .claude/, .obsidian/, and Templates/ directories.
Organise matches into sections by their parent directory:
Format output as:
## Search: "<term>"
### Daily Notes/
- **2024-01-15.md** (line 23): ...matching context...
- **2024-01-14.md** (line 8): ...matching context...
### Projects/
- **Project Alpha.md** (line 45): ...matching context...
### Goals/
- **2024 Goals.md** (line 12): ...matching context...
**Found X matches across Y files**
After showing results, check if any matched files contain [[wiki-links]] to other notes. If so, briefly mention:
💡 Related notes mentioned in results: [[Note A]], [[Note B]]
If no matches are found:
Archives/ if not already included-i: true to the Grep call for case-insensitive searchtask.*complete, #tag-name/daily to quickly find when something was mentioned