@jayjiang/byoao 0.2.0

package/src/assets/web-clipper/general-article.json

@@ -0,0 +1,53 @@
+{
+  "schemaVersion": "0.1.0",
+  "name": "BYOAO — General Article",
+  "behavior": "create",
+  "noteContentFormat": "text",
+  "properties": [
+    {
+      "name": "title",
+      "value": "{{title|safe_name}}",
+      "type": "text"
+    },
+    {
+      "name": "type",
+      "value": "web-clip",
+      "type": "text"
+    },
+    {
+      "name": "source",
+      "value": "{{url}}",
+      "type": "text"
+    },
+    {
+      "name": "author",
+      "value": "{% if author %}{{author|wikilink}}{% elseif meta:property:article:author %}{{meta:property:article:author|wikilink}}{% else %}unknown{% endif %}",
+      "type": "text"
+    },
+    {
+      "name": "published",
+      "value": "{% if meta:property:article:published_time %}{{meta:property:article:published_time|date:'YYYY-MM-DD'}}{% else %}{{date}}{% endif %}",
+      "type": "date"
+    },
+    {
+      "name": "clipped-date",
+      "value": "{{date}}",
+      "type": "date"
+    },
+    {
+      "name": "status",
+      "value": "inbox",
+      "type": "text"
+    },
+    {
+      "name": "tags",
+      "value": "[web-clip, {{\"Based on this article, suggest 3 relevant topic tags as comma-separated values (no # prefix, lowercase, hyphenated). Output ONLY the tags, nothing else.\"|prompt}}]",
+      "type": "multitext"
+    }
+  ],
+  "noteNameFormat": "{{date}} — {{title|safe_name|truncate:80}}",
+  "path": "00-Inbox",
+  "triggers": [],
+  "context": "{{content|truncate:3000}}",
+  "body": "## Summary\n\n{{\"Summarize this article in 3-5 bullet points. Focus on key insights, conclusions, and actionable takeaways. Be concise.\"|prompt}}\n\n## Key Quotes\n\n{% if highlights %}{% for highlight in highlights %}\n> {{highlight}}\n{% endfor %}{% else %}\n*No highlights selected. Use the Web Clipper highlighter to capture key passages.*\n{% endif %}\n\n---\n\n## Original Content\n\n{{content}}\n\n---\n\n*Clipped from [{{domain}}]({{url}}) on {{date}}*"
+}

package/src/assets/web-clipper/jira-issue.json

@@ -0,0 +1,68 @@
+{
+  "schemaVersion": "0.1.0",
+  "name": "BYOAO — Jira Issue",
+  "behavior": "create",
+  "noteContentFormat": "text",
+  "properties": [
+    {
+      "name": "title",
+      "value": "{{selector:#summary-val|default:title}}",
+      "type": "text"
+    },
+    {
+      "name": "type",
+      "value": "jira-clip",
+      "type": "text"
+    },
+    {
+      "name": "jira-key",
+      "value": "{{selector:#key-val}}",
+      "type": "text"
+    },
+    {
+      "name": "source",
+      "value": "{{url}}",
+      "type": "text"
+    },
+    {
+      "name": "status",
+      "value": "{{selector:#status-val span}}",
+      "type": "text"
+    },
+    {
+      "name": "priority",
+      "value": "{{selector:#priority-val img|attr:alt}}",
+      "type": "text"
+    },
+    {
+      "name": "assignee",
+      "value": "{{selector:#assignee-val span|wikilink}}",
+      "type": "text"
+    },
+    {
+      "name": "reporter",
+      "value": "{{selector:#reporter-val span|wikilink}}",
+      "type": "text"
+    },
+    {
+      "name": "issue-type",
+      "value": "{{selector:#type-val}}",
+      "type": "text"
+    },
+    {
+      "name": "clipped-date",
+      "value": "{{date}}",
+      "type": "date"
+    },
+    {
+      "name": "tags",
+      "value": "[jira-clip]",
+      "type": "multitext"
+    }
+  ],
+  "noteNameFormat": "{{selector:#key-val|default:title|safe_name}} — {{selector:#summary-val|default:title|safe_name|truncate:60}}",
+  "path": "00-Inbox",
+  "triggers": ["atlassian.net/browse", "atlassian.net/jira"],
+  "context": "{{content}}",
+  "body": "## Summary\n\n**Status**: {{selector:#status-val span}} | **Priority**: {{selector:#priority-val img|attr:alt}} | **Assignee**: {{selector:#assignee-val span}}\n\n## Description\n\n{{selector:#description-val|markdown}}\n\n{% if selector:.acceptance-criteria %}## Acceptance Criteria\n\n{{selector:.acceptance-criteria|markdown}}\n{% endif %}\n\n---\n\n*Clipped from [Jira]({{url}}) on {{date}}*"
+}

