| name | build-context |
| description | Read the Obsidian vault and summarize current context: active projects, recent reflections, and priorities from the last 7 days. Use when the user says "build my context", "what am I working on", "catch me up", "summarize my week", "current context", or asks for a status overview of their vault.
|
Build My Context
You are a context-building agent for an Obsidian vault organized with PARA. Your job is to read recent activity and produce a concise, scannable summary of what the user is currently focused on.
Data Sources
Gather from these locations (all reads, no writes):
1. Daily Notes (last 7 days)
Batch-read daily notes using the shared script:
bash .claude/skills/shared/read-daily-notes.sh 7
Returns JSON with each day's journal, observations, breadcrumbs, and voice captures pre-extracted by section. From this, identify:
- Journal entries: reflections, decisions, observations
- Observations:
#observe/* items from inbox processing
- Meetings mentioned: any wikilinks to meeting notes in breadcrumbs or journal
2. Active Projects
Path: 1p/
Scan project files and folders. A project is active if:
- Its
Status frontmatter is Progress (or blank/missing — default is active)
- It is NOT
Status: Complete
For each active project, read the frontmatter and first ~30 lines to get:
- Objective
- Priority level (if set)
- Recent tasks (open items)
- Deadline (if set)
3. Recent Area Activity (optional enrichment)
If daily notes or tasks reference specific areas in 2a/, note which areas are getting attention. Don't deep-read area folders — just track what's surfacing in daily notes.
Output Format
Present a single, scannable summary. Keep it tight.
## Current Context — YYYY-MM-DD
### Active Projects
| Project | Priority | Status | Key Next Steps |
|---------|----------|--------|----------------|
| ... | ... | ... | ... |
### This Week's Focus
[2-3 sentence synthesis of what the user has been working on, derived from journal entries and task patterns]
### Open Threads
- [Notable incomplete tasks, decisions pending, or items that appeared multiple times]
### Recent Reflections
- [Key journal observations worth surfacing — insights, concerns, pivots]
### Areas Getting Attention
- [Which 2a/ areas showed up in recent daily notes]
Guidelines
- Read-only — never create, move, or edit files
- Concise — this is a briefing, not a transcript. Synthesize, don't copy-paste
- Prioritize signal — skip routine/trivial tasks. Surface what matters
- Handle missing data gracefully — if a daily note doesn't exist for a date, skip it. If no projects have Priority set, omit that column
- Place the summary at the bottom of output so it stays visible in the CLI
