BrainRepo

**Judgment** BrainRepo is a well-designed, opinionated PKM/second-brain skill that leverages a fixed local Markdown/Git repository. It’s technically sound, conceptually coherent (PARA + Zettelkasten), and suitable for long-term personal knowledge management with AI assistance. **Strengths & Functionality** - Enforces a clear structure at `~/Documents/brainrepo/` with standard folders (Inbox, Projects, Areas, Notes, Resources, Journal, People, Tasks, Archive). - Solid lifecycle: **Dump** to Inbox → **Process** in daily/weekly reviews → **Retrieve** via search and structured queries. - Onboarding is explicit: checks for existing repo, creates directories and seed templates, and can optionally `git init` for versioning. - Provides concrete user-facing commands (setup, save, new project/person, daily/weekly review, “what do I know about X?” retrieval). **Risks & Limitations** - **Fixed path, not configurable:** All data is forced into `~/Documents/brainrepo/`. This is simple but may clash with existing setups or user preferences; migration or multi-brain setups are not supported. - **Plaintext sensitivity:** Users may store highly sensitive information in unencrypted Markdown and optionally in a Git history, which is convenient but not privacy-hardened. - **Template & tooling assumptions:** Onboarding assumes templates exist in `assets/templates/` and that Git is available for optional initialization; missing dependencies could degrade behavior. - **User discipline required:** The system’s effectiveness depends heavily on regular daily/weekly reviews and consistent usage; without that, Inbox clutter and outdated tasks/areas are likely. **Recommended Scenarios** - Individuals who already use or want to adopt Obsidian/VS Code + Markdown for a personal second brain. - Users comfortable with a single, opinionated structure and Git-backed version control for their notes. - AI-assisted workflows where an agent needs to reliably store, organize, and later recall user knowledge over long periods. **Not Ideal For** - Users needing multiple knowledge bases, custom storage locations, or advanced privacy features (encryption, access control). - Teams or shared repositories (the design is clearly personal and single-user oriented).