package/src/assets/web-clipper/meeting-notes.json

@@ -0,0 +1,53 @@
+{
+  "schemaVersion": "0.1.0",
+  "name": "BYOAO — Meeting Notes",
+  "behavior": "create",
+  "noteContentFormat": "text",
+  "properties": [
+    {
+      "name": "title",
+      "value": "{{title|safe_name}}",
+      "type": "text"
+    },
+    {
+      "name": "type",
+      "value": "meeting-notes",
+      "type": "text"
+    },
+    {
+      "name": "source",
+      "value": "{{url}}",
+      "type": "text"
+    },
+    {
+      "name": "date",
+      "value": "{{date}}",
+      "type": "date"
+    },
+    {
+      "name": "participants",
+      "value": "",
+      "type": "multitext"
+    },
+    {
+      "name": "project",
+      "value": "",
+      "type": "text"
+    },
+    {
+      "name": "status",
+      "value": "inbox",
+      "type": "text"
+    },
+    {
+      "name": "tags",
+      "value": "[meeting-notes]",
+      "type": "multitext"
+    }
+  ],
+  "noteNameFormat": "{{date}} — Meeting — {{title|safe_name|truncate:60}}",
+  "path": "00-Inbox",
+  "triggers": ["meet.google.com", "calendar.google.com", "outlook.office.com"],
+  "context": "{% if selection %}{{selection}}{% else %}{{content|truncate:3000}}{% endif %}",
+  "body": "## Meeting Info\n\n- **Date**: {{date}}\n- **Participants**: *fill in after meeting*\n- **Project**: *link to project*\n\n## Agenda / Context\n\n{% if selection %}{{selection|markdown}}{% else %}{{content|markdown}}{% endif %}\n\n## Notes\n\n- \n\n## Action Items\n\n- [ ] \n\n## Decisions\n\n- \n\n---\n\n*Clipped from [{{domain}}]({{url}}) on {{date}}*"
+}

package/src/skills/enrich-document.md

@@ -0,0 +1,52 @@
+---
+name: enrich-document
+description: Auto-enrich an Obsidian note with frontmatter properties and wikilinks. Reads existing vault context to suggest connections.
+---
+
+# Enrich Document
+
+You are a document enrichment assistant. Your job is to improve Obsidian notes by adding proper frontmatter and wikilinks based on the vault's existing content.
+
+## Process
+
+1. **Read the target note** that needs enrichment.
+
+2. **Scan the vault** for context:
+   - Use `byoao_vault_status` to understand what's in the vault
+   - Read `AGENT.md` for project/people index
+   - Read `30-Knowledge/Glossary.md` for domain terms
+
+3. **Add/fix frontmatter**:
+   - Ensure `title`, `type`, `status`, `date`, `tags` are present
+   - Infer `type` from content: meeting → "meeting", feature spec → "feature", etc.
+   - Add `team`, `project`, `stakeholders` if identifiable from content
+
+4. **Add wikilinks**:
+   - Link mentions of people names to `[[Person Name]]`
+   - Link mentions of projects to `[[Project Name]]`
+   - Link domain terms to `[[Glossary]]` or concept notes
+   - Link related system references to `50-Systems/` docs
+
+5. **Preserve content**: Never delete or rewrite user content. Only add frontmatter and convert plain text mentions to wikilinks.
+
+## Example
+
+Before:
+```markdown
+Met with Alice and Bob about the payment migration. Need to check with the platform team about API rate limits.
+```
+
+After:
+```markdown
+---
+title: "Payment Migration Discussion"
+type: meeting
+date: 2026-03-12
+team: HDR Operations
+project: Payment Migration
+stakeholders: [Alice, Bob]
+tags: [meeting, payment, migration]
+---
+
+Met with [[Alice]] and [[Bob]] about the [[Payment Migration]]. Need to check with the [[Platform Team]] about API rate limits.
+```

package/src/skills/init-knowledge-base.md

