What problem does it solve? Maintaining a consistent, well-organized Obsidian knowledge base becomes difficult as documentation grows across multiple projects. This Skill enforces a formal documentation system with strict conventions for document types, frontmatter, tagging, linking, and archival so every note lands in the right place with the right structure. ## Core Features & Use Cases - Structured Document Creation: Generates project documents and shared knowledge notes from canonical templates with complete YAML frontmatter (type, status, area, dates, tags). - Classification & Organization: Routes content to Projects, Shared Knowledge, Resources, or Archives using explicit decision rules and flowcharts. - Archival Workflow: Moves obsolete content to Deprecated, Superseded, or Historical folders with status updates and forward links, never deleting content outright. - Use Case: After finishing a project architecture review, ask the agent to create an ADR in the project's Decisions folder, link it from the architecture document, and archive the superseded design doc with proper status and backlinks. ## Quick Start Create a new Architecture document for my project in the Obsidian vault using the standard template and link it from the Project Overview.
