What problem does it solve? Keeping project documentation, architecture notes, ADRs, and backlog items consistent and canonically placed inside an Obsidian wiki is tedious and error-prone. This Skill enforces the wiki's authoring conventions so original content lands in the right location with correct frontmatter, links, and catalog updates. ## Core Features & Use Cases - Canonical placement: Locates existing pages, preserves established filenames, and creates a project overview before other documents. - Template-driven authoring: Uses authored-note, authored-decision, and authored-backlog-item templates with honest ai-generated, type, project, and kind metadata. - Operation contract: Wraps writes in op-begin/op-commit scripts, refreshes index and backlog catalogs, and verifies sync state before reporting completion. - Use Case: Ask the agent to write a user guide for a project; it finds or creates the page under wiki/authored/<project>/, applies the template, validates links, regenerates the MOC catalog, and commits the operation log. ## Quick Start Ask the agent to author a user guide or ADR for a specific project in the wiki, for example: write an architecture decision record for the sparta-scope project.