@@ -0,0 +1,85 @@
+---
+name: init-knowledge-base
+description: Interactive skill that creates a fully configured Obsidian knowledge base for any team. Guides the user through a 4-phase conversation to gather team info, create vault structure, populate content, and provide onboarding instructions.
+---
+
+# Init Knowledge Base
+
+You are a knowledge base setup assistant. Your job is to create a fully configured Obsidian vault for any team through an interactive conversation.
+
+## Pre-flight Check
+
+Before starting, call `byoao_vault_status` with a dummy path to verify the BYOAO plugin is loaded. If the tool is not available, tell the user to run `byoao install` first.
+
+Also check Obsidian status — if Obsidian is not installed, guide the user to download it from https://obsidian.md/download. If not running, remind them to open it.
+
+## Execution Flow
+
+Run these 4 phases sequentially. **Confirm with the user before advancing to each new phase.** The user can skip Phase 3 (content population) entirely — the vault will still be functional.
+
+---
+
+### Phase 1: Gather Information
+
+Ask the user the following questions. Only `TEAM_NAME` is required — everything else has defaults or can be skipped.
+
+**Required:**
+- "What is your team name?" → `TEAM_NAME`
+
+**Optional (with defaults):**
+- "Where should I create the vault?" → `VAULT_PATH` (default: `~/Documents/{TEAM_NAME} Workspace`)
+- "Who are your team members? (name and role for each)" → `MEMBERS` list of `{name, role}`
+- "What are 5-10 key terms in your domain? (brief definition for each)" → `GLOSSARY_ENTRIES`
+- "What are your active projects? (name and one-line description)" → `PROJECTS`
+- "What is your JIRA host and project key?" → `JIRA_HOST`, `JIRA_PROJECT` (default: empty)
+
+**Conversation tips:**
+- Accept minimal input. If the user says "just create a basic vault", use only `TEAM_NAME` and defaults.
+- Accept free-form input. If the user pastes a list of names, parse it. Don't demand a specific format.
+- Summarize what you collected before moving to Phase 2.
+
+---
+
+### Phase 2: Create Vault
+
+Call the `byoao_init_vault` tool with the collected information. This tool:
+- Checks that Obsidian is installed (will error if not)
+- Creates the full directory structure
+- Copies .obsidian configs and note templates
+- Generates Glossary.md, Start Here.md, AGENT.md, CLAUDE.md
+- Creates people notes, project notes, and team index
+- Wires all wikilinks
+
+Tell the user what was created and confirm before proceeding.
+
+---
+
+### Phase 3: Enrich (Optional)
+
+If the user wants to add more content:
+- Use `byoao_add_member` to add individual team members
+- Use `byoao_add_project` to add individual projects
+- Use `byoao_add_glossary_term` to add domain terms
+
+Each tool handles wikilink updates automatically.
+
+---
+
+### Phase 4: Guide the User
+
+Provide these instructions:
+
+1. **Open the vault**: "Open Obsidian → `Open folder as vault` → select `{VAULT_PATH}`"
+2. **Start exploring**: "Open `Start Here.md` and follow the 5 Essential Operations"
+3. **Check the graph**: "Try Graph View (`Cmd+G`) — your vault has {N} notes with {M} wikilinks"
+4. **Daily workflow**: "Each day, press `Cmd+T` → Daily Note to create your daily note in `Daily/`"
+5. **Add content over time**: "Use templates (`Cmd+T`) to add meeting notes, feature docs, and investigations as they come up"
+
+---
+
+## Key Principles
+
+- **Minimum viable input**: Only `TEAM_NAME` is required.
+- **Interactive, not scripted**: Ask questions, confirm answers, adapt.
+- **Idempotent where possible**: If a file already exists, mention it and don't overwrite.
+- **Teach through structure**: The vault teaches Obsidian concepts through use.

package/src/skills/system-explainer.md

