cli-jaw 0.1.0

package/skills_ref/netlify-deploy/SKILL.md

@@ -0,0 +1,233 @@
+---
+name: netlify-deploy
+description: Deploy web projects to Netlify using the Netlify CLI (`npx netlify`). Use when the user asks to deploy, host, publish, or link a site/repo on Netlify, including preview and production deploys.
+---
+
+# Netlify Deployment Skill
+
+Deploy web projects to Netlify using the Netlify CLI with intelligent detection of project configuration and deployment context.
+
+## Overview
+
+This skill automates Netlify deployments by:
+- Verifying Netlify CLI authentication
+- Detecting project configuration and framework
+- Linking to existing sites or creating new ones
+- Deploying to production or preview environments
+
+## Prerequisites
+
+- **Netlify CLI**: Installed via npx (no global install required)
+- **Authentication**: Netlify account with active login session
+- **Project**: Valid web project in current directory
+
+## Authentication Pattern
+
+The skill uses the **pre-authenticated Netlify CLI** approach:
+
+1. Check authentication status with `npx netlify status`
+2. If not authenticated, guide user through `npx netlify login`
+3. Fail gracefully if authentication cannot be established
+
+Authentication uses either:
+- **Browser-based OAuth** (primary): `netlify login` opens browser for authentication
+- **API Key** (alternative): Set `NETLIFY_AUTH_TOKEN` environment variable
+
+## Workflow
+
+### 1. Verify Netlify CLI Authentication
+
+Check if the user is logged into Netlify:
+
+```bash
+npx netlify status
+```
+
+**Expected output patterns**:
+- ✅ Authenticated: Shows logged-in user email and site link status
+- ❌ Not authenticated: "Not logged into any site" or authentication error
+
+**If not authenticated**, guide the user:
+
+```bash
+npx netlify login
+```
+
+This opens a browser window for OAuth authentication. Wait for user to complete login, then verify with `netlify status` again.
+
+**Alternative: API Key authentication**
+
+If browser authentication isn't available, users can set:
+
+```bash
+export NETLIFY_AUTH_TOKEN=your_token_here
+```
+
+Tokens can be generated at: https://app.netlify.com/user/applications#personal-access-tokens
+
+### 2. Detect Site Link Status
+
+From `netlify status` output, determine:
+- **Linked**: Site already connected to Netlify (shows site name/URL)
+- **Not linked**: Need to link or create site
+
+### 3. Link to Existing Site or Create New
+
+**If already linked** → Skip to step 4
+
+**If not linked**, attempt to link by Git remote:
+
+```bash
+# Check if project is Git-based
+git remote show origin
+
+# If Git-based, extract remote URL
+# Format: https://github.com/username/repo or git@github.com:username/repo.git
+
+# Try to link by Git remote
+npx netlify link --git-remote-url <REMOTE_URL>
+```
+
+**If link fails** (site doesn't exist on Netlify):
+
+```bash
+# Create new site interactively
+npx netlify init
+```
+
+This guides user through:
+1. Choosing team/account
+2. Setting site name
+3. Configuring build settings
+4. Creating netlify.toml if needed
+
+### 4. Verify Dependencies
+
+Before deploying, ensure project dependencies are installed:
+
+```bash
+# For npm projects
+npm install
+
+# For other package managers, detect and use appropriate command
+# yarn install, pnpm install, etc.
+```
+
+### 5. Deploy to Netlify
+
+Choose deployment type based on context:
+
+**Preview/Draft Deploy** (default for existing sites):
+
+```bash
+npx netlify deploy
+```
+
+This creates a deploy preview with a unique URL for testing.
+
+**Production Deploy** (for new sites or explicit production deployments):
+
+```bash
+npx netlify deploy --prod
+```
+
+This deploys to the live production URL.
+
+**Deployment process**:
+1. CLI detects build settings (from netlify.toml or prompts user)
+2. Builds the project locally
+3. Uploads built assets to Netlify
+4. Returns deployment URL
+
+### 6. Report Results
+
+After deployment, report to user:
+- **Deploy URL**: Unique URL for this deployment
+- **Site URL**: Production URL (if production deploy)
+- **Deploy logs**: Link to Netlify dashboard for logs
+- **Next steps**: Suggest `netlify open` to view site or dashboard
+
+## Handling netlify.toml
+
+If a `netlify.toml` file exists, the CLI uses it automatically. If not, the CLI will prompt for:
+- **Build command**: e.g., `npm run build`, `next build`
+- **Publish directory**: e.g., `dist`, `build`, `.next`
+
+Common framework defaults:
+- **Next.js**: build command `npm run build`, publish `.next`
+- **React (Vite)**: build command `npm run build`, publish `dist`
+- **Static HTML**: no build command, publish current directory
+
+The skill should detect framework from `package.json` if possible and suggest appropriate settings.
+
+## Example Full Workflow
+
+```bash
+# 1. Check authentication
+npx netlify status
+
+# If not authenticated:
+npx netlify login
+
+# 2. Link site (if needed)
+# Try Git-based linking first
+git remote show origin
+npx netlify link --git-remote-url https://github.com/user/repo
+
+# If no site exists, create new one:
+npx netlify init
+
+# 3. Install dependencies
+npm install
+
+# 4. Deploy (preview for testing)
+npx netlify deploy
+
+# 5. Deploy to production (when ready)
+npx netlify deploy --prod
+```
+
+## Error Handling
+
+Common issues and solutions:
+
+**"Not logged in"**
+→ Run `npx netlify login`
+
+**"No site linked"**
+→ Run `npx netlify link` or `npx netlify init`
+
+**"Build failed"**
+→ Check build command and publish directory in netlify.toml or CLI prompts
+→ Verify dependencies are installed
+→ Review build logs for specific errors
+
+**"Publish directory not found"**
+→ Verify build command ran successfully
+→ Check publish directory path is correct
+
+## Environment Variables
+
+For secrets and configuration:
+
+1. Never commit secrets to Git
+2. Set in Netlify dashboard: Site Settings → Environment Variables
+3. Access in builds via `process.env.VARIABLE_NAME`
+
+## Tips
+
+- Use `netlify deploy` (no `--prod`) first to test before production
+- Run `netlify open` to view site in Netlify dashboard
+- Run `netlify logs` to view function logs (if using Netlify Functions)
+- Use `netlify dev` for local development with Netlify Functions
+
+## Reference
+
+- Netlify CLI Docs: https://docs.netlify.com/cli/get-started/
+- netlify.toml Reference: https://docs.netlify.com/configure-builds/file-based-configuration/
+
+## Bundled References (Load As Needed)
+
+- [CLI commands](references/cli-commands.md)
+- [Deployment patterns](references/deployment-patterns.md)
+- [netlify.toml guide](references/netlify-toml.md)

package/skills_ref/notion/SKILL.md

@@ -0,0 +1,304 @@
+---
+name: notion
+description: Notion API for creating and managing pages, databases, and blocks.
+homepage: https://developers.notion.com
+metadata:
+  {
+    "openclaw":
+      { "emoji": "📝", "requires": { "env": ["NOTION_API_KEY"] }, "primaryEnv": "NOTION_API_KEY" },
+  }
+---
+
+# notion
+
+Use the Notion API to create/read/update pages, data sources (databases), and blocks.
+
+## Setup
+
+1. Create an integration at https://notion.so/my-integrations
+2. Copy the API key (starts with `ntn_` or `secret_`)
+3. Store it:
+
+```bash
+mkdir -p ~/.config/notion
+echo "ntn_your_key_here" > ~/.config/notion/api_key
+```
+
+4. Share target pages/databases with your integration (click "..." → "Connect to" → your integration name)
+
+## API Basics
+
+All requests need:
+
+```bash
+NOTION_KEY=$(cat ~/.config/notion/api_key)
+curl -X GET "https://api.notion.com/v1/..." \
+  -H "Authorization: Bearer $NOTION_KEY" \
+  -H "Notion-Version: 2025-09-03" \
+  -H "Content-Type: application/json"
+```
+
+> **Note:** The `Notion-Version` header is required. This skill uses `2025-09-03` (latest). In this version, databases are called "data sources" in the API.
+
+## Common Operations
+
+**Search for pages and data sources:**
+
+```bash
+curl -X POST "https://api.notion.com/v1/search" \
+  -H "Authorization: Bearer $NOTION_KEY" \
+  -H "Notion-Version: 2025-09-03" \
+  -H "Content-Type: application/json" \
+  -d '{"query": "page title"}'
+```
+
+**Get page:**
+
+```bash
+curl "https://api.notion.com/v1/pages/{page_id}" \
+  -H "Authorization: Bearer $NOTION_KEY" \
+  -H "Notion-Version: 2025-09-03"
+```
+
+**Get page content (blocks):**
+
+```bash
+curl "https://api.notion.com/v1/blocks/{page_id}/children" \
+  -H "Authorization: Bearer $NOTION_KEY" \
+  -H "Notion-Version: 2025-09-03"
+```
+
+**Create page in a data source:**
+
+```bash
+curl -X POST "https://api.notion.com/v1/pages" \
+  -H "Authorization: Bearer $NOTION_KEY" \
+  -H "Notion-Version: 2025-09-03" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "parent": {"database_id": "xxx"},
+    "properties": {
+      "Name": {"title": [{"text": {"content": "New Item"}}]},
+      "Status": {"select": {"name": "Todo"}}
+    }
+  }'
+```
+
+**Query a data source (database):**
+
+```bash
+curl -X POST "https://api.notion.com/v1/data_sources/{data_source_id}/query" \
+  -H "Authorization: Bearer $NOTION_KEY" \
+  -H "Notion-Version: 2025-09-03" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "filter": {"property": "Status", "select": {"equals": "Active"}},
+    "sorts": [{"property": "Date", "direction": "descending"}]
+  }'
+```
+
+**Create a data source (database):**
+
+```bash
+curl -X POST "https://api.notion.com/v1/data_sources" \
+  -H "Authorization: Bearer $NOTION_KEY" \
+  -H "Notion-Version: 2025-09-03" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "parent": {"page_id": "xxx"},
+    "title": [{"text": {"content": "My Database"}}],
+    "properties": {
+      "Name": {"title": {}},
+      "Status": {"select": {"options": [{"name": "Todo"}, {"name": "Done"}]}},
+      "Date": {"date": {}}
+    }
+  }'
+```
+
+**Update page properties:**
+
+```bash
+curl -X PATCH "https://api.notion.com/v1/pages/{page_id}" \
+  -H "Authorization: Bearer $NOTION_KEY" \
+  -H "Notion-Version: 2025-09-03" \
+  -H "Content-Type: application/json" \
+  -d '{"properties": {"Status": {"select": {"name": "Done"}}}}'
+```
+
+**Add blocks to page:**
+
+```bash
+curl -X PATCH "https://api.notion.com/v1/blocks/{page_id}/children" \
+  -H "Authorization: Bearer $NOTION_KEY" \
+  -H "Notion-Version: 2025-09-03" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "children": [
+      {"object": "block", "type": "paragraph", "paragraph": {"rich_text": [{"text": {"content": "Hello"}}]}}
+    ]
+  }'
+```
+
+## Property Types
+
+Common property formats for database items:
+
+- **Title:** `{"title": [{"text": {"content": "..."}}]}`
+- **Rich text:** `{"rich_text": [{"text": {"content": "..."}}]}`
+- **Select:** `{"select": {"name": "Option"}}`
+- **Multi-select:** `{"multi_select": [{"name": "A"}, {"name": "B"}]}`
+- **Date:** `{"date": {"start": "2024-01-15", "end": "2024-01-16"}}`
+- **Checkbox:** `{"checkbox": true}`
+- **Number:** `{"number": 42}`
+- **URL:** `{"url": "https://..."}`
+- **Email:** `{"email": "a@b.com"}`
+- **Relation:** `{"relation": [{"id": "page_id"}]}`
+
+## Key Differences in 2025-09-03
+
+- **Databases → Data Sources:** Use `/data_sources/` endpoints for queries and retrieval
+- **Two IDs:** Each database now has both a `database_id` and a `data_source_id`
+  - Use `database_id` when creating pages (`parent: {"database_id": "..."}`)
+  - Use `data_source_id` when querying (`POST /v1/data_sources/{id}/query`)
+- **Search results:** Databases return as `"object": "data_source"` with their `data_source_id`
+- **Parent in responses:** Pages show `parent.data_source_id` alongside `parent.database_id`
+- **Finding the data_source_id:** Search for the database, or call `GET /v1/data_sources/{data_source_id}`
+
+## Current Environment
+
+### API Key
+- **Location:** `~/.config/notion/access_token` (also copied to `~/.config/notion/api_key`)
+- **Format:** `ntn_` prefix
+- **Load:** `NOTION_KEY=$(cat ~/.config/notion/api_key)`
+- **OAuth config:** `~/.config/notion/oauth.env` (client_id, client_secret, redirect_uri)
+- **OAuth docs:** `~/Documents/BlogProject/NOTION_OAUTH_SETUP.md`
+
+### Workspace Structure (쭈니님의 워크스페이스)
+
+```
+🚀 Lidge AI (루트) [3113680a-8101-81b8-9cd5-e378212151ce]
+├── 🔬 개인 작업함 [3113680a-8101-8104-b512-db1bfa7631c0]
+│   └── 📦 개인 실험 아카이브
+│
+└── 📅 2026년 3월 출범 [7458b1b1-ffd0-44ed-a38d-818bd6c03f58]
+    ├── 📊 대시보드 [3113680a-8101-8174-b500-dff399ac9046]
+    ├── 🎯 제품 포트폴리오
+    │   ├── 🏥 병원 댓글관리 홍보 자동화 (sujong1 기반)
+    │   ├── 🎓 학원 댓글관리 홍보 자동화 (sujong1 기반)
+    │   └── 🧮 회계·세무 RAG 상담봇
+    ├── 🐾 Cliclaw [3113680a-8101-81c1-bc60-d54ddb678a2d]
+    │   ├── 📋 개요
+    │   ├── ✅ 구현 계획 체크리스트
+    │   ├── 📜 전체 개발 히스토리 (MVP → Finness 12)
+    │   └── 🔧 개발노트 (223, 224, 225, MVP)
+    ├── 📋 예비창업패키지
+    ├── 🏛️ 공공기관 수주 확장
+    ├── ✍️ 콘텐츠
+    ├── ⚙️ 운영
+    │   ├── 📝 자동화 운영 점검 노트
+    │   └── 🎯 창업지원프로그램
+    ├── 🤝 회의록
+    └── 🗄️ 아카이브
+```
+
+### Key Page IDs (Quick Reference)
+- **Lidge AI (root):** `3113680a-8101-81b8-9cd5-e378212151ce`
+- **2026년 3월 출범:** `7458b1b1-ffd0-44ed-a38d-818bd6c03f58`
+- **Cliclaw:** `3113680a-8101-81c1-bc60-d54ddb678a2d`
+- **대시보드:** `3113680a-8101-8174-b500-dff399ac9046`
+- **개인 작업함:** `3113680a-8101-8104-b512-db1bfa7631c0`
+
+### Heartbeat Integration
+- heartbeat job `notion_hourly_upgrade` (120min 주기)가 `Lidge AI/개인 작업함` 범위에서 소규모 개선 자동 수행
+- heartbeat 설정: `~/.cli-jaw/heartbeat.json`
+
+## Visual Design Rules (미감 가이드)
+
+페이지를 꾸밀 때 아래 규칙을 반드시 따른다:
+
+### 1. 멘션 링크 (이중링크) 필수
+
+페이지 이름을 텍스트로 적지 말고, 반드시 `mention` 타입을 사용한다.
+멘션 링크는 클릭 시 해당 페이지로 이동하고, 백링크(역참조)도 자동 생성된다.
+
+```json
+// ✅ 올바른 방법 — mention
+{"type": "mention", "mention": {"type": "page", "page": {"id": "페이지-UUID"}}}
+
+// ❌ 잘못된 방법 — 일반 텍스트
+{"type": "text", "text": {"content": "페이지 이름"}}
+```
+
+### 2. 이모지 중복 금지
+
+멘션 링크는 페이지 아이콘을 자동으로 표시하므로, 텍스트에 이모지를 별도로 넣지 않는다.
+
+```json
+// ✅ 올바른 — 멘션이 알아서 "🐾 Cliclaw" 표시
+[mention("Cliclaw"), text(" — 오픈소스 AI 터미널")]
+
+// ❌ 잘못된 — 이모지 중복 (🐾🐾 Cliclaw)
+[text("🐾 "), mention("Cliclaw"), text(" — 오픈소스 AI 터미널")]
+```
+
+### 3. callout 안에 멘션 링크 사용
+
+callout 블록의 `rich_text` 배열 안에서도 mention 타입을 사용할 수 있다.
+네비게이션 허브나 Quick Links를 만들 때 callout + mention 조합을 활용한다.
+
+```json
+{"object": "block", "type": "callout", "callout": {
+    "rich_text": [
+        {"type": "mention", "mention": {"type": "page", "page": {"id": "대시보드-UUID"}}},
+        {"type": "text", "text": {"content": " · "}},
+        {"type": "mention", "mention": {"type": "page", "page": {"id": "운영-UUID"}}}
+    ],
+    "icon": {"type": "emoji", "emoji": "🏠"},
+    "color": "gray_background"
+}}
+```
+
+### 4. child_page 블록 보호
+
+페이지 블록을 삭제/재작성할 때, `child_page` 타입 블록은 절대 삭제하지 않는다.
+삭제하면 하위 페이지가 아카이브 처리되어 사라진다.
+
+```python
+# 블록 삭제 시 child_page 제외
+for block in children:
+    if block["type"] != "child_page":
+        delete_block(block["id"])
+```
+
+### 5. 페이지 구조 패턴
+
+```
+callout (소개/슬로건) + color_background
+divider
+heading_2 (섹션명)
+callout (멘션 링크 모음) + gray_background  ← 네비게이션
+divider
+heading_2 (Quick Links)
+bulleted_list_item (멘션 → 설명)            ← 바로가기
+divider
+...
+```
+
+### 6. 아이콘 & 커버
+
+- 모든 페이지에 의미 있는 이모지 아이콘 설정
+- 주요 페이지에는 Unsplash 커버 이미지 (w=1500 권장)
+- `update_page(page_id, icon="🐾", cover_url="https://images.unsplash.com/...")`
+
+### 7. 멘션 링크 사용 시 주의사항
+
+- 대상 페이지가 archived 상태면 mention이 일반 텍스트로 변환됨
+- Integration이 해당 페이지에 접근 권한이 있어야 mention 동작
+- API rate limit: ~3 req/s — `time.sleep(0.35)` 권장
+
+## Notes
+
+- Page/database IDs are UUIDs (with or without dashes)
+- The API cannot set database view filters — that's UI-only
+- Rate limit: ~3 requests/second average
+- Use `is_inline: true` when creating data sources to embed them in pages

package/skills_ref/notion-knowledge-capture/SKILL.md

@@ -0,0 +1,56 @@
+---
+name: notion-knowledge-capture
+description: Capture conversations and decisions into structured Notion pages; use when turning chats/notes into wiki entries, how-tos, decisions, or FAQs with proper linking.
+metadata:
+  short-description: Capture conversations into structured Notion pages
+---
+
+# Knowledge Capture
+
+Convert conversations and notes into structured, linkable Notion pages for easy reuse.
+
+## Quick start
+1) Clarify what to capture (decision, how-to, FAQ, learning, documentation) and target audience.
+2) Identify the right database/template in `reference/` (team wiki, how-to, FAQ, decision log, learning, documentation).
+3) Pull any prior context from Notion with `Notion:notion-search` → `Notion:notion-fetch` (existing pages to update/link).
+4) Draft the page with `Notion:notion-create-pages` using the database’s schema; include summary, context, source links, and tags/owners.
+5) Link from hub pages and related records; update status/owners with `Notion:notion-update-page` as the source evolves.
+
+## Workflow
+### 0) If any MCP call fails because Notion MCP is not connected, pause and set it up:
+1. Add the Notion MCP:
+   - `codex mcp add notion --url https://mcp.notion.com/mcp`
+2. Enable remote MCP client:
+   - Set `[features].rmcp_client = true` in `config.toml` **or** run `codex --enable rmcp_client`
+3. Log in with OAuth:
+   - `codex mcp login notion`
+
+After successful login, the user will have to restart codex. You should finish your answer and tell them so when they try again they can continue with Step 1.
+
+### 1) Define the capture
+- Ask purpose, audience, freshness, and whether this is new or an update.
+- Determine content type: decision, how-to, FAQ, concept/wiki entry, learning/note, documentation page.
+
+### 2) Locate destination
+- Pick the correct database using `reference/*-database.md` guides; confirm required properties (title, tags, owner, status, date, relations).
+- If multiple candidate databases, ask the user which to use; otherwise, create in the primary wiki/documentation DB.
+
+### 3) Extract and structure
+- Extract facts, decisions, actions, and rationale from the conversation.
+- For decisions, record alternatives, rationale, and outcomes.
+- For how-tos/docs, capture steps, pre-reqs, links to assets/code, and edge cases.
+- For FAQs, phrase as Q&A with concise answers and links to deeper docs.
+
+### 4) Create/update in Notion
+- Use `Notion:notion-create-pages` with the correct `data_source_id`; set properties (title, tags, owner, status, dates, relations).
+- Use templates in `reference/` to structure content (section headers, checklists).
+- If updating an existing page, fetch then edit via `Notion:notion-update-page`.
+
+### 5) Link and surface
+- Add relations/backlinks to hub pages, related specs/docs, and teams.
+- Add a short summary/changelog for future readers.
+- If follow-up tasks exist, create tasks in the relevant database and link them.
+
+## References and examples
+- `reference/` — database schemas and templates (e.g., `team-wiki-database.md`, `how-to-guide-database.md`, `faq-database.md`, `decision-log-database.md`, `documentation-database.md`, `learning-database.md`, `database-best-practices.md`).
+- `examples/` — capture patterns in practice (e.g., `decision-capture.md`, `how-to-guide.md`, `conversation-to-faq.md`).

