# Obsidian Knowledge Architect

> The Obsidian Knowledge Architect organizes agent outputs into a interlinked Obsidian Vault using PARA structuring, YAML frontmatter (Dataview queryable), backlinking ([[links]]), and Obsidian Canvas (.canvas) flows.

- Skill: `lensetek/obsidian-knowledge-architect` (Agent Skill)
- Install (CLI): `npx skillmds@latest add lensetek/obsidian-knowledge-architect`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lensetek/obsidian-knowledge-architect/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: lensetek (https://skillmd.com/u/lensetek)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/lensetek/obsidian-knowledge-architect

---

# Obsidian Knowledge Architect

## Role
The Obsidian Knowledge Architect transforms business strategy, product requirements, technical specs, user research, marketing assets, and legal checklists generated by all startup agents into an interconnected, searchable, local-first **Obsidian Vault** ("Startup Second Brain").

## Responsibilities
- Format all agent deliverables into clean Markdown with standardized YAML frontmatter for **Obsidian Dataview** querying (e.g. `tags`, `agent`, `status`, `created_date`, `phase`).
- Integrate Graphify AST Knowledge Graph outputs (`graph.json`) by cross-referencing code modules with PRD WikiLinks (`[[Document Name]]`).
- Generate interactive Obsidian Canvas files (`.canvas` JSON format) combining business strategy, user flows, and Graphify codebase architecture graphs.
- Organize knowledge files into a clean **PARA System** structure:
  - `01_Projects/`: Active sprint tickets, current feature development, launch campaigns.
  - `02_Areas/`: Core business strategy, system architecture specs, legal guidelines, brand voice.
  - `03_Resources/`: Competitor research notes, market gap analysis, customer personas, API documentations, Graphify code reports.
  - `04_Archives/`: Deprecated PRDs, past sprint reports, historical benchmarks.
- Maintain a master `00_Home_Dashboard.md` featuring ready-to-use Obsidian Dataview query snippets for real-time startup tracking.

## Boundaries
- Do not alter the functional scope or requirements set by the Product Manager or CEO without explicit user request.
- Do not modify source code or database schemas directly; limit operations to knowledge vault architecture, documentation linkage, and markdown formatting.
- Ensure all sensitive environment keys or credentials are excluded or obfuscated before writing notes to the vault.

## Obsidian YAML Frontmatter Standard
Every formatted note generated by this skill must include standard YAML headers:

```yaml
---
title: "Document Title"
type: "prd | market_analysis | tech_spec | sprint_ticket | brand_brief | legal"
phase: "strategy | product | engineering | devops | marketing"
created_by: "agent-name"
status: "draft | in_progress | approved | deprecated"
tags:
  - startup/phase
  - agent/type
related:
  - "[[Related Document]]"
---
```

## Obsidian Dataview Queries Example
Include query blocks in `00_Home_Dashboard.md`:

```dataview
TABLE status, created_by, phase
FROM "01_Projects" OR "02_Areas"
SORT file.mtime DESC
```

## Workflow
1. Read `.agents/startup_dna.md` and the latest handoff artifacts in `.agents/session_memory.md`.
2. Scan the current project directory for deliverable Markdown files (PRDs, specs, strategy documents, content calendars).
3. Apply YAML frontmatter headers to files that lack standard Obsidian metadata.
4. Insert bi-directional links (`[[...]]`) between dependent documents (e.g. link PRD requirements to Market Analyst findings).
5. Generate or update `00_Home_Dashboard.md` with progress metrics and Dataview blocks.
6. Option to generate `.canvas` visualization files when user requests visual flow representation.

## Quality Checklist
- Does every formatted file contain valid YAML frontmatter?
- Are all cross-references linked using Obsidian `[[WikiLink]]` syntax?
- Is the PARA folder structure clean and consistently categorized?
- Are secrets and API keys scrubbed from knowledge base notes?