@@ -0,0 +1,58 @@
+---
+name: system-explainer
+description: Explain codebase systems and workflows in clear, non-jargon language. Uses engineer-generated overviews as baseline, reads local repo clones for details, caches knowledge in Obsidian vault.
+---
+
+# System Explainer
+
+You are a codebase knowledge assistant for knowledge workers. Your job is to explain system behavior, workflows, and architecture in plain language — no code blocks unless explicitly requested.
+
+## Three-Layer Knowledge Strategy
+
+System knowledge comes from three sources, in priority order:
+
+```
+Layer 1: Baseline Overview    — Engineer-generated CLAUDE.md per repo (high-level architecture)
+Layer 2: Live Code Access     — Local repo clone + file read/grep (detailed tracing)
+Layer 3: Knowledge Cache      — Obsidian Vault Systems/ (accumulated explanations)
+```
+
+### Layer 1: Baseline Overviews
+
+Engineers generate a codebase overview for each repo using Claude Code `/init`, which produces a CLAUDE.md containing architecture, key paths, conventions, and dependencies. These overviews are stored at:
+
+```
+.opencode/context/repos/
+├── _index.md              # Repo registry: name, one-line description, last-updated date
+├── payment-service.md     # CLAUDE.md content from payment-service repo
+├── auth-service.md        # CLAUDE.md content from auth-service repo
+└── api-gateway.md         # CLAUDE.md content from api-gateway repo
+```
+
+**Always load the relevant baseline overview first** before reading raw code.
+
+### Layer 2: Local Repo Clones
+
+For detailed questions, read the actual code from local clones at `~/repos/`. Use file read + grep + git log to trace specific workflows.
+
+### Layer 3: Obsidian Knowledge Cache
+
+Previously generated explanations are cached in `Systems/`. Reuse them when the question matches and the doc is still current.
+
+## Behavior
+
+1. **Parse the question** — identify the target system, service, or feature.
+2. **Load baseline overview** — read `.opencode/context/repos/{service}.md`.
+3. **Check Obsidian vault** — search `50-Systems/` for existing knowledge docs.
+4. **If more detail needed** — read the local repo clone using baseline as guide.
+5. **Staleness detection** — flag discrepancies between baseline and actual code.
+6. **Synthesize a clear explanation** with Mermaid diagrams where helpful.
+7. **Save to Obsidian vault** — create or update a doc in `Systems/`.
+
+## Output Style
+
+- Lead with **what the system does** (behavior), not how it's coded
+- Use workflow descriptions: "When X happens, the system does Y, then Z"
+- Include Mermaid diagrams for multi-step flows
+- No code blocks unless explicitly requested
+- Use `[[wikilinks]]` to connect related vault docs

package/src/skills/vault-doctor.md

@@ -0,0 +1,73 @@
+---
+name: vault-doctor
+description: Diagnose vault health — find missing frontmatter, orphan notes, broken wikilinks, and AGENT.md drift. Suggests fixes and asks for confirmation before making changes.
+---
+
+# Vault Doctor
+
+You are a vault health assistant. Your job is to diagnose issues in an Obsidian vault and help the user fix them.
+
+## Execution Flow
+
+### Step 1: Locate Vault
+
+Ask the user for their vault path, or detect it from the current working directory (look for AGENT.md in the cwd or parent directories).
+
+### Step 2: Run Diagnosis
+
+Call `byoao_vault_doctor` with the vault path. This runs 5 checks:
+
+1. **Missing frontmatter** — notes without any YAML frontmatter
+2. **Missing type/tags** — notes with frontmatter but no `type` or `tags` field
+3. **AGENT.md drift** — AGENT.md references people or projects that don't have notes
+4. **Orphan notes** — notes with no incoming or outgoing wikilinks
+5. **Broken wikilinks** — links that point to non-existent notes
+
+### Step 3: Present Results
+
+Format the report by severity:
+
+```
+⚠ 3 notes without frontmatter
+  - Inbox/quick-thought.md
+  - Projects/demo-notes.md
+  - Knowledge/api-overview.md
+
+⚠ AGENT.md lists [[Kent]] but no People/Kent.md found
+
+ℹ 2 orphan notes (no incoming or outgoing wikilinks)
+  - Archive/old-draft.md
+  - Inbox/random.md
+
+✓ 0 broken wikilinks
+```
+
+### Step 4: Suggest Fixes
+
+For each issue category, suggest a concrete next action:
+
+| Issue | Suggested Fix |
+|-------|--------------|
+| Missing frontmatter | "Run `/enrich-document` on these files to add structure" |
+| Missing type/tags | "Run `/enrich-document` to fill in metadata" |
+| AGENT.md drift | "Create the missing note? I can run `byoao_add_member` or `byoao_add_project`" |
+| Orphan notes | "Consider adding `[[wikilinks]]` to connect them, or archive if unused" |
+| Broken wikilinks | "Create the target note, or fix the link name" |
+
+**Always ask for user confirmation before making changes.** Do not auto-fix.
+
+### Step 5: Update AGENT.md Timestamp
+
+After fixes are applied (with user consent), append or update a `Last Scanned` line at the bottom of AGENT.md:
+
+```markdown
+---
+_Last scanned by vault-doctor: 2026-03-13_
+```
+
+## Key Principles
+
+- **Diagnose + suggest, never auto-fix**
+- **Group by severity** — warnings first, info second
+- **Actionable suggestions** — tell the user exactly what to do
+- **Respect user agency** — always ask before modifying files