rubber-ducks-syndicate

obsidian-adr

Specialist skill for Architecture Decision Records (ADRs) in an Obsidian vault. Normally invoked by the obsidian-documentation orchestrator. Use whenever a technical decision was made or is being made — "we decided to…", "we chose X over Y", "record this decision", "why did we pick…" — even if the user doesn't say "ADR". Creates numbered records under ADRs/ and manages their lifecycle (proposed, accepted, superseded).

obsidian-architecture

Specialist skill for documenting system design in an Obsidian vault — component overviews, data flows, infrastructure layout, integration landscapes, and architecture notes. Normally invoked by the obsidian-documentation orchestrator. Use when the user discusses how the system is shaped, asks "document our architecture", describes services and how they connect, or after architecture discussions/refactors. Produces notes under Architecture/, Infrastructure/, and Integrations/.

obsidian-doc-prompter

Documentation reflex for coding sessions. Consult this skill whenever you have just implemented, modified, refactored, or fixed something in a project — a feature, an endpoint, a component, a schema change, an architectural change, a dependency swap — even if the user never mentioned documentation. It checks whether the change is worth documenting, asks the user, and on yes hands a pre-approved scope to the obsidian-documentation orchestrator. It never documents without consent.

obsidian-documentation

Orchestrator and ONLY entrypoint for all Obsidian documentation work. Use this skill whenever the user wants to document anything in their Obsidian vault — features, architecture, decisions (ADRs), diagrams, tags, links/MOCs, or vault cleanup — or says things like "document this", "write this up in Obsidian", "add this to the vault", "create an ADR", "update the docs". Even if the request seems to match a specialist skill directly, route through this skill. It analyzes intent, gathers context (git diff, repo, vault, conversation), delegates to specialist skills, and assembles one coherent documentation package.

obsidian-feature

Specialist skill for documenting features (backend + frontend) in an Obsidian vault. Normally invoked by the obsidian-documentation orchestrator, but also use it directly when the user asks to document a feature, a new capability, an endpoint, a UI flow, or "what I just built" — including from a git diff or PR. Produces feature notes under Features/ with backend/frontend sub-notes, ready for the tagging and linking pass.

obsidian-linking

Specialist skill that owns the knowledge graph of an Obsidian vault — bidirectional wiki links, Maps of Content (MOCs), backlink maintenance, and orphan prevention. Normally invoked by the obsidian-documentation orchestrator as the final pass of every documentation run, and directly for "connect these notes", "build a MOC", "find orphan notes", "the graph view is a mess" requests.

obsidian-maintenance

Specialist skill for keeping an Obsidian vault healthy over time — deduplicating overlapping notes, merging, refactoring outdated documentation, fixing structural mess, and updating docs after code changes. Normally invoked by the obsidian-documentation orchestrator. Use for "clean up the vault", "these notes overlap", "the docs are outdated", "refactor the documentation", or when any skill notices duplication or rot.

obsidian-query

Specialist skill for answering questions FROM the Obsidian vault — "how does X work", "why did we choose Y", "what do we know about Z", "find the docs about…". It owns the hidden per-project index (a catalog of every note with one-line summaries, in <vault>/.claude-docs/) and run log, reads the index first to locate relevant notes, then synthesizes a cited answer. Valuable answers can be filed back into the vault. Use whenever the user asks a question whose answer should live in the documentation, or asks to find/locate notes.

obsidian-tagging

Specialist skill that owns the tag taxonomy of an Obsidian vault — assigning tags to new notes, keeping tags consistent, extending the hierarchy, and auditing/fixing tag drift. Normally invoked by the obsidian-documentation orchestrator as the final pass of every documentation run, and directly for "fix my tags", "what tags should this have", "tags are a mess" requests.