| name | fieldnotes |
| description | Load Fieldnotes context and conventions. Use when starting work on any project or topic, when creating or updating project notes, or when the user asks about Fieldnotes structure or conventions. |
Fieldnotes
Fieldnotes is an Obsidian folder at $OBSIDIAN_VAULT/Fieldnotes ($OBSIDIAN_VAULT is an env var; falls back to ~/vaults/Main if unset) that supplements the auto-memory system.
Fieldnotes is shared — read and edited by both the user and the agent. Treat it as a collaborative workspace. Contrast with ~/.claude/projects/.../memory/, which is agent-only private notes.
What belongs in Fieldnotes
- Project information — goals, scope, constraints, current status, stakeholders, open questions, decisions and their rationale
- Structured knowledge — notes that build understanding of a domain, system, codebase, or workflow over time; things the user might revisit, share, or hand to a teammate
- Anything the user might want to read or modify themselves that doesn't fit in code, docs, or git
What does not belong in Fieldnotes
- Ephemeral task state or scratch work for the current conversation — use tasks/plans
- Personal preferences, feedback rules, durable facts about the user — those go in auto-memory
- Information already authoritative elsewhere (codebase, git history, GitHub, etc.) — link to it instead of duplicating
How to use it
Do all of the following proactively, without waiting to be asked:
- Read first. When starting work on a project or topic, check Fieldnotes for relevant notes before doing anything else.
- No prescribed structure. Organize however the content suggests; let conventions emerge. Prefer extending existing notes over creating parallel ones.
- Create when missing. If there is no Fieldnote for a project or topic you're working on, create one.
- Update as you learn. When something changes — a constraint, a decision, a deadline, new context — update the relevant note rather than letting it go stale.
- Update after completing work. At the end of a task, review relevant Fieldnotes and bring them up to date.
- Write for a human reader. Use clear prose and Markdown that renders well in Obsidian. Avoid agent-only shorthand.
