菜单
Obsidian Knowledge Architecture — primary brain for all project knowledge. Vault location, folder structure, canvas architecture, session-end ritual, and Jira/Notion linkage conventions. Load this skill before writing any Obsidian files.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Builds production-grade Claude Projects and CustomGPTs, improves AI output quality using meta-thinking prompts, and architects self-improving AI systems. Use proactively when a founder wants to build a reliable AI workflow, automate a repeatable task with AI, improve the quality of AI outputs they're getting, feels stuck with generic AI responses, or wants to build internal tools powered by Claude. Trigger for "build a Claude project", "my AI outputs are generic", "how do I make Claude more specific", "build an AI workflow", "automate this with AI", or "my prompts aren't working".
One-command review pipeline. Chains CEO review → design review → eng review automatically. Surfaces only taste decisions for PD approval. Everything else runs autonomously.
Performance baseline measurement. Captures page load times, Core Web Vitals, and resource sizes. Compare before/after on every PR.
Playbook for bootstrapped and early-stage SaaS founders based on proven case studies ($0 to $5M ARR with 6 people, and creator-to-business flywheel models). Use proactively when a founder is bootstrapped or capital-efficient, needs to grow without paid acquisition, is facing a churn crisis, wants to build a freemium or usage-based model, or asks "how do I grow without VC money". Also trigger for "PLG", "inbound-led outbound", "creator-led growth", "build in public", or "how did [bootstrapped company] grow".
Real browser automation for testing, QA, and demo verification. Provides Playwright-based browser control for navigating the live app, clicking elements, filling forms, taking screenshots, and verifying visual state.
Post-deploy monitoring. After release-engineer pushes to production, canary watches the live site for errors, performance regressions, and page failures.
| name | obsidian |
| description | Obsidian Knowledge Architecture — primary brain for all project knowledge. Vault location, folder structure, canvas architecture, session-end ritual, and Jira/Notion linkage conventions. Load this skill before writing any Obsidian files. |
| used_by | ["ceo-thinking-partner","workflow-architect","product-manager"] |
Obsidian is the primary brain — the single source of truth for all project knowledge. Everything flows FROM Obsidian TO Jira, Notion, and other tools. Never the reverse.
Obsidian (brain)
↓ tickets → Jira (task tracking)
↓ dashboards → Notion (stakeholder view)
↓ notifications → [COMMS_CHANNEL] (real-time comms)
↓ code → GitHub (source of truth)
[OBSIDIAN_VAULT_PATH]
Write directly with Write/Edit tools — zero API cost, zero token cost.
| Folder | What goes here | Update frequency |
|---|---|---|
daily-logs/ | Session summaries (YYYY-MM-DD.md) | Every session |
sprint-tracking/ | Sprint status files | Every sprint change |
provocateur/ | Audit reports from provocateur agent | Post-sprint |
decisions/ | Key decisions with rationale and date | When decisions are made |
brainstorms/ | Ideas, strategy notes, CEO thinking sessions | Ad-hoc |
process-flows/ | Mermaid diagrams, user journeys | When flows change |
agent-reports/ | Roll calls, status reports | Per agent session |
handoffs/ | Agent handoff backups | Per handoff |
personas/ | Persona maps, story gaps | When persona data changes |
investor/ | Pitch notes, investor Q&A | Pre-meeting |
architecture/ | System diagrams, DB tables | When architecture changes |
File: [PROJECT_NAME] Command Center.canvas
This is the VISUAL BRAIN. Rebuild after every sprint. Sections:
// Local Obsidian file
{"id": "x", "type": "file", "file": "[project]/path/file.md", "x": 0, "y": 0, "width": 560, "height": 300}
// External URL (GitHub, deploy URL, Notion)
{"id": "x", "type": "link", "url": "https://...", "x": 0, "y": 0, "width": 360, "height": 80}
// Text with markdown (use for Jira ticket links — type:link embeds don't show ticket text)
{"id": "x", "type": "text", "text": "[[JIRA_PROJECT_KEY]-168 — Title](https://your-jira.atlassian.net/browse/[JIRA_PROJECT_KEY]-168)", "x": 0, "y": 0, "width": 560, "height": 60}
// Group container (visual only — nodes inside must be within group bounds)
{"id": "x", "type": "group", "label": "Sprint 1", "x": -50, "y": -50, "width": 660, "height": 800}
| Color code | Meaning |
|---|---|
"1" (red) | Critical / VETO / blocked |
"2" (orange) | In progress / warning |
"3" (yellow) | Needs decision |
"4" (green) | Done / shipped |
"5" (blue/cyan) | External link / info |
"6" (purple) | Design system |
Every sprint-tracking file must have this header:
# Sprint X Status — [start] → [end]
**Jira Sprint:** [sprint name in Jira]
**Jira Filter:** [direct URL to sprint board]
## Tickets
- [ ] [[JIRA_PROJECT_KEY]-XXX — Title](https://your-jira.atlassian.net/browse/[JIRA_PROJECT_KEY]-XXX) — [agent] — [pts]
Every decision file must have:
# Decision: [title]
**Date:** YYYY-MM-DD
**Jira:** [[JIRA_PROJECT_KEY]-XXX if applicable]
**Notion:** [page URL if applicable]
**Status:** Active | Superseded | Parked
Update daily log — append session summary (YYYY-MM-DD.md)
Update sprint-tracking/sprint-X-status.md
Update canvas (if sprint state changed significantly)
Write decisions (if new constraint or decision made)
decisions/YYYY-MM-DD-[slug].md[[file]] for cross-references within vault