package/skills_ref/notion-meeting-intelligence/SKILL.md

@@ -0,0 +1,60 @@
+---
+name: notion-meeting-intelligence
+description: Prepare meeting materials with Notion context and Codex research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.
+metadata:
+  short-description: Prep meetings with Notion context and tailored agendas
+---
+
+# Meeting Intelligence
+
+Prep meetings by pulling Notion context, tailoring agendas/pre-reads, and enriching with Codex research.
+
+## Quick start
+1) Confirm meeting goal, attendees, date/time, and decisions needed.
+2) Gather context: search with `Notion:notion-search`, then fetch with `Notion:notion-fetch` (prior notes, specs, OKRs, decisions).
+3) Pick the right template via `reference/template-selection-guide.md` (status, decision, planning, retro, 1:1, brainstorming).
+4) Draft agenda/pre-read in Notion with `Notion:notion-create-pages`, embedding source links and owner/timeboxes.
+5) Enrich with Codex research (industry insights, benchmarks, risks) and update the page with `Notion:notion-update-page` as plans change.
+
+## Workflow
+### 0) If any MCP call fails because Notion MCP is not connected, pause and set it up:
+1. Add the Notion MCP:
+   - `codex mcp add notion --url https://mcp.notion.com/mcp`
+2. Enable remote MCP client:
+   - Set `[features].rmcp_client = true` in `config.toml` **or** run `codex --enable rmcp_client`
+3. Log in with OAuth:
+   - `codex mcp login notion`
+
+After successful login, the user will have to restart codex. You should finish your answer and tell them so when they try again they can continue with Step 1.
+
+### 1) Gather inputs
+- Ask for objective, desired outcomes/decisions, attendees, duration, date/time, and prior materials.
+- Search Notion for relevant docs, past notes, specs, and action items (`Notion:notion-search`), then fetch key pages (`Notion:notion-fetch`).
+- Capture blockers/risks and open questions up front.
+
+### 2) Choose format
+- Status/update → status template.
+- Decision/approval → decision template.
+- Planning (sprint/project) → planning template.
+- Retro/feedback → retrospective template.
+- 1:1 → one-on-one template.
+- Ideation → brainstorming template.
+- Use `reference/template-selection-guide.md` to confirm.
+
+### 3) Build the agenda/pre-read
+- Start from the chosen template in `reference/` and adapt sections (context, goals, agenda, owner/time per item, decisions, risks, prep asks).
+- Include links to pulled Notion pages and any required pre-reading.
+- Assign owners for each agenda item; call out timeboxes and expected outputs.
+
+### 4) Enrich with research
+- Add concise Codex research where helpful: market/industry facts, benchmarks, risks, best practices.
+- Keep claims cited with source links; separate fact from opinion.
+
+### 5) Finalize and share
+- Add next steps and owners for follow-ups.
+- If tasks arise, create/link tasks in the relevant Notion database.
+- Update the page via `Notion:notion-update-page` when details change; keep a brief changelog if multiple edits.
+
+## References and examples
+- `reference/` — template picker and meeting templates (e.g., `template-selection-guide.md`, `status-update-template.md`, `decision-meeting-template.md`, `sprint-planning-template.md`, `one-on-one-template.md`, `retrospective-template.md`, `brainstorming-template.md`).
+- `examples/` — end-to-end meeting preps (e.g., `executive-review.md`, `project-decision.md`, `sprint-planning.md`, `customer-meeting.md`).