{
"canonical_name": "starascendin/lifeos-plugin",
"compilation_id": "pack_281302ac4a1a4ffc800ed79f9f0fb557",
"created_at": "2026-05-24T13:36:33.262441+00:00",
"created_by": "project-pack-compiler",
"feedback": {
"carrier_selection_notes": [
"viable_asset_types=mcp_config, recipe, host_instruction, eval, preflight",
"recommended_asset_types=mcp_config, recipe, host_instruction, eval, preflight"
],
"evidence_delta": {
"confirmed_claims": [
"identity_anchor_present",
"capability_and_host_targets_present",
"install_path_declared_or_better"
],
"missing_required_fields": [],
"must_verify_forwarded": [
"Run or inspect `npm install -g @starascendin/lifeos-mcp` in an isolated environment.",
"Confirm the project exposes the claimed capability to at least one target host."
],
"quickstart_execution_scope": "allowlisted_sandbox_smoke",
"sandbox_command": "npm install -g @starascendin/lifeos-mcp",
"sandbox_container_image": "node:22-slim",
"sandbox_execution_backend": "docker",
"sandbox_planner_decision": "llm_execute_isolated_install",
"sandbox_validation_id": "sbx_126ecf565e484e4a820ac6b522356e3b"
},
"feedback_event_type": "project_pack_compilation_feedback",
"learning_candidate_reasons": [],
"template_gaps": []
},
"identity": {
"canonical_id": "project_481454b107c83a3e4d8d870bfb1432a0",
"canonical_name": "starascendin/lifeos-plugin",
"homepage_url": null,
"license": "unknown",
"repo_url": "https://github.com/starascendin/lifeos-plugin",
"slug": "lifeos-plugin",
"source_packet_id": "phit_c14537f473d54a189958fa00fd68413a",
"source_validation_id": "dval_2b869867bfa14bf0a0a6e55815a364d2"
},
"merchandising": {
"best_for": "需要工具连接与集成能力，并使用 mcp_host的用户",
"github_forks": 0,
"github_stars": 0,
"one_liner_en": "LifeOS plugin - 20 workflow skills and MCP integration for Claude Code, OpenCode, and other AI agents",
"one_liner_zh": "LifeOS plugin - 20 workflow skills and MCP integration for Claude Code, OpenCode, and other AI agents",
"primary_category": {
"category_id": "tool-integrations",
"confidence": "high",
"name_en": "Tool Integrations",
"name_zh": "工具连接与集成",
"reason": "matched_keywords:mcp, integration, github"
},
"target_user": "使用 mcp_host, claude, claude_code 等宿主 AI 的用户",
"title_en": "lifeos-plugin",
"title_zh": "lifeos-plugin 能力包",
"visible_tags": [
{
"label_en": "MCP Tools",
"label_zh": "MCP 工具",
"source": "repo_evidence_project_characteristics",
"tag_id": "product_domain-mcp-tools",
"type": "product_domain"
},
{
"label_en": "Knowledge Base Q&A",
"label_zh": "知识库问答",
"source": "repo_evidence_project_characteristics",
"tag_id": "user_job-knowledge-base-q-a",
"type": "user_job"
},
{
"label_en": "Multi-agent Collaboration",
"label_zh": "多 Agent 协作",
"source": "repo_evidence_project_characteristics",
"tag_id": "core_capability-multi-agent-collaboration",
"type": "core_capability"
},
{
"label_en": "Multi-role Workflow",
"label_zh": "多角色协作流程",
"source": "repo_evidence_project_characteristics",
"tag_id": "workflow_pattern-multi-role-workflow",
"type": "workflow_pattern"
},
{
"label_en": "Evaluation Suite",
"label_zh": "评测体系",
"source": "repo_evidence_project_characteristics",
"tag_id": "selection_signal-evaluation-suite",
"type": "selection_signal"
}
]
},
"packet_id": "phit_c14537f473d54a189958fa00fd68413a",
"page_model": {
"artifacts": {
"artifact_slug": "lifeos-plugin",
"files": [
"PROJECT_PACK.json",
"QUICK_START.md",
"PROMPT_PREVIEW.md",
"HUMAN_MANUAL.md",
"AI_CONTEXT_PACK.md",
"BOUNDARY_RISK_CARD.md",
"PITFALL_LOG.md",
"REPO_INSPECTION.json",
"REPO_INSPECTION.md",
"CAPABILITY_CONTRACT.json",
"EVIDENCE_INDEX.json",
"CLAIM_GRAPH.json"
],
"required_files": [
"PROJECT_PACK.json",
"QUICK_START.md",
"PROMPT_PREVIEW.md",
"HUMAN_MANUAL.md",
"AI_CONTEXT_PACK.md",
"BOUNDARY_RISK_CARD.md",
"PITFALL_LOG.md",
"REPO_INSPECTION.json"
]
},
"detail": {
"capability_source": "Project Hit Packet + DownstreamValidationResult",
"commands": [
{
"command": "npm install -g @starascendin/lifeos-mcp",
"label": "Node.js / npm · 官方安装入口",
"source": "https://github.com/starascendin/lifeos-plugin#readme",
"verified": true
}
],
"display_tags": [
"MCP 工具",
"知识库问答",
"多 Agent 协作",
"多角色协作流程",
"评测体系"
],
"eyebrow": "工具连接与集成",
"glance": [
{
"body": "判断自己是不是目标用户。",
"label": "最适合谁",
"value": "需要工具连接与集成能力，并使用 mcp_host的用户"
},
{
"body": "先理解能力边界，再决定是否继续。",
"label": "核心价值",
"value": "LifeOS plugin - 20 workflow skills and MCP integration for Claude Code, OpenCode, and other AI agents"
},
{
"body": "未完成验证前保持审慎。",
"label": "继续前",
"value": "publish to Doramagic.ai project surfaces"
}
],
"guardrail_source": "Boundary & Risk Card",
"guardrails": [
{
"body": "Prompt Preview 只展示流程，不证明项目已安装或运行。",
"label": "Check 1",
"value": "不要把试用当真实运行"
},
{
"body": "mcp_host, claude, claude_code",
"label": "Check 2",
"value": "确认宿主兼容"
},
{
"body": "publish to Doramagic.ai project surfaces",
"label": "Check 3",
"value": "先隔离验证"
}
],
"mode": "mcp_config, recipe, host_instruction, eval, preflight",
"pitfall_log": {
"items": [
{
"body": "项目面向 Claude/Cursor/Codex/Gemini/OpenCode 等宿主，或安装命令涉及用户配置目录。",
"category": "配置坑",
"evidence": [
"capability.host_targets | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | host_targets=mcp_host, claude, claude_code"
],
"severity": "medium",
"suggested_check": "列出会写入的配置文件、目录和卸载/回滚步骤。",
"title": "可能修改宿主 AI 配置",
"user_impact": "安装可能改变本机 AI 工具行为，用户需要知道写入位置和回滚方法。"
},
{
"body": "README/documentation is current enough for a first validation pass.",
"category": "能力坑",
"evidence": [
"capability.assumptions | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | README/documentation is current enough for a first validation pass."
],
"severity": "medium",
"suggested_check": "将假设转成下游验证清单。",
"title": "能力判断依赖假设",
"user_impact": "假设不成立时，用户拿不到承诺的能力。"
},
{
"body": "未记录 last_activity_observed。",
"category": "维护坑",
"evidence": [
"evidence.maintainer_signals | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | last_activity_observed missing"
],
"severity": "medium",
"suggested_check": "补 GitHub 最近 commit、release、issue/PR 响应信号。",
"title": "维护活跃度未知",
"user_impact": "新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。"
},
{
"body": "no_demo",
"category": "安全/权限坑",
"evidence": [
"downstream_validation.risk_items | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | no_demo; severity=medium"
],
"severity": "medium",
"suggested_check": "进入安全/权限治理复核队列。",
"title": "下游验证发现风险项",
"user_impact": "下游已经要求复核，不能在页面中弱化。"
},
{
"body": "no_demo",
"category": "安全/权限坑",
"evidence": [
"risks.scoring_risks | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | no_demo; severity=medium"
],
"severity": "medium",
"suggested_check": "把风险写入边界卡，并确认是否需要人工复核。",
"title": "存在评分风险",
"user_impact": "风险会影响是否适合普通用户安装。"
},
{
"body": "issue_or_pr_quality=unknown。",
"category": "维护坑",
"evidence": [
"evidence.maintainer_signals | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | issue_or_pr_quality=unknown"
],
"severity": "low",
"suggested_check": "抽样最近 issue/PR，判断是否长期无人处理。",
"title": "issue/PR 响应质量未知",
"user_impact": "用户无法判断遇到问题后是否有人维护。"
},
{
"body": "release_recency=unknown。",
"category": "维护坑",
"evidence": [
"evidence.maintainer_signals | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | release_recency=unknown"
],
"severity": "low",
"suggested_check": "确认最近 release/tag 和 README 安装命令是否一致。",
"title": "发布节奏不明确",
"user_impact": "安装命令和文档可能落后于代码，用户踩坑概率升高。"
}
],
"source": "ProjectPitfallLog + ProjectHitPacket + validation + community signals",
"summary": "发现 7 个潜在踩坑项，其中 0 个为 high/blocking；最高优先级：配置坑 - 可能修改宿主 AI 配置。",
"title": "踩坑日志"
},
"snapshot": {
"contributors": 2,
"forks": 0,
"license": "unknown",
"note": "站点快照，非实时质量证明；用于开工前背景判断。",
"stars": 0
},
"source_url": "https://github.com/starascendin/lifeos-plugin",
"steps": [
{
"body": "不安装项目，先体验能力节奏。",
"code": "preview",
"title": "先试 Prompt"
},
{
"body": "理解输入、输出、失败模式和边界。",
"code": "manual",
"title": "读说明书"
},
{
"body": "把上下文交给宿主 AI 继续工作。",
"code": "context",
"title": "带给 AI"
},
{
"body": "进入主力环境前先完成安装入口与风险边界验证。",
"code": "verify",
"title": "沙箱验证"
}
],
"subtitle": "LifeOS plugin - 20 workflow skills and MCP integration for Claude Code, OpenCode, and other AI agents",
"title": "lifeos-plugin 能力包",
"trial_prompt": "# lifeos-plugin - Prompt Preview\n\n> Copy the prompt below into your AI host before installing anything.\n> Its purpose is to let you safely feel the project's workflow, not to claim the project has already run.\n\n## Copy this prompt\n\n```text\nYou are using an independent Doramagic capability pack for starascendin/lifeos-plugin.\n\nProject:\n- Name: lifeos-plugin\n- Repository: https://github.com/starascendin/lifeos-plugin\n- Summary: LifeOS plugin - 20 workflow skills and MCP integration for Claude Code, OpenCode, and other AI agents\n- Host target: mcp_host, claude, claude_code\n\nGoal:\nHelp me evaluate this project for the following task without installing it yet: LifeOS plugin - 20 workflow skills and MCP integration for Claude Code, OpenCode, and other AI agents\n\nBefore taking action:\n1. Restate my task, success standard, and boundary.\n2. Identify whether the next step requires tools, browser access, network access, filesystem access, credentials, package installation, or host configuration.\n3. Use only the Doramagic Project Pack, the upstream repository, and the source-linked evidence listed below.\n4. If a real command, install step, API call, file write, or host integration is required, mark it as \"requires post-install verification\" and ask for approval first.\n5. If evidence is missing, say \"evidence is missing\" instead of filling the gap.\n\nPreviewable capabilities:\n- Capability 1: Use the source-backed project context to guide one small, checkable workflow step.\n\nCapabilities that require post-install verification:\n- Capability 1: Use the source-backed project context to guide one small, checkable workflow step.\n- Capability 2: Use the source-backed project context to guide one small, checkable workflow step.\n\nCore service flow:\n1. overview: Overview. Produce one small intermediate artifact and wait for confirmation.\n2. skills-overview: Skills Overview. Produce one small intermediate artifact and wait for confirmation.\n3. daily-workflows: Daily Workflows. Produce one small intermediate artifact and wait for confirmation.\n4. project-management: Project Management. Produce one small intermediate artifact and wait for confirmation.\n5. client-management: Client Management. Produce one small intermediate artifact and wait for confirmation.\n\nSource-backed evidence to keep in mind:\n- https://github.com/starascendin/lifeos-plugin\n- https://github.com/starascendin/lifeos-plugin#readme\n- skills/blind-spot-finder/SKILL.md\n- skills/capture/SKILL.md\n- skills/client-brief/SKILL.md\n- skills/client-health/SKILL.md\n- skills/coach-memory/SKILL.md\n- skills/coaching-action-items/SKILL.md\n- skills/coaching-overview/SKILL.md\n- skills/coaching-session-review/SKILL.md\n\nFirst response rules:\n1. Start Step 1 only.\n2. Explain the one service action you will perform first.\n3. Ask exactly three questions about my target workflow, success standard, and sandbox boundary.\n4. Stop and wait for my answers.\n\nStep 1 follow-up protocol:\n- After I answer the first three questions, stay in Step 1.\n- Produce six parts only: clarified task, success standard, boundary conditions, two or three options, tradeoffs for each option, and one recommendation.\n- End by asking whether I confirm the recommendation.\n- Do not move to Step 2 until I explicitly confirm.\n\nConversation rules:\n- Advance one step at a time and wait for confirmation after each small artifact.\n- Write outputs as recommendations or planned checks, not as completed execution.\n- Do not claim tests passed, files changed, commands ran, APIs were called, or the project was installed.\n- If the user asks for execution, first provide the sandbox setup, expected output, rollback, and approval checkpoint.\n```\n",
"voices": [
{
"body": "当前没有项目级社区来源；不会把未抓取讨论包装成社会证明。",
"items": [],
"status": "待发现 Agent 补证",
"title": "社区讨论"
}
]
},
"homepage_card": {
"category": "工具连接与集成",
"desc": "LifeOS plugin - 20 workflow skills and MCP integration for Claude Code, OpenCode, and other AI agents",
"effort": "安装已验证",
"forks": 0,
"icon": "link",
"name": "lifeos-plugin 能力包",
"risk": "需复核",
"slug": "lifeos-plugin",
"stars": 0,
"tags": [
"MCP 工具",
"知识库问答",
"多 Agent 协作",
"多角色协作流程",
"评测体系"
],
"thumb": "gray",
"type": "MCP 配置"
},
"manual": {
"markdown": "# https://github.com/starascendin/lifeos-plugin 项目说明书\n\n生成时间：2026-05-18 00:31:52 UTC\n\n## 目录\n\n- [Overview](#overview)\n- [Installation Guide](#installation)\n- [Skills Overview](#skills-overview)\n- [Daily Workflows](#daily-workflows)\n- [Habits & Accountability](#habits-accountability)\n- [Health Integration (Oura Ring)](#health-integration)\n- [Project Management](#project-management)\n- [Client Management](#client-management)\n- [People & Relationships](#people-relationships)\n- [Review Workflows](#review-workflows)\n- [Finance Management](#finance-management)\n- [Coaching System](#coaching-system)\n\n\n\n## Overview\n\n### 相关页面\n\n相关主题：[Installation Guide](#installation), [Skills Overview](#skills-overview)\n\n\nRelevant Source Files
\n\n以下源码文件用于生成本页说明：\n\n- [README.md](https://github.com/starascendin/lifeos-plugin/blob/main/README.md)\n- [AGENTS.md](https://github.com/starascendin/lifeos-plugin/blob/main/AGENTS.md)\n- [skills/daily-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/daily-plan/SKILL.md)\n- [skills/weekly-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/weekly-plan/SKILL.md)\n- [skills/sprint-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/sprint-plan/SKILL.md)\n- [skills/ppv/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/ppv/SKILL.md)\n- [skills/health-weekly/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/health-weekly/SKILL.md)\n- [skills/daily-training-report/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/daily-training-report/SKILL.md)\n- [skills/customer-success-triage/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md)\n- [skills/llm-council/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/llm-council/SKILL.md)\n- [skills/blind-spot-finder/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/blind-spot-finder/SKILL.md)\n \n\n# Overview\n\nLifeOS Plugin is a universal skills and MCP (Model Context Protocol) integration layer for LifeOS—a personal productivity operating system powered by Convex. The plugin extends AI agents (such as Claude Code and OpenCode) with 37 workflow skills, 126 MCP tools, and 28 MCP prompts, enabling them to interact with personal productivity data including tasks, projects, contacts, health metrics, finances, coaching insights, and life design systems.\n\n## Purpose and Scope\n\nThe primary purpose of LifeOS Plugin is to bridge AI agents with LifeOS data, allowing users to leverage AI capabilities for daily planning, project management, client relationship management, health tracking, and personal development through natural language commands.\n\nThe plugin provides:\n\n- **Workflow Automation**: Pre-built skills that execute complete workflows (e.g., daily planning, weekly review, sprint planning)\n- **Direct Data Access**: MCP tools enabling CRUD operations on all LifeOS entities\n- **Multi-Agent Compatibility**: Support for Claude Code, OpenCode, and any MCP-compatible client\n- **Mutating and Read Operations**: Both query and modification capabilities across the productivity stack\n\n资料来源：[README.md:1]()\n\n## Architecture\n\n### System Components\n\n```mermaid\ngraph TD\n A[AI Agent
Claude Code / OpenCode] --> B[LifeOS Plugin Skills]\n A --> C[MCP Client]\n C --> D[lifeos-mcp Server
@starascendin/lifeos-mcp]\n D --> E[LifeOS Convex Backend]\n E --> F[(Convex Database)]\n \n B -->|\"Invokes Skills\"| A\n C -->|\"MCP Protocol
126 Tools, 28 Prompts\"| D\n \n style F fill:#e1f5fe\n style D fill:#fff3e0\n style B fill:#e8f5e9\n```\n\n### Data Flow\n\n```mermaid\nsequenceDiagram\n participant User\n participant Agent as AI Agent\n participant Skills as Plugin Skills\n participant MCP as MCP Server\n participant Convex as LifeOS Backend\n \n User->>Agent: /daily-plan \"Plan my day\"\n Agent->>Skills: Invoke daily-plan skill\n Skills->>MCP: get_planning_context()\n MCP->>Convex: Query tasks, habits, calendar\n Convex-->>MCP: Planning data\n MCP-->>Skills: Context object\n Skills->>Skills: Build day plan\n Skills->>MCP: apply_planning_patch(mode=\"day\")\n MCP->>Convex: Mutate due dates, priorities\n Convex-->>MCP: Confirmation\n MCP-->>Skills: Applied changes\n Skills-->>Agent: Summary report\n Agent-->>User: Today's top 3 + changes\n```\n\n## Installation Methods\n\n### Agent-Specific Setup\n\n| Agent | Method | Command/Steps |\n|-------|--------|---------------|\n| Claude Code | Single command | `claude plugin add github:starascendin/lifeos-plugin` |\n| OpenCode | Copy or symlink | `cp -r skills/ .claude/skills/lifeos/` or symlink |\n| Manual | Copy directory | Copy `skills/` to agent's skills location |\n\n资料来源：[README.md:16-37]()\n\n### Environment Configuration\n\nRequired credentials must be configured via environment variables:\n\n```bash\nexport LIFEOS_CONVEX_URL=https://your-app.convex.site\nexport LIFEOS_USER_ID=your-user-id\nexport LIFEOS_API_KEY=your-api-key\n```\n\n| Variable | Description | Source |\n|----------|-------------|--------|\n| `LIFEOS_CONVEX_URL` | Convex deployment URL (`.convex.site`) | Convex Dashboard |\n| `LIFEOS_USER_ID` | LifeOS user identifier | Convex Dashboard > Users |\n| `LIFEOS_API_KEY` | API authentication key | LifeOS Settings |\n\n资料来源：[README.md:5-8]()\n\n### MCP Server Configuration\n\nFor MCP-compatible clients, configure the server in your MCP settings:\n\n```json\n{\n \"mcpServers\": {\n \"lifeos\": {\n \"command\": \"npx\",\n \"args\": [\n \"@starascendin/lifeos-mcp@latest\",\n \"--url\", \"YOUR_CONVEX_URL\",\n \"--user-id\", \"YOUR_USER_ID\",\n \"--api-key\", \"YOUR_API_KEY\"\n ]\n }\n }\n}\n```\n\n资料来源：[README.md:31-44]()\n\n## Skills Catalog\n\nThe plugin provides 37 workflow skills organized into categories. Each skill is a self-contained workflow that can be invoked via slash commands (e.g., `/daily-plan`).\n\n资料来源：[AGENTS.md:1]()\n\n### Daily Workflows\n\n| Skill | Purpose |\n|-------|---------|\n| `daily-standup` | Morning briefing with agenda, tasks, and sprint progress |\n| `daily-plan` | Plan today with due date, priority, cycle, and Daily Note changes |\n| `end-of-day` | EOD wrap-up with completion summary and tomorrow planning |\n| `capture` | Quick capture of thoughts, tasks, or notes with auto-routing |\n\n### Reviews\n\n| Skill | Purpose |\n|-------|---------|\n| `weekly-review` | Review completed work, in-progress items, and sprint health |\n| `weekly-plan` | Plan the week with current cycle, due date, priority, and note changes |\n| `monthly-review` | Accomplishments, project progress, and next month planning |\n| `cycle-review` | Sprint review with rollover options |\n| `initiative-review` | Yearly initiative progress by category |\n\n### Project & Client Management\n\n| Skill | Purpose |\n|-------|---------|\n| `project-status` | Phase breakdown, task stats, and blockers |\n| `client-brief` | Full client briefing with projects and communications |\n| `client-health` | Health dashboard across all clients |\n| `sprint-plan` | Plan the current cycle and apply task/cycle mutations |\n\n### People & Relationships\n\n| Skill | Purpose |\n|-------|---------|\n| `contact-lookup` | Full contact dossier with AI insights |\n| `meeting-prep` | Prepare for meetings with full context |\n| `follow-ups` | Track follow-ups needed with people and clients |\n| `relationship-pulse` | Check on neglected relationships |\n| `context-switch` | Fast context loading for a client or project |\n\n### Inbox & Tasks\n\n| Skill | Purpose |\n|-------|---------|\n| `inbox-triage` | Process notes into tasks |\n| `overdue` | Overdue and slipping items |\n\n### Voice & Notes\n\n| Skill | Purpose |\n|-------|---------|\n| `voice-notes` | Interactive memo exploration |\n| `voice-notes-crystallize` | Save conversation insights |\n\n### Health & Fitness\n\n| Skill | Purpose |\n|-------|---------|\n| `health-check` | Quick Oura health overview: scores and trends |\n| `health-weekly` | Weekly health review with workouts |\n| `screentime-report` | Screen time analysis and top apps |\n| `habit-check` | Daily habit check-in, streaks, and completions |\n| `daily-training-report` | Daily training report with health + habits |\n\n### Finance\n\n| Skill | Purpose |\n|-------|---------|\n| `finance-overview` | Net worth, accounts, and trends |\n| `finance-spending` | Spending analysis and patterns |\n\n### Coaching & Development\n\n| Skill | Purpose |\n|-------|---------|\n| `coaching-overview` | Coaching profiles, sessions, and action items |\n| `coaching-action-items` | Manage coaching action items |\n| `coaching-session-review` | Review coaching session insights |\n| `coach-memory` | View AI coach's accumulated knowledge |\n\n### Life Design\n\n| Skill | Purpose |\n|-------|---------|\n| `ppv` | Manage PPV vision, identity, pillars, project links, weekly actions, reflections, and adjustments |\n\n### Advanced AI Workflows\n\n| Skill | Purpose |\n|-------|---------|\n| `llm-council` | Multi-model deliberation for complex decisions |\n| `blind-spot-finder` | Multi-model council to find blind spots and self-deceptions |\n| `customer-success-triage` | Triage client requests using workspace, chats, meetings, and tasks |\n\n资料来源：[README.md:15-50](), [AGENTS.md:1-20]()\n\n## MCP Tools (126 Total)\n\nThe MCP server exposes 126 tools providing full CRUD operations across LifeOS entities:\n\n### Data Categories\n\n| Category | Operations | Examples |\n|----------|------------|----------|\n| Projects | CRUD | `get_projects`, `create_project`, `update_project` |\n| Tasks/Issues | CRUD | `get_tasks`, `create_issue`, `update_issue`, `schedule_issue` |\n| Cycles | CRUD | `get_current_cycle`, `update_cycle_goals` |\n| Clients | CRUD | `get_clients`, `create_client`, `update_client` |\n| People/Contacts | CRUD | `get_contacts`, `create_person`, `update_person` |\n| Notes | CRUD | `get_notes`, `create_note`, `update_client_note` |\n| Voice Memos | CRUD | `get_voice_memos`, `create_voice_memo` |\n| Meetings | Read | `get_granola_meeting`, `get_fathom_meeting` |\n| Health (Oura Ring) | Read | `get_health_sleep`, `get_health_activity`, `get_health_readiness`, `get_health_stress` |\n| Finance | Read | `get_finance_net_worth`, `get_finance_transactions` |\n| Habits | CRUD | `get_habits`, `get_habits_for_date` |\n| Coaching | CRUD | `get_coaching_action_items`, `create_coaching_action_item` |\n| PPV Life Design | CRUD | `get_ppv_workspace`, `upsert_ppv_vision`, `create_ppv_pillar` |\n\n资料来源：[AGENTS.md:21-24]()\n\n### Planning Workflow Tools\n\n```mermaid\ngraph LR\n A[get_planning_context] --> B[Build Plan]\n B --> C[apply_planning_patch]\n \n C --> D[\"create_issue\"]\n C --> E[\"schedule_issue\"]\n C --> F[\"update_issue\"]\n C --> G[\"assign_issue_to_current_cycle\"]\n C --> H[\"set_top_priority\"]\n C --> I[\"update_cycle_goals\"]\n C --> J[\"save_daily_note\"]\n C --> K[\"save_weekly_note\"]\n \n style A fill:#bbdefb\n style B fill:#c8e6c9\n style C fill:#ffe0b2\n```\n\nThe `apply_planning_patch` operation supports multiple mutation types depending on the planning mode:\n\n| Mode | Purpose | Common Operations |\n|------|---------|-------------------|\n| `day` | Daily planning | Schedule tasks, set top 3 priorities, update daily note |\n| `week` | Weekly planning | Assign backlog to cycle, update cycle goals, save weekly note |\n| `cycle` | Sprint planning | Assign issues, update cycle goals, schedule near-term work |\n\n资料来源：[skills/daily-plan/SKILL.md:1-35](), [skills/weekly-plan/SKILL.md:1-40](), [skills/sprint-plan/SKILL.md:1-35]()\n\n## MCP Prompts (28 Total)\n\nThe plugin exposes 28 MCP prompts—same workflows as the skills, but callable via MCP protocol. Any MCP-compatible client can invoke these prompts to trigger comprehensive workflow execution without directly invoking a skill file.\n\n资料来源：[AGENTS.md:25-27]()\n\n## Core Workflow Patterns\n\n### Planning Workflow Pattern\n\nMost planning skills follow a consistent three-step pattern:\n\n```mermaid\ngraph TD\n A[Step 1: Gather Context
get_planning_context] --> B[Step 2: Build Plan
Analyze and decide]\n B --> C[Step 3: Apply Changes
apply_planning_patch]\n \n A --> A1[\"daily=true
weekly=true
currentCycle=true
backlog=true
habits=true
dailyFields=true
calendar=true
voiceMemos=true\"]\n \n B --> B1[\"Pick top 3 priorities
Schedule tasks by dueDate
Assign backlog to cycle
Update cycle goals if needed\"]\n \n C --> C1[\"mode=day|week|cycle
dryRun=false\"]\n```\n\n### Mutating vs. Read-Only Workflows\n\nThe plugin distinguishes between:\n\n| Type | Behavior | Examples |\n|------|----------|----------|\n| **Mutating** | Modifies LifeOS data | `daily-plan`, `weekly-plan`, `sprint-plan`, `ppv` |\n| **Read-Only** | Queries and presents data | `health-weekly`, `finance-overview`, `contact-lookup` |\n\nMutating workflows execute without asking for confirmation—the user expects the plugin to modify LifeOS data automatically.\n\n资料来源：[skills/daily-plan/SKILL.md:33-36](), [skills/weekly-plan/SKILL.md:37-40](), [skills/sprint-plan/SKILL.md:33-36]()\n\n## PPV Life Design System\n\nThe PPV (Purpose, Principles, Values) system is a core component for long-term life design. It connects desired future states to daily execution.\n\n### PPV Data Model\n\n```mermaid\ngraph TD\n V[Vision
Future State] --> I[Identity
Who you are]\n V --> P[Pillars
Ongoing Systems]\n V --> PR[Projects
Existing LifeOS Projects]\n \n I --> B[Beliefs]\n I --> BH[Behaviors]\n \n P --> WA[Weekly Actions
Small, Concrete]\n \n PR --> TASKS[Tasks/Issues]\n \n WA --> R[Reflections
Weekly Energy Check]\n R --> AD[Adjustments
Feedback Loop]\n \n AD --> I\n AD --> P\n AD --> PR\n AD --> WA\n```\n\n### PPV Operations\n\n| Operation | Tool | Purpose |\n|-----------|------|---------|\n| View workspace | `get_ppv_workspace` | Get vision, identity, pillars, linked projects, actions |\n| View graph | `get_active_vision_graph` | Unified graph of vision + linked entities |\n| Create vision | `upsert_ppv_vision` | Set vivid, emotional, directional vision |\n| Edit identity | `upsert_ppv_identity` | Update coreIdentities, beliefs, behaviors |\n| Manage pillars | `create_ppv_pillar`, `update_ppv_pillar`, `delete_ppv_pillar` | Ongoing systems |\n| Execute | `create_ppv_weekly_action`, `update_ppv_weekly_action` | Small, identity-aligned actions |\n| Reflect | `create_ppv_reflection` | Capture weekly energy, resistance, alignment |\n| Adjust | `create_ppv_adjustment` | Feed insights back into the system |\n\n资料来源：[skills/ppv/SKILL.md:1-80]()\n\n## Health Integration\n\nThe plugin integrates with Oura Ring data through dedicated health tools:\n\n### Health Data Points\n\n| Category | Tools | Data Retrieved |\n|----------|-------|----------------|\n| Sleep | `get_health_sleep` | Scores, durations, bedtime, breath rate, restless periods |\n| Activity | `get_health_activity` | Steps, active days, calorie burn |\n| Readiness | `get_health_readiness` | Score trends, stress vs recovery |\n| Stress | `get_health_stress` | Stress levels, recovery balance |\n| Workouts | `get_health_workouts` | Workout history with labels |\n| Heart Rate | `get_health_heart_rate` | HR trends |\n| Resilience | `get_health_resilience` | Resilience levels and contributors |\n| VO2 Max | `get_health_vo2_max` | Cardiovascular fitness estimate |\n| Cardio Age | `get_health_cardio_age` | Cardiovascular age |\n| SpO2 | `get_health_spo2` | Blood oxygen, breathing disturbance |\n\n资料来源：[skills/health-weekly/SKILL.md:1-50](), [AGENTS.md:23]()\n\n## Advanced AI Workflows\n\n### LLM Council\n\nThe `llm-council` skill uses multiple AI models to deliberate on complex decisions:\n\n1. **Round 1**: Individual model responses to the question\n2. **Round 2**: Peer review and cross-evaluation\n3. **Chairman Synthesis**: Final authoritative answer\n\nOutput presentation includes individual responses, rankings table, and chairman's synthesis.\n\n资料来源：[skills/llm-council/SKILL.md:1-60]()\n\n### Blind Spot Finder\n\nThe `blind-spot-finder` skill uses multi-model analysis to identify unknown unknowns:\n\n1. Gather context (working memory, habits, health, finances)\n2. Build a comprehensive brief\n3. Run multi-model council for blind spot detection\n4. Analyze patterns and local maxima\n5. User selects one blind spot to work on\n\n资料来源：[skills/blind-spot-finder/SKILL.md:1-60]()\n\n## Daily Training Report\n\nThe `daily-training-report` skill generates a comprehensive daily briefing combining:\n\n- **Yesterday's Results**: Habit scorecard, streaks, health scores\n- **Today's Game Plan**: Top 3 priorities, scheduled habits\n- **Initiative Progress**: Yearly goal tracking\n- **Coaching Action Items**: Pending homework\n\nData sources include habits, health metrics, daily agenda, tasks, initiatives, and coaching items.\n\n资料来源：[skills/daily-training-report/SKILL.md:1-60]()\n\n## Customer Success Triage\n\nThe `customer-success-triage` skill provides structured triage for client work:\n\n1. Fetch client workspace\n2. Review threads, meetings, notes, and open tasks\n3. Drill down when needed (Beeper, Fathom, Granola, notes)\n4. Classify into: New Requirements, Follow-Ups, Risks/Blockers, Already Tracked\n5. Create notes or tasks as appropriate\n\n资料来源：[skills/customer-success-triage/SKILL.md:1-40]()\n\n## Updating the Plugin\n\n```bash\n# Update the plugin repository\ncd /path/to/lifeos-plugin && git pull\n\n# Update the MCP server (auto-updates with npx @latest)\n# Or pin a version in .mcp.json\n# \"@starascendin/lifeos-mcp@0.7.0\"\n```\n\n资料来源：[README.md:56-62]()\n\n## Summary\n\nLifeOS Plugin transforms AI agents into comprehensive personal productivity assistants by providing:\n\n1. **37 workflow skills** covering daily planning, reviews, project management, relationships, health, finance, coaching, and life design\n2. **126 MCP tools** for direct CRUD operations across all LifeOS entities\n3. **28 MCP prompts** for programmatic workflow invocation\n4. **Multi-agent support** via Claude Code plugin system and OpenCode native skills\n5. **Mutating capabilities** that execute changes without confirmation for automated productivity workflows\n\nThe plugin bridges the gap between AI reasoning capabilities and personal productivity data, enabling users to manage complex workflows through natural language commands while maintaining data consistency in their personal operating system.\n\n---\n\n\n\n## Installation Guide\n\n### 相关页面\n\n相关主题：[Overview](#overview)\n\n\nRelevant Source Files
\n\n以下源码文件用于生成本页说明：\n\n- [README.md](https://github.com/starascendin/lifeos-plugin/blob/main/README.md)\n- [AGENTS.md](https://github.com/starascendin/lifeos-plugin/blob/main/AGENTS.md)\n- [skills/daily-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/daily-plan/SKILL.md)\n- [skills/weekly-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/weekly-plan/SKILL.md)\n- [skills/sprint-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/sprint-plan/SKILL.md)\n \n\n# Installation Guide\n\nThis guide covers the complete installation process for integrating LifeOS Plugin with AI agents, enabling universal skills and MCP (Model Context Protocol) access to your personal productivity OS powered by Convex.\n\n## Overview\n\nThe LifeOS Plugin provides 37 workflow skills for project management, contacts, agendas, voice notes, health tracking (Oura Ring), finance, coaching, life direction, and more. The plugin works with multiple AI agent platforms including Claude Code and OpenCode.\n\n| Component | Description |\n|-----------|-------------|\n| **Skills** | 37 workflow automation skills (daily-plan, weekly-plan, health-check, etc.) |\n| **MCP Tools** | 126 full CRUD tools for data operations |\n| **MCP Prompts** | 28 prompts exposed via MCP protocol |\n| **Supported Agents** | Claude Code, OpenCode |\n\n资料来源：[README.md]()\n\n## Prerequisites\n\nBefore installing the LifeOS Plugin, you must obtain three credentials from the LifeOS Convex deployment.\n\n### Required Credentials\n\n| Variable | Description | Where to Find |\n|----------|-------------|---------------|\n| `LIFEOS_CONVEX_URL` | Your Convex deployment URL (format: `https://*.convex.site`) | Convex dashboard |\n| `LIFEOS_USER_ID` | Your LifeOS user ID | Convex dashboard > Users table |\n| `LIFEOS_API_KEY` | API key for authentication | Generated in LifeOS settings |\n\n资料来源：[AGENTS.md]()\n\n### Environment Variable Configuration\n\nSet the environment variables in your shell configuration:\n\n```bash\nexport LIFEOS_CONVEX_URL=https://your-app.convex.site\nexport LIFEOS_USER_ID=your-user-id\nexport LIFEOS_API_KEY=your-api-key\n```\n\nAlternatively, you can pass these credentials directly to the MCP server via command-line arguments or configuration files.\n\n资料来源：[README.md]()\n\n## Installation Methods\n\n### Claude Code Installation\n\nThe simplest installation method for Claude Code users.\n\n```bash\nclaude plugin add github:starascendin/lifeos-plugin\n```\n\nThis single command installs both the skills and MCP server automatically. After installation, ensure the environment variables are set for the MCP server to authenticate.\n\n资料来源：[README.md]()\n\n### OpenCode Installation\n\nOpenCode reads `.claude/skills/` natively. Two options are available:\n\n**Option A: Copy skills directory**\n```bash\ngit clone git@github.com:starascendin/lifeos-plugin.git /tmp/life\ncp -r /tmp/life/skills .claude/skills/lifeos\n```\n\n**Option B: Symlink skills directory**\n```bash\nln -s /path/to/lifeos-plugin/skills .claude/skills/lifeos\n```\n\n资料来源：[README.md]()\n\n### Manual MCP Server Setup\n\nFor custom agent integrations, configure the MCP server manually.\n\n```json\n{\n \"mcpServers\": {\n \"lifeos\": {\n \"command\": \"npx\",\n \"args\": [\n \"@starascendin/lifeos-mcp@latest\",\n \"--url\", \"YOUR_CONVEX_URL\",\n \"--user-id\", \"YOUR_USER_ID\",\n \"--api-key\", \"YOUR_API_KEY\"\n ]\n }\n }\n}\n```\n\n资料来源：[README.md]()\n\n### Version Pinning\n\nTo pin a specific MCP server version, update `.mcp.json`:\n\n```json\n{\n \"mcpServers\": {\n \"lifeos\": {\n \"command\": \"npx\",\n \"args\": [\n \"@starascendin/lifeos-mcp@0.7.0\",\n \"--url\", \"YOUR_CONVEX_URL\",\n \"--user-id\", \"YOUR_USER_ID\",\n \"--api-key\", \"YOUR_API_KEY\"\n ]\n }\n }\n}\n```\n\n资料来源：[README.md]()\n\n## Plugin Architecture\n\n```mermaid\ngraph TD\n A[AI Agent] --> B[LifeOS Plugin]\n B --> C[Skills Directory]\n B --> D[MCP Server]\n D --> E[Convex Backend]\n E --> F[LifeOS Database]\n \n C --> G[37 Workflow Skills]\n G --> H[Mutating Workflows]\n G --> I[Read-only Workflows]\n \n D --> J[126 MCP Tools]\n D --> K[28 MCP Prompts]\n \n J --> L[Projects CRUD]\n J --> M[Tasks CRUD]\n J --> N[Health Data]\n J --> O[Finance Data]\n J --> P[Contacts]\n```\n\n## Available Skills\n\nAfter installation, the following skill categories become available:\n\n### Daily Workflows\n\n| Skill | Purpose |\n|-------|---------|\n| `daily-standup` | Morning briefing with agenda, tasks, and sprint progress |\n| `daily-plan` | Plan today with due dates, priorities, cycle assignments, and Daily Note |\n| `end-of-day` | EOD wrap-up with completion summary and tomorrow planning |\n| `capture` | Quick capture a thought, task, or note with auto-routing |\n\n### Reviews\n\n| Skill | Purpose |\n|-------|---------|\n| `weekly-review` | Completed work, in-progress items, sprint health |\n| `weekly-plan` | Plan the week with cycle, due dates, priorities, and note updates |\n| `monthly-review` | Accomplishments, project progress, next month planning |\n| `cycle-review` | Sprint review with rollover options |\n| `initiative-review` | Yearly initiative progress by category |\n\n### Project & Client Management\n\n| Skill | Purpose |\n|-------|---------|\n| `project-status` | Phase breakdown, task stats, blockers |\n| `client-brief` | Full client briefing with projects and comms |\n| `client-health` | Health dashboard across all clients |\n| `sprint-plan` | Plan current cycle and apply task/cycle mutations |\n\n### People & Relationships\n\n| Skill | Purpose |\n|-------|---------|\n| `contact-lookup` | Full contact dossier with AI insights |\n| `meeting-prep` | Prepare for meetings with full context |\n| `follow-ups` | Track follow-ups needed |\n| `relationship-pulse` | Check on neglected relationships |\n| `context-switch` | Fast context loading for client/project |\n\n### Health & Fitness\n\n| Skill | Purpose |\n|-------|---------|\n| `health-check` | Quick Oura health overview: scores, trends |\n| `health-weekly` | Weekly health review with workouts |\n| `daily-training-report` | Daily training report with health + habits |\n\n### Finance\n\n| Skill | Purpose |\n|-------|---------|\n| `finance-overview` | Net worth, accounts, trends |\n| `finance-spending` | Spending analysis and patterns |\n\n### Personal Development\n\n| Skill | Purpose |\n|-------|---------|\n| `ppv` | PPV life design: vision, identity, pillars, weekly actions |\n| `llm-council` | Multi-model deliberation for complex decisions |\n| `blind-spot-finder` | Multi-model analysis for finding blind spots |\n\n资料来源：[README.md]()\n\n## Skill Invocation Patterns\n\nAfter installation, skills are invoked using slash commands in the agent interface.\n\n### Basic Invocation\n\n```bash\n/daily-plan\n/weekly-plan \"2024-01-15\"\n/health-check\n/finance-overview\n```\n\n### Client-Focused Skills\n\n```bash\n/project-status \"ACME\"\n/client-brief \"Acme Corp\"\n/meeting-prep \"John\"\n/customer-success-triage \"Acme Corp\"\n```\n\n### Planning Workflows\n\nThe planning skills (`daily-plan`, `weekly-plan`, `sprint-plan`) use the same underlying MCP tools:\n\n1. Call `get_planning_context` with relevant include flags\n2. Build the plan based on current cycle, backlog, and calendar\n3. Call `apply_planning_patch` with `dryRun=false` to apply mutations\n\n资料来源：[skills/daily-plan/SKILL.md]()\n资料来源：[skills/weekly-plan/SKILL.md]()\n资料来源：[skills/sprint-plan/SKILL.md]()\n\n## Updating the Plugin\n\n### Update Plugin Repository\n\n```bash\ncd /path/to/lifeos-plugin && git pull\n```\n\n### Update MCP Server\n\nThe MCP server auto-updates when using `@latest`:\n\n```bash\nnpx @starascendin/lifeos-mcp@latest\n```\n\nOr pin to a specific version in `.mcp.json` to prevent unexpected updates.\n\n资料来源：[README.md]()\n\n## MCP Tools Overview\n\nThe installation provides access to 126 MCP tools for full CRUD operations:\n\n| Category | Operations |\n|----------|------------|\n| Projects | Create, read, update, delete projects |\n| Tasks/Issues | Full task lifecycle management |\n| Cycles | Sprint/cycle planning and tracking |\n| Phases | Project phase management |\n| Clients | Client workspace and communications |\n| People/Contacts | Contact management with AI insights |\n| Notes | Note creation and retrieval |\n| Voice Memos | Voice memo recording and analysis |\n| Health | Oura Ring: sleep, activity, readiness, stress, SpO2, heart rate, workouts |\n| Finance | Accounts, net worth, transactions, snapshots, daily spending |\n| Habits | Habit tracking and streak management |\n| Coaching | Session tracking and action items |\n| PPV Life Design | Vision, identity, pillars, reflections, adjustments |\n\n资料来源：[AGENTS.md]()\n\n## Troubleshooting\n\n### Environment Variables Not Recognized\n\nEnsure environment variables are exported in the shell where the agent runs:\n\n```bash\n# Check if variables are set\necho $LIFEOS_CONVEX_URL\necho $LIFEOS_USER_ID\necho $LIFEOS_API_KEY\n```\n\n### MCP Server Connection Issues\n\nVerify the Convex URL format is correct:\n- Must be `https://*.convex.site`\n- User ID must match an entry in the Convex Users table\n- API key must be generated from LifeOS settings\n\n### Skills Not Available\n\nFor Claude Code: Re-run the plugin installation command\nFor OpenCode: Verify the skills directory exists at `.claude/skills/lifeos/`\n\n---\n\n\n\n## Skills Overview\n\n### 相关页面\n\n相关主题：[Daily Workflows](#daily-workflows), [Review Workflows](#review-workflows), [Project Management](#project-management), [Health Integration (Oura Ring)](#health-integration), [Coaching System](#coaching-system)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [README.md](https://github.com/starascendin/lifeos-plugin/blob/main/README.md)\n- [AGENTS.md](https://github.com/starascendin/lifeos-plugin/blob/main/AGENTS.md)\n- [skills/daily-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/daily-plan/SKILL.md)\n- [skills/weekly-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/weekly-plan/SKILL.md)\n- [skills/sprint-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/sprint-plan/SKILL.md)\n- [skills/customer-success-triage/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md)\n- [skills/ppv/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/ppv/SKILL.md)\n \n\n# Skills Overview\n\n## Introduction\n\nSkills are the core building blocks of the LifeOS Plugin, representing 37 pre-defined workflow skills that enable AI agents to interact with LifeOS data and execute productivity operations. Each skill is a structured instruction set that guides an AI agent through a specific workflow using the LifeOS MCP (Model Context Protocol) tools.\n\n资料来源：[README.md:1]()\n\nSkills serve as the human-readable workflow definitions that bridge AI agent reasoning with LifeOS data mutations. They encapsulate domain knowledge about productivity workflows—including planning, reviewing, client management, health tracking, and life design—into reusable, executable units.\n\n## Architecture\n\n```mermaid\ngraph TD\n A[AI Agent] -->|Invokes| B[Skill /slash command]\n B -->|Loads| C[SKILL.md Definition]\n C -->|Directs| D[MCP Tools]\n D -->|CRUD Operations| E[LifeOS Convex Backend]\n E -->|Returns Data| D\n D -->|Formats Response| F[User-Facing Report]\n \n G[Alternative: MCP Protocol] -->|28 Prompts| H[Direct MCP Invocation]\n H -->|Same Tools| E\n```\n\nThe plugin provides two complementary interfaces:\n\n| Interface Type | Count | Description |\n|----------------|-------|-------------|\n| Skills | 37 | Human-readable workflow definitions for slash command invocation |\n| MCP Prompts | 28 | Same workflows exposed via MCP protocol for programmatic clients |\n| MCP Tools | 126 | Full CRUD operations across all LifeOS domains |\n\n资料来源：[AGENTS.md:1]()\n\n## Skill Categories\n\nSkills are organized into functional categories that map to different aspects of personal and professional productivity.\n\n### Daily Workflows\n\nCore daily planning and reflection skills that drive day-to-day execution.\n\n| Skill | Command | Purpose |\n|-------|---------|---------|\n| daily-standup | `/daily-standup` | Morning briefing with agenda, tasks, and sprint progress |\n| daily-plan | `/daily-plan` | Plan today with due dates, priorities, cycle assignments, and Daily Note updates |\n| end-of-day | `/end-of-day` | EOD wrap-up with completion summary and tomorrow planning |\n| capture | `/capture \"thought\"` | Quick capture of thoughts, tasks, or notes with auto-routing |\n\n资料来源：[README.md:42-45]()\n\n### Reviews\n\nPeriodic reflection and planning skills for maintaining strategic alignment.\n\n| Skill | Command | Purpose |\n|-------|---------|---------|\n| weekly-review | `/weekly-review` | Completed work, in-progress items, sprint health |\n| weekly-plan | `/weekly-plan` | Plan the week with current cycle, due dates, priorities, and note changes |\n| monthly-review | `/monthly-review` | Accomplishments, project progress, next month planning |\n| cycle-review | `/cycle-review` | Sprint review with rollover options |\n| initiative-review | `/initiative-review 2026` | Yearly initiative progress by category |\n\n资料来源：[README.md:46-51]()\n\n### Project & Client Management\n\nSkills for managing client relationships and project execution.\n\n| Skill | Command | Purpose |\n|-------|---------|---------|\n| project-status | `/project-status ACME` | Phase breakdown, task stats, blockers |\n| client-brief | `/client-brief \"Acme Corp\"` | Full client briefing with projects and comms |\n| client-health | `/client-health` | Health dashboard across all clients |\n| sprint-plan | `/sprint-plan` | Plan current cycle with goals, backlog pull, due dates, priorities |\n| customer-success-triage | `/customer-success-triage \"Acme Corp\"` | Triage requests using chats, meetings, notes, and open work |\n\n资料来源：[README.md:52-57]()\n\n### People & Relationships\n\nSkills for managing contacts, meetings, and relationship health.\n\n| Skill | Command | Purpose |\n|-------|---------|---------|\n| contact-lookup | `/contact-lookup \"John\"` | Full contact dossier with AI insights |\n| meeting-prep | `/meeting-prep \"John\"` | Prepare for meetings with full context |\n| follow-ups | `/follow-ups` | Track follow-ups needed with people and clients |\n| relationship-pulse | `/relationship-pulse` | Check on neglected relationships |\n| context-switch | `/context-switch \"Acme\"` | Fast context loading for a client or project |\n\n资料来源：[README.md:58-63]()\n\n### Health & Fitness\n\nSkills integrating with Oura Ring data for health monitoring.\n\n| Skill | Command | Purpose |\n|-------|---------|---------|\n| health-check | `/health-check` | Quick Oura health overview: scores, trends |\n| health-weekly | `/health-weekly` | Weekly health review with workouts |\n| daily-training-report | `/daily-training-report` | Daily training report with health + habits |\n| habit-check | `/habit-check` | Daily habit check-in, streaks, completions |\n| screentime-report | `/screentime-report` | Screen time analysis and top apps |\n\n资料来源：[AGENTS.md:1]()\n\n### Finance\n\nSkills for financial tracking and analysis.\n\n| Skill | Command | Purpose |\n|-------|---------|---------|\n| finance-overview | `/finance-overview` | Net worth, accounts, trends |\n| finance-spending | `/finance-spending` | Spending analysis and patterns |\n\n### Coaching & Personal Development\n\nSkills for coaching integration and personal growth tracking.\n\n| Skill | Command | Purpose |\n|-------|---------|---------|\n| coaching-overview | `/coaching-overview` | Coaching profiles, sessions, action items |\n| coaching-action-items | `/coaching-action-items` | Manage coaching action items |\n| coaching-session-review | `/coaching-session-review` | Review coaching session insights |\n| coach-memory | `/coach-memory` | View AI coach's accumulated knowledge |\n| blind-spot-finder | `/blind-spot-finder` | Multi-model council to find blind spots |\n| decision-framework | `/decision-framework` | Structured decision-making with experiments |\n| llm-council | `/llm-council` | Multi-model deliberation for complex decisions |\n\n### PPV Life Design\n\nSkills for the Purpose, Priority, Vision (PPV) life design system.\n\n| Skill | Command | Purpose |\n|-------|---------|---------|\n| ppv | `/ppv` | Manage vision, identity, pillars, projects, weekly actions, reflections, adjustments |\n\n资料来源：[skills/ppv/SKILL.md:1]()\n\n## Skill Structure\n\nEach skill follows a standardized structure defined in `SKILL.md` files.\n\n### Anatomy of a SKILL.md File\n\n```yaml\n---\nname: skill-name\ndescription: One-line description of what the skill does\n---\n\n# Detailed instructions follow\n```\n\n### Standard Execution Pattern\n\n```mermaid\nsequenceDiagram\n participant U as User\n participant A as AI Agent\n participant M as MCP Tools\n participant L as LifeOS\n \n U->>A: Invoke skill /slash command\n A->>M: Call get_* context tool(s)\n M->>L: Query data\n L->>M: Return context\n M->>A: Context data\n A->>A: Analyze & plan\n A->>M: Call apply_* or update_* mutations\n M->>L: Execute changes\n L->>M: Confirmation\n M->>A: Results\n A->>U: Report summary\n```\n\n### Mutating vs. Read-Only Skills\n\nSkills are classified by their effect on LifeOS data:\n\n| Type | Characteristics | Examples |\n|------|-----------------|----------|\n| **Mutating** | Creates, updates, or deletes data | daily-plan, weekly-plan, sprint-plan, ppv |\n| **Read-Only** | Only queries and reports | health-check, finance-overview, contact-lookup |\n\n资料来源：[skills/daily-plan/SKILL.md:1]()\n\n## MCP Tool Integration\n\nSkills leverage the 126 MCP tools for data operations. The tools are organized by domain:\n\n### Planning Tools\n\nUsed by daily-plan, weekly-plan, sprint-plan, and similar skills.\n\n| Tool | Purpose |\n|------|---------|\n| `get_planning_context` | Retrieve comprehensive planning context including daily, weekly, current cycle, backlog, habits, and calendar |\n| `apply_planning_patch` | Apply batch mutations (mode: \"day\", \"week\", or \"cycle\") |\n| `create_issue` | Create new tasks |\n| `schedule_issue` | Set due dates and schedules |\n| `update_issue` | Modify task properties |\n| `assign_issue_to_current_cycle` | Add work to active cycle |\n| `set_top_priority` | Set today's top 3 priorities |\n| `update_cycle_goals` | Modify current cycle objectives |\n\n资料来源：[skills/daily-plan/SKILL.md:5-15]()\n\n### Planning Patch Operations\n\nThe `apply_planning_patch` tool supports multiple operation types:\n\n```json\n{\n \"mode\": \"day\" | \"week\" | \"cycle\",\n \"dryRun\": false,\n \"operations\": [\n { \"type\": \"create_issue\", \"data\": {...} },\n { \"type\": \"schedule_issue\", \"issueId\": \"...\", \"dueDate\": \"...\" },\n { \"type\": \"update_issue\", \"issueId\": \"...\", \"changes\": {...} },\n { \"type\": \"assign_issue_to_current_cycle\", \"issueId\": \"...\" },\n { \"type\": \"set_top_priority\", \"issueIds\": [...] },\n { \"type\": \"update_cycle_goals\", \"goals\": \"...\" },\n { \"type\": \"save_daily_note\", \"content\": \"...\" },\n { \"type\": \"save_weekly_note\", \"content\": \"...\" },\n { \"type\": \"add_issue_comment\", \"issueId\": \"...\", \"comment\": \"...\" }\n ]\n}\n```\n\n### Domain-Specific Tool Categories\n\n| Domain | Tool Count | Operations |\n|--------|------------|------------|\n| Projects | 20+ | CRUD, status, phases, statistics |\n| Issues/Tasks | 30+ | CRUD, assignment, scheduling, priorities |\n| Cycles | 10+ | CRUD, goals, planning |\n| Clients | 15+ | Workspace, health, notes |\n| People/Contacts | 10+ | Lookup, context graphs |\n| Health (Oura) | 30+ | Sleep, activity, readiness, stress, workouts, VO2 max |\n| Finance | 15+ | Accounts, net worth, transactions, spending |\n| Notes & Memos | 20+ | Voice memos, AI summaries, Beeper/Granola integration |\n| Coaching | 10+ | Action items, memories, PPV management |\n\n资料来源：[AGENTS.md:1]()\n\n## Installation & Setup\n\n### Claude Code\n\n```bash\nclaude plugin add github:starascendin/lifeos-plugin\n```\n\n资料来源：[README.md:10]()\n\n### OpenCode\n\n```bash\n# Option A: Clone and copy\ngit clone git@github.com:starascendin/lifeos-plugin.git /tmp/life\n\n# Option B: Symlink\nln -s /path/to/lifeos-plugin/skills .claude/skills/lifeos\n```\n\n资料来源：[AGENTS.md:1]()\n\n### MCP Server Configuration\n\nConfigure the MCP server in your agent's settings:\n\n```json\n{\n \"mcpServers\": {\n \"lifeos\": {\n \"command\": \"npx\",\n \"args\": [\n \"@starascendin/lifeos-mcp@latest\",\n \"--url\", \"YOUR_CONVEX_URL\",\n \"--user-id\", \"YOUR_USER_ID\",\n \"--api-key\", \"YOUR_API_KEY\"\n ]\n }\n }\n}\n```\n\n### Environment Variables\n\n| Variable | Description |\n|----------|-------------|\n| `LIFEOS_CONVEX_URL` | Convex deployment URL (`.convex.site`) |\n| `LIFEOS_USER_ID` | LifeOS user ID from Convex dashboard |\n| `LIFEOS_API_KEY` | API key for authentication |\n\n资料来源：[README.md:30-39]()\n\n## Example Skill: daily-plan\n\nThe `daily-plan` skill demonstrates the typical skill execution flow:\n\n```mermaid\ngraph TD\n A[Invoke /daily-plan] --> B[get_planning_context]\n B --> C{Include Options}\n C -->|daily=true| D[Today's tasks & agenda]\n C -->|weekly=true| E[This week's context]\n C -->|currentCycle=true| F[Active cycle data]\n C -->|backlog=true| G[Available backlog]\n C -->|habits=true| H[Habit data]\n C -->|dailyFields=true| I[Daily fields]\n C -->|calendar=true| J[Calendar events]\n C -->|voiceMemos=true| K[Recent memos]\n \n D --> L[Build Day Plan]\n E --> L\n F --> L\n G --> L\n H --> L\n I --> L\n J --> L\n K --> L\n \n L --> M[Select Top 3 Priorities]\n L --> N[Schedule Tasks by dueDate]\n L --> O[Pull Backlog into Cycle]\n L --> P[Update Cycle Goals if Needed]\n P --> Q[apply_planning_patch mode=day]\n M --> Q\n N --> Q\n O --> Q\n \n Q --> R[Mutations Applied]\n R --> S[Report: Top 3, Changes, Notes]\n```\n\n资料来源：[skills/daily-plan/SKILL.md:1]()\n\n## Example Skill: customer-success-triage\n\nThe `customer-success-triage` skill shows a domain-specific workflow:\n\n```mermaid\ngraph TD\n A[Invoke /customer-success-triage \"Acme Corp\"] --> B[get_client_success_workspace]\n B --> C{Workspace Contents}\n C --> D[recentThreads]\n C --> E[recentMeetings]\n C --> F[notes]\n C --> G[openTasks]\n C --> H[projects]\n \n D --> I[Drill Down if Needed]\n E --> I\n F --> I\n G --> I\n H --> I\n \n I --> J[get_beeper_thread_messages]\n I --> K[get_fathom_meeting]\n I --> L[get_granola_meeting]\n I --> M[get_client_notes]\n \n J --> N{Classify Findings}\n K --> N\n L --> N\n M --> N\n \n N --> O[New Requirements]\n N --> P[Follow-Ups]\n N --> Q[Risks / Blockers]\n N --> R[Already Tracked]\n \n O --> S[create_client_note]\n P --> S\n Q --> S\n R --> S\n \n S --> T[Report Classification]\n```\n\n资料来源：[skills/customer-success-triage/SKILL.md:1]()\n\n## PPV Life Design System\n\nThe PPV (Purpose, Priority, Vision) skill implements a comprehensive life design system:\n\n### Data Model\n\n```mermaid\ngraph TD\n A[Vision] --> B[Identity]\n A --> C[Pillars]\n C --> D[Projects]\n C --> E[Weekly Actions]\n E --> F[Reflections]\n F --> G[Adjustments]\n G --> B\n G --> C\n G --> D\n G --> E\n```\n\n### Vision Operations\n\n- `get_ppv_workspace` — Retrieve all PPV data plus available LifeOS projects\n- `get_active_vision_graph` — Unified graph of vision with linked projects, issues, and memos\n- `upsert_ppv_vision` — Create or update vision (vivid, emotional, directional)\n\n### Identity Operations\n\n- `upsert_ppv_identity` — Manage core identities, beliefs, and behaviors\n\n### Pillar Operations\n\n- `create_ppv_pillar`, `update_ppv_pillar`, `delete_ppv_pillar` — Manage ongoing systems\n\n### Execution Operations\n\n- `create_ppv_weekly_action`, `update_ppv_weekly_action`, `delete_ppv_weekly_action` — Weekly concrete actions\n\n### Learning Loop Operations\n\n- `create_ppv_reflection` — Capture weekly energy, resistance, alignment, momentum\n- `create_ppv_adjustment` — Update identity, pillars, projects, or actions based on reflection\n\n资料来源：[skills/ppv/SKILL.md:1]()\n\n## Updating\n\n```bash\n# Update the plugin repo\ncd /path/to/lifeos-plugin && git pull\n\n# Update the MCP server (auto-updates with npx @latest)\n# Or pin a version in .mcp.json: \"@starascendin/lifeos-mcp@0.7.0\"\n```\n\n资料来源：[README.md:88-94]()\n\n## Best Practices\n\n1. **Mutating Skills Don't Ask for Confirmation** — Skills like `daily-plan`, `weekly-plan`, and `sprint-plan` are designed to execute immediately when invoked.\n\n2. **Use Appropriate Planning Context** — Always include the relevant context flags when calling `get_planning_context`:\n - Daily planning: `daily=true`, `currentCycle=true`, `habits=true`\n - Weekly planning: `weekly=true`, `daily=true`, `currentCycle=true`, `backlog=true`\n - Cycle planning: `currentCycle=true`, `backlog=true`, `weekly=true`, `daily=true`\n\n3. **Avoid Duplicates** — When triaging or capturing, prefer updating existing notes/tasks over creating new ones.\n\n4. **Link, Don't Duplicate** — PPV pillars should link to existing LifeOS projects via `projectIds` rather than creating parallel systems.\n\n5. **Small, Concrete Weekly Actions** — PPV weekly actions should be identity-aligned and linkable to pillars or projects.\n\n6. **One Useful Mutation** — Keep PPV changes focused; prefer one useful mutation over comprehensive restructuring.\n\n资料来源：[skills/ppv/SKILL.md:10](), [skills/daily-plan/SKILL.md:24]()\n\n## Summary\n\nSkills are the primary interface through which AI agents interact with LifeOS. They provide:\n\n- **37 pre-defined workflows** covering daily planning, reviews, client management, health, finance, coaching, and life design\n- **Standardized structure** using SKILL.md files with clear execution patterns\n- **MCP tool integration** leveraging 126 CRUD operations across all LifeOS domains\n- **Two invocation methods** — slash commands for natural interaction and MCP prompts for programmatic access\n- **Mutating and read-only variants** — Some skills only query data, others apply changes directly\n\nThe skills system enables AI agents to act as knowledgeable productivity assistants, executing complex multi-step workflows while maintaining consistency and best practices.\n\n---\n\n\n\n## Daily Workflows\n\n### 相关页面\n\n相关主题：[Review Workflows](#review-workflows), [Habits & Accountability](#habits-accountability), [Project Management](#project-management)\n\n\nRelevant Source Files
\n\n以下源码文件用于生成本页说明：\n\n- [skills/daily-standup/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/daily-standup/SKILL.md)\n- [skills/daily-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/daily-plan/SKILL.md)\n- [skills/end-of-day/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/end-of-day/SKILL.md)\n- [skills/capture/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/capture/SKILL.md)\n- [README.md](https://github.com/starascendin/lifeos-plugin/blob/main/README.md)\n \n\n# Daily Workflows\n\n## Overview\n\nDaily Workflows in LifeOS provide a structured, AI-powered approach to managing day-to-day productivity. These four complementary skills form a complete daily rhythm: from morning preparation through execution to end-of-day reflection.\n\nThe workflows are designed to be **mutating** operations that directly modify LifeOS data through the MCP (Model Context Protocol) integration with Convex. They require no user confirmation once invoked—the system applies changes automatically based on AI-generated plans.\n\n| Workflow | Purpose | Type |\n|----------|---------|------|\n| `daily-standup` | Morning briefing with agenda, tasks, and sprint progress | Read-only |\n| `daily-plan` | Plan the day and apply mutations to due dates, priorities, cycles, and notes | Mutating |\n| `end-of-day` | EOD wrap-up with completion summary and tomorrow planning | Mutating |\n| `capture` | Quick capture of thoughts, tasks, or notes with auto-routing | Mutating |\n\n资料来源：[README.md](https://github.com/starascendin/lifeos-plugin/blob/main/README.md)\n\n## Architecture\n\n### Integration with LifeOS MCP\n\nDaily Workflows leverage the LifeOS MCP server (`@starascendin/lifeos-mcp`) which exposes 126 tools for full CRUD operations across the LifeOS data model. All workflows communicate exclusively through this MCP interface.\n\n```mermaid\ngraph TD\n A[User/Agent] -->|Invoke Skill| B[Daily Workflow Skill]\n B -->|MCP Tool Calls| C[LifeOS MCP Server]\n C -->|HTTP/WebSocket| D[Convex Backend]\n D -->|Real-time Sync| E[LifeOS Data Store]\n \n F[Oura Ring] -->|Health Data| D\n G[Calendar] -->|Schedule Data| D\n H[Voice Memos] -->|Audio Data| D\n```\n\n资料来源：[AGENTS.md](https://github.com/starascendin/lifeos-plugin/blob/main/AGENTS.md)\n\n### Workflow Data Flow\n\n```mermaid\ngraph LR\n A[daily-standup] -->|Read Context| B[get_daily_agenda]\n A -->|Read Tasks| C[get_todays_tasks]\n A -->|Read Sprint| D[get_current_cycle]\n \n E[daily-plan] -->|Read Context| F[get_planning_context]\n E -->|Write Changes| G[apply_planning_patch]\n \n H[end-of-day] -->|Write Summary| I[save_daily_note]\n H -->|Plan Tomorrow| J[schedule_issue]\n \n K[capture] -->|Quick Create| L[create_issue]\n K -->|Route| M[assign_issue_to_current_cycle]\n```\n\n## Daily Standup\n\n**Skill File:** `skills/daily-standup/SKILL.md`\n\n### Purpose\n\nThe `daily-standup` workflow provides a concise morning briefing covering today's agenda, tasks due, and sprint progress. It is a **read-only** operation that does not modify any data.\n\n### MCP Tools Used\n\n| Tool | Purpose |\n|------|---------|\n| `get_daily_agenda` | Today's tasks, calendar events, top priorities |\n| `get_todays_tasks` | Complete task list for today |\n| `get_overdue_tasks` | Open tasks that are past their due date |\n| `get_current_cycle` | Sprint progress and statistics |\n\n资料来源：[skills/daily-standup/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/daily-standup/SKILL.md)\n\n### Output Format\n\nThe workflow synthesizes data into a standup-style briefing:\n\n- **Today's Focus**: Top 3 priorities\n- **Tasks Due**: Tasks due today with priority levels\n- **Overdue**: Late tasks requiring immediate triage\n- **Sprint Progress**: Cycle completion percentage and key statistics\n- **Calendar**: Scheduled meetings and events\n\n### Date Parameter\n\nWhen `$ARGUMENTS` contains a date, the workflow uses that date instead of the current date for historical or future-day standups.\n\n## Daily Plan\n\n**Skill File:** `skills/daily-plan/SKILL.md`\n\n### Purpose\n\nThe `daily-plan` workflow plans the day and applies mutations to LifeOS. This is a **mutating workflow** that directly modifies due dates, priorities, cycle assignments, and Daily Notes.\n\n### Execution Steps\n\n```mermaid\ngraph TD\n 1[Call get_planning_context] --> 2[Build Day Plan]\n 2 --> 3[Pick Top 3 Priorities]\n 2 --> 4[Schedule Tasks by dueDate]\n 2 --> 5[Pull Backlog into Cycle]\n 2 --> 6[Update Cycle Goals if Needed]\n 3 --> 7[Call apply_planning_patch]\n 4 --> 7\n 5 --> 7\n 6 --> 7\n 7 --> 8[Report Changes]\n```\n\n资料来源：[skills/daily-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/daily-plan/SKILL.md)\n\n### Planning Context Parameters\n\nWhen calling `get_planning_context`, the workflow includes:\n\n| Parameter | Value | Purpose |\n|-----------|-------|---------|\n| `date` | From `$ARGUMENTS` or today | Target planning date |\n| `include.daily` | `true` | Daily context |\n| `include.weekly` | `true` | Weekly overview |\n| `include.currentCycle` | `true` | Sprint/cycle data |\n| `include.backlog` | `true` | Available backlog items |\n| `include.habits` | `true` | Habit tracking |\n| `include.dailyFields` | `true` | Daily field configurations |\n| `include.calendar` | `true` | Calendar events |\n| `include.voiceMemos` | `true` | Recent voice memos |\n\n### Available Mutations\n\n| Operation | Use Case |\n|-----------|----------|\n| `create_issue` | New tasks discovered during planning |\n| `schedule_issue` | Set due dates for scheduled work |\n| `update_issue` | Modify status, priority, estimate, title |\n| `assign_issue_to_current_cycle` | Pull backlog into active cycle |\n| `set_top_priority` | Designate today's top 3 |\n| `update_cycle_goals` | Adjust cycle focus when needed |\n| `save_daily_note` | Write readable plan to Agenda Daily Note |\n| `add_issue_comment` | Document planning rationale on tasks |\n\n### Post-Execution Report\n\nAfter applying changes, the workflow reports:\n- Today's top 3 priorities\n- Tasks created, scheduled, or reassigned\n- Current cycle modifications\n- Daily Note content saved\n\n## End of Day\n\n**Skill File:** `skills/end-of-day/SKILL.md`\n\n### Purpose\n\nThe `end-of-day` workflow provides EOD wrap-up with completion summary and tomorrow planning. This completes the daily productivity loop by reviewing accomplishments and preparing for the next day.\n\n### Core Functions\n\n1. **Completion Review**: Summarize what was accomplished today\n2. **Tomorrow Planning**: Schedule and prioritize work for the next day\n3. **Daily Note Updates**: Save EOD reflections and plans\n4. **Cycle Sync**: Ensure cycle progress is accurately tracked\n\n资料来源：[skills/end-of-day/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/end-of-day/SKILL.md)\n\n## Capture\n\n**Skill File:** `skills/capture/SKILL.md`\n\n### Purpose\n\nThe `capture` workflow enables quick capture of thoughts, tasks, or notes with automatic routing. It is designed for rapid input during the day when users encounter items that need to be tracked.\n\n### Auto-Routing Logic\n\nThe capture workflow uses AI to determine:\n- Whether the capture is a task, note, or reference\n- Appropriate project/cycle assignment\n- Priority level based on content\n- Whether it belongs in the current cycle or backlog\n\n### Available Operations\n\n| Operation | Purpose |\n|-----------|---------|\n| `create_issue` | Convert capture to tracked task |\n| `assign_issue_to_current_cycle` | Route to active sprint |\n| `create_note` | Save as reference note |\n| `add_issue_comment` | Attach to existing task |\n\n资料来源：[skills/capture/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/capture/SKILL.md)\n\n## MCP Tools Reference\n\nAll Daily Workflows depend on these core MCP tools from the 126 available:\n\n### Planning Context\n\n| Tool | Returns |\n|------|---------|\n| `get_planning_context` | Unified context for day/week/cycle planning |\n| `get_daily_agenda` | Today's complete agenda |\n| `get_todays_tasks` | Task list filtered for today |\n| `get_current_cycle` | Active sprint/cycle details |\n\n### Mutations\n\n| Tool | Parameters |\n|------|------------|\n| `apply_planning_patch` | `mode`: \"day\" \\| \"week\" \\| \"cycle\", `dryRun`: boolean |\n| `create_issue` | `title`, `projectId`, `priority`, `dueDate`, `estimate` |\n| `schedule_issue` | `issueId`, `dueDate` |\n| `update_issue` | `issueId`, fields to update |\n| `assign_issue_to_current_cycle` | `issueId` |\n| `set_top_priority` | Array of issue IDs |\n| `save_daily_note` | `date`, `content` |\n\n资料来源：[AGENTS.md](https://github.com/starascendin/lifeos-plugin/blob/main/AGENTS.md)\n\n## Configuration\n\n### Environment Variables\n\n```bash\nexport LIFEOS_CONVEX_URL=https://your-app.convex.site\nexport LIFEOS_USER_ID=your-user-id\nexport LIFEOS_API_KEY=your-api-key\n```\n\n### MCP Server Configuration\n\n```json\n{\n \"mcpServers\": {\n \"lifeos\": {\n \"command\": \"npx\",\n \"args\": [\n \"@starascendin/lifeos-mcp@latest\",\n \"--url\", \"YOUR_CONVEX_URL\",\n \"--user-id\", \"YOUR_USER_ID\",\n \"--api-key\", \"YOUR_API_KEY\"\n ]\n }\n }\n}\n```\n\n资料来源：[README.md](https://github.com/starascendin/lifeos-plugin/blob/main/README.md)\n\n## Daily Rhythm Summary\n\n```mermaid\ngraph LR\n subgraph Morning\n A[daily-standup] --> B[daily-plan]\n end\n \n subgraph Day\n C[Execute Tasks]\n D[capture] -->|Ad-hoc| C\n end\n \n subgraph Evening\n E[end-of-day]\n end\n \n B --> C\n C --> E\n E -->|Tomorrow| B\n```\n\n| Phase | Workflow | Action |\n|-------|----------|--------|\n| Morning (start) | `daily-standup` | Read context, understand the day |\n| Morning (plan) | `daily-plan` | Mutate tasks, set priorities |\n| Throughout day | `capture` | Quick input, auto-routing |\n| End of day | `end-of-day` | Review, plan tomorrow |\n\n## Skill Invocation\n\n### Claude Code\n\n```bash\nclaude plugin add github:starascendin/lifeos-plugin\n\n# Then invoke:\n/daily-standup\n/daily-plan\n/end-of-day\n/capture\n```\n\n### OpenCode\n\nSkills are read from `.claude/skills/` directory. Symlink or copy:\n\n```bash\nln -s /path/to/lifeos-plugin/skills .claude/skills/lifeos\n\n---\n\n\n\n## Habits & Accountability\n\n### 相关页面\n\n相关主题：[Daily Workflows](#daily-workflows), [Health Integration (Oura Ring)](#health-integration), [Coaching System](#coaching-system)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [skills/habit-check/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/habit-check/SKILL.md)\n- [skills/daily-training-report/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/daily-training-report/SKILL.md)\n \n\n# Habits & Accountability\n\n## Overview\n\nThe **Habits & Accountability** system in LifeOS is a core productivity feature that enables users to track daily habits, maintain streaks, and stay accountable to their personal commitments. This system integrates with the broader LifeOS ecosystem, connecting habit data to health metrics, coaching insights, and daily planning workflows.\n\nThe habit system serves three primary purposes:\n\n1. **Tracking** — Recording habit completions on a daily basis\n2. **Streaks** — Motivating consistent behavior through streak counters\n3. **Accountability** — Providing direct, actionable feedback when habits are missed or at risk\n\n资料来源：[skills/habit-check/SKILL.md:1-3]()\n\n## Architecture\n\nThe Habits & Accountability system consists of three interconnected layers:\n\n```mermaid\ngraph TD\n A[User Actions] --> B[Habit Check-in]\n B --> C[Streak Calculator]\n C --> D{Streak Status}\n D -->|3+ days| E[Streak Alert]\n D -->|Broken| F[Streak Broken Alert]\n D -->|Safe| G[Normal Tracking]\n \n H[get_habits] --> I[Habit Dashboard]\n J[get_habits_for_date] --> I\n K[check_in_habit] --> B\n \n I --> L[Daily Training Report]\n I --> M[Weekly Planning]\n I --> N[Blind Spot Finder]\n \n style E fill:#ff6b6b\n style F fill:#ee5a24\n```\n\n### Core Components\n\n| Component | Purpose | Source File |\n|-----------|---------|-------------|\n| Habit Check-in | Mark habits as completed for a specific date | `habit-check/SKILL.md` |\n| Habit Dashboard | Display all habits, statuses, and streaks | `habit-check/SKILL.md` |\n| Daily Training Report | Aggregate habit data with health metrics | `daily-training-report/SKILL.md` |\n| Streak Alerts | Warn users when streaks are at risk | `habit-check/SKILL.md` |\n\n资料来源：[skills/habit-check/SKILL.md:1-40]()\n\n## Habit Check Skill\n\nThe `habit-check` skill is the primary interface for daily habit management. It provides an interactive daily check-in experience with direct accountability messaging.\n\n### Workflow\n\n```mermaid\ngraph LR\n A[Call get_habits_for_date] --> B[Call get_habits]\n B --> C[Build Dashboard]\n C --> D{Habits Complete?}\n D -->|Yes| E[Celebrate]\n D -->|No| F[Flag Pending]\n F --> G{Streak >= 3?}\n G -->|Yes| H[Streak At Risk Alert]\n G -->|No| I[Normal Reminder]\n```\n\n### Data Fetching\n\nThe skill retrieves habit data through two parallel calls:\n\n| API Call | Parameters | Purpose |\n|----------|------------|---------|\n| `get_habits_for_date` | `date` (today or `$ARGUMENTS`) | Scheduled habits and their completion status |\n| `get_habits` | none | Full habit list with streak data |\n\n资料来源：[skills/habit-check/SKILL.md:14-20]()\n\n### Dashboard Output\n\nThe habit dashboard presents information in four sections:\n\n**1. Today's Habits**\n\nEach habit displays:\n- Icon + Name\n- Status: `completed` / `pending` / `skipped` / `incomplete`\n- Current streak (e.g., \"🔥 12 days\")\n\n**2. Completion Rate**\n\nFormat: `X/Y habits completed today (percentage)`\n\n**3. Streak Alerts**\n\n| Condition | Action |\n|-----------|--------|\n| Active streak (3+ days) + pending | Flag as \"streak at risk\" |\n| Streak broken yesterday | Call out explicitly |\n\n**4. Never Skip a Rep**\n\nWhen habits are pending:\n- Direct accountability message: \"You haven't done X yet today. Your streak is at Y days. Don't break it.\"\n\nWhen all habits are done:\n- Celebration message: \"All habits completed. No reps skipped.\"\n\n资料来源：[skills/habit-check/SKILL.md:22-38]()\n\n### Interactive Features\n\nUsers can mark habits completed during the check-in by specifying habit names in `$ARGUMENTS`:\n\n```\nInput: \"mark meditation done\"\nAction: Calls check_in_habit for today's date\n```\n\n## Daily Training Report Integration\n\nThe `daily-training-report` skill aggregates habit data as part of a comprehensive personal performance overview. This demonstrates how habit tracking connects to the broader productivity system.\n\n### Habit Data Sources\n\nThe daily training report pulls habit data from three endpoints:\n\n| API Call | Date Parameter | Data Retrieved |\n|----------|----------------|----------------|\n| `get_habits_for_date` | yesterday's date | Yesterday's completion status |\n| `get_habits_for_date` | today's date | Today's scheduled habits |\n| `get_habits` | none | Streak overview for all habits |\n\n资料来源：[skills/daily-training-report/SKILL.md:8-11]()\n\n### Report Structure\n\nThe habit component of the daily training report follows this structure:\n\n```mermaid\ngraph TD\n A[Daily Training Report] --> B[YESTERDAY'S RESULTS]\n A --> C[TODAY'S GAME PLAN]\n \n B --> B1[Habit Scorecard: X/Y]\n B --> B2[Streaks Maintained]\n B --> B3[Streaks Broken]\n B --> B4[Health Scores]\n B --> B5[Day Rating]\n \n C --> C1[Top 3 Priorities]\n C --> C2[Today's Scheduled Habits]\n C --> C3[Streak Counts]\n```\n\n**Yesterday's Results Section:**\n- Habit scorecard: `X/Y completed` with list of each habit and status\n- Streaks maintained or broken (broken streaks called out explicitly)\n- Health scores from Oura integration\n- Day rating based on habit completion + health scores\n\n**Today's Game Plan Section:**\n- Top 3 priorities from agenda + top priority tasks\n- Habits scheduled for today with streak counts\n\n资料来源：[skills/daily-training-report/SKILL.md:13-24]()\n\n## MCP Tools Reference\n\nThe following MCP tools are used for habit management:\n\n| Tool | Purpose | Used In |\n|------|---------|---------|\n| `get_habits` | Retrieve all habits with streak data | habit-check, daily-training-report |\n| `get_habits_for_date` | Get habits scheduled for a specific date | habit-check, daily-training-report |\n| `check_in_habit` | Mark a habit as completed | habit-check |\n\n### get_habits_for_date Parameters\n\n| Parameter | Type | Required | Description |\n|-----------|------|----------|-------------|\n| `date` | string | Yes | The date to check habits for (ISO format or \"today\"/\"yesterday\") |\n\n### get_habits Response\n\nThe `get_habits` call returns:\n- All defined habits\n- Completion status for the queried date\n- Streak counters for each habit\n- Scheduled frequency (daily, specific days, etc.)\n\n## Accountability Philosophy\n\nThe Habits & Accountability system follows a \"personal trainer\" philosophy:\n\n| Principle | Implementation |\n|-----------|----------------|\n| Direct messaging | No fluff or excessive encouragement |\n| Streak protection | Explicit alerts when streaks are at risk |\n| Immediate feedback | Real-time status updates during check-in |\n| Celebration | Acknowledgment when all habits are completed |\n| Accountability | Call out missed reps directly |\n\nThe tone is described as: \"Direct, like a personal trainer. No fluff. Celebrate wins, call out misses.\"\n\n资料来源：[skills/habit-check/SKILL.md:38-40]()\n\n## Related Skills\n\nThe habit system integrates with several other LifeOS skills:\n\n| Skill | Integration Point |\n|-------|-------------------|\n| `daily-plan` | Habits included in planning context via `include.habits=true` |\n| `weekly-plan` | Habits included in weekly planning context |\n| `sprint-plan` | Habit compliance affects energy/focus capacity |\n| `blind-spot-finder` | Uses habit completion rates to identify patterns |\n| `health-weekly` | Habit data complements health metrics |\n\n资料来源：[skills/daily-plan/SKILL.md:9](), [skills/weekly-plan/SKILL.md:9](), [skills/blind-spot-finder/SKILL.md:10]()\n\n## Data Flow\n\n```mermaid\nsequenceDiagram\n participant User\n participant habit-check\n participant MCP Tools\n participant LifeOS\n \n User->>habit-check: Invoke skill\n habit-check->>MCP Tools: get_habits_for_date(today)\n MCP Tools->>LifeOS: Query habit table\n LifeOS->>MCP Tools: Habit status array\n MCP Tools->>habit-check: Response\n habit-check->>MCP Tools: get_habits\n MCP Tools->>LifeOS: Query all habits with streaks\n LifeOS->>MCP Tools: Full habit list\n MCP Tools->>habit-check: Response\n habit-check->>habit-check: Build dashboard\n habit-check->>User: Display results\n \n alt User marks complete\n User->>habit-check: \"mark X done\"\n habit-check->>MCP Tools: check_in_habit(habitId, today)\n MCP Tools->>LifeOS: Update completion record\n LifeOS->>MCP Tools: Success\n MCP Tools->>habit-check: Confirmation\n habit-check->>User: Updated dashboard\n end\n```\n\n## Best Practices\n\n1. **Daily Check-in** — Run `habit-check` each morning to review and update habit status\n2. **Streak Awareness** — Pay attention to \"streak at risk\" alerts to maintain momentum\n3. **Comprehensive View** — Use `daily-training-report` weekly to see habit patterns in context\n4. **Integration** — Reference habit data in planning sessions for realistic scheduling\n\n---\n\n\n\n## Health Integration (Oura Ring)\n\n### 相关页面\n\n相关主题：[Habits & Accountability](#habits-accountability), [Daily Workflows](#daily-workflows), [Review Workflows](#review-workflows)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [skills/health-check/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/health-check/SKILL.md)\n- [skills/health-weekly/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/health-weekly/SKILL.md)\n- [skills/daily-training-report/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/daily-training-report/SKILL.md)\n- [README.md](https://github.com/starascendin/lifeos-plugin/blob/main/README.md)\n- [AGENTS.md](https://github.com/starascendin/lifeos-plugin/blob/main/AGENTS.md)\n \n\n# Health Integration (Oura Ring)\n\n## Overview\n\nThe Health Integration system in LifeOS plugin provides comprehensive biometric data synchronization with Oura Ring devices. This integration aggregates sleep analysis, activity tracking, readiness scoring, stress measurement, and cardiovascular health metrics into a unified health dashboard accessible through MCP (Model Context Protocol) tools.\n\nThe system serves as the health data layer for 37 workflow skills, enabling AI agents to make informed recommendations based on real-time biometric data. It transforms raw Oura Ring measurements into actionable health insights for daily planning, coaching, and personal optimization workflows.\n\n## Architecture\n\n```mermaid\ngraph TD\n subgraph \"Data Sources\"\n OR[Oura Ring Device]\n end\n \n subgraph \"LifeOS MCP Server\"\n HMC[Health MCP Tools]\n SK[Skills Layer]\n end\n \n subgraph \"Health Data Categories\"\n SL[Sleep]\n AC[Activity]\n RD[Readiness]\n ST[Stress]\n HR[Heart Rate]\n RS[Resilience]\n FT[Fitness]\n OX[Oxygen]\n end\n \n subgraph \"Consuming Skills\"\n HC[health-check]\n HW[health-weekly]\n DT[daily-training-report]\n end\n \n OR --> HMC\n HMC --> SK\n SK --> HC\n SK --> HW\n SK --> DT\n \n HMC --> SL\n HMC --> AC\n HMC --> RD\n HMC --> ST\n HMC --> HR\n HMC --> RS\n HMC --> FT\n HMC --> OX\n```\n\n资料来源：[README.md:1-40]()\n\n## Available Health MCP Tools\n\nThe plugin exposes 10 dedicated health MCP tools that retrieve Oura Ring data. All tools accept a `days` parameter to specify the lookback window.\n\n### Health Data Retrieval Tools\n\n| Tool Name | Purpose | Key Metrics |\n|-----------|---------|-------------|\n| `get_health_sleep` | Sleep quality analysis | Scores, durations, bedtime, breath rate, restless periods |\n| `get_health_activity` | Physical activity tracking | Activity scores, steps, active calories |\n| `get_health_readiness` | Daily readiness assessment | Readiness scores, trends |\n| `get_health_stress` | Stress and recovery balance | Stress levels, recovery data |\n| `get_health_workouts` | Exercise history | Workout type, duration, intensity |\n| `get_health_heart_rate` | Cardiovascular metrics | Resting HR, HRV trends |\n| `get_health_resilience` | Resilience levels | Daily resilience, contributors |\n| `get_health_vo2_max` | Aerobic capacity | VO2 max estimates |\n| `get_health_cardio_age` | Cardiovascular age | Cardiovascular age vs actual |\n| `get_health_spo2` | Blood oxygen | SpO2 levels, breathing disturbance index |\n\n资料来源：[skills/health-check/SKILL.md:1-30]()\n\n## Available Health Skills\n\n### Health Check\n\nA quick daily health overview that pulls 7 days of biometric data.\n\n**Invocation:** `health-check [days]`\n\n**Data Sources Called:**\n1. `get_health_sleep` — 7 days\n2. `get_health_activity` — 7 days\n3. `get_health_readiness` — 7 days\n4. `get_health_heart_rate` — 7 days\n5. `get_health_resilience` — 7 days\n6. `get_health_vo2_max` — 7 days\n7. `get_health_cardio_age` — 7 days\n\n资料来源：[skills/health-check/SKILL.md:1-35]()\n\n**Output Structure:**\n\n| Section | Content |\n|---------|---------|\n| Overall Status | Quick assessment (great / good / needs attention) |\n| Sleep | Average score, duration trend, bedtime consistency, breath rate |\n| Activity | Average score, daily steps, active calories |\n| Readiness | Average score, trend direction |\n| Heart Rate | Resting HR trend, HRV |\n| Resilience | Current level and trend |\n| Fitness | VO2 max trend, cardiovascular age comparison |\n| Insights | 2-3 actionable observations |\n\n```mermaid\ngraph LR\n A[health-check] --> B[7-Day Window]\n B --> C[Aggregate Data]\n C --> D[Trend Analysis]\n D --> E[Concise Dashboard]\n E --> F[Actionable Insights]\n```\n\n### Health Weekly\n\nA comprehensive 7-day rolling health review that analyzes 14 days of data for deeper trend analysis.\n\n**Invocation:** `health-weekly`\n\n**Data Sources Called:**\n1. `get_health_sleep` — 14 days\n2. `get_health_activity` — 14 days\n3. `get_health_readiness` — 14 days\n4. `get_health_stress` — 14 days\n5. `get_health_workouts` — 14 days\n6. `get_health_heart_rate` — 14 days\n7. `get_health_resilience` — 14 days\n8. `get_health_vo2_max` — 14 days\n9. `get_health_cardio_age` — 14 days\n10. `get_health_spo2` — 14 days\n\n资料来源：[skills/health-weekly/SKILL.md:1-45]()\n\n**Output Structure:**\n\n| Section | Metrics |\n|---------|--------|\n| Sleep Quality | Weekly averages, best/worst nights, deep/REM balance, bedtime consistency, breath rate |\n| Activity Patterns | Step averages, active vs rest days, calorie burn |\n| Readiness & Recovery | Score trends, stress vs recovery balance |\n| Resilience | Daily levels trend, contributor breakdown (sleep recovery, daytime recovery, stress) |\n| Fitness | VO2 max trend, cardiovascular age, week-over-week changes |\n| Workouts | Workout history with display names |\n\n```mermaid\ngraph TD\n A[health-weekly] --> B[14-Day Window]\n B --> C[Multi-Source Aggregation]\n C --> D[Category Analysis]\n D --> E[Trend Detection]\n E --> F[Weekly Report]\n F --> G[Recovery Insights]\n F --> H[Fitness Assessment]\n```\n\n### Daily Training Report\n\nA comprehensive daily briefing that combines health data with habit tracking and task management.\n\n**Invocation:** `daily-training-report`\n\n**Workflow:**\n\n```mermaid\ngraph TD\n subgraph \"Data Collection\"\n A1[Yesterday's Habits] --> D[Synthesize Report]\n A2[Today's Habits] --> D\n A3[All Habits] --> D\n A4[Sleep 1 day] --> D\n A5[Readiness 1 day] --> D\n A6[Activity 1 day] --> D\n A7[Today's Agenda] --> D\n A8[Today's Tasks] --> D\n A9[Initiatives] --> D\n A10[Coaching Items] --> D\n end\n \n subgraph \"Synthesis\"\n D --> E[YESTERDAY'S RESULTS]\n D --> F[TODAY'S GAME PLAN]\n D --> G[HABIT SCORECARD]\n D --> H[STREAK STATUS]\n end\n```\n\n**Report Sections:**\n\n| Section | Content |\n|---------|---------|\n| Yesterday's Results | Habit scorecard, streaks, health scores, day rating |\n| Today's Game Plan | Top 3 priorities, scheduled habits with streak counts |\n| Health Integration | Sleep/Readiness/Activity scores from Oura Ring |\n\n资料来源：[skills/daily-training-report/SKILL.md:1-50]()\n\n## Data Flow\n\n```mermaid\nsequenceDiagram\n participant User\n participant Skill\n participant MCP_Tools\n participant Convex\n participant Oura\n\n User->>Skill: Invoke health skill\n Skill->>MCP_Tools: Call get_health_*\n MCP_Tools->>Convex: Fetch data\n Convex->>Oura: Request sync\n Oura-->>Convex: Biometric data\n Convex-->>MCP_Tools: Processed metrics\n MCP_Tools-->>Skill: Health data array\n Skill->>Skill: Aggregate & analyze\n Skill-->>User: Formatted report\n```\n\n## Health Metrics Reference\n\n### Sleep Metrics\n\n| Metric | Description | Used By |\n|--------|-------------|---------|\n| Sleep score | Overall 0-100 quality score | health-check, health-weekly |\n| Duration | Total sleep time in hours | health-check, health-weekly |\n| Bedtime | Sleep onset time | health-weekly |\n| Breath rate | Average breathing during sleep | health-check, health-weekly |\n| Deep sleep | Deep sleep duration | health-weekly |\n| REM sleep | REM duration | health-weekly |\n| Restless periods | Wake episodes during sleep | health-weekly |\n\n### Activity Metrics\n\n| Metric | Description | Used By |\n|--------|-------------|---------|\n| Activity score | Daily activity rating | health-check, health-weekly |\n| Steps | Daily step count | health-check, health-weekly |\n| Active calories | Calories burned through activity | health-check, health-weekly |\n| Active vs rest days | Day type classification | health-weekly |\n\n### Readiness Metrics\n\n| Metric | Description | Used By |\n|--------|-------------|---------|\n| Readiness score | Overall readiness 0-100 | health-check, health-weekly, daily-training-report |\n| Trend direction | Improving/declining/stable | health-check |\n| Temperature trend | Body temperature patterns | health-weekly |\n\n### Cardiovascular Metrics\n\n| Metric | Description | Used By |\n|--------|-------------|---------|\n| Resting heart rate | Minimum HR during rest | health-check, health-weekly |\n| HRV | Heart rate variability | health-check |\n| VO2 max | Maximum oxygen uptake | health-check, health-weekly |\n| Cardiovascular age | Estimated cardiovascular age | health-check, health-weekly |\n| SpO2 | Blood oxygen saturation | health-weekly |\n\n### Resilience Metrics\n\n| Metric | Description | Used By |\n|--------|-------------|---------|\n| Resilience level | Daily resilience score | health-check, health-weekly |\n| Sleep recovery contribution | Sleep's role in resilience | health-weekly |\n| Daytime recovery contribution | Activity's role in resilience | health-weekly |\n| Stress contribution | Stress's impact on resilience | health-weekly |\n\n资料来源：[skills/health-check/SKILL.md:15-30]()\n\n## Configuration\n\nHealth data requires the standard LifeOS MCP server connection configured with:\n\n```json\n{\n \"mcpServers\": {\n \"lifeos\": {\n \"command\": \"npx\",\n \"args\": [\n \"@starascendin/lifeos-mcp@latest\",\n \"--url\", \"YOUR_CONVEX_URL\",\n \"--user-id\", \"YOUR_USER_ID\",\n \"--api-key\", \"YOUR_API_KEY\"\n ]\n }\n }\n}\n```\n\nOr environment variables:\n\n```bash\nexport LIFEOS_CONVEX_URL=https://your-app.convex.site\nexport LIFEOS_USER_ID=your-user-id\nexport LIFEOS_API_KEY=your-api-key\n```\n\n资料来源：[README.md:45-60]()\n\n## Usage Patterns\n\n### Quick Health Check\n\n```\nUser: health-check\n→ Returns 7-day health dashboard with scores, trends, and 2-3 insights\n```\n\n### Extended Health Review\n\n```\nUser: health-check 14\n→ Returns 14-day health overview instead of default 7 days\n```\n\n### Weekly Deep Dive\n\n```\nUser: health-weekly\n→ Returns comprehensive 14-day analysis with recovery insights and fitness trends\n```\n\n### Training Integration\n\n```\nUser: daily-training-report\n→ Combines health data with habits, tasks, and coaching items for complete daily briefing\n```\n\n## Skill Comparison\n\n| Feature | health-check | health-weekly | daily-training-report |\n|---------|--------------|---------------|----------------------|\n| Data window | 7 days (default) | 14 days | 1 day |\n| Sleep analysis | ✓ | ✓✓ | ✓ |\n| Activity analysis | ✓ | ✓✓ | ✓ |\n| Readiness tracking | ✓ | ✓✓ | ✓ |\n| Stress metrics | - | ✓ | - |\n| Heart rate | ✓ | ✓ | - |\n| Resilience | ✓ | ✓✓ | - |\n| VO2 max | ✓ | ✓ | - |\n| Cardio age | ✓ | ✓ | - |\n| SpO2 | - | ✓ | - |\n| Workouts | - | ✓ | - |\n| Habit integration | - | - | ✓✓ |\n| Task integration | - | - | ✓ |\n| Initiative tracking | - | - | ✓ |\n\n## Integration with Other Systems\n\nHealth data flows into multiple LifeOS subsystems:\n\n```mermaid\ngraph LR\n subgraph \"Health Data\"\n H[Oura Ring]\n end\n \n subgraph \"Integrated Systems\"\n D[Daily Planning]\n C[Coaching]\n PP[PPV Life Design]\n T[Task Management]\n end\n \n H --> D\n H --> C\n H --> PP\n H --> T\n \n D -->|Affects| D1[Priority Setting]\n D -->|Affects| D2[Due Dates]\n C -->|Drives| C1[Action Items]\n PP -->|Influences| PP1[Energy Levels]\n T -->|Adjusts| T1[Capacity Planning]\n```\n\n### Daily Training Report Integration\n\nThe `daily-training-report` skill demonstrates deep integration, combining:\n\n- **Habit compliance** data with health scores\n- **Streak tracking** synchronized with biometric trends\n- **Initiative progress** aligned with energy levels\n- **Coaching action items** based on health patterns\n\n资料来源：[skills/daily-training-report/SKILL.md:1-50]()\n\n## Best Practices\n\n1. **Use health-check for daily standups** — Quick 7-day snapshot provides context without overwhelming detail\n\n2. **Reserve health-weekly for planning sessions** — The 14-day window reveals trends better suited for strategic decisions\n\n3. **Incorporate health data into daily-training-report** — Biometric context enhances habit coaching effectiveness\n\n4. **Review resilience metrics weekly** — Sleep recovery, daytime recovery, and stress contributions reveal optimization opportunities\n\n5. **Monitor VO2 max trends monthly** — Cardiovascular fitness changes slowly but meaningfully over 4-week periods\n\n---\n\n\n\n## Project Management\n\n### 相关页面\n\n相关主题：[Client Management](#client-management), [Review Workflows](#review-workflows), [Daily Workflows](#daily-workflows)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [skills/sprint-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/sprint-plan/SKILL.md)\n- [skills/weekly-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/weekly-plan/SKILL.md)\n- [skills/daily-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/daily-plan/SKILL.md)\n- [skills/daily-standup/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/daily-standup/SKILL.md)\n- [AGENTS.md](https://github.com/starascendin/lifeos-plugin/blob/main/AGENTS.md)\n- [README.md](https://github.com/starascendin/lifeos-plugin/blob/main/README.md)\n \n\n# Project Management\n\nProject Management in LifeOS is a comprehensive framework for managing work across projects, sprints (cycles), initiatives, and clients. It integrates with the Convex-powered personal productivity OS to provide full CRUD operations for projects, tasks/issues, cycles, phases, clients, and people/contacts through 126 MCP tools.\n\n## Overview\n\nThe Project Management system operates on multiple levels:\n\n| Level | Scope | Tools Available |\n|-------|-------|-----------------|\n| **Initiative** | Yearly goals by category | Progress tracking, initiative review |\n| **Cycle/Sprint** | Current sprint planning and execution | Cycle goals, backlog pull, due dates, priorities |\n| **Weekly** | Week planning across projects | Task scheduling, cycle assignments, note updates |\n| **Daily** | Day-to-day execution | Top priorities, due dates, daily notes |\n| **Project** | Phase breakdown, task stats, blockers | Status reporting, project metrics |\n| **Client** | Client projects, communications, health | Briefs, health dashboards, triage |\n\n## Core Architecture\n\n```mermaid\ngraph TD\n A[LifeOS Plugin] --> B[Planning Context API]\n A --> C[Planning Patch API]\n B --> D[Convex Backend]\n C --> D\n \n E[get_planning_context] --> F[daily
weekly
currentCycle
backlog
habits
calendar
voiceMemos]\n G[apply_planning_patch] --> H[mode: day|week|cycle]\n H --> I[Mutations]\n I --> J[create_issue
schedule_issue
update_issue
assign_to_cycle
set_top_priority
update_cycle_goals
save_daily_note
save_weekly_note]\n```\n\n## Planning Workflow\n\n### Step 1: Gather Planning Context\n\nThe foundation of all project management operations is `get_planning_context`. This single API call aggregates data across multiple dimensions:\n\n| Parameter | Values | Description |\n|-----------|--------|-------------|\n| `date` | ISO date string | Target date for daily planning |\n| `weekStartDate` | ISO date string | Week start for weekly planning |\n| `include.daily` | `true` | Include daily agenda and tasks |\n| `include.weekly` | `true` | Include weekly view |\n| `include.currentCycle` | `true` | Include active sprint/cycle data |\n| `include.backlog` | `true` | Include backlog items |\n| `include.habits` | `true` | Include habit data |\n| `include.dailyFields` | `true` | Include daily custom fields |\n| `include.calendar` | `true` | Include calendar events |\n| `include.voiceMemos` | `true` | Include voice memos |\n\n资料来源：[skills/daily-plan/SKILL.md:8-18]()\n\n### Step 2: Apply Planning Mutations\n\nAfter analyzing the context, mutations are applied via `apply_planning_patch` with three modes:\n\n| Mode | Use Case | Scope |\n|------|----------|-------|\n| `day` | Daily execution planning | Today's top 3, due dates, daily note |\n| `week` | Week planning | Schedule across week, cycle assignments |\n| `cycle` | Sprint planning | Cycle goals, backlog pull, capacity |\n\n## Project Management Skills\n\n### Sprint Planning (`/sprint-plan`)\n\nThe sprint-plan skill manages the current cycle with mutating operations:\n\n1. Fetch planning context with current cycle and backlog\n2. Build cycle plan with goal updates and backlog prioritization\n3. Apply mutations with `mode=\"cycle\"`\n\n**Key Mutations:**\n\n```javascript\n// Assign work to current cycle\nassign_issue_to_current_cycle(issueId, cycleId)\n\n// Update cycle goals\nupdate_cycle_goals(cycleId, goals)\n\n// Schedule work with due dates\nschedule_issue(issueId, dueDate)\n\n// Set immediate priorities\nset_top_priority([issueId1, issueId2, issueId3])\n```\n\n资料来源：[skills/sprint-plan/SKILL.md:1-45]()\n\n### Weekly Planning (`/weekly-plan`)\n\nWeekly planning operates at a broader scope, scheduling work across multiple days:\n\n```mermaid\ngraph LR\n A[Week Start] --> B[Update Cycle Goals]\n B --> C[Pull Backlog Items]\n C --> D[Schedule Due Dates]\n D --> E[Set Top Priorities]\n E --> F[Save Weekly Note]\n```\n\n**Workflow:**\n1. Call `get_planning_context` with `weekStartDate`\n2. Update active cycle goals when needed\n3. Assign backlog tasks to current cycle\n4. Schedule work across the week using `dueDate`\n5. Set near-term top priorities\n6. Call `apply_planning_patch` with `mode=\"week\"` and `dryRun=false`\n\n资料来源：[skills/weekly-plan/SKILL.md:1-40]()\n\n### Daily Planning (`/daily-plan`)\n\nDaily planning focuses on immediate execution:\n\n| Priority Level | Description |\n|----------------|-------------|\n| Top 3 | Must-complete items for today |\n| Due Today | Tasks with today's due date |\n| Overdue | Late tasks requiring triage |\n| Scheduled | Pre-scheduled calendar work |\n\n**Mutations Available:**\n\n- `create_issue` - New tasks\n- `schedule_issue` - Due date changes\n- `update_issue` - Status, priority, estimate, title\n- `assign_issue_to_current_cycle` - Cycle reassignment\n- `set_top_priority` - Today's focus\n- `update_cycle_goals` - Active cycle changes\n- `save_daily_note` - Write to Agenda Daily Note\n- `add_issue_comment` - Planning rationale\n\n资料来源：[skills/daily-plan/SKILL.md:1-45]()\n\n### Daily Standup (`/daily-standup`)\n\nQuick briefing for daily synchronization:\n\n```mermaid\ngraph TD\n A[Daily Standup] --> B[get_daily_agenda]\n A --> C[get_todays_tasks]\n A --> D[get_overdue_tasks]\n A --> E[get_current_cycle]\n \n B --> F[Today's Focus]\n C --> G[Tasks Due]\n D --> H[Overdue Items]\n E --> I[Sprint Progress]\n```\n\n**Output Sections:**\n- **Today's Focus**: Top 3 priorities\n- **Tasks Due**: Tasks due today with priority\n- **Overdue**: Late tasks needing triage\n- **Sprint Progress**: Cycle completion percentage and stats\n- **Calendar**: Meetings and events\n\n资料来源：[skills/daily-standup/SKILL.md:1-35]()\n\n## Client & Project Reporting\n\n### Project Status (`/project-status`)\n\nProvides phase breakdown, task statistics, and blocker identification:\n\n```mermaid\ngraph TD\n A[Project Status] --> B[Phase Breakdown]\n A --> C[Task Statistics]\n A --> D[Blocker Analysis]\n \n B --> E[Active Phases]\n C --> F[Completion %]\n D --> G[Risk Items]\n```\n\n资料来源：[AGENTS.md:1-30]()\n\n### Client Brief (`/client-brief`)\n\nFull client briefing combining projects and communications:\n\n| Component | Data Source |\n|-----------|-------------|\n| Projects | Active client projects |\n| Communications | Beeper threads, meetings |\n| Open Tasks | Client-related issues |\n| Notes | Recent client notes |\n\n### Client Health (`/client-health`)\n\nDashboard across all clients for relationship health tracking.\n\n### Customer Success Triage (`/customer-success-triage`)\n\nWorkflow for triaging client requests:\n\n1. Call `get_client_success_workspace` with client name\n2. Review workspace output:\n - `recentThreads` - Business chats\n - `recentMeetings` - Fathom and Granola meetings\n - `notes` - Client notes\n - `openTasks` - Active issues\n - `projects` - Client projects\n\n3. Drill down as needed:\n - Chat detail: `get_beeper_thread_messages`\n - Meeting detail: `get_fathom_meeting`, `get_granola_meeting`\n - Transcript: `get_fathom_transcript`, `get_granola_transcript`\n - Note history: `get_client_notes`\n\n4. Classify findings:\n - **New Requirements**: Net-new asks\n - **Follow-Ups**: Items waiting on response\n - **Risks/Blockers**: Scope ambiguity, overdue work, churn risk\n - **Already Tracked**: Existing notes or tasks\n\n资料来源：[skills/customer-success-triage/SKILL.md:1-40]()\n\n## Initiative & Cycle Review\n\n### Initiative Review (`/initiative-review`)\n\nYearly goal progress by category. Tracks progress against annual initiatives with configurable year (e.g., `/initiative-review 2026`).\n\n### Cycle Review (`/sprint-review`)\n\nSprint review with rollover options for managing incomplete work between cycles.\n\n## Data Model Relationships\n\n```mermaid\ngraph TD\n I[Initiative] -->|1:N| C[Cycle]\n I -->|1:N| P[Project]\n \n C -->|1:N| T[Task/Issue]\n P -->|1:N| T\n \n C -->|has| G[Cycle Goals]\n P -->|has| Ph[Phases]\n \n T -->|assigned to| C\n T -->|scheduled on| D[Due Date]\n \n C -->|1:N| C2[Next Cycle]\n \n Cl[Client] -->|1:N| P\n Cl -->|1:N| Co[Contact]\n Cl -->|1:N| N[Notes]\n```\n\n## MCP Tools Summary\n\n| Category | Tools | Operations |\n|----------|-------|------------|\n| Projects | `get_project`, `create_project`, `update_project`, `delete_project` | Full CRUD |\n| Issues/Tasks | `get_issue`, `create_issue`, `update_issue`, `delete_issue`, `schedule_issue` | Full CRUD + scheduling |\n| Cycles | `get_current_cycle`, `get_cycle_goals`, `update_cycle_goals`, `assign_issue_to_current_cycle` | Cycle management |\n| Clients | `get_client_success_workspace`, `create_client_note`, `update_client_note` | Client workspace |\n| Planning | `get_planning_context`, `apply_planning_patch` | Context + mutations |\n\n资料来源：[README.md:1-50]()\n资料来源：[AGENTS.md:1-60]()\n\n## Best Practices\n\n1. **Always fetch context first** - Use `get_planning_context` before any planning mutation to ensure you have the latest data\n2. **Set dryRun=true initially** - Preview changes before applying mutations\n3. **Use appropriate mode** - Match the mutation mode (day/week/cycle) to your planning scope\n4. **Save notes as artifacts** - Use `save_daily_note` and `save_weekly_note` to create readable plan artifacts\n5. **Link existing projects** - When using PPV or other systems, prefer linking to existing projects over creating duplicates\n\n---\n\n\n\n## Client Management\n\n### 相关页面\n\n相关主题：[Project Management](#project-management), [People & Relationships](#people-relationships)\n\n\nRelevant Source Files
\n\n以下源码文件用于生成本页说明：\n\n- [skills/client-brief/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/client-brief/SKILL.md)\n- [skills/client-health/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/client-health/SKILL.md)\n- [skills/customer-success-triage/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md)\n- [skills/inbox-triage/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/inbox-triage/SKILL.md)\n \n\n# Client Management\n\nClient Management in LifeOS provides a comprehensive system for managing client relationships, tracking customer-success work, and maintaining client health across your entire portfolio. It leverages the LifeOS MCP tools to aggregate data from multiple sources including Beeper threads, Fathom/Granola meetings, notes, and open tasks into unified client workspaces.\n\n## Overview\n\nThe Client Management system consists of four primary skills that work together to provide complete client visibility and actionable workflows:\n\n| Skill | Purpose | Invocation |\n|-------|---------|------------|\n| `client-brief` | Full client briefing with projects and communications | `/client-brief \"Acme Corp\"` |\n| `client-health` | Health dashboard across all clients | `/client-health` |\n| `customer-success-triage` | Triage requests using chats, meetings, notes, and open work | `/customer-success-triage \"Acme Corp\"` |\n| `inbox-triage` | Process notes into tasks | `/inbox-triage` |\n\n资料来源：[README.md:28-32](https://github.com/starascendin/lifeos-plugin/blob/main/README.md)\n\n## Architecture\n\n```mermaid\ngraph TD\n A[User Request] --> B{Client Management Skills}\n \n B --> C[client-brief]\n B --> D[client-health]\n B --> E[customer-success-triage]\n B --> F[inbox-triage]\n \n C --> G[get_client_success_workspace]\n D --> H[get_all_clients]\n E --> G\n E --> I[Meeting Tools]\n E --> J[Communication Tools]\n \n G --> K[Projects, Tasks, Notes, Threads]\n I --> L[get_fathom_meeting, get_granola_meeting]\n J --> M[get_beeper_thread_messages]\n \n K --> N[apply_planning_patch]\n L --> N\n M --> N\n \n N --> O[LifeOS Convex Backend]\n```\n\n## Core Skills\n\n### Client Brief\n\nThe `client-brief` skill generates a comprehensive client briefing that includes all projects, communications, and current status information for a specific client. It is invoked with the client name or ID as an argument.\n\n资料来源：[AGENTS.md:24](https://github.com/starascendin/lifeos-plugin/blob/main/AGENTS.md)\n\n**Workflow:**\n1. Call `get_client_success_workspace` with the client identifier\n2. Aggregate all related data: projects, open tasks, notes, recent threads, meetings\n3. Present a structured briefing with actionable insights\n\n### Client Health Dashboard\n\nThe `client-health` skill provides a health dashboard across all clients, allowing you to quickly identify which client relationships need attention and which are performing well.\n\n资料来源：[README.md:29](https://github.com/starascendin/lifeos-plugin/blob/main/README.md)\n\n**Key Metrics Tracked:**\n- Communication frequency\n- Open task counts\n- Blocked or overdue items\n- Recent meeting activity\n- Note activity and recency\n\n### Customer Success Triage\n\nThe `customer-success-triage` skill is designed for reviewing customer asks, checking whether work is already tracked, capturing requirement summaries, and deciding what should become a task.\n\n资料来源：[skills/customer-success-triage/SKILL.md:1-6](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md)\n\n**Input Format:**\n```\n$ARGUMENTS should contain the client name or ID, plus an optional focus area\n```\n\n## Customer Success Triage Workflow\n\n```mermaid\ngraph TD\n A[Start Triage: Client Name/ID] --> B[Call get_client_success_workspace]\n B --> C{Workspace Data}\n \n C --> D[recentThreads]\n C --> E[recentMeetings]\n C --> F[notes]\n C --> G[openTasks]\n C --> H[projects]\n \n D --> I{Drill Down Needed?}\n E --> I\n F --> I\n G --> I\n H --> I\n \n I -->|Threads| J[get_beeper_thread_messages]\n I -->|Fathom| K[get_fathom_meeting
get_fathom_transcript]\n I -->|Granola| L[get_granola_meeting
get_granola_transcript]\n I -->|Notes| M[get_client_notes]\n \n J --> N{Classification}\n K --> N\n L --> N\n M --> N\n \n N --> O[New Requirements]\n N --> P[Follow-Ups]\n N --> Q[Risks / Blockers]\n N --> R[Already Tracked]\n \n O --> S[create_issue
update_issue]\n P --> S\n Q --> S\n R --> S\n \n S --> T[create_client_note
update_client_note]\n T --> U[Present Triage Results]\n```\n\n资料来源：[skills/customer-success-triage/SKILL.md:7-28](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md)\n\n## Classification Framework\n\nWhen triaging customer-success work, findings should be classified into four categories:\n\n| Classification | Description | Action |\n|----------------|-------------|--------|\n| **New Requirements** | Net-new asks or requested changes | Create issues or capture in notes |\n| **Follow-Ups** | Things waiting on you or the team | Track and schedule follow-ups |\n| **Risks / Blockers** | Scope ambiguity, overdue work, delivery risk, churn risk | Prioritize and escalate |\n| **Already Tracked** | Notes or tasks that already cover the request | Link and reference existing work |\n\n资料来源：[skills/customer-success-triage/SKILL.md:17-20](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md)\n\n## MCP Tools Reference\n\n### Client Workspace Tools\n\n| Tool | Purpose | Source |\n|------|---------|--------|\n| `get_client_success_workspace` | Retrieve comprehensive workspace for a client | [customer-success-triage/SKILL.md:8](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md) |\n| `get_client_notes` | Retrieve existing note history for a client | [customer-success-triage/SKILL.md:16](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md) |\n\n### Meeting Integration Tools\n\n| Tool | Purpose | Source |\n|------|---------|--------|\n| `get_fathom_meeting` | Retrieve Fathom meeting details | [customer-success-triage/SKILL.md:14](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md) |\n| `get_fathom_transcript` | Get full Fathom meeting transcript | [customer-success-triage/SKILL.md:14](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md) |\n| `get_granola_meeting` | Retrieve Granola meeting details | [customer-success-triage/SKILL.md:15](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md) |\n| `get_granola_transcript` | Get full Granola meeting transcript | [customer-success-triage/SKILL.md:15](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md) |\n\n### Communication Tools\n\n| Tool | Purpose | Source |\n|------|---------|--------|\n| `get_beeper_thread_messages` | Retrieve Beeper thread communications | [customer-success-triage/SKILL.md:13](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md) |\n\n### Write Operations\n\n| Tool | Purpose | When to Use |\n|------|---------|-------------|\n| `create_client_note` | Save durable account memory | New insights, decisions, context |\n| `update_client_note` | Update existing client notes | Refine or extend existing notes |\n| `create_issue` | Create execution work items | New requirements that need action |\n| `update_issue` | Modify existing issues | Status changes, priority updates |\n\n资料来源：[skills/customer-success-triage/SKILL.md:21-25](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md)\n\n## Inbox Triage Integration\n\nThe `inbox-triage` skill works in conjunction with Client Management to process notes into actionable tasks. When client communications result in notes that need to be converted into work items, this skill provides the bridge between captured information and tracked work.\n\n资料来源：[AGENTS.md:21](https://github.com/starascendin/lifeos-plugin/blob/main/AGENTS.md)\n\n**Typical Flow:**\n1. Customer-success triage identifies new requirements\n2. Client notes are created or updated with requirements\n3. Inbox triage converts notes into issues\n4. Issues are linked to relevant projects and cycles\n\n## Best Practices\n\n### Write Operations\n\nBased on the triage workflow design, follow these guidelines for write operations:\n\n1. **Save durable account memory** with `create_client_note` or `update_client_note` for insights, decisions, and context\n2. **Use `create_issue` or `update_issue`** only for execution work that requires tracking\n3. **Prefer updating existing notes/tasks** over creating duplicates\n4. **Do not delete anything** — maintain complete audit trails of client interactions\n\n资料来源：[skills/customer-success-triage/SKILL.md:22-25](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md)\n\n### Drill-Down Strategy\n\nWhen triaging, follow this prioritized approach:\n\n1. **Review the workspace output first** — examine `recentThreads`, `recentMeetings`, `notes`, `openTasks`, and `projects`\n2. **Drill down only when needed** — not every piece of information requires deep investigation\n3. **Match the drill-down tool to the source** — use the appropriate tool for the data type being investigated\n\n资料来源：[skills/customer-success-triage/SKILL.md:8-16](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md)\n\n## Usage Examples\n\n### Generate a Client Brief\n\n```bash\n/client-brief \"Acme Corp\"\n```\n\n### Check Client Health Across Portfolio\n\n```bash\n/client-health\n```\n\n### Triage Customer Success Work\n\n```bash\n/customer-success-triage \"Acme Corp\"\n```\n\n### Triage with Focus Area\n\n```bash\n/customer-success-triage \"Acme Corp\" --focus \"billing issues\"\n```\n\n## Data Flow Summary\n\n```mermaid\ngraph LR\n A[Beeper Threads] --> D[Client Workspace]\n B[Fathom Meetings] --> D\n C[Granola Meetings] --> D\n E[Open Tasks] --> D\n F[Projects] --> D\n G[Notes] --> D\n \n D --> H{Triage Classification}\n H --> I[New Requirements]\n H --> J[Follow-Ups]\n H --> K[Risks/Blockers]\n H --> L[Already Tracked]\n \n I --> M[Issues + Notes]\n J --> M\n K --> M\n L --> N[Reference Link]\n \n M --> O[LifeOS Backend]\n N --> O\n```\n\n## Related Skills\n\n- **Project Management** — Link client work to specific projects and phases\n- **Sprint Plan** — Assign client work to current cycles\n- **Weekly Review** — Include client health in periodic reviews\n- **Follow-ups** — Track outstanding client communications\n\n---\n\n\n\n## People & Relationships\n\n### 相关页面\n\n相关主题：[Client Management](#client-management)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [skills/contact-lookup/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/contact-lookup/SKILL.md)\n- [skills/relationship-pulse/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/relationship-pulse/SKILL.md)\n- [skills/inbox-triage/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/inbox-triage/SKILL.md)\n- [skills/blind-spot-finder/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/blind-spot-finder/SKILL.md)\n- [AGENTS.md](https://github.com/starascendin/lifeos-plugin/blob/main/AGENTS.md)\n \n\n# People & Relationships\n\nThe People & Relationships module within LifeOS Plugin provides a comprehensive system for managing contacts, tracking interactions, preparing for meetings, and maintaining meaningful professional and personal relationships. This module serves as the social intelligence layer of the productivity OS, connecting human interaction data with actionable workflow skills.\n\n## Overview\n\nThe People & Relationships system integrates with multiple data sources to build complete dossiers on contacts, including Beeper messaging threads, Granola meeting records with AI-generated notes, voice memos, and calendar events. The system enables agents to perform relationship maintenance tasks such as identifying neglected contacts, tracking follow-up obligations, and rapidly switching context between different clients or people.\n\n资料来源：[skills/contact-lookup/SKILL.md:1-5]()\n\nThe core philosophy treats relationships as first-class productivity assets. Rather than siloing contact information in a traditional CRM, LifeOS weaves relationship data into daily workflows, enabling proactive relationship maintenance alongside task and project management.\n\n## Core Skills\n\n### Contact Lookup\n\nThe `contact-lookup` skill provides a complete dossier on any person in the system.\n\n**Entry Point**: `get_contact_dossier` with a name query\n\n**Dossier Components**:\n\n| Component | Data Source | Description |\n|-----------|-------------|-------------|\n| Person Info | LifeOS database | Name, relationship type, contact info, system notes |\n| AI Insights | AI-generated | Communication style, personality indicators, relationship tips |\n| Beeper Threads | Beeper API | Messaging history linked to this contact |\n| Granola Meetings | Granola API | Meeting records with AI notes and calendar events |\n| Voice Memos | Voice memo system | Audio recordings involving or mentioning this person |\n\n资料来源：[skills/contact-lookup/SKILL.md:10-25]()\n\n**Workflow**:\n\n```mermaid\ngraph TD\n A[User Query: Contact Name] --> B[Call get_contact_dossier]\n B --> C{Contact Found?}\n C -->|Yes| D[Extract Data Sources]\n C -->|No| E[Request Valid Name]\n D --> F[Fetch Beeper Threads]\n D --> G[Fetch Granola Meetings]\n D --> H[Fetch Voice Memos]\n F --> I[Aggregate Dossier]\n G --> I\n H --> I\n I --> J[Present Structured Output]\n```\n\n**Output Structure**:\n\n```markdown\n- **Profile**: Name, relationship type, contact info, notes\n- **AI Insights**: Communication style, personality, relationship tips\n- **Recent Interactions**: Last voice memos, meetings, messages sorted by recency\n- **Meeting History**: Granola meetings with key takeaways\n- **Chat Threads**: Beeper conversation threads\n```\n\n资料来源：[skills/contact-lookup/SKILL.md:12-25]()\n\n### Meeting Preparation\n\nThe `meeting-prep` skill aggregates relevant context before scheduled meetings with contacts.\n\n**Data Pulled**:\n\n- Contact dossier from `get_contact_dossier`\n- Recent Beeper threads with the person\n- Granola meeting notes from previous encounters\n- Open tasks or projects related to the person\n- Any pending follow-ups or commitments\n\n**Purpose**: Ensures agents enter meetings with full context, avoiding the need to re-explain background or rediscover relationship history.\n\n### Follow-ups Tracking\n\nThe `follow-ups` skill identifies communication obligations across the network.\n\n**Tracking Criteria**:\n\n| Category | Threshold | Priority |\n|----------|-----------|----------|\n| Active threads | Unreplied messages | High |\n| Scheduled meetings | Confirmed but unheld | Medium |\n| Promised responses | Past commitment date | High |\n| Project updates | Stale status | Medium |\n\n**Output**: Prioritized list of contacts requiring responses, grouped by urgency and relationship type.\n\n资料来源：[AGENTS.md:25-28]()\n\n### Relationship Pulse\n\nThe `relationship-pulse` skill proactively monitors relationship health by analyzing interaction frequency against relationship type expectations.\n\n**Data Sources**:\n\n- `get_people` — All contacts with relationship classifications\n- `get_beeper_threads` — Message activity and recency\n- `get_granola_meetings` — Meeting history\n\n资料来源：[skills/relationship-pulse/SKILL.md:1-10]()\n\n**Neglect Thresholds**:\n\n| Relationship Type | Threshold | Priority Level |\n|-------------------|-----------|----------------|\n| Family / Close friends | 14+ days no contact | Critical |\n| Friends | 30+ days no contact | High |\n| Colleagues / Mentors | 60+ days no contact | Medium |\n| Acquaintances | 90+ days no contact | Low (optional) |\n\n资料来源：[skills/relationship-pulse/SKILL.md:22-28]()\n\n**Output Categories**:\n\n- **Reach out soon**: Prioritized by relationship closeness\n- **Consider reconnecting**: Re-engagement opportunities\n- **Suggested touchpoints**: Quick actions like replying to old threads or scheduling catch-ups\n\n```mermaid\ngraph TD\n A[get_people] --> B[Classify Each Contact]\n A --> C[get_beeper_threads]\n A --> D[get_granola_meetings]\n C --> E[Calculate Last Interaction]\n D --> E\n E --> F{Compare to Thresholds}\n F -->|Exceeded| G[Add to Neglected List]\n F -->|Within bounds| H[Mark as Active]\n G --> I[Prioritize by Relationship]\n I --> J[Generate Action Suggestions]\n```\n\n### Context Switch\n\nThe `context-switch` skill enables rapid context loading for a specific client or person, useful when switching between active workstreams.\n\n**Usage**: When working on multiple clients or projects, agents can invoke context-switch to immediately load relevant data without manual retrieval.\n\n**Loaded Data**:\n\n- Recent client notes\n- Active projects and tasks\n- Meeting history\n- Outstanding communications\n- Project-specific context\n\n资料来源：[AGENTS.md:30-31]()\n\n## Data Models\n\n### Person Entity\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `id` | string | Unique identifier |\n| `name` | string | Full name |\n| `relationshipType` | enum | Family, Friend, Colleague, Mentor, Client, Acquaintance |\n| `contactInfo` | object | Email, phone, social links |\n| `notes` | string | Agent-added notes |\n| `createdAt` | timestamp | Creation date |\n| `updatedAt` | timestamp | Last modification |\n\n### Interaction Record\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `personId` | string | Foreign key to person |\n| `type` | enum | Message, Meeting, VoiceMemo, Note |\n| `timestamp` | timestamp | When interaction occurred |\n| `source` | string | Beeper, Granola, VoiceNotes, etc. |\n| `summary` | string | AI-generated summary |\n| `metadata` | object | Source-specific data |\n\n### Relationship Health Score\n\n| Level | Criteria | Action |\n|-------|----------|--------|\n| Active | Recent interaction within threshold | Maintain |\n| Needs Attention | Approaching threshold | Schedule contact |\n| Neglected | Exceeded threshold | Prioritize outreach |\n| At Risk | Significantly exceeded + commitments pending | Immediate action |\n\n## MCP Tool Integration\n\nThe People & Relationships module leverages the LifeOS MCP server for data operations:\n\n### Read Operations\n\n| Tool | Purpose |\n|------|---------|\n| `get_contact_dossier` | Full person dossier with all data sources |\n| `get_people` | List all contacts |\n| `get_beeper_threads` | Messaging threads, optionally filtered by person |\n| `get_granola_meetings` | Meeting records with AI notes |\n| `get_granola_meeting` | Single meeting details |\n| `get_granola_transcript` | Full meeting transcript |\n| `get_voice_memos_by_labels` | Voice memos filtered by labels |\n| `get_client_notes` | Client-specific notes history |\n\n资料来源：[skills/contact-lookup/SKILL.md:16-22]()\n\n### Write Operations\n\n| Tool | Purpose |\n|------|---------|\n| `create_client_note` | Save durable account memory |\n| `update_client_note` | Update existing note |\n| `link_memo_to_person` | Connect voice memo to contact |\n\n资料来源：[skills/contact-lookup/SKILL.md:25-27]()\n\n## Workflow Integration\n\nThe People & Relationships module connects with other LifeOS workflow skills:\n\n### Integration with Planning\n\nDuring daily and weekly planning, the system can surface:\n\n- Pending follow-ups requiring attention\n- Meeting preparations needed\n- Relationship pulse alerts\n\n```mermaid\ngraph LR\n A[Daily Planning] --> B[get_planning_context]\n B --> C{Include People Data?}\n C -->|Yes| D[Fetch Follow-ups]\n C -->|Yes| E[Fetch Relationship Pulse]\n D --> F[Surface in Day Plan]\n E --> F\n```\n\n### Integration with Reviews\n\nDuring cycle and initiative reviews, contact data informs:\n\n- Client health across projects\n- Communication patterns with stakeholders\n- Meeting frequency analysis\n\n### Integration with Capture\n\nThe `inbox-triage` skill uses person data for:\n\n- Linking captured notes to contacts via `link_memo_to_person`\n- Suggesting contacts when notes mention people\n- Creating tasks tied to relationship obligations\n\n资料来源：[skills/inbox-triage/SKILL.md:10-18]()\n\n## Relationship Intelligence\n\n### AI-Generated Insights\n\nThe system uses AI to generate relationship intelligence:\n\n- **Communication style**: How the person prefers to communicate\n- **Personality indicators**: Extracted from interaction patterns\n- **Relationship tips**: Customized advice for maintaining the relationship\n\nThese insights are generated during `get_contact_dossier` calls and stored as part of the person record.\n\n### Blind Spot Detection\n\nThe `blind-spot-finder` skill incorporates relationship data to identify patterns:\n\n- Screening time analysis vs. relationship investment\n- Say-do gaps in stated priorities vs. actual relationship maintenance\n- Patterns the user cannot see from inside their own behavior\n\n资料来源：[skills/blind-spot-finder/SKILL.md:5-12]()\n\n## Best Practices\n\n### Regular Maintenance\n\n1. Run `relationship-pulse` weekly to identify neglected contacts\n2. Review `follow-ups` daily during planning\n3. Use `contact-lookup` before any significant meeting\n\n### Data Quality\n\n1. Ensure relationship types are accurately set for proper threshold calculation\n2. Add notes during interactions for future context\n3. Link voice memos and meeting notes to relevant contacts\n\n### Avoiding Duplication\n\n- Prefer updating existing notes over creating duplicates\n- Use `update_client_note` instead of `create_client_note` when history exists\n- Link to existing contacts rather than creating new person records\n\n资料来源：[skills/contact-lookup/SKILL.md:26-27]()\n\n## Summary\n\nThe People & Relationships module provides a holistic approach to relationship management within LifeOS. By integrating messaging, meetings, voice notes, and AI-generated insights, it enables proactive relationship maintenance alongside productivity work. The system treats relationships as living data that requires regular attention, not static contacts to be occasionally referenced.\n\nKey capabilities include:\n\n- Complete contact dossiers aggregating all interaction data\n- Proactive neglect detection with customizable thresholds\n- Meeting preparation with full historical context\n- Follow-up tracking across multiple communication channels\n- Rapid context switching for multi-client workflows\n\n---\n\n\n\n## Review Workflows\n\n### 相关页面\n\n相关主题：[Daily Workflows](#daily-workflows), [Project Management](#project-management), [Finance Management](#finance-management)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [skills/weekly-review/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/weekly-review/SKILL.md)\n- [skills/weekly-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/weekly-plan/SKILL.md)\n- [skills/monthly-review/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/monthly-review/SKILL.md)\n- [skills/cycle-review/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/cycle-review/SKILL.md)\n- [skills/initiative-review/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/initiative-review/SKILL.md)\n- [skills/customer-success-triage/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md)\n- [skills/blind-spot-finder/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/blind-spot-finder/SKILL.md)\n- [skills/sprint-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/sprint-plan/SKILL.md)\n \n\n# Review Workflows\n\n## Overview\n\nReview Workflows are periodic assessment and reflection skills that enable users to systematically evaluate their progress across different time horizons—from daily standups to yearly initiative reviews. These workflows pull data from LifeOS via MCP (Model Context Protocol) tools, present structured insights, and in some cases apply mutations to the system.\n\nThe review system follows a temporal hierarchy aligned with typical sprint and goal-setting cadences:\n\n```mermaid\ngraph TB\n subgraph \"Review Hierarchy\"\n DR[Daily Review
daily-plan]\n WR[Weekly Review
weekly-review]\n CR[Cycle Review
cycle-review]\n MR[Monthly Review
monthly-review]\n IR[Initiative Review
initiative-review]\n end\n \n subgraph \"Specialized Reviews\"\n CST[Customer Success
Triage]\n BSF[Blind Spot
Finder]\n end\n \n DR --> WR\n WR --> CR\n CR --> MR\n MR --> IR\n \n WR -.-> CST\n WR -.-> BSF\n```\n\nEach review type serves a distinct purpose in the feedback loop of planning, execution, and reflection.\n\n资料来源：[skills/weekly-review/SKILL.md:1-6](https://github.com/starascendin/lifeos-plugin/blob/main/skills/weekly-review/SKILL.md)\n资料来源：[skills/cycle-review/SKILL.md:1-6](https://github.com/starascendin/lifeos-plugin/blob/main/skills/cycle-review/SKILL.md)\n\n---\n\n## Review Workflow Types\n\n### Comparison Table\n\n| Review Type | Time Horizon | Mutating | Primary Data Sources | Skill File |\n|-------------|--------------|----------|---------------------|------------|\n| Daily Plan | Today | Yes | Planning context, calendar, habits | `daily-plan/SKILL.md` |\n| Weekly Review | This week | No | Weekly agenda, cycle, tasks | `weekly-review/SKILL.md` |\n| Weekly Plan | This week | Yes | Planning context, backlog | `weekly-plan/SKILL.md` |\n| Cycle Review | Current sprint | Partial | Current cycle, tasks | `cycle-review/SKILL.md` |\n| Sprint Plan | Current sprint | Yes | Planning context, backlog | `sprint-plan/SKILL.md` |\n| Monthly Review | This month | No | Monthly agenda, cycles, projects | `monthly-review/SKILL.md` |\n| Initiative Review | This year | No | Yearly initiative rollup | `initiative-review/SKILL.md` |\n| Customer Success Triage | Per client | Partial | Client workspace, threads, meetings | `customer-success-triage/SKILL.md` |\n| Blind Spot Finder | Ad-hoc | Partial | Working memory, health, habits | `blind-spot-finder/SKILL.md` |\n\n资料来源：[skills/weekly-review/SKILL.md:1-20](https://github.com/starascendin/lifeos-plugin/blob/main/skills/weekly-review/SKILL.md)\n资料来源：[skills/monthly-review/SKILL.md:1-25](https://github.com/starascendin/lifeos-plugin/blob/main/skills/monthly-review/SKILL.md)\n资料来源：[skills/initiative-review/SKILL.md:1-15](https://github.com/starascendin/lifeos-plugin/blob/main/skills/initiative-review/SKILL.md)\n\n---\n\n## Weekly Review\n\nThe **weekly-review** skill provides a comprehensive assessment of the current week's work, sprint health, and upcoming priorities.\n\n### Purpose\n\n> \"Run weekly review with completed work, in-progress items, sprint health, and blockers\"\n\n资料来源：[skills/weekly-review/SKILL.md:1-2](https://github.com/starascendin/lifeos-plugin/blob/main/skills/weekly-review/SKILL.md)\n\n### Data Gathering Flow\n\n```mermaid\ngraph LR\n A[get_weekly_agenda] --> B[Present Weekly Review]\n C[get_current_cycle] --> B\n D[get_tasks status=done] --> B\n E[get_tasks status=in_progress] --> B\n F[get_tasks status=todo] --> B\n```\n\n### MCP Tools Used\n\n| Tool | Purpose |\n|------|---------|\n| `get_weekly_agenda` | Week's agenda and AI summary |\n| `get_current_cycle` | Sprint progress |\n| `get_tasks` (status: done) | Completed work this week |\n| `get_tasks` (status: in_progress) | Active work |\n| `get_tasks` (status: todo) | Upcoming work |\n\n### Output Structure\n\nThe weekly review presents:\n- **Completed**: What got done this week\n- **In Progress**: What's still being worked on\n- **Sprint Health**: Cycle progress, burndown status\n- **Blockers**: Anything overdue or stuck\n- **Next Week**: Key items to tackle\n\nThe skill optionally accepts a date argument to review a specific week.\n\n资料来源：[skills/weekly-review/SKILL.md:1-25](https://github.com/starascendin/lifeos-plugin/blob/main/skills/weekly-review/SKILL.md)\n\n---\n\n## Monthly Review\n\nThe **monthly-review** skill provides a broader perspective on accomplishments, project progress, and themes across an entire month.\n\n### Purpose\n\n> \"Run monthly review with accomplishments, project progress, and next month planning\"\n\n资料来源：[skills/monthly-review/SKILL.md:1-2](https://github.com/starascendin/lifeos-plugin/blob/main/skills/monthly-review/SKILL.md)\n\n### Data Gathering Flow\n\n```mermaid\ngraph TB\n A[get_monthly_agenda] --> Z[Monthly Review Output]\n B[get_cycles] --> Z\n C[get_tasks status=done] --> Z\n D[get_projects] --> Z\n E[get_clients] --> Z\n F[get_recent_notes limit=20] --> Z\n```\n\n### MCP Tools Used\n\n| Tool | Purpose | Data Retrieved |\n|------|---------|----------------|\n| `get_monthly_agenda` | Month overview and AI summary | Full month's context |\n| `get_cycles` | All sprints this month | Completion rates |\n| `get_tasks` (status: done) | Everything completed | Accomplishments |\n| `get_projects` | Project progress and health | Status tracking |\n| `get_clients` | Client relationship status | Health of client relationships |\n| `get_recent_notes` (limit: 20) | Captured thoughts | Themes and patterns |\n\n### Output Structure\n\nThe monthly review presents:\n- **Accomplishments**: Major wins and completed work\n- **Projects Progress**: Status of each active project\n- **Sprint Performance**: Average completion rate across cycles\n- **Client Health**: Relationship status per client\n- **Themes**: Patterns from notes and completed work\n- **Carried Forward**: What's rolling into next month\n- **Reflections**: What worked, what didn't\n- **Next Month Focus**: Top 3 priorities\n\nSupports optional month argument (e.g., \"january\" or \"2024-01\").\n\n资料来源：[skills/monthly-review/SKILL.md:1-30](https://github.com/starascendin/lifeos-plugin/blob/main/skills/monthly-review/SKILL.md)\n\n---\n\n## Cycle Review\n\nThe **cycle-review** skill focuses on the current sprint/iteration, providing progress metrics and rollover options for incomplete work.\n\n### Purpose\n\n> \"Review the current cycle/sprint with progress, incomplete items, and rollover options\"\n\n资料来源：[skills/cycle-review/SKILL.md:1-2](https://github.com/starascendin/lifeos-plugin/blob/main/skills/cycle-review/SKILL.md)\n\n### Data Gathering\n\n| Tool | Purpose |\n|------|---------|\n| `get_current_cycle` | Active cycle with progress stats |\n| `get_cycles` (status: upcoming) | What's next |\n| `get_tasks` (status: in_progress) | Active work |\n| `get_tasks` (status: backlog or todo) | Incomplete items in cycle |\n\n### Output Structure\n\n- **Cycle Summary**: Name, dates, days remaining\n- **Progress**: Completion %, issues done vs total\n- **Incomplete Items**: All non-done/non-cancelled issues with status and priority\n- **Next Cycle**: The upcoming cycle (if any)\n- **Recommendations**: Closing suggestions, reprioritization advice\n\n### Cycle Management Actions\n\n| Argument | Action | MCP Call |\n|----------|--------|----------|\n| `close` | Close cycle WITHOUT rollover | `close_cycle` |\n| `rollover` | Close cycle WITH rollover | `close_cycle` with `rolloverIncomplete=true` |\n| None | Prompt user for action | — |\n\n资料来源：[skills/cycle-review/SKILL.md:1-35](https://github.com/starascendin/lifeos-plugin/blob/main/skills/cycle-review/SKILL.md)\n\n---\n\n## Initiative Review\n\nThe **initiative-review** skill provides a yearly perspective on goals, tracking progress across multiple initiative categories.\n\n### Purpose\n\n> \"Review yearly initiative progress with stats per category and highlight stalled initiatives\"\n\n资料来源：[skills/initiative-review/SKILL.md:1-2](https://github.com/starascendin/lifeos-plugin/blob/main/skills/initiative-review/SKILL.md)\n\n### Data Gathering Flow\n\n```mermaid\ngraph TB\n A[get_initiative_yearly_rollup] --> B{Low Progress?}\n B -->|Yes| C[get_initiative_with_stats]\n B -->|No| D[Present Review]\n C --> D\n```\n\n### Output Structure\n\n- **Year Overview**: Total initiatives, active vs completed, average progress\n- **By Category**: Group by (career, health, learning, etc.) with progress\n- **Each Initiative**: Title, status, progress %, tasks completed/total, linked projects, habits\n- **Highlights**: Initiatives at 80%+ progress\n- **Concerns**: Flag 0% progress, no linked projects, or \"paused\" status\n- **Recommendations**: Next actions\n\nSupports optional year argument (e.g., \"2025\").\n\n资料来源：[skills/initiative-review/SKILL.md:1-30](https://github.com/starascendin/lifeos-plugin/blob/main/skills/initiative-review/SKILL.md)\n\n---\n\n## Customer Success Triage\n\nThe **customer-success-triage** skill is a specialized review for customer-facing work, synthesizing communications and tracking across multiple channels.\n\n### Purpose\n\n> \"Triage client requests and customer-success work using the client workspace, business chats, Fathom and Granola meetings, notes, and open tasks.\"\n\n资料来源：[skills/customer-success-triage/SKILL.md:1-5](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md)\n\n### Data Gathering Flow\n\n```mermaid\ngraph TB\n A[get_client_success_workspace] --> B[Review Workspace]\n B --> C[recentThreads]\n B --> D[recentMeetings]\n B --> E[notes]\n B --> F[openTasks]\n B --> G[projects]\n \n C --> H[Drill Down Options]\n D --> H\n E --> H\n \n H --> I[get_beeper_thread_messages]\n H --> J[get_fathom_meeting/transcript]\n H --> K[get_granola_meeting/transcript]\n H --> L[get_client_notes]\n```\n\n### Classification Framework\n\n| Category | Description |\n|----------|-------------|\n| **New Requirements** | Net-new asks or requested changes |\n| **Follow-Ups** | Things waiting on you or the team |\n| **Risks / Blockers** | Scope ambiguity, overdue work, delivery risk, churn risk |\n| **Already Tracked** | Notes or tasks that already cover the request |\n\n### Write Operations\n\n| Operation | When to Use |\n|-----------|-------------|\n| `create_client_note` | Save durable account memory |\n| `update_client_note` | Update existing account memory |\n| `create_issue` | New execution work only |\n| `update_issue` | Modify existing tasks |\n\n**Guidelines**: Prefer updating existing notes/tasks over creating duplicates. Do not delete anything.\n\n资料来源：[skills/customer-success-triage/SKILL.md:1-35](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md)\n\n---\n\n## Blind Spot Finder\n\nThe **blind-spot-finder** skill uses multi-model AI evaluation to identify self-deceptions, local maxima, and blind spots that the user cannot see from within their own perspective.\n\n### Purpose\n\n> \"Use multiple AI models to find what I'm NOT seeing. This is about the unknown unknowns.\"\n\n资料来源：[skills/blind-spot-finder/SKILL.md:1-3](https://github.com/starascendin/lifeos-plugin/blob/main/skills/blind-spot-finder/SKILL.md)\n\n### Data Gathering (Parallel Calls)\n\n```mermaid\ngraph TB\n subgraph \"Context Gathering\"\n A[get_working_memory] \n B[get_coaching_action_items]\n C[get_habits]\n D[get_screentime_summary]\n E[get_health_sleep]\n F[get_finance_net_worth]\n end\n \n A & B & C & D & E & F --> G[Build Blind Spot Brief]\n G --> H[Multi-Model Council]\n H --> I[Synthesized Insights]\n```\n\n### Multi-Model Council Process\n\n| Round | Focus | Purpose |\n|-------|-------|---------|\n| Round 1 | Blind Spot Detection | Identify top 3-5 blind spots, self-deceptions, local maxima |\n| Round 2 | Peer Evaluation | Models review each other's responses |\n| Round 3 | Synthesis | Chairman's final synthesized perspective |\n\n### Focus Areas for Blind Spot Detection\n\n- Self-deceptions they're maintaining\n- Local maxima they're stuck in\n- Assumptions they haven't questioned\n- Patterns they can't see because they're inside them\n- Things they SAY they want but systematically avoid\n\n资料来源：[skills/blind-spot-finder/SKILL.md:1-50](https://github.com/starascendin/lifeos-plugin/blob/main/skills/blind-spot-finder/SKILL.md)\n\n---\n\n## Planning Integration\n\nReview workflows connect to planning workflows to close the feedback loop between reflection and action.\n\n### Review → Plan Flow\n\n```mermaid\ngraph LR\n WR[Weekly Review] --> WP[Weekly Plan]\n CR[Cycle Review] --> SP[Sprint Plan]\n MR[Monthly Review] --> WP\n \n WP --> AP[apply_planning_patch]\n SP --> AP\n \n AP -->|Creates| NI[new_issue]\n AP -->|Schedules| SI[scheduled_issue]\n AP -->|Assigns| ACI[assign_issue_to_current_cycle]\n AP -->|Updates| UG[update_cycle_goals]\n```\n\n### Mutating Operations Available\n\n| Operation | Purpose | Available In |\n|-----------|---------|---------------|\n| `create_issue` | New work | Weekly Plan, Sprint Plan |\n| `schedule_issue` | Due date changes | Weekly Plan, Sprint Plan |\n| `update_issue` | Status, priority, estimate, title | Weekly Plan, Sprint Plan |\n| `assign_issue_to_current_cycle` | Cycle assignment | Weekly Plan, Sprint Plan |\n| `set_top_priority` | Immediate focus | Weekly Plan, Sprint Plan |\n| `update_cycle_goals` | Cycle focus changes | Weekly Plan, Sprint Plan |\n| `save_weekly_note` | Readable weekly plan artifact | Weekly Plan |\n| `save_daily_note` | Concrete execution plan | Weekly Plan |\n\n资料来源：[skills/weekly-plan/SKILL.md:1-30](https://github.com/starascendin/lifeos-plugin/blob/main/skills/weekly-plan/SKILL.md)\n资料来源：[skills/sprint-plan/SKILL.md:1-30](https://github.com/starascendin/lifeos-plugin/blob/main/skills/sprint-plan/SKILL.md)\n\n---\n\n## MCP Tool Reference\n\n### Commonly Used Tools Across Reviews\n\n| Tool | Returns | Review Types |\n|------|---------|--------------|\n| `get_weekly_agenda` | Week's agenda, AI summary | Weekly Review, Weekly Plan |\n| `get_monthly_agenda` | Month overview, AI summary | Monthly Review |\n| `get_current_cycle` | Active cycle stats | Weekly Review, Cycle Review, Sprint Plan |\n| `get_cycles` | All cycles with status | Cycle Review, Monthly Review |\n| `get_tasks` | Tasks filtered by status | All reviews |\n| `get_projects` | Project list with status | Monthly Review |\n| `get_clients` | Client relationships | Monthly Review |\n| `get_initiative_yearly_rollup` | Initiative stats by year | Initiative Review |\n| `get_working_memory` | User's working memory | Blind Spot Finder |\n\n### Planning Context Tool\n\nThe `get_planning_context` tool is fundamental to planning workflows:\n\n| Parameter | Type | Purpose |\n|-----------|------|---------|\n| `date` | string | Specific date for daily planning |\n| `weekStartDate` | string | Week start for weekly planning |\n| `include.daily` | boolean | Include daily fields |\n| `include.weekly` | boolean | Include weekly context |\n| `include.currentCycle` | boolean | Include current cycle |\n| `include.backlog` | boolean | Include backlog items |\n| `include.habits` | boolean | Include habit data |\n| `include.dailyFields` | boolean | Include daily field values |\n| `include.calendar` | boolean | Include calendar events |\n| `include.voiceMemos` | boolean | Include voice memos |\n\n资料来源：[skills/daily-plan/SKILL.md:1-25](https://github.com/starascendin/lifeos-plugin/blob/main/skills/daily-plan/SKILL.md)\n资料来源：[skills/weekly-plan/SKILL.md:1-30](https://github.com/starascendin/lifeos-plugin/blob/main/skills/weekly-plan/SKILL.md)\n\n---\n\n## Best Practices\n\n### When to Use Each Review Type\n\n| Scenario | Recommended Review |\n|----------|-------------------|\n| Start of week planning | Weekly Plan + Weekly Review (if previous week ended) |\n| Mid-sprint check | Cycle Review |\n| End of sprint | Cycle Review + Sprint Plan (for next) |\n| Month transition | Monthly Review |\n| Quarterly planning | Initiative Review + Monthly Review |\n| New client engagement | Customer Success Triage |\n| Feeling stuck or plateaued | Blind Spot Finder |\n\n### Review Cadence\n\n```mermaid\ngantt\n title Review Cadence\n dateFormat X\n axisFormat %j\n \n section Weekly\n Weekly Review :active, r1, 0, 1d\n Weekly Plan :active, r2, 1, 1d\n \n section Monthly\n Monthly Review :active, m1, 30, 1d\n \n section Cycle\n Cycle Review :active, c1, 14, 1d\n Sprint Plan :active, c2, 14, 1d\n```\n\n### Output Expectations\n\n- **Non-mutating reviews** (Weekly Review, Monthly Review, Initiative Review) present data without changes\n- **Mutating workflows** (Weekly Plan, Sprint Plan) automatically apply changes—do not ask for confirmation\n- **Partial mutating** (Cycle Review, Customer Success Triage) offer options but require user input for destructive actions\n\n资料来源：[skills/cycle-review/SKILL.md:25-35](https://github.com/starascendin/lifeos-plugin/blob/main/skills/cycle-review/SKILL.md)\n资料来源：[skills/weekly-plan/SKILL.md:28-32](https://github.com/starascendin/lifeos-plugin/blob/main/skills/weekly-plan/SKILL.md)\n\n---\n\n## See Also\n\n- [Daily Workflows](README.md#daily-workflows) - Daily planning and standup skills\n- [Project & Client Management](README.md#project--client-management) - Project status and client briefing skills\n- [Skills Index](AGENTS.md) - Complete list of all 37 skills\n\n---\n\n\n\n## Finance Management\n\n### 相关页面\n\n相关主题：[Review Workflows](#review-workflows), [Health Integration (Oura Ring)](#health-integration)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [skills/finance-overview/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/finance-overview/SKILL.md)\n- [skills/finance-spending/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/finance-spending/SKILL.md)\n- [README.md](https://github.com/starascendin/lifeos-plugin/blob/main/README.md)\n- [AGENTS.md](https://github.com/starascendin/lifeos-plugin/blob/main/AGENTS.md)\n \n\n# Finance Management\n\nThe Finance Management module within LifeOS provides a comprehensive suite of tools for tracking, analyzing, and understanding personal finances. It integrates directly with Convex-powered backend services to deliver real-time financial insights through 126 MCP (Model Context Protocol) tools available to AI agents.\n\n## Overview\n\nThe Finance Management system consists of two primary skill workflows that enable users to:\n\n- Monitor net worth, account balances, and financial trends\n- Analyze spending patterns with detailed transaction data\n- Track daily income versus spending\n- Identify financial patterns and anomalies\n\n资料来源：[README.md](https://github.com/starascendin/lifeos-plugin/blob/main/README.md)\n\n## Architecture\n\nThe Finance Management module operates within the broader LifeOS ecosystem, leveraging MCP tools to communicate with the Convex backend. All monetary values are stored in cents and converted to dollars for display.\n\n```mermaid\ngraph TD\n A[User Request] --> B[Finance Skill Workflow]\n B --> C[MCP Tool Calls]\n C --> D[Convex Backend]\n D --> E[(Financial Data)]\n \n C --> F[get_finance_net_worth]\n C --> G[get_finance_accounts]\n C --> H[get_finance_snapshots]\n C --> I[get_finance_daily_spending]\n C --> J[get_finance_transactions]\n \n F --> K[Net Worth Dashboard]\n G --> L[Account Breakdown]\n H --> M[90-Day Trend]\n I --> N[Daily Spending Pattern]\n J --> O[Transaction History]\n```\n\n资料来源：[skills/finance-overview/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/finance-overview/SKILL.md) & [skills/finance-spending/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/finance-spending/SKILL.md)\n\n## Available Skills\n\n### Finance Overview\n\nThe `finance-overview` skill provides a comprehensive financial dashboard including net worth summary, account balances, and net worth trends.\n\n| Component | Description |\n|-----------|-------------|\n| Net Worth | Current total with change over the period |\n| Assets | Total assets by account type (checking, savings, investments, retirement) |\n| Liabilities | Total liabilities by type (credit cards, loans) |\n| Trend | Net worth direction over 90 days (growing/declining/stable) |\n| Accounts | Individual account listing with name, type, and balance |\n| Insights | Notable changes or patterns |\n\n资料来源：[skills/finance-overview/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/finance-overview/SKILL.md)\n\n**Usage:**\n```bash\n/finance-overview\n```\n\n**Custom Days Parameter:**\n```bash\n/finance-overview 30\n```\nWhen a number is provided as an argument, it overrides the default 90-day trend period.\n\n### Finance Spending\n\nThe `finance-spending` skill analyzes spending patterns with daily income/spending aggregation and recent transaction details.\n\n| Component | Description |\n|-----------|-------------|\n| Summary | Total income, total spending, net for the period |\n| Daily Average | Average daily spending calculation |\n| Spending Pattern | High-spending days and behavioral patterns |\n| Recent Transactions | Most notable recent transactions |\n| Insights | Spending trends, unusual activity, suggestions |\n\n资料来源：[skills/finance-spending/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/finance-spending/SKILL.md)\n\n**Usage:**\n```bash\n/finance-spending\n```\n\n**Custom Days Parameter:**\n```bash\n/finance-spending 14\n```\nWhen a number is provided, it overrides the default 30-day analysis period.\n\n## MCP Tool Reference\n\nThe Finance Management system exposes the following MCP tools for programmatic access:\n\n| Tool | Purpose |\n|------|---------|\n| `get_finance_net_worth` | Current net worth and account breakdown |\n| `get_finance_accounts` | All account details |\n| `get_finance_snapshots` | Net worth trend data with configurable days |\n| `get_finance_daily_spending` | Daily income/spending aggregation |\n| `get_finance_transactions` | Recent transaction details |\n\n资料来源：[AGENTS.md](https://github.com/starascendin/lifeos-plugin/blob/main/AGENTS.md)\n\n## Data Models\n\n### Financial Data Types\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `balance` | integer | Monetary value stored in cents |\n| `accountType` | string | Type of account (checking, savings, investment, retirement, credit_card, loan) |\n| `netWorth` | integer | Total net worth in cents |\n| `snapshotDate` | date | Date of the financial snapshot |\n\n> **Note:** All monetary amounts are stored in cents and must be converted to dollars for display purposes.\n\n## Workflow Diagram\n\n```mermaid\ngraph LR\n A[Start: /finance-overview] --> B[get_finance_net_worth]\n A --> C[get_finance_accounts]\n A --> D[get_finance_snapshots days=90]\n \n B --> E[Aggregate Data]\n C --> E\n D --> E\n \n E --> F[Build Dashboard]\n F --> G[Net Worth Display]\n F --> H[Assets Breakdown]\n F --> I[Liabilities Breakdown]\n F --> J[90-Day Trend]\n F --> K[Insights]\n```\n\n## Integration Points\n\nThe Finance Management module integrates with:\n\n- **PPV (Purpose, Pillar, Vision) System** - For linking financial goals to life design\n- **Coaching System** - Financial coaching insights and action items\n- **Habits Tracking** - Financial habit compliance\n- **Initiatives** - Yearly financial goals tracked as initiatives\n\n资料来源：[AGENTS.md](https://github.com/starascendin/lifeos-plugin/blob/main/AGENTS.md)\n\n## Quick Reference\n\n| Command | Description | Default Period |\n|---------|-------------|----------------|\n| `/finance-overview` | Net worth dashboard | 90-day trend |\n| `/finance-spending` | Spending analysis | 30-day analysis |\n\nAll commands support numeric arguments to override default periods (e.g., `/finance-overview 30` or `/finance-spending 14`).\n\n---\n\n\n\n## Coaching System\n\n### 相关页面\n\n相关主题：[Habits & Accountability](#habits-accountability)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [skills/coaching-overview/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/coaching-overview/SKILL.md)\n- [skills/coaching-action-items/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/coaching-action-items/SKILL.md)\n- [skills/coaching-session-review/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/coaching-session-review/SKILL.md)\n- [skills/coach-memory/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/coach-memory/SKILL.md)\n- [skills/blind-spot-finder/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/blind-spot-finder/SKILL.md)\n- [skills/llm-council/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/llm-council/SKILL.md)\n \n\n# Coaching System\n\n## Overview\n\nThe Coaching System is an integrated personal development framework within LifeOS that leverages multiple AI models to provide structured coaching, track action items, maintain coach memory, and help users identify blind spots. The system operates as a multi-layered coaching layer that sits atop the core LifeOS data, utilizing the MCP (Model Context Protocol) interface to access user data and apply mutations.\n\nThe coaching system serves as the \"meta-layer\" for personal growth, distinguishing itself from task management by focusing on identity, behavioral patterns, and sustained development rather than discrete deliverables. It coordinates with other LifeOS features like health data, habits, and finance to provide contextually-aware coaching insights.\n\n**资料来源：** [skills/coaching-overview/SKILL.md:1-4]()\n\n## Architecture\n\nThe Coaching System architecture consists of three primary layers:\n\n```mermaid\ngraph TD\n A[Coaching System] --> B[Skill Layer]\n A --> C[Memory Layer]\n A --> D[Multi-Model Layer]\n \n B --> B1[coaching-overview]\n B --> B2[coaching-action-items]\n B --> B3[coaching-session-review]\n B --> B4[coach-memory]\n \n C --> C1[Working Memory]\n C --> C2[Session Summaries]\n C --> C3[Action Items]\n \n D --> D1[llm-council]\n D --> D2[blind-spot-finder]\n \n C1 --> E[LifeOS Data]\n C2 --> E\n C3 --> E\n```\n\n### Skill Layer\n\nThe skill layer consists of discrete workflow skills that can be invoked individually:\n\n| Skill | Purpose | Mutating |\n|-------|---------|----------|\n| `coaching-overview` | Dashboard of coaches, sessions, and action items | No |\n| `coaching-action-items` | Manage coaching action items | Yes |\n| `coaching-session-review` | Review session summaries and insights | No |\n| `coach-memory` | View and update AI coach's working memory | Yes |\n\n**资料来源：** [skills/coaching-overview/SKILL.md:1-18]()\n\n### Memory Layer\n\nThe memory layer maintains persistent knowledge about the user across coaching interactions:\n\n- **Core Struggles**: Consistent challenges the user faces\n- **Values**: Deeply held principles\n- **Triggers**: Causes of spirals, procrastination, or withdrawal\n- **Breakthroughs**: Moments of clarity or growth\n- **Personality**: Cognitive patterns and characteristics\n- **Communication Style**: Coaching delivery preferences\n- **Patterns**: Recurring behavioral patterns\n- **Energy Sources**: What energizes vs drains\n- **Relationships**: Key relationship dynamics\n- **Context**: Current life circumstances\n\n**资料来源：** [skills/coach-memory/SKILL.md:8-25]()\n\n### Multi-Model Layer\n\nThe multi-model layer employs multiple AI models for deliberation and insight generation:\n\n- **LLM Council**: Structured deliberation with peer review and synthesis\n- **Blind Spot Finder**: Multi-model analysis to identify unknown unknowns\n\n**资料来源：** [skills/llm-council/SKILL.md:1-5]()\n\n## MCP Tools\n\nThe Coaching System exposes its functionality through the following MCP tools:\n\n### Query Tools\n\n| Tool | Returns | Source |\n|------|---------|--------|\n| `get_coaching_profiles` | All coach personas with names, focus areas, session cadence | 资料来源：[skills/coaching-overview/SKILL.md:8]() |\n| `get_coaching_sessions` | Recent sessions grouped by coach | 资料来源：[skills/coaching-session-review/SKILL.md:6]() |\n| `get_coaching_session` | Full session details including summary and action items | 资料来源：[skills/coaching-session-review/SKILL.md:9]() |\n| `get_coaching_action_items` | Action items with status filtering | 资料来源：[skills/coaching-overview/SKILL.md:9]() |\n| `get_working_memory` | All memory sections with confidence levels | 资料来源：[skills/coach-memory/SKILL.md:7]() |\n\n### Mutation Tools\n\n| Tool | Purpose | Source |\n|------|---------|--------|\n| `create_coaching_action_item` | Create new coaching homework/experiments | 资料来源：[skills/blind-spot-finder/SKILL.md:28]() |\n| `update_coaching_action_item` | Update status or content of action items | 资料来源：[skills/coaching-action-items/SKILL.md]() |\n| `update_working_memory` | Update coach's accumulated knowledge | 资料来源：[skills/blind-spot-finder/SKILL.md:29]() |\n\n## Coaching Workflows\n\n### Dashboard Overview\n\nThe `coaching-overview` skill provides a consolidated dashboard by executing three parallel queries:\n\n1. `get_coaching_profiles` — List all coach personas\n2. `get_coaching_sessions` with `limit=10` — Recent sessions across all coaches\n3. `get_coaching_action_items` with `status=\"pending\"` — Outstanding action items\n\n**资料来源：** [skills/coaching-overview/SKILL.md:5-13]()\n\nThe dashboard presents:\n\n- **Coaches**: Each coach profile with name, focus areas, and session cadence\n- **Recent Sessions**: Grouped by coach with title, date, and status\n- **Pending Action Items**: Count per coach with top 3 most urgent items shown\n- **Insights**: Active coaches, overdue items, suggested next sessions\n\n```mermaid\ngraph LR\n A[coaching-overview] --> B[get_coaching_profiles]\n A --> C[get_coaching_sessions]\n A --> D[get_coaching_action_items]\n \n B --> E[Dashboard Output]\n C --> E\n D --> E\n```\n\n**资料来源：** [skills/coaching-overview/SKILL.md:13-18]()\n\n### Session Review\n\nThe `coaching-session-review` skill provides in-depth review of coaching sessions:\n\n1. Find sessions via `get_coaching_sessions` with `limit=5`\n2. Resolve session ID from arguments or find most recent\n3. Fetch full details via `get_coaching_session`\n\n**资料来源：** [skills/coaching-session-review/SKILL.md:4-11]()\n\nThe session review displays:\n\n- **Session Info**: Coach name, date, duration, mood at start\n- **Summary**: AI-generated session summary\n- **Key Insights**: All key insights from the session\n- **Action Items**: All action items with current status\n- **Follow-up**: Suggested next session topics based on insights and pending items\n\n**资料来源：** [skills/coaching-session-review/SKILL.md:11-18]()\n\n### Action Item Management\n\nThe `coaching-action-items` skill manages the coaching homework cycle:\n\n```mermaid\ngraph TD\n A[Create Action Item] --> B[Pending Status]\n B --> C[In Progress]\n C --> D{Complete?}\n D -->|Yes| E[Completed]\n D -->|No| F[Update/Extend]\n F --> C\n \n E --> G[Review in Session]\n G --> A\n```\n\nAction items should be:\n- Specific experiments to test hypotheses\n- Linked to insights from sessions or blind spot discovery\n- Tracked with clear status progression\n\n**资料来源：** [skills/blind-spot-finder/SKILL.md:27-28]()\n\n### Coach Memory Management\n\nThe `coach-memory` skill provides visibility into the AI coach's accumulated knowledge:\n\n```mermaid\ngraph TD\n A[get_working_memory] --> B{All Sections}\n B --> C[Core Struggles]\n B --> D[Values]\n B --> E[Triggers]\n B --> F[Breakthroughs]\n B --> G[Personality]\n B --> H[Communication Style]\n B --> I[Patterns]\n B --> J[Energy Sources]\n B --> K[Relationships]\n B --> L[Context]\n \n M[Offer Update] --> N[update_working_memory]\n```\n\nFor each section, the skill displays:\n- Content of the section\n- Confidence level\n- Flagged sections that are empty or stale\n\n**资料来源：** [skills/coach-memory/SKILL.md:7-25]()\n\n## Multi-Model Deliberation\n\n### LLM Council\n\nThe `llm-council` skill implements a structured multi-model deliberation process:\n\n```mermaid\ngraph TD\n A[Start Council] --> B[Stage 1: Individual Responses]\n B --> C[Each Model Responds]\n C --> D[Stage 2: Peer Review]\n D --> E[Models Evaluate Each Other]\n E --> F[Rankings Generated]\n F --> G[Stage 3: Chairman Synthesis]\n G --> H[Final Authoritative Answer]\n \n H --> I[Optional: Save Summary]\n```\n\n**Execution flow:**\n1. **Stage 1** — Each council member provides an individual response\n2. **Stage 2** — Peer review with rankings table showing average rank per model\n3. **Stage 3** — Chairman synthesizes all perspectives into a final answer\n\n**资料来源：** [skills/llm-council/SKILL.md:35-50]()\n\nThe council uses the `zen consensus` tool for deliberation. Estimated completion:\n- Normal tier: 2-5 minutes\n- Pro tier: 5-10 minutes\n\n**资料来源：** [skills/llm-council/SKILL.md:33-34]()\n\n### Blind Spot Finder\n\nThe `blind-spot-finder` skill uses multi-model council to identify unknown unknowns:\n\n```mermaid\ngraph TD\n A[Context Gathering] --> B[Working Memory]\n A --> C[Pending Action Items]\n A --> D[Habits Completion]\n A --> E[Screen Time 3 Days]\n A --> F[Sleep 14 Days]\n A --> G[Finance Net Worth]\n \n B --> H[Blind Spot Brief]\n C --> H\n D --> H\n E --> H\n F --> H\n G --> H\n \n H --> I[Multi-Model Council]\n I --> J[3-5 Blind Spots Identified]\n \n J --> K[User Chooses ONE]\n K --> L[create_coaching_action_item]\n L --> M[update_working_memory]\n```\n\n**资料来源：** [skills/blind-spot-finder/SKILL.md:8-28]()\n\nThe blind spot brief includes:\n- Working memory patterns and triggers\n- Say-do gaps between stated goals and actual behavior\n- Incomplete action items\n- Screen time vs stated priorities\n- Any visible self-deceptions\n\n**资料来源：** [skills/blind-spot-finder/SKILL.md:15-25]()\n\nThe council focuses on:\n- Self-deceptions being maintained\n- Local maxima being stuck in\n- Unquestioned assumptions\n- Invisible patterns from inside them\n- Things systematically avoided despite stated desire\n\n**资料来源：** [skills/blind-spot-finder/SKILL.md:25-31]()\n\n## Integration with LifeOS\n\nThe Coaching System integrates with other LifeOS modules to provide contextually-aware coaching:\n\n| Module | Integration Point | Purpose |\n|--------|-------------------|---------|\n| Health | Sleep, readiness data via Oura | Correlate well-being with patterns |\n| Habits | Habit completion rates | Track behavior change consistency |\n| Finance | Net worth tracking | Ground goals in financial reality |\n| Projects | Initiative progress | Connect coaching to execution |\n| Working Memory | All memory sections | Persistent coach knowledge |\n\n**资料来源：** [skills/blind-spot-finder/SKILL.md:9-14]()\n\n## Skill Invocation\n\n### Via MCP Protocol\n\nAll coaching skills are exposed as MCP prompts, allowing any MCP client to invoke them:\n\n```bash\n/coaching-overview # Dashboard view\n/coaching-action-items # Manage action items\n/coaching-session-review # Review session\n/coach-memory # View/manage memory\n/blind-spot-finder # Find blind spots\n/llm-council # Multi-model deliberation\n```\n\n**资料来源：** [AGENTS.md:1-45]()\n\n### Via Claude Code\n\n```bash\nclaude plugin add github:starascendin/lifeos-plugin\n```\n\nSkills are then accessible through the Claude Code agent's skill system.\n\n**资料来源：** [README.md:1-35]()\n\n## Data Models\n\n### Coaching Profile\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `id` | string | Unique profile identifier |\n| `name` | string | Coach persona name |\n| `focusAreas` | string[] | Coaching specializations |\n| `sessionCadence` | string | Recommended session frequency |\n\n### Coaching Session\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `id` | string | Session identifier |\n| `coachId` | string | Reference to coach profile |\n| `title` | string | Session title/topic |\n| `date` | datetime | Session date |\n| `duration` | number | Duration in minutes |\n| `moodAtStart` | string | Mood indicator |\n| `summary` | string | AI-generated summary |\n| `keyInsights` | string[] | List of key insights |\n| `status` | string | Session status |\n\n**资料来源：** [skills/coaching-session-review/SKILL.md:11-15]()\n\n### Working Memory Section\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `sectionName` | string | Memory section identifier |\n| `content` | string | Section content |\n| `confidenceLevel` | string | AI confidence in accuracy |\n| `lastUpdated` | datetime | Last modification timestamp |\n\n**资料来源：** [skills/coach-memory/SKILL.md:20-25]()\n\n### Coaching Action Item\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `id` | string | Action item identifier |\n| `title` | string | Brief description |\n| `status` | enum | pending, in_progress, completed |\n| `linkedInsight` | string | Source insight or blind spot |\n| `createdAt` | datetime | Creation timestamp |\n| `dueDate` | datetime | Target completion date |\n\n**资料来源：** [skills/blind-spot-finder/SKILL.md:27-28]()\n\n## Best Practices\n\n### Coach Memory Maintenance\n\n- Review memory sections regularly for accuracy\n- Flag stale sections that need updating\n- Update memory after breakthrough insights\n- Use memory to inform coaching delivery style\n\n**资料来源：** [skills/coach-memory/SKILL.md:24-26]()\n\n### Action Item Creation\n\n- Create specific experiments, not vague goals\n- Link items to identified blind spots or insights\n- Use `create_coaching_action_item` for durable tracking\n- Update working memory when genuinely new insight emerges\n\n**资料来源：** [skills/blind-spot-finder/SKILL.md:28-29]()\n\n### Multi-Model Council Usage\n\n- Be patient for deliberation results (2-10 minutes)\n- Present all three stages for transparency\n- Highlight individual model perspectives of value\n- Offer to save insights via `create_ai_convo_summary`\n\n**资料来源：** [skills/llm-council/SKILL.md:46-52]()\n\n### Session Review\n\n- Always check for pending action items\n- Ground insights in user's specific context\n- Suggest forward-looking next steps\n- Reference working memory for continuity\n\n**资料来源：** [skills/coaching-session-review/SKILL.md:15-18]()\n\n---\n\n---\n\n## Doramagic Pitfall Log\n\nProject: starascendin/lifeos-plugin\n\nSummary: Found 7 potential pitfall items; 0 are high/blocking. Highest priority: configuration - 可能修改宿主 AI 配置.\n\n## 1. configuration · 可能修改宿主 AI 配置\n\n- Severity: medium\n- Evidence strength: source_linked\n- Finding: 项目面向 Claude/Cursor/Codex/Gemini/OpenCode 等宿主，或安装命令涉及用户配置目录。\n- User impact: 安装可能改变本机 AI 工具行为，用户需要知道写入位置和回滚方法。\n- Suggested check: 列出会写入的配置文件、目录和卸载/回滚步骤。\n- Guardrail action: 涉及宿主配置目录时必须给回滚路径，不能只给安装命令。\n- Evidence: capability.host_targets | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | host_targets=mcp_host, claude, claude_code\n\n## 2. capability · 能力判断依赖假设\n\n- Severity: medium\n- Evidence strength: source_linked\n- Finding: README/documentation is current enough for a first validation pass.\n- User impact: 假设不成立时，用户拿不到承诺的能力。\n- Suggested check: 将假设转成下游验证清单。\n- Guardrail action: 假设必须转成验证项；没有验证结果前不能写成事实。\n- Evidence: capability.assumptions | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | README/documentation is current enough for a first validation pass.\n\n## 3. maintenance · 维护活跃度未知\n\n- Severity: medium\n- Evidence strength: source_linked\n- Finding: 未记录 last_activity_observed。\n- User impact: 新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。\n- Suggested check: 补 GitHub 最近 commit、release、issue/PR 响应信号。\n- Guardrail action: 维护活跃度未知时，推荐强度不能标为高信任。\n- Evidence: evidence.maintainer_signals | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | last_activity_observed missing\n\n## 4. security_permissions · 下游验证发现风险项\n\n- Severity: medium\n- Evidence strength: source_linked\n- Finding: no_demo\n- User impact: 下游已经要求复核，不能在页面中弱化。\n- Suggested check: 进入安全/权限治理复核队列。\n- Guardrail action: 下游风险存在时必须保持 review/recommendation 降级。\n- Evidence: downstream_validation.risk_items | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | no_demo; severity=medium\n\n## 5. security_permissions · 存在评分风险\n\n- Severity: medium\n- Evidence strength: source_linked\n- Finding: no_demo\n- User impact: 风险会影响是否适合普通用户安装。\n- Suggested check: 把风险写入边界卡，并确认是否需要人工复核。\n- Guardrail action: 评分风险必须进入边界卡，不能只作为内部分数。\n- Evidence: risks.scoring_risks | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | no_demo; severity=medium\n\n## 6. maintenance · issue/PR 响应质量未知\n\n- Severity: low\n- Evidence strength: source_linked\n- Finding: issue_or_pr_quality=unknown。\n- User impact: 用户无法判断遇到问题后是否有人维护。\n- Suggested check: 抽样最近 issue/PR，判断是否长期无人处理。\n- Guardrail action: issue/PR 响应未知时，必须提示维护风险。\n- Evidence: evidence.maintainer_signals | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | issue_or_pr_quality=unknown\n\n## 7. maintenance · 发布节奏不明确\n\n- Severity: low\n- Evidence strength: source_linked\n- Finding: release_recency=unknown。\n- User impact: 安装命令和文档可能落后于代码，用户踩坑概率升高。\n- Suggested check: 确认最近 release/tag 和 README 安装命令是否一致。\n- Guardrail action: 发布节奏未知或过期时，安装说明必须标注可能漂移。\n- Evidence: evidence.maintainer_signals | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | release_recency=unknown\n\n\n",
"markdown_key": "lifeos-plugin",
"pages": "draft",
"source_refs": [
{
"evidence_id": "github_repo:1156470663",
"kind": "repo",
"supports_claim_ids": [
"claim_identity",
"claim_distribution",
"claim_capability"
],
"url": "https://github.com/starascendin/lifeos-plugin"
},
{
"evidence_id": "art_9414d1f5788f4226888c26ef330151e0",
"kind": "docs",
"supports_claim_ids": [
"claim_identity",
"claim_distribution",
"claim_capability"
],
"url": "https://github.com/starascendin/lifeos-plugin#readme"
}
],
"summary": "DeepWiki/Human Wiki output with a Doramagic pitfall appendix.",
"title": "lifeos-plugin 说明书",
"toc": [
"https://github.com/starascendin/lifeos-plugin 项目说明书",
"目录",
"Overview",
"Purpose and Scope",
"Architecture",
"Installation Methods",
"Skills Catalog",
"MCP Tools (126 Total)",
"Doramagic 踩坑日志"
]
}
},
"quality_gate": {
"blocking_gaps": [],
"category_confidence": "medium",
"compile_status": "ready_for_review",
"five_assets_present": true,
"install_sandbox_verified": true,
"missing_evidence": [],
"next_action": "publish to Doramagic.ai project surfaces",
"prompt_preview_boundary_ok": true,
"publish_status": "publishable",
"quick_start_verified": true,
"repo_clone_verified": true,
"repo_commit": "a583fdeeeea58b1633c94d8ab55cf78ed8b0a5a1",
"repo_inspection_error": null,
"repo_inspection_files": [
"README.md"
],
"repo_inspection_verified": true,
"review_reasons": [
"community_discussion_evidence_below_public_threshold"
],
"tag_count_ok": true,
"unsupported_claims": []
},
"schema_version": "0.1",
"user_assets": {
"ai_context_pack": {
"asset_id": "ai_context_pack",
"filename": "AI_CONTEXT_PACK.md",
"markdown": "# lifeos-plugin - Doramagic AI Context Pack\n\n> 定位：安装前体验与判断资产。它帮助宿主 AI 有一个好的开始，但不代表已经安装、执行或验证目标项目。\n\n## 充分原则\n\n- **充分原则，不是压缩原则**：AI Context Pack 应该充分到让宿主 AI 在开工前理解项目价值、能力边界、使用入口、风险和证据来源；它可以分层组织，但不以最短摘要为目标。\n- **压缩策略**：只压缩噪声和重复内容，不压缩会影响判断和开工质量的上下文。\n\n## 给宿主 AI 的使用方式\n\n你正在读取 Doramagic 为 lifeos-plugin 编译的 AI Context Pack。请把它当作开工前上下文：帮助用户理解适合谁、能做什么、如何开始、哪些必须安装后验证、风险在哪里。不要声称你已经安装、运行或执行了目标项目。\n\n## Claim 消费规则\n\n- **事实来源**：Repo Evidence + Claim/Evidence Graph；Human Wiki 只提供显著性、术语和叙事结构。\n- **事实最低状态**：`supported`\n- `supported`：可以作为项目事实使用，但回答中必须引用 claim_id 和证据路径。\n- `weak`：只能作为低置信度线索，必须要求用户继续核实。\n- `inferred`：只能用于风险提示或待确认问题，不能包装成项目事实。\n- `unverified`：不得作为事实使用，应明确说证据不足。\n- `contradicted`：必须展示冲突来源，不得替用户强行选择一个版本。\n\n## 它最适合谁\n\n- **正在使用 Claude/Codex/Cursor/Gemini 等宿主 AI 的开发者**：README 或插件配置提到多个宿主 AI。 证据：`README.md` Claim：`clm_0004` supported 0.86\n- **希望把专业流程带进宿主 AI 的用户**：仓库包含 Skill 文档。 证据：`skills/blind-spot-finder/SKILL.md`, `skills/capture/SKILL.md`, `skills/client-brief/SKILL.md`, `skills/client-health/SKILL.md` 等 Claim：`clm_0005` supported 0.86\n\n## 它能做什么\n\n- **AI Skill / Agent 指令资产库**（可做安装前预览）：项目包含可被宿主 AI 读取的 Skill 或 Agent 指令文件，可用于把专业流程带入 Claude、Codex、Cursor 等宿主。 证据：`skills/blind-spot-finder/SKILL.md`, `skills/capture/SKILL.md`, `skills/client-brief/SKILL.md`, `skills/client-health/SKILL.md` 等 Claim：`clm_0001` supported 0.86\n- **多宿主安装与分发**（需要安装后验证）：项目包含插件或 marketplace 配置，说明它面向一个或多个 AI 宿主的安装和分发。 证据：`.claude-plugin/plugin.json` Claim：`clm_0002` supported 0.86\n- **命令行启动或安装流程**（需要安装后验证）：项目文档中存在可执行命令，真实使用需要在本地或宿主环境中运行这些命令。 证据：`AGENTS.md`, `README.md` Claim：`clm_0003` supported 0.86\n\n## 怎么开始\n\n- `npm install -g @starascendin/lifeos-mcp` 证据：`README.md` Claim：`clm_0006` supported 0.86\n- `git clone git@github.com:starascendin/lifeos-plugin.git /tmp/lifeos-plugin` 证据：`AGENTS.md` Claim：`clm_0007` supported 0.86\n- `git clone git@github.com:starascendin/lifeos-plugin.git /opt/lifeos-plugin` 证据：`AGENTS.md` Claim：`clm_0008` supported 0.86\n- `git clone git@github.com:starascendin/lifeos-plugin.git /shared/lifeos-plugin` 证据：`AGENTS.md` Claim：`clm_0009` supported 0.86\n\n## 继续前判断卡\n\n- **当前建议**：需要管理员/安全审批\n- **为什么**：继续前可能涉及密钥、账号、外部服务或敏感上下文，建议先经过管理员或安全审批。\n\n### 30 秒判断\n\n- **现在怎么做**：需要管理员/安全审批\n- **最小安全下一步**：先跑 Prompt Preview；若涉及凭证或企业环境，先审批再试装\n- **先别相信**：工具权限边界不能在安装前相信。\n- **继续会触碰**：命令执行、宿主 AI 配置、本地环境或项目文件\n\n### 现在可以相信\n\n- **适合人群线索：正在使用 Claude/Codex/Cursor/Gemini 等宿主 AI 的开发者**（supported）：有 supported claim 或项目证据支撑，但仍不等于真实安装效果。 证据：`README.md` Claim：`clm_0004` supported 0.86\n- **适合人群线索：希望把专业流程带进宿主 AI 的用户**（supported）：有 supported claim 或项目证据支撑，但仍不等于真实安装效果。 证据：`skills/blind-spot-finder/SKILL.md`, `skills/capture/SKILL.md`, `skills/client-brief/SKILL.md`, `skills/client-health/SKILL.md` 等 Claim：`clm_0005` supported 0.86\n- **能力存在：AI Skill / Agent 指令资产库**（supported）：可以相信项目包含这类能力线索；是否适合你的具体任务仍要试用或安装后验证。 证据：`skills/blind-spot-finder/SKILL.md`, `skills/capture/SKILL.md`, `skills/client-brief/SKILL.md`, `skills/client-health/SKILL.md` 等 Claim：`clm_0001` supported 0.86\n- **能力存在：多宿主安装与分发**（supported）：可以相信项目包含这类能力线索；是否适合你的具体任务仍要试用或安装后验证。 证据：`.claude-plugin/plugin.json` Claim：`clm_0002` supported 0.86\n- **能力存在：命令行启动或安装流程**（supported）：可以相信项目包含这类能力线索；是否适合你的具体任务仍要试用或安装后验证。 证据：`AGENTS.md`, `README.md` Claim：`clm_0003` supported 0.86\n- **存在 Quick Start / 安装命令线索**（supported）：可以相信项目文档出现过启动或安装入口；不要因此直接在主力环境运行。 证据：`README.md` Claim：`clm_0006` supported 0.86\n\n### 现在还不能相信\n\n- **工具权限边界不能在安装前相信。**（unverified）：MCP/tool 类项目通常会触碰文件、网络、浏览器或外部 API，必须真实检查权限和日志。\n- **真实输出质量不能在安装前相信。**（unverified）：Prompt Preview 只能展示引导方式，不能证明真实项目中的结果质量。\n- **宿主 AI 版本兼容性不能在安装前相信。**（unverified）：Claude、Cursor、Codex、Gemini 等宿主加载规则和版本差异必须在真实环境验证。\n- **不会污染现有宿主 AI 行为，不能直接相信。**（inferred）：Skill、plugin、AGENTS/CLAUDE/GEMINI 指令可能改变宿主 AI 的默认行为。 证据：`.claude-plugin/plugin.json`, `AGENTS.md`, `skills/blind-spot-finder/SKILL.md`, `skills/capture/SKILL.md` 等\n- **可安全回滚不能默认相信。**（unverified）：除非项目明确提供卸载和恢复说明，否则必须先在隔离环境验证。\n- **真实安装后是否与用户当前宿主 AI 版本兼容？**（unverified）：兼容性只能通过实际宿主环境验证。 证据：`.claude-plugin/plugin.json`\n- **项目输出质量是否满足用户具体任务？**（unverified）：安装前预览只能展示流程和边界，不能替代真实评测。\n- **安装命令是否需要网络、权限或全局写入？**（unverified）：这影响企业环境和个人环境的安装风险。 证据：`README.md`\n\n### 继续会触碰什么\n\n- **命令执行**：包管理器、网络下载、本地插件目录、项目配置或用户主目录。 原因：运行第一条命令就可能产生环境改动；必须先判断是否值得跑。 证据：`AGENTS.md`, `README.md`\n- **宿主 AI 配置**：Claude/Codex/Cursor/Gemini/OpenCode 等宿主的 plugin、Skill 或规则加载配置。 原因：宿主配置会改变 AI 后续工作方式，可能和用户已有规则冲突。 证据：`.claude-plugin/plugin.json`, `AGENTS.md`, `skills/blind-spot-finder/SKILL.md`, `skills/capture/SKILL.md` 等\n- **本地环境或项目文件**：安装结果、插件缓存、项目配置或本地依赖目录。 原因：安装前无法证明写入范围和回滚方式，需要隔离验证。 证据：`.claude-plugin/plugin.json`, `AGENTS.md`, `README.md`\n- **环境变量 / API Key**：项目入口文档明确出现 API key、token、secret 或账号凭证配置。 原因：如果真实安装需要凭证，应先使用测试凭证并经过权限/合规判断。 证据：`.mcp.json`, `AGENTS.md`, `README.md`\n- **宿主 AI 上下文**：AI Context Pack、Prompt Preview、Skill 路由、风险规则和项目事实。 原因：导入上下文会影响宿主 AI 后续判断，必须避免把未验证项包装成事实。\n\n### 最小安全下一步\n\n- **先跑 Prompt Preview**：用安装前交互式试用判断工作方式是否匹配，不需要授权或改环境。（适用：任何项目都适用，尤其是输出质量未知时。）\n- **只在隔离目录或测试账号试装**：避免安装命令污染主力宿主 AI、真实项目或用户主目录。（适用：存在命令执行、插件配置或本地写入线索时。）\n- **先备份宿主 AI 配置**：Skill、plugin、规则文件可能改变 Claude/Cursor/Codex 的默认行为。（适用：存在插件 manifest、Skill 或宿主规则入口时。）\n- **不要使用真实生产凭证**：环境变量/API key 一旦进入宿主或工具链，可能产生账号和合规风险。（适用：出现 API、TOKEN、KEY、SECRET 等环境线索时。）\n- **安装后只验证一个最小任务**：先验证加载、兼容、输出质量和回滚，再决定是否深用。（适用：准备从试用进入真实工作流时。）\n\n### 退出方式\n\n- **保留安装前状态**：记录原始宿主配置和项目状态，后续才能判断是否可恢复。\n- **准备移除宿主 plugin / Skill / 规则入口**：如果试装后行为异常，可以把宿主 AI 恢复到试装前状态。\n- **记录安装命令和写入路径**：没有明确卸载说明时，至少要知道哪些目录或配置需要手动清理。\n- **准备撤销测试 API key 或 token**：测试凭证泄露或误用时，可以快速止损。\n- **如果没有回滚路径，不进入主力环境**：不可回滚是继续前阻断项，不应靠信任或运气继续。\n\n## 哪些只能预览\n\n- 解释项目适合谁和能做什么\n- 基于项目文档演示典型对话流程\n- 帮助用户判断是否值得安装或继续研究\n\n## 哪些必须安装后验证\n\n- 真实安装 Skill、插件或 CLI\n- 执行脚本、修改本地文件或访问外部服务\n- 验证真实输出质量、性能和兼容性\n\n## 边界与风险判断卡\n\n- **把安装前预览误认为真实运行**：用户可能高估项目已经完成的配置、权限和兼容性验证。 处理方式：明确区分 prompt_preview_can_do 与 runtime_required。 Claim：`clm_0010` inferred 0.45\n- **宿主 AI 插件或 Skill 规则冲突**：新规则可能改变用户现有宿主 AI 的工作方式。 处理方式：安装前先检查插件 manifest 和 Skill 文件，必要时隔离测试。 证据：`.claude-plugin/plugin.json` Claim：`clm_0011` supported 0.86\n- **命令执行会修改本地环境**：安装命令可能写入用户主目录、宿主插件目录或项目配置。 处理方式：先在隔离环境或测试账号中运行。 证据：`AGENTS.md`, `README.md` Claim：`clm_0012` supported 0.86\n- **待确认**：真实安装后是否与用户当前宿主 AI 版本兼容？。原因：兼容性只能通过实际宿主环境验证。\n- **待确认**：项目输出质量是否满足用户具体任务？。原因：安装前预览只能展示流程和边界，不能替代真实评测。\n- **待确认**：安装命令是否需要网络、权限或全局写入？。原因：这影响企业环境和个人环境的安装风险。\n\n## 开工前工作上下文\n\n### 加载顺序\n\n- 先读取 how_to_use.host_ai_instruction，建立安装前判断资产的边界。\n- 读取 claim_graph_summary，确认事实来自 Claim/Evidence Graph，而不是 Human Wiki 叙事。\n- 再读取 intended_users、capabilities 和 quick_start_candidates，判断用户是否匹配。\n- 需要执行具体任务时，优先查 role_skill_index，再查 evidence_index。\n- 遇到真实安装、文件修改、网络访问、性能或兼容性问题时，转入 risk_card 和 boundaries.runtime_required。\n\n### 任务路由\n\n- **AI Skill / Agent 指令资产库**：先基于 role_skill_index / evidence_index 帮用户挑选可用角色、Skill 或工作流。 边界：可做安装前 Prompt 体验。 证据：`skills/blind-spot-finder/SKILL.md`, `skills/capture/SKILL.md`, `skills/client-brief/SKILL.md`, `skills/client-health/SKILL.md` 等 Claim：`clm_0001` supported 0.86\n- **多宿主安装与分发**：先说明这是安装后验证能力，再给出安装前检查清单。 边界：必须真实安装或运行后验证。 证据：`.claude-plugin/plugin.json` Claim：`clm_0002` supported 0.86\n- **命令行启动或安装流程**：先说明这是安装后验证能力，再给出安装前检查清单。 边界：必须真实安装或运行后验证。 证据：`AGENTS.md`, `README.md` Claim：`clm_0003` supported 0.86\n\n### 上下文规模\n\n- 文件总数：44\n- 重要文件覆盖：40/44\n- 证据索引条目：44\n- 角色 / Skill 条目：39\n\n### 证据不足时的处理\n\n- **missing_evidence**：说明证据不足，要求用户提供目标文件、README 段落或安装后验证记录；不要补全事实。\n- **out_of_scope_request**：说明该任务超出当前 AI Context Pack 证据范围，并建议用户先查看 Human Manual 或真实安装后验证。\n- **runtime_request**：给出安装前检查清单和命令来源，但不要替用户执行命令或声称已执行。\n- **source_conflict**：同时展示冲突来源，标记为待核实，不要强行选择一个版本。\n\n## Prompt Recipes\n\n### 适配判断\n\n- 目标：判断这个项目是否适合用户当前任务。\n- 预期输出：适配结论、关键理由、证据引用、安装前可预览内容、必须安装后验证内容、下一步建议。\n\n```text\n请基于 lifeos-plugin 的 AI Context Pack，先问我 3 个必要问题，然后判断它是否适合我的任务。回答必须包含：适合谁、能做什么、不能做什么、是否值得安装、证据来自哪里。所有项目事实必须引用 evidence_refs、source_paths 或 claim_id。\n```\n\n### 安装前体验\n\n- 目标：让用户在安装前感受核心工作流，同时避免把预览包装成真实能力或营销承诺。\n- 预期输出：一段带边界标签的体验剧本、安装后验证清单和谨慎建议；不含真实运行承诺或强营销表述。\n\n```text\n请把 lifeos-plugin 当作安装前体验资产，而不是已安装工具或真实运行环境。\n\n请严格输出四段：\n1. 先问我 3 个必要问题。\n2. 给出一段“体验剧本”：用 [安装前可预览]、[必须安装后验证]、[证据不足] 三种标签展示它可能如何引导工作流。\n3. 给出安装后验证清单：列出哪些能力只有真实安装、真实宿主加载、真实项目运行后才能确认。\n4. 给出谨慎建议：只能说“值得继续研究/试装”“先补充信息后再判断”或“不建议继续”，不得替项目背书。\n\n硬性边界：\n- 不要声称已经安装、运行、执行测试、修改文件或产生真实结果。\n- 不要写“自动适配”“确保通过”“完美适配”“强烈建议安装”等承诺性表达。\n- 如果描述安装后的工作方式，必须使用“如果安装成功且宿主正确加载 Skill，它可能会……”这种条件句。\n- 体验剧本只能写成“示例台词/假设流程”：使用“可能会询问/可能会建议/可能会展示”，不要写“已写入、已生成、已通过、正在运行、正在生成”。\n- Prompt Preview 不负责给安装命令；如用户准备试装，只能提示先阅读 Quick Start 和 Risk Card，并在隔离环境验证。\n- 所有项目事实必须来自 supported claim、evidence_refs 或 source_paths；inferred/unverified 只能作风险或待确认项。\n\n```\n\n### 角色 / Skill 选择\n\n- 目标：从项目里的角色或 Skill 中挑选最匹配的资产。\n- 预期输出：候选角色或 Skill 列表，每项包含适用场景、证据路径、风险边界和是否需要安装后验证。\n\n```text\n请读取 role_skill_index，根据我的目标任务推荐 3-5 个最相关的角色或 Skill。每个推荐都要说明适用场景、可能输出、风险边界和 evidence_refs。\n```\n\n### 风险预检\n\n- 目标：安装或引入前识别环境、权限、规则冲突和质量风险。\n- 预期输出：环境、权限、依赖、许可、宿主冲突、质量风险和未知项的检查清单。\n\n```text\n请基于 risk_card、boundaries 和 quick_start_candidates，给我一份安装前风险预检清单。不要替我执行命令，只说明我应该检查什么、为什么检查、失败会有什么影响。\n```\n\n### 宿主 AI 开工指令\n\n- 目标：把项目上下文转成一次对话开始前的宿主 AI 指令。\n- 预期输出：一段边界明确、证据引用明确、适合复制给宿主 AI 的开工前指令。\n\n```text\n请基于 lifeos-plugin 的 AI Context Pack，生成一段我可以粘贴给宿主 AI 的开工前指令。这段指令必须遵守 not_runtime=true，不能声称项目已经安装、运行或产生真实结果。\n```\n\n\n## 角色 / Skill 索引\n\n- 共索引 39 个角色 / Skill / 项目文档条目。\n\n- **blind-spot-finder**（skill）：Multi-model council to find your blind spots, local maxima, and self-deceptions 激活提示：当用户任务与“blind-spot-finder”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/blind-spot-finder/SKILL.md`\n- **capture**（skill）：Quick capture a thought, task, or note with auto-routing based on content 激活提示：当用户任务与“capture”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/capture/SKILL.md`\n- **client-brief**（skill）：Full client briefing with projects, phases, completion stats, and recent communications 激活提示：当用户任务与“client-brief”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/client-brief/SKILL.md`\n- **client-health**（skill）：Show health dashboard across all clients with risk indicators 激活提示：当用户任务与“client-health”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/client-health/SKILL.md`\n- **coach-memory**（skill）：View and manage the AI coach's accumulated knowledge about you 激活提示：当用户任务与“coach-memory”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/coach-memory/SKILL.md`\n- **coaching-action-items**（skill）：Review and manage coaching action items across all coaches 激活提示：当用户任务与“coaching-action-items”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/coaching-action-items/SKILL.md`\n- **coaching-overview**（skill）：Dashboard of coaching profiles, recent sessions, and pending action items 激活提示：当用户任务与“coaching-overview”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/coaching-overview/SKILL.md`\n- **coaching-session-review**（skill）：Review a coaching session's summary, key insights, and action items 激活提示：当用户任务与“coaching-session-review”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/coaching-session-review/SKILL.md`\n- **contact-lookup**（skill）：Full contact dossier with profile, AI insights, meetings, messages, and voice memos 激活提示：当用户任务与“contact-lookup”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/contact-lookup/SKILL.md`\n- **context-switch**（skill）：Quickly load context for a client or project for fast mental context switching 激活提示：当用户任务与“context-switch”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/context-switch/SKILL.md`\n- **customer-success-triage**（skill）：Triage client requests and customer-success work using the client workspace, business chats, Fathom and Granola meetings, notes, and open tasks. Use when reviewing customer asks, checking whether work is already tracked, capturing requirement summaries, or deciding what should become a task. 激活提示：当用户任务与“customer-success-triage”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/customer-success-triage/SKILL.md`\n- **cycle-review**（skill）：Review the current cycle/sprint with progress, incomplete items, and rollover options 激活提示：当用户任务与“cycle-review”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/cycle-review/SKILL.md`\n- **daily-plan**（skill）：Plan the day in LifeOS and apply mutations to due dates, top priorities, current-cycle assignments, and the Daily Note 激活提示：当用户任务与“daily-plan”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/daily-plan/SKILL.md`\n- **daily-standup**（skill）：Get daily standup briefing with agenda, tasks due today, and sprint progress 激活提示：当用户任务与“daily-standup”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/daily-standup/SKILL.md`\n- **daily-training-report**（skill）：Comprehensive daily training report - yesterday's results, today's focus, habit compliance, health data, ADHD focus management 激活提示：当用户任务与“daily-training-report”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/daily-training-report/SKILL.md`\n- **decision-framework**（skill）：Structured multi-model deliberation for big life decisions Denver vs Taiwan, what to build, etc. 激活提示：当用户任务与“decision-framework”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/decision-framework/SKILL.md`\n- **end-of-day**（skill）：Run end-of-day wrap-up with completion summary and tomorrow planning 激活提示：当用户任务与“end-of-day”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/end-of-day/SKILL.md`\n- **falkor-graph**（skill）：Use when the user asks for FalkorDB, Cypher graph traversal, graph schema inspection, or agent-owned PPV relationship links over visions, pillars, identities, and projects. 激活提示：当用户任务与“falkor-graph”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/falkor-graph/SKILL.md`\n- **finance-overview**（skill）：Financial overview with net worth summary, account balances, and net worth trend 激活提示：当用户任务与“finance-overview”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/finance-overview/SKILL.md`\n- **finance-spending**（skill）：Spending analysis with daily patterns, income vs spending, and recent transactions 激活提示：当用户任务与“finance-spending”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/finance-spending/SKILL.md`\n- **follow-ups**（skill）：Track follow-ups needed with people and clients 激活提示：当用户任务与“follow-ups”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/follow-ups/SKILL.md`\n- **habit-check**（skill）：Daily habit check-in - review today's habits, mark completions, celebrate streaks, flag missed reps 激活提示：当用户任务与“habit-check”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/habit-check/SKILL.md`\n- **health-check**（skill）：Quick health overview with recent Oura Ring scores, trends, and insights 激活提示：当用户任务与“health-check”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/health-check/SKILL.md`\n- **health-weekly**（skill）：Weekly health review with sleep, activity, readiness trends, workouts, and recovery insights 激活提示：当用户任务与“health-weekly”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/health-weekly/SKILL.md`\n- **inbox-triage**（skill）：Process captured notes and triage into actionable tasks, tags, and links 激活提示：当用户任务与“inbox-triage”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/inbox-triage/SKILL.md`\n- **initiative-review**（skill）：Review yearly initiative progress with stats per category and highlight stalled initiatives 激活提示：当用户任务与“initiative-review”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/initiative-review/SKILL.md`\n- **llm-council**（skill）：Run a multi-model LLM Council deliberation with peer review and chairman synthesis Karpathy's 3-stage process 激活提示：当用户任务与“llm-council”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/llm-council/SKILL.md`\n- **meeting-prep**（skill）：Prepare for a meeting with contact dossier, past meetings, recent messages, and open items 激活提示：当用户任务与“meeting-prep”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/meeting-prep/SKILL.md`\n- **monthly-review**（skill）：Run monthly review with accomplishments, project progress, and next month planning 激活提示：当用户任务与“monthly-review”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/monthly-review/SKILL.md`\n- **overdue**（skill）：Show what's overdue or slipping - tasks, projects, and sprint items 激活提示：当用户任务与“overdue”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/overdue/SKILL.md`\n- **ppv**（skill）：Manage the PPV life design system in LifeOS: vision, identity, pillars, and existing projects 激活提示：当用户任务与“ppv”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/ppv/SKILL.md`\n- **project-status**（skill）：Project status report with phases, task breakdown, blockers, and urgent items 激活提示：当用户任务与“project-status”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/project-status/SKILL.md`\n- **relationship-pulse**（skill）：Check on neglected relationships and suggest reconnection actions 激活提示：当用户任务与“relationship-pulse”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/relationship-pulse/SKILL.md`\n- **screentime-report**（skill）：Screen time analysis with usage patterns, top time-sink apps, social media alerts, and category breakdown 激活提示：当用户任务与“screentime-report”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/screentime-report/SKILL.md`\n- **sprint-plan**（skill）：Plan the current sprint/current cycle and apply mutations to cycle goals, task assignments, priorities, and due dates 激活提示：当用户任务与“sprint-plan”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/sprint-plan/SKILL.md`\n- **voice-notes-crystallize**（skill）：Save a crystallized summary of AI conversation about voice notes - preserve insights, plans, and ideas 激活提示：当用户任务与“voice-notes-crystallize”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/voice-notes-crystallize/SKILL.md`\n- **voice-notes**（skill）：Explore and work with voice notes interactively - review, analyze, and discuss your recorded thoughts 激活提示：当用户任务与“voice-notes”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/voice-notes/SKILL.md`\n- **weekly-plan**（skill）：Plan the week in LifeOS and apply mutations to due dates, current cycle goals, cycle assignments, priorities, and weekly/daily notes 激活提示：当用户任务与“weekly-plan”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/weekly-plan/SKILL.md`\n- **weekly-review**（skill）：Run weekly review with completed work, in-progress items, sprint health, and blockers 激活提示：当用户任务与“weekly-review”描述的流程高度相关时，先用它做安装前体验，再决定是否安装。 证据：`skills/weekly-review/SKILL.md`\n\n## 证据索引\n\n- 共索引 44 条证据。\n\n- **Setting Up Agents with LifeOS**（documentation）：How to give any AI agent access to your LifeOS data and workflows. 证据：`AGENTS.md`\n- **LifeOS Plugin**（documentation）：Universal skills and MCP integration for LifeOS — your personal productivity OS powered by Convex. 证据：`README.md`\n- **Step 1: Gather Context**（skill_instruction）：Use multiple AI models to find what I'm NOT seeing. This is about the unknown unknowns. 证据：`skills/blind-spot-finder/SKILL.md`\n- **Skill**（skill_instruction）：Quick capture a thought, task, or note. $ARGUMENTS contains what to capture. 证据：`skills/capture/SKILL.md`\n- **Skill**（skill_instruction）：Get a full client briefing. $ARGUMENTS should be the client name or ID. 证据：`skills/client-brief/SKILL.md`\n- **Skill**（skill_instruction）：Show health dashboard across all clients. Use the LifeOS MCP tools: 证据：`skills/client-health/SKILL.md`\n- **Skill**（skill_instruction）：Show me the coach's working memory. Use the LifeOS MCP tools: 证据：`skills/coach-memory/SKILL.md`\n- **Skill**（skill_instruction）：Review my coaching action items. Use the LifeOS MCP tools: 证据：`skills/coaching-action-items/SKILL.md`\n- **Skill**（skill_instruction）：Show me a coaching dashboard. Use the LifeOS MCP tools: 证据：`skills/coaching-overview/SKILL.md`\n- **Skill**（skill_instruction）：Review a coaching session in depth. Use the LifeOS MCP tools: 证据：`skills/coaching-session-review/SKILL.md`\n- **Skill**（skill_instruction）：Look up everything about a contact. $ARGUMENTS should be a person's name. 证据：`skills/contact-lookup/SKILL.md`\n- **Skill**（skill_instruction）：Quickly load context for a client or project. $ARGUMENTS should be the client or project name. 证据：`skills/context-switch/SKILL.md`\n- **Skill**（skill_instruction）：Triage customer-success work. $ARGUMENTS should contain the client name or ID, plus an optional focus area. 证据：`skills/customer-success-triage/SKILL.md`\n- **Skill**（skill_instruction）：Review my current cycle/sprint. Use the LifeOS MCP tools: 证据：`skills/cycle-review/SKILL.md`\n- **Skill**（skill_instruction）：Plan my day in LifeOS and apply the resulting changes. This is a mutating workflow. 证据：`skills/daily-plan/SKILL.md`\n- **Skill**（skill_instruction）：Get my daily standup briefing. Use the LifeOS MCP tools to gather: 证据：`skills/daily-standup/SKILL.md`\n- **Skill**（skill_instruction）：Generate a comprehensive daily training report. This is your personal trainer's daily briefing. 证据：`skills/daily-training-report/SKILL.md`\n- **Step 1: Define the Decision**（skill_instruction）：Help me think through a big life decision using structured deliberation and multiple AI perspectives. 证据：`skills/decision-framework/SKILL.md`\n- **Skill**（skill_instruction）：Run my end-of-day wrap-up. Use the LifeOS MCP tools: 证据：`skills/end-of-day/SKILL.md`\n- **Skill**（skill_instruction）：Use the LifeOS FalkorDB sidecar graph. This skill is for graph traversal and agent-owned relationship links, not canonical entity edits. 证据：`skills/falkor-graph/SKILL.md`\n- **Skill**（skill_instruction）：Give me a financial overview. Use the LifeOS MCP tools: 证据：`skills/finance-overview/SKILL.md`\n- **Skill**（skill_instruction）：Analyze my spending patterns. Use the LifeOS MCP tools: 证据：`skills/finance-spending/SKILL.md`\n- **Skill**（skill_instruction）：Track follow-ups needed with people and clients. Use the LifeOS MCP tools: 证据：`skills/follow-ups/SKILL.md`\n- **Skill**（skill_instruction）：Run a daily habit check-in. Use the LifeOS MCP tools to: 证据：`skills/habit-check/SKILL.md`\n- **Skill**（skill_instruction）：Give me a quick health overview. Use the LifeOS MCP tools to gather Oura Ring data: 证据：`skills/health-check/SKILL.md`\n- **Skill**（skill_instruction）：Run a weekly health review. Use the LifeOS MCP tools: 证据：`skills/health-weekly/SKILL.md`\n- **Skill**（skill_instruction）：Process captured notes and triage into actionable items. Use the LifeOS MCP tools: 证据：`skills/inbox-triage/SKILL.md`\n- **Skill**（skill_instruction）：Review my yearly initiative progress. Use the LifeOS MCP tools: 证据：`skills/initiative-review/SKILL.md`\n- **Step 1: Get the Question**（skill_instruction）：Run a full LLM Council deliberation on a question or topic. Multiple AI models answer independently, then anonymously peer-review each other's responses, and finally a chairman synthesizes the best answer. 证据：`skills/llm-council/SKILL.md`\n- **Skill**（skill_instruction）：Prepare for a meeting with someone. $ARGUMENTS should be the person's name. 证据：`skills/meeting-prep/SKILL.md`\n- **Skill**（skill_instruction）：Run my monthly review. Use the LifeOS MCP tools: 证据：`skills/monthly-review/SKILL.md`\n- **Skill**（skill_instruction）：Show what's overdue or slipping. Use the LifeOS MCP tools: 证据：`skills/overdue/SKILL.md`\n- **Skill**（skill_instruction）：Manage my PPV life design system. This is a mutating workflow when the request implies creating, updating, linking, or changing lifecycle status. 证据：`skills/ppv/SKILL.md`\n- **Skill**（skill_instruction）：Get project status. $ARGUMENTS should be a project key like \"ACME\" or project name. 证据：`skills/project-status/SKILL.md`\n- **Skill**（skill_instruction）：Check on neglected relationships. Use the LifeOS MCP tools: 证据：`skills/relationship-pulse/SKILL.md`\n- **Skill**（skill_instruction）：Generate a screen time report. Use the LifeOS MCP tools to gather data: 证据：`skills/screentime-report/SKILL.md`\n- **Skill**（skill_instruction）：Help me plan my sprint/current cycle in LifeOS and apply the resulting changes. This is a mutating workflow. 证据：`skills/sprint-plan/SKILL.md`\n- **Skill**（skill_instruction）：Save a crystallized summary of our conversation about voice notes. Use the LifeOS MCP tools. 证据：`skills/voice-notes-crystallize/SKILL.md`\n- **Skill**（skill_instruction）：Explore and work with my voice notes interactively. Use the LifeOS MCP tools. 证据：`skills/voice-notes/SKILL.md`\n- **Skill**（skill_instruction）：Plan my week in LifeOS and apply the resulting changes. This is a mutating workflow. 证据：`skills/weekly-plan/SKILL.md`\n- **Skill**（skill_instruction）：Run my weekly review. Use the LifeOS MCP tools to gather: 证据：`skills/weekly-review/SKILL.md`\n- **Plugin**（structured_config）：{ \"name\": \"lifeos\", \"description\": \"LifeOS productivity suite - project management, contacts, agendas, PPV life design, SurrealDB graph links, health Oura , finance, and workflow automation via MCP\", \"version\": \"1.2.0\", \"author\": { \"name\": \"starascendin\" }, \"repository\": \"https://github.com/starascendin/lifeos-plugin\", \"keywords\": \"lifeos\", \"productivity\", \"project-management\", \"life-design\", \"graph\", \"surrealdb\", \"mcp\" } 证据：`.claude-plugin/plugin.json`\n- **.Mcp**（structured_config）：{ \"mcpServers\": { \"lifeos\": { \"command\": \"npx\", \"args\": \"@starascendin/lifeos-mcp@latest\", \"--url\", \"${LIFEOS CONVEX URL}\", \"--user-id\", \"${LIFEOS USER ID}\", \"--api-key\", \"${LIFEOS API KEY}\" , \"env\": { \"SURREAL ENDPOINT\": \"${SURREAL ENDPOINT}\", \"SURREAL USER\": \"${SURREAL USER}\", \"SURREAL PASS\": \"${SURREAL PASS}\", \"SURREAL NS\": \"${SURREAL NS}\", \"SURREAL DB\": \"${SURREAL DB}\" } } } } 证据：`.mcp.json`\n- **.Mcp.Json**（source_file）：{ \"mcpServers\": { \"lifeos\": { \"command\": \"npx\", \"args\": \"@starascendin/lifeos-mcp@latest\", \"--url\", \"https://YOUR APP.convex.site\", \"--user-id\", \"YOUR USER ID\", \"--api-key\", \"YOUR API KEY\" , \"env\": { \"SURREAL ENDPOINT\": \"https://YOUR SURREAL ENDPOINT\", \"SURREAL USER\": \"YOUR SURREAL USER\", \"SURREAL PASS\": \"YOUR SURREAL PASS\", \"SURREAL NS\": \"lifeos\", \"SURREAL DB\": \"graph\" } } } } 证据：`.mcp.json.example`\n\n## 宿主 AI 必须遵守的规则\n\n- **把本资产当作开工前上下文，而不是运行环境。**：AI Context Pack 只包含证据化项目理解，不包含目标项目的可执行状态。 证据：`AGENTS.md`, `README.md`, `skills/blind-spot-finder/SKILL.md`\n- **回答用户时区分可预览内容与必须安装后才能验证的内容。**：安装前体验的消费者价值来自降低误装和误判，而不是伪装成真实运行。 证据：`AGENTS.md`, `README.md`, `skills/blind-spot-finder/SKILL.md`\n\n## 用户开工前应该回答的问题\n\n- 你准备在哪个宿主 AI 或本地环境中使用它？\n- 你只是想先体验工作流，还是准备真实安装？\n- 你最在意的是安装成本、输出质量、还是和现有规则的冲突？\n\n## 验收标准\n\n- 所有能力声明都能回指到 evidence_refs 中的文件路径。\n- AI_CONTEXT_PACK.md 没有把预览包装成真实运行。\n- 用户能在 3 分钟内看懂适合谁、能做什么、如何开始和风险边界。\n\n---\n\n## Doramagic Context Augmentation\n\nThe following material strengthens the Repomix/AI Context Pack body. Human Manual is only a reading skeleton; pitfall logs become hard operating constraints for the host AI.\n\n## Human Manual Skeleton\n\nUsage rule: this is only a reading path and salience signal, not factual authority. Concrete facts must still come from repo evidence / Claim Graph.\n\nHard rules for the host AI:\n- Do not treat page titles, order, summaries, or importance as project facts.\n- When explaining the Human Manual skeleton, state that it is only a reading path / salience signal.\n- Capability, installation, compatibility, runtime status, and risk judgments must cite repo evidence, source paths, or Claim Graph.\n\n- **Overview**：importance `high`\n - source_paths: README.md, AGENTS.md\n- **Installation Guide**：importance `high`\n - source_paths: README.md, .mcp.json.example\n- **Skills Overview**：importance `high`\n - source_paths: README.md, AGENTS.md\n- **Daily Workflows**：importance `high`\n - source_paths: skills/daily-standup/SKILL.md, skills/daily-plan/SKILL.md, skills/end-of-day/SKILL.md, skills/capture/SKILL.md\n- **Habits & Accountability**：importance `medium`\n - source_paths: skills/habit-check/SKILL.md, skills/daily-training-report/SKILL.md\n- **Health Integration (Oura Ring)**：importance `medium`\n - source_paths: skills/health-check/SKILL.md, skills/health-weekly/SKILL.md, skills/screentime-report/SKILL.md\n- **Project Management**：importance `high`\n - source_paths: skills/project-status/SKILL.md, skills/sprint-plan/SKILL.md, skills/cycle-review/SKILL.md, skills/initiative-review/SKILL.md\n- **Client Management**：importance `high`\n - source_paths: skills/client-brief/SKILL.md, skills/client-health/SKILL.md, skills/customer-success-triage/SKILL.md, skills/inbox-triage/SKILL.md\n\n## Repo Inspection Evidence\n\n- repo_clone_verified: true\n- repo_inspection_verified: true\n- repo_commit: `a583fdeeeea58b1633c94d8ab55cf78ed8b0a5a1`\n- inspected_files: `README.md`\n\nHard rules for the host AI:\n- Without repo_clone_verified=true, do not claim the source code has been read.\n- Without repo_inspection_verified=true, do not turn README/docs/package observations into facts.\n- Without quick_start_verified=true, do not claim the Quick Start has been successfully run.\n\n## Doramagic Pitfall Constraints\n\nThese rules come from Doramagic discovery, validation, or compilation pitfalls. The host AI must treat them as operating constraints, not general background notes.\n\n### Constraint 1: 可能修改宿主 AI 配置\n\n- Trigger: 项目面向 Claude/Cursor/Codex/Gemini/OpenCode 等宿主，或安装命令涉及用户配置目录。\n- Host AI rule: 列出会写入的配置文件、目录和卸载/回滚步骤。\n- Why it matters: 安装可能改变本机 AI 工具行为，用户需要知道写入位置和回滚方法。\n- Evidence: capability.host_targets | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | host_targets=mcp_host, claude, claude_code\n- Hard boundary: do not present this pitfall as solved, verified, or safe to ignore unless later validation evidence explicitly closes it.\n\n### Constraint 2: 能力判断依赖假设\n\n- Trigger: README/documentation is current enough for a first validation pass.\n- Host AI rule: 将假设转成下游验证清单。\n- Why it matters: 假设不成立时，用户拿不到承诺的能力。\n- Evidence: capability.assumptions | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | README/documentation is current enough for a first validation pass.\n- Hard boundary: do not present this pitfall as solved, verified, or safe to ignore unless later validation evidence explicitly closes it.\n\n### Constraint 3: 维护活跃度未知\n\n- Trigger: 未记录 last_activity_observed。\n- Host AI rule: 补 GitHub 最近 commit、release、issue/PR 响应信号。\n- Why it matters: 新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。\n- Evidence: evidence.maintainer_signals | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | last_activity_observed missing\n- Hard boundary: do not present this pitfall as solved, verified, or safe to ignore unless later validation evidence explicitly closes it.\n\n### Constraint 4: 下游验证发现风险项\n\n- Trigger: no_demo\n- Host AI rule: 进入安全/权限治理复核队列。\n- Why it matters: 下游已经要求复核，不能在页面中弱化。\n- Evidence: downstream_validation.risk_items | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | no_demo; severity=medium\n- Hard boundary: do not present this pitfall as solved, verified, or safe to ignore unless later validation evidence explicitly closes it.\n\n### Constraint 5: 存在评分风险\n\n- Trigger: no_demo\n- Host AI rule: 把风险写入边界卡，并确认是否需要人工复核。\n- Why it matters: 风险会影响是否适合普通用户安装。\n- Evidence: risks.scoring_risks | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | no_demo; severity=medium\n- Hard boundary: do not present this pitfall as solved, verified, or safe to ignore unless later validation evidence explicitly closes it.\n\n### Constraint 6: issue/PR 响应质量未知\n\n- Trigger: issue_or_pr_quality=unknown。\n- Host AI rule: 抽样最近 issue/PR，判断是否长期无人处理。\n- Why it matters: 用户无法判断遇到问题后是否有人维护。\n- Evidence: evidence.maintainer_signals | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | issue_or_pr_quality=unknown\n- Hard boundary: do not present this pitfall as solved, verified, or safe to ignore unless later validation evidence explicitly closes it.\n\n### Constraint 7: 发布节奏不明确\n\n- Trigger: release_recency=unknown。\n- Host AI rule: 确认最近 release/tag 和 README 安装命令是否一致。\n- Why it matters: 安装命令和文档可能落后于代码，用户踩坑概率升高。\n- Evidence: evidence.maintainer_signals | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | release_recency=unknown\n- Hard boundary: do not present this pitfall as solved, verified, or safe to ignore unless later validation evidence explicitly closes it.\n",
"summary": "Context and operating boundaries for host AI agents.",
"title": "AI Context Pack"
},
"boundary_risk_card": {
"asset_id": "boundary_risk_card",
"filename": "BOUNDARY_RISK_CARD.md",
"markdown": "# Boundary & Risk Card\n\nProject: starascendin/lifeos-plugin\n\n## Doramagic Trial Decision\n\nCurrent decision: it can enter pre-publication recommendation checks. First use should still start with least privilege, a temporary directory, and reversible configuration.\n\n## What The User Can Do Now\n\n- Read the Human Manual first to understand the project purpose and main workflows.\n- Use Prompt Preview for pre-install exploration; it validates interaction shape, not real execution.\n- Run official Quick Start commands only inside an isolated environment, not a primary setup.\n\n## Do Not Do Yet\n\n- Do not treat Prompt Preview as a real project execution result.\n- Do not treat metadata-only validation as sandbox installation validation.\n- Do not describe unverified capabilities as supported, working, or safe to install.\n- Do not provide production data, private files, real secrets, or primary host configuration on first trial.\n\n## Pre-Install Checklist\n\n- Host AI match: mcp_host, claude, claude_code\n- Official installation entry status: official entry point found\n- Isolated temporary directory, temporary host, or container validation: required\n- Configuration rollback path: required\n- API keys, network access, file access, or host configuration changes: treat as high risk until confirmed\n- Installation command, actual output, and failure logs: must be recorded\n\n## Current Blockers\n\n- review_required: community_discussion_evidence_below_public_threshold\n\n## Project-Specific Pitfalls\n\n- 可能修改宿主 AI 配置 (medium): 安装可能改变本机 AI 工具行为，用户需要知道写入位置和回滚方法。 Suggested check: 列出会写入的配置文件、目录和卸载/回滚步骤。\n- 能力判断依赖假设 (medium): 假设不成立时，用户拿不到承诺的能力。 Suggested check: 将假设转成下游验证清单。\n- 维护活跃度未知 (medium): 新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。 Suggested check: 补 GitHub 最近 commit、release、issue/PR 响应信号。\n- 下游验证发现风险项 (medium): 下游已经要求复核，不能在页面中弱化。 Suggested check: 进入安全/权限治理复核队列。\n- 存在评分风险 (medium): 风险会影响是否适合普通用户安装。 Suggested check: 把风险写入边界卡，并确认是否需要人工复核。\n\n## Risk And Permission Notes\n\n- no_demo: medium\n\n## Evidence Gaps\n\n- No structured evidence gaps are currently visible.\n",
"summary": "Installation, permission, validation, and pre-recommendation risks.",
"title": "Boundary & Risk Card"
},
"human_manual": {
"asset_id": "human_manual",
"filename": "HUMAN_MANUAL.md",
"markdown": "# https://github.com/starascendin/lifeos-plugin 项目说明书\n\n生成时间：2026-05-18 00:31:52 UTC\n\n## 目录\n\n- [Overview](#overview)\n- [Installation Guide](#installation)\n- [Skills Overview](#skills-overview)\n- [Daily Workflows](#daily-workflows)\n- [Habits & Accountability](#habits-accountability)\n- [Health Integration (Oura Ring)](#health-integration)\n- [Project Management](#project-management)\n- [Client Management](#client-management)\n- [People & Relationships](#people-relationships)\n- [Review Workflows](#review-workflows)\n- [Finance Management](#finance-management)\n- [Coaching System](#coaching-system)\n\n\n\n## Overview\n\n### 相关页面\n\n相关主题：[Installation Guide](#installation), [Skills Overview](#skills-overview)\n\n\nRelevant Source Files
\n\n以下源码文件用于生成本页说明：\n\n- [README.md](https://github.com/starascendin/lifeos-plugin/blob/main/README.md)\n- [AGENTS.md](https://github.com/starascendin/lifeos-plugin/blob/main/AGENTS.md)\n- [skills/daily-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/daily-plan/SKILL.md)\n- [skills/weekly-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/weekly-plan/SKILL.md)\n- [skills/sprint-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/sprint-plan/SKILL.md)\n- [skills/ppv/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/ppv/SKILL.md)\n- [skills/health-weekly/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/health-weekly/SKILL.md)\n- [skills/daily-training-report/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/daily-training-report/SKILL.md)\n- [skills/customer-success-triage/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md)\n- [skills/llm-council/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/llm-council/SKILL.md)\n- [skills/blind-spot-finder/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/blind-spot-finder/SKILL.md)\n \n\n# Overview\n\nLifeOS Plugin is a universal skills and MCP (Model Context Protocol) integration layer for LifeOS—a personal productivity operating system powered by Convex. The plugin extends AI agents (such as Claude Code and OpenCode) with 37 workflow skills, 126 MCP tools, and 28 MCP prompts, enabling them to interact with personal productivity data including tasks, projects, contacts, health metrics, finances, coaching insights, and life design systems.\n\n## Purpose and Scope\n\nThe primary purpose of LifeOS Plugin is to bridge AI agents with LifeOS data, allowing users to leverage AI capabilities for daily planning, project management, client relationship management, health tracking, and personal development through natural language commands.\n\nThe plugin provides:\n\n- **Workflow Automation**: Pre-built skills that execute complete workflows (e.g., daily planning, weekly review, sprint planning)\n- **Direct Data Access**: MCP tools enabling CRUD operations on all LifeOS entities\n- **Multi-Agent Compatibility**: Support for Claude Code, OpenCode, and any MCP-compatible client\n- **Mutating and Read Operations**: Both query and modification capabilities across the productivity stack\n\n资料来源：[README.md:1]()\n\n## Architecture\n\n### System Components\n\n```mermaid\ngraph TD\n A[AI Agent
Claude Code / OpenCode] --> B[LifeOS Plugin Skills]\n A --> C[MCP Client]\n C --> D[lifeos-mcp Server
@starascendin/lifeos-mcp]\n D --> E[LifeOS Convex Backend]\n E --> F[(Convex Database)]\n \n B -->|\"Invokes Skills\"| A\n C -->|\"MCP Protocol
126 Tools, 28 Prompts\"| D\n \n style F fill:#e1f5fe\n style D fill:#fff3e0\n style B fill:#e8f5e9\n```\n\n### Data Flow\n\n```mermaid\nsequenceDiagram\n participant User\n participant Agent as AI Agent\n participant Skills as Plugin Skills\n participant MCP as MCP Server\n participant Convex as LifeOS Backend\n \n User->>Agent: /daily-plan \"Plan my day\"\n Agent->>Skills: Invoke daily-plan skill\n Skills->>MCP: get_planning_context()\n MCP->>Convex: Query tasks, habits, calendar\n Convex-->>MCP: Planning data\n MCP-->>Skills: Context object\n Skills->>Skills: Build day plan\n Skills->>MCP: apply_planning_patch(mode=\"day\")\n MCP->>Convex: Mutate due dates, priorities\n Convex-->>MCP: Confirmation\n MCP-->>Skills: Applied changes\n Skills-->>Agent: Summary report\n Agent-->>User: Today's top 3 + changes\n```\n\n## Installation Methods\n\n### Agent-Specific Setup\n\n| Agent | Method | Command/Steps |\n|-------|--------|---------------|\n| Claude Code | Single command | `claude plugin add github:starascendin/lifeos-plugin` |\n| OpenCode | Copy or symlink | `cp -r skills/ .claude/skills/lifeos/` or symlink |\n| Manual | Copy directory | Copy `skills/` to agent's skills location |\n\n资料来源：[README.md:16-37]()\n\n### Environment Configuration\n\nRequired credentials must be configured via environment variables:\n\n```bash\nexport LIFEOS_CONVEX_URL=https://your-app.convex.site\nexport LIFEOS_USER_ID=your-user-id\nexport LIFEOS_API_KEY=your-api-key\n```\n\n| Variable | Description | Source |\n|----------|-------------|--------|\n| `LIFEOS_CONVEX_URL` | Convex deployment URL (`.convex.site`) | Convex Dashboard |\n| `LIFEOS_USER_ID` | LifeOS user identifier | Convex Dashboard > Users |\n| `LIFEOS_API_KEY` | API authentication key | LifeOS Settings |\n\n资料来源：[README.md:5-8]()\n\n### MCP Server Configuration\n\nFor MCP-compatible clients, configure the server in your MCP settings:\n\n```json\n{\n \"mcpServers\": {\n \"lifeos\": {\n \"command\": \"npx\",\n \"args\": [\n \"@starascendin/lifeos-mcp@latest\",\n \"--url\", \"YOUR_CONVEX_URL\",\n \"--user-id\", \"YOUR_USER_ID\",\n \"--api-key\", \"YOUR_API_KEY\"\n ]\n }\n }\n}\n```\n\n资料来源：[README.md:31-44]()\n\n## Skills Catalog\n\nThe plugin provides 37 workflow skills organized into categories. Each skill is a self-contained workflow that can be invoked via slash commands (e.g., `/daily-plan`).\n\n资料来源：[AGENTS.md:1]()\n\n### Daily Workflows\n\n| Skill | Purpose |\n|-------|---------|\n| `daily-standup` | Morning briefing with agenda, tasks, and sprint progress |\n| `daily-plan` | Plan today with due date, priority, cycle, and Daily Note changes |\n| `end-of-day` | EOD wrap-up with completion summary and tomorrow planning |\n| `capture` | Quick capture of thoughts, tasks, or notes with auto-routing |\n\n### Reviews\n\n| Skill | Purpose |\n|-------|---------|\n| `weekly-review` | Review completed work, in-progress items, and sprint health |\n| `weekly-plan` | Plan the week with current cycle, due date, priority, and note changes |\n| `monthly-review` | Accomplishments, project progress, and next month planning |\n| `cycle-review` | Sprint review with rollover options |\n| `initiative-review` | Yearly initiative progress by category |\n\n### Project & Client Management\n\n| Skill | Purpose |\n|-------|---------|\n| `project-status` | Phase breakdown, task stats, and blockers |\n| `client-brief` | Full client briefing with projects and communications |\n| `client-health` | Health dashboard across all clients |\n| `sprint-plan` | Plan the current cycle and apply task/cycle mutations |\n\n### People & Relationships\n\n| Skill | Purpose |\n|-------|---------|\n| `contact-lookup` | Full contact dossier with AI insights |\n| `meeting-prep` | Prepare for meetings with full context |\n| `follow-ups` | Track follow-ups needed with people and clients |\n| `relationship-pulse` | Check on neglected relationships |\n| `context-switch` | Fast context loading for a client or project |\n\n### Inbox & Tasks\n\n| Skill | Purpose |\n|-------|---------|\n| `inbox-triage` | Process notes into tasks |\n| `overdue` | Overdue and slipping items |\n\n### Voice & Notes\n\n| Skill | Purpose |\n|-------|---------|\n| `voice-notes` | Interactive memo exploration |\n| `voice-notes-crystallize` | Save conversation insights |\n\n### Health & Fitness\n\n| Skill | Purpose |\n|-------|---------|\n| `health-check` | Quick Oura health overview: scores and trends |\n| `health-weekly` | Weekly health review with workouts |\n| `screentime-report` | Screen time analysis and top apps |\n| `habit-check` | Daily habit check-in, streaks, and completions |\n| `daily-training-report` | Daily training report with health + habits |\n\n### Finance\n\n| Skill | Purpose |\n|-------|---------|\n| `finance-overview` | Net worth, accounts, and trends |\n| `finance-spending` | Spending analysis and patterns |\n\n### Coaching & Development\n\n| Skill | Purpose |\n|-------|---------|\n| `coaching-overview` | Coaching profiles, sessions, and action items |\n| `coaching-action-items` | Manage coaching action items |\n| `coaching-session-review` | Review coaching session insights |\n| `coach-memory` | View AI coach's accumulated knowledge |\n\n### Life Design\n\n| Skill | Purpose |\n|-------|---------|\n| `ppv` | Manage PPV vision, identity, pillars, project links, weekly actions, reflections, and adjustments |\n\n### Advanced AI Workflows\n\n| Skill | Purpose |\n|-------|---------|\n| `llm-council` | Multi-model deliberation for complex decisions |\n| `blind-spot-finder` | Multi-model council to find blind spots and self-deceptions |\n| `customer-success-triage` | Triage client requests using workspace, chats, meetings, and tasks |\n\n资料来源：[README.md:15-50](), [AGENTS.md:1-20]()\n\n## MCP Tools (126 Total)\n\nThe MCP server exposes 126 tools providing full CRUD operations across LifeOS entities:\n\n### Data Categories\n\n| Category | Operations | Examples |\n|----------|------------|----------|\n| Projects | CRUD | `get_projects`, `create_project`, `update_project` |\n| Tasks/Issues | CRUD | `get_tasks`, `create_issue`, `update_issue`, `schedule_issue` |\n| Cycles | CRUD | `get_current_cycle`, `update_cycle_goals` |\n| Clients | CRUD | `get_clients`, `create_client`, `update_client` |\n| People/Contacts | CRUD | `get_contacts`, `create_person`, `update_person` |\n| Notes | CRUD | `get_notes`, `create_note`, `update_client_note` |\n| Voice Memos | CRUD | `get_voice_memos`, `create_voice_memo` |\n| Meetings | Read | `get_granola_meeting`, `get_fathom_meeting` |\n| Health (Oura Ring) | Read | `get_health_sleep`, `get_health_activity`, `get_health_readiness`, `get_health_stress` |\n| Finance | Read | `get_finance_net_worth`, `get_finance_transactions` |\n| Habits | CRUD | `get_habits`, `get_habits_for_date` |\n| Coaching | CRUD | `get_coaching_action_items`, `create_coaching_action_item` |\n| PPV Life Design | CRUD | `get_ppv_workspace`, `upsert_ppv_vision`, `create_ppv_pillar` |\n\n资料来源：[AGENTS.md:21-24]()\n\n### Planning Workflow Tools\n\n```mermaid\ngraph LR\n A[get_planning_context] --> B[Build Plan]\n B --> C[apply_planning_patch]\n \n C --> D[\"create_issue\"]\n C --> E[\"schedule_issue\"]\n C --> F[\"update_issue\"]\n C --> G[\"assign_issue_to_current_cycle\"]\n C --> H[\"set_top_priority\"]\n C --> I[\"update_cycle_goals\"]\n C --> J[\"save_daily_note\"]\n C --> K[\"save_weekly_note\"]\n \n style A fill:#bbdefb\n style B fill:#c8e6c9\n style C fill:#ffe0b2\n```\n\nThe `apply_planning_patch` operation supports multiple mutation types depending on the planning mode:\n\n| Mode | Purpose | Common Operations |\n|------|---------|-------------------|\n| `day` | Daily planning | Schedule tasks, set top 3 priorities, update daily note |\n| `week` | Weekly planning | Assign backlog to cycle, update cycle goals, save weekly note |\n| `cycle` | Sprint planning | Assign issues, update cycle goals, schedule near-term work |\n\n资料来源：[skills/daily-plan/SKILL.md:1-35](), [skills/weekly-plan/SKILL.md:1-40](), [skills/sprint-plan/SKILL.md:1-35]()\n\n## MCP Prompts (28 Total)\n\nThe plugin exposes 28 MCP prompts—same workflows as the skills, but callable via MCP protocol. Any MCP-compatible client can invoke these prompts to trigger comprehensive workflow execution without directly invoking a skill file.\n\n资料来源：[AGENTS.md:25-27]()\n\n## Core Workflow Patterns\n\n### Planning Workflow Pattern\n\nMost planning skills follow a consistent three-step pattern:\n\n```mermaid\ngraph TD\n A[Step 1: Gather Context
get_planning_context] --> B[Step 2: Build Plan
Analyze and decide]\n B --> C[Step 3: Apply Changes
apply_planning_patch]\n \n A --> A1[\"daily=true
weekly=true
currentCycle=true
backlog=true
habits=true
dailyFields=true
calendar=true
voiceMemos=true\"]\n \n B --> B1[\"Pick top 3 priorities
Schedule tasks by dueDate
Assign backlog to cycle
Update cycle goals if needed\"]\n \n C --> C1[\"mode=day|week|cycle
dryRun=false\"]\n```\n\n### Mutating vs. Read-Only Workflows\n\nThe plugin distinguishes between:\n\n| Type | Behavior | Examples |\n|------|----------|----------|\n| **Mutating** | Modifies LifeOS data | `daily-plan`, `weekly-plan`, `sprint-plan`, `ppv` |\n| **Read-Only** | Queries and presents data | `health-weekly`, `finance-overview`, `contact-lookup` |\n\nMutating workflows execute without asking for confirmation—the user expects the plugin to modify LifeOS data automatically.\n\n资料来源：[skills/daily-plan/SKILL.md:33-36](), [skills/weekly-plan/SKILL.md:37-40](), [skills/sprint-plan/SKILL.md:33-36]()\n\n## PPV Life Design System\n\nThe PPV (Purpose, Principles, Values) system is a core component for long-term life design. It connects desired future states to daily execution.\n\n### PPV Data Model\n\n```mermaid\ngraph TD\n V[Vision
Future State] --> I[Identity
Who you are]\n V --> P[Pillars
Ongoing Systems]\n V --> PR[Projects
Existing LifeOS Projects]\n \n I --> B[Beliefs]\n I --> BH[Behaviors]\n \n P --> WA[Weekly Actions
Small, Concrete]\n \n PR --> TASKS[Tasks/Issues]\n \n WA --> R[Reflections
Weekly Energy Check]\n R --> AD[Adjustments
Feedback Loop]\n \n AD --> I\n AD --> P\n AD --> PR\n AD --> WA\n```\n\n### PPV Operations\n\n| Operation | Tool | Purpose |\n|-----------|------|---------|\n| View workspace | `get_ppv_workspace` | Get vision, identity, pillars, linked projects, actions |\n| View graph | `get_active_vision_graph` | Unified graph of vision + linked entities |\n| Create vision | `upsert_ppv_vision` | Set vivid, emotional, directional vision |\n| Edit identity | `upsert_ppv_identity` | Update coreIdentities, beliefs, behaviors |\n| Manage pillars | `create_ppv_pillar`, `update_ppv_pillar`, `delete_ppv_pillar` | Ongoing systems |\n| Execute | `create_ppv_weekly_action`, `update_ppv_weekly_action` | Small, identity-aligned actions |\n| Reflect | `create_ppv_reflection` | Capture weekly energy, resistance, alignment |\n| Adjust | `create_ppv_adjustment` | Feed insights back into the system |\n\n资料来源：[skills/ppv/SKILL.md:1-80]()\n\n## Health Integration\n\nThe plugin integrates with Oura Ring data through dedicated health tools:\n\n### Health Data Points\n\n| Category | Tools | Data Retrieved |\n|----------|-------|----------------|\n| Sleep | `get_health_sleep` | Scores, durations, bedtime, breath rate, restless periods |\n| Activity | `get_health_activity` | Steps, active days, calorie burn |\n| Readiness | `get_health_readiness` | Score trends, stress vs recovery |\n| Stress | `get_health_stress` | Stress levels, recovery balance |\n| Workouts | `get_health_workouts` | Workout history with labels |\n| Heart Rate | `get_health_heart_rate` | HR trends |\n| Resilience | `get_health_resilience` | Resilience levels and contributors |\n| VO2 Max | `get_health_vo2_max` | Cardiovascular fitness estimate |\n| Cardio Age | `get_health_cardio_age` | Cardiovascular age |\n| SpO2 | `get_health_spo2` | Blood oxygen, breathing disturbance |\n\n资料来源：[skills/health-weekly/SKILL.md:1-50](), [AGENTS.md:23]()\n\n## Advanced AI Workflows\n\n### LLM Council\n\nThe `llm-council` skill uses multiple AI models to deliberate on complex decisions:\n\n1. **Round 1**: Individual model responses to the question\n2. **Round 2**: Peer review and cross-evaluation\n3. **Chairman Synthesis**: Final authoritative answer\n\nOutput presentation includes individual responses, rankings table, and chairman's synthesis.\n\n资料来源：[skills/llm-council/SKILL.md:1-60]()\n\n### Blind Spot Finder\n\nThe `blind-spot-finder` skill uses multi-model analysis to identify unknown unknowns:\n\n1. Gather context (working memory, habits, health, finances)\n2. Build a comprehensive brief\n3. Run multi-model council for blind spot detection\n4. Analyze patterns and local maxima\n5. User selects one blind spot to work on\n\n资料来源：[skills/blind-spot-finder/SKILL.md:1-60]()\n\n## Daily Training Report\n\nThe `daily-training-report` skill generates a comprehensive daily briefing combining:\n\n- **Yesterday's Results**: Habit scorecard, streaks, health scores\n- **Today's Game Plan**: Top 3 priorities, scheduled habits\n- **Initiative Progress**: Yearly goal tracking\n- **Coaching Action Items**: Pending homework\n\nData sources include habits, health metrics, daily agenda, tasks, initiatives, and coaching items.\n\n资料来源：[skills/daily-training-report/SKILL.md:1-60]()\n\n## Customer Success Triage\n\nThe `customer-success-triage` skill provides structured triage for client work:\n\n1. Fetch client workspace\n2. Review threads, meetings, notes, and open tasks\n3. Drill down when needed (Beeper, Fathom, Granola, notes)\n4. Classify into: New Requirements, Follow-Ups, Risks/Blockers, Already Tracked\n5. Create notes or tasks as appropriate\n\n资料来源：[skills/customer-success-triage/SKILL.md:1-40]()\n\n## Updating the Plugin\n\n```bash\n# Update the plugin repository\ncd /path/to/lifeos-plugin && git pull\n\n# Update the MCP server (auto-updates with npx @latest)\n# Or pin a version in .mcp.json\n# \"@starascendin/lifeos-mcp@0.7.0\"\n```\n\n资料来源：[README.md:56-62]()\n\n## Summary\n\nLifeOS Plugin transforms AI agents into comprehensive personal productivity assistants by providing:\n\n1. **37 workflow skills** covering daily planning, reviews, project management, relationships, health, finance, coaching, and life design\n2. **126 MCP tools** for direct CRUD operations across all LifeOS entities\n3. **28 MCP prompts** for programmatic workflow invocation\n4. **Multi-agent support** via Claude Code plugin system and OpenCode native skills\n5. **Mutating capabilities** that execute changes without confirmation for automated productivity workflows\n\nThe plugin bridges the gap between AI reasoning capabilities and personal productivity data, enabling users to manage complex workflows through natural language commands while maintaining data consistency in their personal operating system.\n\n---\n\n\n\n## Installation Guide\n\n### 相关页面\n\n相关主题：[Overview](#overview)\n\n\nRelevant Source Files
\n\n以下源码文件用于生成本页说明：\n\n- [README.md](https://github.com/starascendin/lifeos-plugin/blob/main/README.md)\n- [AGENTS.md](https://github.com/starascendin/lifeos-plugin/blob/main/AGENTS.md)\n- [skills/daily-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/daily-plan/SKILL.md)\n- [skills/weekly-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/weekly-plan/SKILL.md)\n- [skills/sprint-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/sprint-plan/SKILL.md)\n \n\n# Installation Guide\n\nThis guide covers the complete installation process for integrating LifeOS Plugin with AI agents, enabling universal skills and MCP (Model Context Protocol) access to your personal productivity OS powered by Convex.\n\n## Overview\n\nThe LifeOS Plugin provides 37 workflow skills for project management, contacts, agendas, voice notes, health tracking (Oura Ring), finance, coaching, life direction, and more. The plugin works with multiple AI agent platforms including Claude Code and OpenCode.\n\n| Component | Description |\n|-----------|-------------|\n| **Skills** | 37 workflow automation skills (daily-plan, weekly-plan, health-check, etc.) |\n| **MCP Tools** | 126 full CRUD tools for data operations |\n| **MCP Prompts** | 28 prompts exposed via MCP protocol |\n| **Supported Agents** | Claude Code, OpenCode |\n\n资料来源：[README.md]()\n\n## Prerequisites\n\nBefore installing the LifeOS Plugin, you must obtain three credentials from the LifeOS Convex deployment.\n\n### Required Credentials\n\n| Variable | Description | Where to Find |\n|----------|-------------|---------------|\n| `LIFEOS_CONVEX_URL` | Your Convex deployment URL (format: `https://*.convex.site`) | Convex dashboard |\n| `LIFEOS_USER_ID` | Your LifeOS user ID | Convex dashboard > Users table |\n| `LIFEOS_API_KEY` | API key for authentication | Generated in LifeOS settings |\n\n资料来源：[AGENTS.md]()\n\n### Environment Variable Configuration\n\nSet the environment variables in your shell configuration:\n\n```bash\nexport LIFEOS_CONVEX_URL=https://your-app.convex.site\nexport LIFEOS_USER_ID=your-user-id\nexport LIFEOS_API_KEY=your-api-key\n```\n\nAlternatively, you can pass these credentials directly to the MCP server via command-line arguments or configuration files.\n\n资料来源：[README.md]()\n\n## Installation Methods\n\n### Claude Code Installation\n\nThe simplest installation method for Claude Code users.\n\n```bash\nclaude plugin add github:starascendin/lifeos-plugin\n```\n\nThis single command installs both the skills and MCP server automatically. After installation, ensure the environment variables are set for the MCP server to authenticate.\n\n资料来源：[README.md]()\n\n### OpenCode Installation\n\nOpenCode reads `.claude/skills/` natively. Two options are available:\n\n**Option A: Copy skills directory**\n```bash\ngit clone git@github.com:starascendin/lifeos-plugin.git /tmp/life\ncp -r /tmp/life/skills .claude/skills/lifeos\n```\n\n**Option B: Symlink skills directory**\n```bash\nln -s /path/to/lifeos-plugin/skills .claude/skills/lifeos\n```\n\n资料来源：[README.md]()\n\n### Manual MCP Server Setup\n\nFor custom agent integrations, configure the MCP server manually.\n\n```json\n{\n \"mcpServers\": {\n \"lifeos\": {\n \"command\": \"npx\",\n \"args\": [\n \"@starascendin/lifeos-mcp@latest\",\n \"--url\", \"YOUR_CONVEX_URL\",\n \"--user-id\", \"YOUR_USER_ID\",\n \"--api-key\", \"YOUR_API_KEY\"\n ]\n }\n }\n}\n```\n\n资料来源：[README.md]()\n\n### Version Pinning\n\nTo pin a specific MCP server version, update `.mcp.json`:\n\n```json\n{\n \"mcpServers\": {\n \"lifeos\": {\n \"command\": \"npx\",\n \"args\": [\n \"@starascendin/lifeos-mcp@0.7.0\",\n \"--url\", \"YOUR_CONVEX_URL\",\n \"--user-id\", \"YOUR_USER_ID\",\n \"--api-key\", \"YOUR_API_KEY\"\n ]\n }\n }\n}\n```\n\n资料来源：[README.md]()\n\n## Plugin Architecture\n\n```mermaid\ngraph TD\n A[AI Agent] --> B[LifeOS Plugin]\n B --> C[Skills Directory]\n B --> D[MCP Server]\n D --> E[Convex Backend]\n E --> F[LifeOS Database]\n \n C --> G[37 Workflow Skills]\n G --> H[Mutating Workflows]\n G --> I[Read-only Workflows]\n \n D --> J[126 MCP Tools]\n D --> K[28 MCP Prompts]\n \n J --> L[Projects CRUD]\n J --> M[Tasks CRUD]\n J --> N[Health Data]\n J --> O[Finance Data]\n J --> P[Contacts]\n```\n\n## Available Skills\n\nAfter installation, the following skill categories become available:\n\n### Daily Workflows\n\n| Skill | Purpose |\n|-------|---------|\n| `daily-standup` | Morning briefing with agenda, tasks, and sprint progress |\n| `daily-plan` | Plan today with due dates, priorities, cycle assignments, and Daily Note |\n| `end-of-day` | EOD wrap-up with completion summary and tomorrow planning |\n| `capture` | Quick capture a thought, task, or note with auto-routing |\n\n### Reviews\n\n| Skill | Purpose |\n|-------|---------|\n| `weekly-review` | Completed work, in-progress items, sprint health |\n| `weekly-plan` | Plan the week with cycle, due dates, priorities, and note updates |\n| `monthly-review` | Accomplishments, project progress, next month planning |\n| `cycle-review` | Sprint review with rollover options |\n| `initiative-review` | Yearly initiative progress by category |\n\n### Project & Client Management\n\n| Skill | Purpose |\n|-------|---------|\n| `project-status` | Phase breakdown, task stats, blockers |\n| `client-brief` | Full client briefing with projects and comms |\n| `client-health` | Health dashboard across all clients |\n| `sprint-plan` | Plan current cycle and apply task/cycle mutations |\n\n### People & Relationships\n\n| Skill | Purpose |\n|-------|---------|\n| `contact-lookup` | Full contact dossier with AI insights |\n| `meeting-prep` | Prepare for meetings with full context |\n| `follow-ups` | Track follow-ups needed |\n| `relationship-pulse` | Check on neglected relationships |\n| `context-switch` | Fast context loading for client/project |\n\n### Health & Fitness\n\n| Skill | Purpose |\n|-------|---------|\n| `health-check` | Quick Oura health overview: scores, trends |\n| `health-weekly` | Weekly health review with workouts |\n| `daily-training-report` | Daily training report with health + habits |\n\n### Finance\n\n| Skill | Purpose |\n|-------|---------|\n| `finance-overview` | Net worth, accounts, trends |\n| `finance-spending` | Spending analysis and patterns |\n\n### Personal Development\n\n| Skill | Purpose |\n|-------|---------|\n| `ppv` | PPV life design: vision, identity, pillars, weekly actions |\n| `llm-council` | Multi-model deliberation for complex decisions |\n| `blind-spot-finder` | Multi-model analysis for finding blind spots |\n\n资料来源：[README.md]()\n\n## Skill Invocation Patterns\n\nAfter installation, skills are invoked using slash commands in the agent interface.\n\n### Basic Invocation\n\n```bash\n/daily-plan\n/weekly-plan \"2024-01-15\"\n/health-check\n/finance-overview\n```\n\n### Client-Focused Skills\n\n```bash\n/project-status \"ACME\"\n/client-brief \"Acme Corp\"\n/meeting-prep \"John\"\n/customer-success-triage \"Acme Corp\"\n```\n\n### Planning Workflows\n\nThe planning skills (`daily-plan`, `weekly-plan`, `sprint-plan`) use the same underlying MCP tools:\n\n1. Call `get_planning_context` with relevant include flags\n2. Build the plan based on current cycle, backlog, and calendar\n3. Call `apply_planning_patch` with `dryRun=false` to apply mutations\n\n资料来源：[skills/daily-plan/SKILL.md]()\n资料来源：[skills/weekly-plan/SKILL.md]()\n资料来源：[skills/sprint-plan/SKILL.md]()\n\n## Updating the Plugin\n\n### Update Plugin Repository\n\n```bash\ncd /path/to/lifeos-plugin && git pull\n```\n\n### Update MCP Server\n\nThe MCP server auto-updates when using `@latest`:\n\n```bash\nnpx @starascendin/lifeos-mcp@latest\n```\n\nOr pin to a specific version in `.mcp.json` to prevent unexpected updates.\n\n资料来源：[README.md]()\n\n## MCP Tools Overview\n\nThe installation provides access to 126 MCP tools for full CRUD operations:\n\n| Category | Operations |\n|----------|------------|\n| Projects | Create, read, update, delete projects |\n| Tasks/Issues | Full task lifecycle management |\n| Cycles | Sprint/cycle planning and tracking |\n| Phases | Project phase management |\n| Clients | Client workspace and communications |\n| People/Contacts | Contact management with AI insights |\n| Notes | Note creation and retrieval |\n| Voice Memos | Voice memo recording and analysis |\n| Health | Oura Ring: sleep, activity, readiness, stress, SpO2, heart rate, workouts |\n| Finance | Accounts, net worth, transactions, snapshots, daily spending |\n| Habits | Habit tracking and streak management |\n| Coaching | Session tracking and action items |\n| PPV Life Design | Vision, identity, pillars, reflections, adjustments |\n\n资料来源：[AGENTS.md]()\n\n## Troubleshooting\n\n### Environment Variables Not Recognized\n\nEnsure environment variables are exported in the shell where the agent runs:\n\n```bash\n# Check if variables are set\necho $LIFEOS_CONVEX_URL\necho $LIFEOS_USER_ID\necho $LIFEOS_API_KEY\n```\n\n### MCP Server Connection Issues\n\nVerify the Convex URL format is correct:\n- Must be `https://*.convex.site`\n- User ID must match an entry in the Convex Users table\n- API key must be generated from LifeOS settings\n\n### Skills Not Available\n\nFor Claude Code: Re-run the plugin installation command\nFor OpenCode: Verify the skills directory exists at `.claude/skills/lifeos/`\n\n---\n\n\n\n## Skills Overview\n\n### 相关页面\n\n相关主题：[Daily Workflows](#daily-workflows), [Review Workflows](#review-workflows), [Project Management](#project-management), [Health Integration (Oura Ring)](#health-integration), [Coaching System](#coaching-system)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [README.md](https://github.com/starascendin/lifeos-plugin/blob/main/README.md)\n- [AGENTS.md](https://github.com/starascendin/lifeos-plugin/blob/main/AGENTS.md)\n- [skills/daily-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/daily-plan/SKILL.md)\n- [skills/weekly-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/weekly-plan/SKILL.md)\n- [skills/sprint-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/sprint-plan/SKILL.md)\n- [skills/customer-success-triage/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md)\n- [skills/ppv/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/ppv/SKILL.md)\n \n\n# Skills Overview\n\n## Introduction\n\nSkills are the core building blocks of the LifeOS Plugin, representing 37 pre-defined workflow skills that enable AI agents to interact with LifeOS data and execute productivity operations. Each skill is a structured instruction set that guides an AI agent through a specific workflow using the LifeOS MCP (Model Context Protocol) tools.\n\n资料来源：[README.md:1]()\n\nSkills serve as the human-readable workflow definitions that bridge AI agent reasoning with LifeOS data mutations. They encapsulate domain knowledge about productivity workflows—including planning, reviewing, client management, health tracking, and life design—into reusable, executable units.\n\n## Architecture\n\n```mermaid\ngraph TD\n A[AI Agent] -->|Invokes| B[Skill /slash command]\n B -->|Loads| C[SKILL.md Definition]\n C -->|Directs| D[MCP Tools]\n D -->|CRUD Operations| E[LifeOS Convex Backend]\n E -->|Returns Data| D\n D -->|Formats Response| F[User-Facing Report]\n \n G[Alternative: MCP Protocol] -->|28 Prompts| H[Direct MCP Invocation]\n H -->|Same Tools| E\n```\n\nThe plugin provides two complementary interfaces:\n\n| Interface Type | Count | Description |\n|----------------|-------|-------------|\n| Skills | 37 | Human-readable workflow definitions for slash command invocation |\n| MCP Prompts | 28 | Same workflows exposed via MCP protocol for programmatic clients |\n| MCP Tools | 126 | Full CRUD operations across all LifeOS domains |\n\n资料来源：[AGENTS.md:1]()\n\n## Skill Categories\n\nSkills are organized into functional categories that map to different aspects of personal and professional productivity.\n\n### Daily Workflows\n\nCore daily planning and reflection skills that drive day-to-day execution.\n\n| Skill | Command | Purpose |\n|-------|---------|---------|\n| daily-standup | `/daily-standup` | Morning briefing with agenda, tasks, and sprint progress |\n| daily-plan | `/daily-plan` | Plan today with due dates, priorities, cycle assignments, and Daily Note updates |\n| end-of-day | `/end-of-day` | EOD wrap-up with completion summary and tomorrow planning |\n| capture | `/capture \"thought\"` | Quick capture of thoughts, tasks, or notes with auto-routing |\n\n资料来源：[README.md:42-45]()\n\n### Reviews\n\nPeriodic reflection and planning skills for maintaining strategic alignment.\n\n| Skill | Command | Purpose |\n|-------|---------|---------|\n| weekly-review | `/weekly-review` | Completed work, in-progress items, sprint health |\n| weekly-plan | `/weekly-plan` | Plan the week with current cycle, due dates, priorities, and note changes |\n| monthly-review | `/monthly-review` | Accomplishments, project progress, next month planning |\n| cycle-review | `/cycle-review` | Sprint review with rollover options |\n| initiative-review | `/initiative-review 2026` | Yearly initiative progress by category |\n\n资料来源：[README.md:46-51]()\n\n### Project & Client Management\n\nSkills for managing client relationships and project execution.\n\n| Skill | Command | Purpose |\n|-------|---------|---------|\n| project-status | `/project-status ACME` | Phase breakdown, task stats, blockers |\n| client-brief | `/client-brief \"Acme Corp\"` | Full client briefing with projects and comms |\n| client-health | `/client-health` | Health dashboard across all clients |\n| sprint-plan | `/sprint-plan` | Plan current cycle with goals, backlog pull, due dates, priorities |\n| customer-success-triage | `/customer-success-triage \"Acme Corp\"` | Triage requests using chats, meetings, notes, and open work |\n\n资料来源：[README.md:52-57]()\n\n### People & Relationships\n\nSkills for managing contacts, meetings, and relationship health.\n\n| Skill | Command | Purpose |\n|-------|---------|---------|\n| contact-lookup | `/contact-lookup \"John\"` | Full contact dossier with AI insights |\n| meeting-prep | `/meeting-prep \"John\"` | Prepare for meetings with full context |\n| follow-ups | `/follow-ups` | Track follow-ups needed with people and clients |\n| relationship-pulse | `/relationship-pulse` | Check on neglected relationships |\n| context-switch | `/context-switch \"Acme\"` | Fast context loading for a client or project |\n\n资料来源：[README.md:58-63]()\n\n### Health & Fitness\n\nSkills integrating with Oura Ring data for health monitoring.\n\n| Skill | Command | Purpose |\n|-------|---------|---------|\n| health-check | `/health-check` | Quick Oura health overview: scores, trends |\n| health-weekly | `/health-weekly` | Weekly health review with workouts |\n| daily-training-report | `/daily-training-report` | Daily training report with health + habits |\n| habit-check | `/habit-check` | Daily habit check-in, streaks, completions |\n| screentime-report | `/screentime-report` | Screen time analysis and top apps |\n\n资料来源：[AGENTS.md:1]()\n\n### Finance\n\nSkills for financial tracking and analysis.\n\n| Skill | Command | Purpose |\n|-------|---------|---------|\n| finance-overview | `/finance-overview` | Net worth, accounts, trends |\n| finance-spending | `/finance-spending` | Spending analysis and patterns |\n\n### Coaching & Personal Development\n\nSkills for coaching integration and personal growth tracking.\n\n| Skill | Command | Purpose |\n|-------|---------|---------|\n| coaching-overview | `/coaching-overview` | Coaching profiles, sessions, action items |\n| coaching-action-items | `/coaching-action-items` | Manage coaching action items |\n| coaching-session-review | `/coaching-session-review` | Review coaching session insights |\n| coach-memory | `/coach-memory` | View AI coach's accumulated knowledge |\n| blind-spot-finder | `/blind-spot-finder` | Multi-model council to find blind spots |\n| decision-framework | `/decision-framework` | Structured decision-making with experiments |\n| llm-council | `/llm-council` | Multi-model deliberation for complex decisions |\n\n### PPV Life Design\n\nSkills for the Purpose, Priority, Vision (PPV) life design system.\n\n| Skill | Command | Purpose |\n|-------|---------|---------|\n| ppv | `/ppv` | Manage vision, identity, pillars, projects, weekly actions, reflections, adjustments |\n\n资料来源：[skills/ppv/SKILL.md:1]()\n\n## Skill Structure\n\nEach skill follows a standardized structure defined in `SKILL.md` files.\n\n### Anatomy of a SKILL.md File\n\n```yaml\n---\nname: skill-name\ndescription: One-line description of what the skill does\n---\n\n# Detailed instructions follow\n```\n\n### Standard Execution Pattern\n\n```mermaid\nsequenceDiagram\n participant U as User\n participant A as AI Agent\n participant M as MCP Tools\n participant L as LifeOS\n \n U->>A: Invoke skill /slash command\n A->>M: Call get_* context tool(s)\n M->>L: Query data\n L->>M: Return context\n M->>A: Context data\n A->>A: Analyze & plan\n A->>M: Call apply_* or update_* mutations\n M->>L: Execute changes\n L->>M: Confirmation\n M->>A: Results\n A->>U: Report summary\n```\n\n### Mutating vs. Read-Only Skills\n\nSkills are classified by their effect on LifeOS data:\n\n| Type | Characteristics | Examples |\n|------|-----------------|----------|\n| **Mutating** | Creates, updates, or deletes data | daily-plan, weekly-plan, sprint-plan, ppv |\n| **Read-Only** | Only queries and reports | health-check, finance-overview, contact-lookup |\n\n资料来源：[skills/daily-plan/SKILL.md:1]()\n\n## MCP Tool Integration\n\nSkills leverage the 126 MCP tools for data operations. The tools are organized by domain:\n\n### Planning Tools\n\nUsed by daily-plan, weekly-plan, sprint-plan, and similar skills.\n\n| Tool | Purpose |\n|------|---------|\n| `get_planning_context` | Retrieve comprehensive planning context including daily, weekly, current cycle, backlog, habits, and calendar |\n| `apply_planning_patch` | Apply batch mutations (mode: \"day\", \"week\", or \"cycle\") |\n| `create_issue` | Create new tasks |\n| `schedule_issue` | Set due dates and schedules |\n| `update_issue` | Modify task properties |\n| `assign_issue_to_current_cycle` | Add work to active cycle |\n| `set_top_priority` | Set today's top 3 priorities |\n| `update_cycle_goals` | Modify current cycle objectives |\n\n资料来源：[skills/daily-plan/SKILL.md:5-15]()\n\n### Planning Patch Operations\n\nThe `apply_planning_patch` tool supports multiple operation types:\n\n```json\n{\n \"mode\": \"day\" | \"week\" | \"cycle\",\n \"dryRun\": false,\n \"operations\": [\n { \"type\": \"create_issue\", \"data\": {...} },\n { \"type\": \"schedule_issue\", \"issueId\": \"...\", \"dueDate\": \"...\" },\n { \"type\": \"update_issue\", \"issueId\": \"...\", \"changes\": {...} },\n { \"type\": \"assign_issue_to_current_cycle\", \"issueId\": \"...\" },\n { \"type\": \"set_top_priority\", \"issueIds\": [...] },\n { \"type\": \"update_cycle_goals\", \"goals\": \"...\" },\n { \"type\": \"save_daily_note\", \"content\": \"...\" },\n { \"type\": \"save_weekly_note\", \"content\": \"...\" },\n { \"type\": \"add_issue_comment\", \"issueId\": \"...\", \"comment\": \"...\" }\n ]\n}\n```\n\n### Domain-Specific Tool Categories\n\n| Domain | Tool Count | Operations |\n|--------|------------|------------|\n| Projects | 20+ | CRUD, status, phases, statistics |\n| Issues/Tasks | 30+ | CRUD, assignment, scheduling, priorities |\n| Cycles | 10+ | CRUD, goals, planning |\n| Clients | 15+ | Workspace, health, notes |\n| People/Contacts | 10+ | Lookup, context graphs |\n| Health (Oura) | 30+ | Sleep, activity, readiness, stress, workouts, VO2 max |\n| Finance | 15+ | Accounts, net worth, transactions, spending |\n| Notes & Memos | 20+ | Voice memos, AI summaries, Beeper/Granola integration |\n| Coaching | 10+ | Action items, memories, PPV management |\n\n资料来源：[AGENTS.md:1]()\n\n## Installation & Setup\n\n### Claude Code\n\n```bash\nclaude plugin add github:starascendin/lifeos-plugin\n```\n\n资料来源：[README.md:10]()\n\n### OpenCode\n\n```bash\n# Option A: Clone and copy\ngit clone git@github.com:starascendin/lifeos-plugin.git /tmp/life\n\n# Option B: Symlink\nln -s /path/to/lifeos-plugin/skills .claude/skills/lifeos\n```\n\n资料来源：[AGENTS.md:1]()\n\n### MCP Server Configuration\n\nConfigure the MCP server in your agent's settings:\n\n```json\n{\n \"mcpServers\": {\n \"lifeos\": {\n \"command\": \"npx\",\n \"args\": [\n \"@starascendin/lifeos-mcp@latest\",\n \"--url\", \"YOUR_CONVEX_URL\",\n \"--user-id\", \"YOUR_USER_ID\",\n \"--api-key\", \"YOUR_API_KEY\"\n ]\n }\n }\n}\n```\n\n### Environment Variables\n\n| Variable | Description |\n|----------|-------------|\n| `LIFEOS_CONVEX_URL` | Convex deployment URL (`.convex.site`) |\n| `LIFEOS_USER_ID` | LifeOS user ID from Convex dashboard |\n| `LIFEOS_API_KEY` | API key for authentication |\n\n资料来源：[README.md:30-39]()\n\n## Example Skill: daily-plan\n\nThe `daily-plan` skill demonstrates the typical skill execution flow:\n\n```mermaid\ngraph TD\n A[Invoke /daily-plan] --> B[get_planning_context]\n B --> C{Include Options}\n C -->|daily=true| D[Today's tasks & agenda]\n C -->|weekly=true| E[This week's context]\n C -->|currentCycle=true| F[Active cycle data]\n C -->|backlog=true| G[Available backlog]\n C -->|habits=true| H[Habit data]\n C -->|dailyFields=true| I[Daily fields]\n C -->|calendar=true| J[Calendar events]\n C -->|voiceMemos=true| K[Recent memos]\n \n D --> L[Build Day Plan]\n E --> L\n F --> L\n G --> L\n H --> L\n I --> L\n J --> L\n K --> L\n \n L --> M[Select Top 3 Priorities]\n L --> N[Schedule Tasks by dueDate]\n L --> O[Pull Backlog into Cycle]\n L --> P[Update Cycle Goals if Needed]\n P --> Q[apply_planning_patch mode=day]\n M --> Q\n N --> Q\n O --> Q\n \n Q --> R[Mutations Applied]\n R --> S[Report: Top 3, Changes, Notes]\n```\n\n资料来源：[skills/daily-plan/SKILL.md:1]()\n\n## Example Skill: customer-success-triage\n\nThe `customer-success-triage` skill shows a domain-specific workflow:\n\n```mermaid\ngraph TD\n A[Invoke /customer-success-triage \"Acme Corp\"] --> B[get_client_success_workspace]\n B --> C{Workspace Contents}\n C --> D[recentThreads]\n C --> E[recentMeetings]\n C --> F[notes]\n C --> G[openTasks]\n C --> H[projects]\n \n D --> I[Drill Down if Needed]\n E --> I\n F --> I\n G --> I\n H --> I\n \n I --> J[get_beeper_thread_messages]\n I --> K[get_fathom_meeting]\n I --> L[get_granola_meeting]\n I --> M[get_client_notes]\n \n J --> N{Classify Findings}\n K --> N\n L --> N\n M --> N\n \n N --> O[New Requirements]\n N --> P[Follow-Ups]\n N --> Q[Risks / Blockers]\n N --> R[Already Tracked]\n \n O --> S[create_client_note]\n P --> S\n Q --> S\n R --> S\n \n S --> T[Report Classification]\n```\n\n资料来源：[skills/customer-success-triage/SKILL.md:1]()\n\n## PPV Life Design System\n\nThe PPV (Purpose, Priority, Vision) skill implements a comprehensive life design system:\n\n### Data Model\n\n```mermaid\ngraph TD\n A[Vision] --> B[Identity]\n A --> C[Pillars]\n C --> D[Projects]\n C --> E[Weekly Actions]\n E --> F[Reflections]\n F --> G[Adjustments]\n G --> B\n G --> C\n G --> D\n G --> E\n```\n\n### Vision Operations\n\n- `get_ppv_workspace` — Retrieve all PPV data plus available LifeOS projects\n- `get_active_vision_graph` — Unified graph of vision with linked projects, issues, and memos\n- `upsert_ppv_vision` — Create or update vision (vivid, emotional, directional)\n\n### Identity Operations\n\n- `upsert_ppv_identity` — Manage core identities, beliefs, and behaviors\n\n### Pillar Operations\n\n- `create_ppv_pillar`, `update_ppv_pillar`, `delete_ppv_pillar` — Manage ongoing systems\n\n### Execution Operations\n\n- `create_ppv_weekly_action`, `update_ppv_weekly_action`, `delete_ppv_weekly_action` — Weekly concrete actions\n\n### Learning Loop Operations\n\n- `create_ppv_reflection` — Capture weekly energy, resistance, alignment, momentum\n- `create_ppv_adjustment` — Update identity, pillars, projects, or actions based on reflection\n\n资料来源：[skills/ppv/SKILL.md:1]()\n\n## Updating\n\n```bash\n# Update the plugin repo\ncd /path/to/lifeos-plugin && git pull\n\n# Update the MCP server (auto-updates with npx @latest)\n# Or pin a version in .mcp.json: \"@starascendin/lifeos-mcp@0.7.0\"\n```\n\n资料来源：[README.md:88-94]()\n\n## Best Practices\n\n1. **Mutating Skills Don't Ask for Confirmation** — Skills like `daily-plan`, `weekly-plan`, and `sprint-plan` are designed to execute immediately when invoked.\n\n2. **Use Appropriate Planning Context** — Always include the relevant context flags when calling `get_planning_context`:\n - Daily planning: `daily=true`, `currentCycle=true`, `habits=true`\n - Weekly planning: `weekly=true`, `daily=true`, `currentCycle=true`, `backlog=true`\n - Cycle planning: `currentCycle=true`, `backlog=true`, `weekly=true`, `daily=true`\n\n3. **Avoid Duplicates** — When triaging or capturing, prefer updating existing notes/tasks over creating new ones.\n\n4. **Link, Don't Duplicate** — PPV pillars should link to existing LifeOS projects via `projectIds` rather than creating parallel systems.\n\n5. **Small, Concrete Weekly Actions** — PPV weekly actions should be identity-aligned and linkable to pillars or projects.\n\n6. **One Useful Mutation** — Keep PPV changes focused; prefer one useful mutation over comprehensive restructuring.\n\n资料来源：[skills/ppv/SKILL.md:10](), [skills/daily-plan/SKILL.md:24]()\n\n## Summary\n\nSkills are the primary interface through which AI agents interact with LifeOS. They provide:\n\n- **37 pre-defined workflows** covering daily planning, reviews, client management, health, finance, coaching, and life design\n- **Standardized structure** using SKILL.md files with clear execution patterns\n- **MCP tool integration** leveraging 126 CRUD operations across all LifeOS domains\n- **Two invocation methods** — slash commands for natural interaction and MCP prompts for programmatic access\n- **Mutating and read-only variants** — Some skills only query data, others apply changes directly\n\nThe skills system enables AI agents to act as knowledgeable productivity assistants, executing complex multi-step workflows while maintaining consistency and best practices.\n\n---\n\n\n\n## Daily Workflows\n\n### 相关页面\n\n相关主题：[Review Workflows](#review-workflows), [Habits & Accountability](#habits-accountability), [Project Management](#project-management)\n\n\nRelevant Source Files
\n\n以下源码文件用于生成本页说明：\n\n- [skills/daily-standup/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/daily-standup/SKILL.md)\n- [skills/daily-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/daily-plan/SKILL.md)\n- [skills/end-of-day/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/end-of-day/SKILL.md)\n- [skills/capture/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/capture/SKILL.md)\n- [README.md](https://github.com/starascendin/lifeos-plugin/blob/main/README.md)\n \n\n# Daily Workflows\n\n## Overview\n\nDaily Workflows in LifeOS provide a structured, AI-powered approach to managing day-to-day productivity. These four complementary skills form a complete daily rhythm: from morning preparation through execution to end-of-day reflection.\n\nThe workflows are designed to be **mutating** operations that directly modify LifeOS data through the MCP (Model Context Protocol) integration with Convex. They require no user confirmation once invoked—the system applies changes automatically based on AI-generated plans.\n\n| Workflow | Purpose | Type |\n|----------|---------|------|\n| `daily-standup` | Morning briefing with agenda, tasks, and sprint progress | Read-only |\n| `daily-plan` | Plan the day and apply mutations to due dates, priorities, cycles, and notes | Mutating |\n| `end-of-day` | EOD wrap-up with completion summary and tomorrow planning | Mutating |\n| `capture` | Quick capture of thoughts, tasks, or notes with auto-routing | Mutating |\n\n资料来源：[README.md](https://github.com/starascendin/lifeos-plugin/blob/main/README.md)\n\n## Architecture\n\n### Integration with LifeOS MCP\n\nDaily Workflows leverage the LifeOS MCP server (`@starascendin/lifeos-mcp`) which exposes 126 tools for full CRUD operations across the LifeOS data model. All workflows communicate exclusively through this MCP interface.\n\n```mermaid\ngraph TD\n A[User/Agent] -->|Invoke Skill| B[Daily Workflow Skill]\n B -->|MCP Tool Calls| C[LifeOS MCP Server]\n C -->|HTTP/WebSocket| D[Convex Backend]\n D -->|Real-time Sync| E[LifeOS Data Store]\n \n F[Oura Ring] -->|Health Data| D\n G[Calendar] -->|Schedule Data| D\n H[Voice Memos] -->|Audio Data| D\n```\n\n资料来源：[AGENTS.md](https://github.com/starascendin/lifeos-plugin/blob/main/AGENTS.md)\n\n### Workflow Data Flow\n\n```mermaid\ngraph LR\n A[daily-standup] -->|Read Context| B[get_daily_agenda]\n A -->|Read Tasks| C[get_todays_tasks]\n A -->|Read Sprint| D[get_current_cycle]\n \n E[daily-plan] -->|Read Context| F[get_planning_context]\n E -->|Write Changes| G[apply_planning_patch]\n \n H[end-of-day] -->|Write Summary| I[save_daily_note]\n H -->|Plan Tomorrow| J[schedule_issue]\n \n K[capture] -->|Quick Create| L[create_issue]\n K -->|Route| M[assign_issue_to_current_cycle]\n```\n\n## Daily Standup\n\n**Skill File:** `skills/daily-standup/SKILL.md`\n\n### Purpose\n\nThe `daily-standup` workflow provides a concise morning briefing covering today's agenda, tasks due, and sprint progress. It is a **read-only** operation that does not modify any data.\n\n### MCP Tools Used\n\n| Tool | Purpose |\n|------|---------|\n| `get_daily_agenda` | Today's tasks, calendar events, top priorities |\n| `get_todays_tasks` | Complete task list for today |\n| `get_overdue_tasks` | Open tasks that are past their due date |\n| `get_current_cycle` | Sprint progress and statistics |\n\n资料来源：[skills/daily-standup/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/daily-standup/SKILL.md)\n\n### Output Format\n\nThe workflow synthesizes data into a standup-style briefing:\n\n- **Today's Focus**: Top 3 priorities\n- **Tasks Due**: Tasks due today with priority levels\n- **Overdue**: Late tasks requiring immediate triage\n- **Sprint Progress**: Cycle completion percentage and key statistics\n- **Calendar**: Scheduled meetings and events\n\n### Date Parameter\n\nWhen `$ARGUMENTS` contains a date, the workflow uses that date instead of the current date for historical or future-day standups.\n\n## Daily Plan\n\n**Skill File:** `skills/daily-plan/SKILL.md`\n\n### Purpose\n\nThe `daily-plan` workflow plans the day and applies mutations to LifeOS. This is a **mutating workflow** that directly modifies due dates, priorities, cycle assignments, and Daily Notes.\n\n### Execution Steps\n\n```mermaid\ngraph TD\n 1[Call get_planning_context] --> 2[Build Day Plan]\n 2 --> 3[Pick Top 3 Priorities]\n 2 --> 4[Schedule Tasks by dueDate]\n 2 --> 5[Pull Backlog into Cycle]\n 2 --> 6[Update Cycle Goals if Needed]\n 3 --> 7[Call apply_planning_patch]\n 4 --> 7\n 5 --> 7\n 6 --> 7\n 7 --> 8[Report Changes]\n```\n\n资料来源：[skills/daily-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/daily-plan/SKILL.md)\n\n### Planning Context Parameters\n\nWhen calling `get_planning_context`, the workflow includes:\n\n| Parameter | Value | Purpose |\n|-----------|-------|---------|\n| `date` | From `$ARGUMENTS` or today | Target planning date |\n| `include.daily` | `true` | Daily context |\n| `include.weekly` | `true` | Weekly overview |\n| `include.currentCycle` | `true` | Sprint/cycle data |\n| `include.backlog` | `true` | Available backlog items |\n| `include.habits` | `true` | Habit tracking |\n| `include.dailyFields` | `true` | Daily field configurations |\n| `include.calendar` | `true` | Calendar events |\n| `include.voiceMemos` | `true` | Recent voice memos |\n\n### Available Mutations\n\n| Operation | Use Case |\n|-----------|----------|\n| `create_issue` | New tasks discovered during planning |\n| `schedule_issue` | Set due dates for scheduled work |\n| `update_issue` | Modify status, priority, estimate, title |\n| `assign_issue_to_current_cycle` | Pull backlog into active cycle |\n| `set_top_priority` | Designate today's top 3 |\n| `update_cycle_goals` | Adjust cycle focus when needed |\n| `save_daily_note` | Write readable plan to Agenda Daily Note |\n| `add_issue_comment` | Document planning rationale on tasks |\n\n### Post-Execution Report\n\nAfter applying changes, the workflow reports:\n- Today's top 3 priorities\n- Tasks created, scheduled, or reassigned\n- Current cycle modifications\n- Daily Note content saved\n\n## End of Day\n\n**Skill File:** `skills/end-of-day/SKILL.md`\n\n### Purpose\n\nThe `end-of-day` workflow provides EOD wrap-up with completion summary and tomorrow planning. This completes the daily productivity loop by reviewing accomplishments and preparing for the next day.\n\n### Core Functions\n\n1. **Completion Review**: Summarize what was accomplished today\n2. **Tomorrow Planning**: Schedule and prioritize work for the next day\n3. **Daily Note Updates**: Save EOD reflections and plans\n4. **Cycle Sync**: Ensure cycle progress is accurately tracked\n\n资料来源：[skills/end-of-day/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/end-of-day/SKILL.md)\n\n## Capture\n\n**Skill File:** `skills/capture/SKILL.md`\n\n### Purpose\n\nThe `capture` workflow enables quick capture of thoughts, tasks, or notes with automatic routing. It is designed for rapid input during the day when users encounter items that need to be tracked.\n\n### Auto-Routing Logic\n\nThe capture workflow uses AI to determine:\n- Whether the capture is a task, note, or reference\n- Appropriate project/cycle assignment\n- Priority level based on content\n- Whether it belongs in the current cycle or backlog\n\n### Available Operations\n\n| Operation | Purpose |\n|-----------|---------|\n| `create_issue` | Convert capture to tracked task |\n| `assign_issue_to_current_cycle` | Route to active sprint |\n| `create_note` | Save as reference note |\n| `add_issue_comment` | Attach to existing task |\n\n资料来源：[skills/capture/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/capture/SKILL.md)\n\n## MCP Tools Reference\n\nAll Daily Workflows depend on these core MCP tools from the 126 available:\n\n### Planning Context\n\n| Tool | Returns |\n|------|---------|\n| `get_planning_context` | Unified context for day/week/cycle planning |\n| `get_daily_agenda` | Today's complete agenda |\n| `get_todays_tasks` | Task list filtered for today |\n| `get_current_cycle` | Active sprint/cycle details |\n\n### Mutations\n\n| Tool | Parameters |\n|------|------------|\n| `apply_planning_patch` | `mode`: \"day\" \\| \"week\" \\| \"cycle\", `dryRun`: boolean |\n| `create_issue` | `title`, `projectId`, `priority`, `dueDate`, `estimate` |\n| `schedule_issue` | `issueId`, `dueDate` |\n| `update_issue` | `issueId`, fields to update |\n| `assign_issue_to_current_cycle` | `issueId` |\n| `set_top_priority` | Array of issue IDs |\n| `save_daily_note` | `date`, `content` |\n\n资料来源：[AGENTS.md](https://github.com/starascendin/lifeos-plugin/blob/main/AGENTS.md)\n\n## Configuration\n\n### Environment Variables\n\n```bash\nexport LIFEOS_CONVEX_URL=https://your-app.convex.site\nexport LIFEOS_USER_ID=your-user-id\nexport LIFEOS_API_KEY=your-api-key\n```\n\n### MCP Server Configuration\n\n```json\n{\n \"mcpServers\": {\n \"lifeos\": {\n \"command\": \"npx\",\n \"args\": [\n \"@starascendin/lifeos-mcp@latest\",\n \"--url\", \"YOUR_CONVEX_URL\",\n \"--user-id\", \"YOUR_USER_ID\",\n \"--api-key\", \"YOUR_API_KEY\"\n ]\n }\n }\n}\n```\n\n资料来源：[README.md](https://github.com/starascendin/lifeos-plugin/blob/main/README.md)\n\n## Daily Rhythm Summary\n\n```mermaid\ngraph LR\n subgraph Morning\n A[daily-standup] --> B[daily-plan]\n end\n \n subgraph Day\n C[Execute Tasks]\n D[capture] -->|Ad-hoc| C\n end\n \n subgraph Evening\n E[end-of-day]\n end\n \n B --> C\n C --> E\n E -->|Tomorrow| B\n```\n\n| Phase | Workflow | Action |\n|-------|----------|--------|\n| Morning (start) | `daily-standup` | Read context, understand the day |\n| Morning (plan) | `daily-plan` | Mutate tasks, set priorities |\n| Throughout day | `capture` | Quick input, auto-routing |\n| End of day | `end-of-day` | Review, plan tomorrow |\n\n## Skill Invocation\n\n### Claude Code\n\n```bash\nclaude plugin add github:starascendin/lifeos-plugin\n\n# Then invoke:\n/daily-standup\n/daily-plan\n/end-of-day\n/capture\n```\n\n### OpenCode\n\nSkills are read from `.claude/skills/` directory. Symlink or copy:\n\n```bash\nln -s /path/to/lifeos-plugin/skills .claude/skills/lifeos\n\n---\n\n\n\n## Habits & Accountability\n\n### 相关页面\n\n相关主题：[Daily Workflows](#daily-workflows), [Health Integration (Oura Ring)](#health-integration), [Coaching System](#coaching-system)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [skills/habit-check/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/habit-check/SKILL.md)\n- [skills/daily-training-report/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/daily-training-report/SKILL.md)\n \n\n# Habits & Accountability\n\n## Overview\n\nThe **Habits & Accountability** system in LifeOS is a core productivity feature that enables users to track daily habits, maintain streaks, and stay accountable to their personal commitments. This system integrates with the broader LifeOS ecosystem, connecting habit data to health metrics, coaching insights, and daily planning workflows.\n\nThe habit system serves three primary purposes:\n\n1. **Tracking** — Recording habit completions on a daily basis\n2. **Streaks** — Motivating consistent behavior through streak counters\n3. **Accountability** — Providing direct, actionable feedback when habits are missed or at risk\n\n资料来源：[skills/habit-check/SKILL.md:1-3]()\n\n## Architecture\n\nThe Habits & Accountability system consists of three interconnected layers:\n\n```mermaid\ngraph TD\n A[User Actions] --> B[Habit Check-in]\n B --> C[Streak Calculator]\n C --> D{Streak Status}\n D -->|3+ days| E[Streak Alert]\n D -->|Broken| F[Streak Broken Alert]\n D -->|Safe| G[Normal Tracking]\n \n H[get_habits] --> I[Habit Dashboard]\n J[get_habits_for_date] --> I\n K[check_in_habit] --> B\n \n I --> L[Daily Training Report]\n I --> M[Weekly Planning]\n I --> N[Blind Spot Finder]\n \n style E fill:#ff6b6b\n style F fill:#ee5a24\n```\n\n### Core Components\n\n| Component | Purpose | Source File |\n|-----------|---------|-------------|\n| Habit Check-in | Mark habits as completed for a specific date | `habit-check/SKILL.md` |\n| Habit Dashboard | Display all habits, statuses, and streaks | `habit-check/SKILL.md` |\n| Daily Training Report | Aggregate habit data with health metrics | `daily-training-report/SKILL.md` |\n| Streak Alerts | Warn users when streaks are at risk | `habit-check/SKILL.md` |\n\n资料来源：[skills/habit-check/SKILL.md:1-40]()\n\n## Habit Check Skill\n\nThe `habit-check` skill is the primary interface for daily habit management. It provides an interactive daily check-in experience with direct accountability messaging.\n\n### Workflow\n\n```mermaid\ngraph LR\n A[Call get_habits_for_date] --> B[Call get_habits]\n B --> C[Build Dashboard]\n C --> D{Habits Complete?}\n D -->|Yes| E[Celebrate]\n D -->|No| F[Flag Pending]\n F --> G{Streak >= 3?}\n G -->|Yes| H[Streak At Risk Alert]\n G -->|No| I[Normal Reminder]\n```\n\n### Data Fetching\n\nThe skill retrieves habit data through two parallel calls:\n\n| API Call | Parameters | Purpose |\n|----------|------------|---------|\n| `get_habits_for_date` | `date` (today or `$ARGUMENTS`) | Scheduled habits and their completion status |\n| `get_habits` | none | Full habit list with streak data |\n\n资料来源：[skills/habit-check/SKILL.md:14-20]()\n\n### Dashboard Output\n\nThe habit dashboard presents information in four sections:\n\n**1. Today's Habits**\n\nEach habit displays:\n- Icon + Name\n- Status: `completed` / `pending` / `skipped` / `incomplete`\n- Current streak (e.g., \"🔥 12 days\")\n\n**2. Completion Rate**\n\nFormat: `X/Y habits completed today (percentage)`\n\n**3. Streak Alerts**\n\n| Condition | Action |\n|-----------|--------|\n| Active streak (3+ days) + pending | Flag as \"streak at risk\" |\n| Streak broken yesterday | Call out explicitly |\n\n**4. Never Skip a Rep**\n\nWhen habits are pending:\n- Direct accountability message: \"You haven't done X yet today. Your streak is at Y days. Don't break it.\"\n\nWhen all habits are done:\n- Celebration message: \"All habits completed. No reps skipped.\"\n\n资料来源：[skills/habit-check/SKILL.md:22-38]()\n\n### Interactive Features\n\nUsers can mark habits completed during the check-in by specifying habit names in `$ARGUMENTS`:\n\n```\nInput: \"mark meditation done\"\nAction: Calls check_in_habit for today's date\n```\n\n## Daily Training Report Integration\n\nThe `daily-training-report` skill aggregates habit data as part of a comprehensive personal performance overview. This demonstrates how habit tracking connects to the broader productivity system.\n\n### Habit Data Sources\n\nThe daily training report pulls habit data from three endpoints:\n\n| API Call | Date Parameter | Data Retrieved |\n|----------|----------------|----------------|\n| `get_habits_for_date` | yesterday's date | Yesterday's completion status |\n| `get_habits_for_date` | today's date | Today's scheduled habits |\n| `get_habits` | none | Streak overview for all habits |\n\n资料来源：[skills/daily-training-report/SKILL.md:8-11]()\n\n### Report Structure\n\nThe habit component of the daily training report follows this structure:\n\n```mermaid\ngraph TD\n A[Daily Training Report] --> B[YESTERDAY'S RESULTS]\n A --> C[TODAY'S GAME PLAN]\n \n B --> B1[Habit Scorecard: X/Y]\n B --> B2[Streaks Maintained]\n B --> B3[Streaks Broken]\n B --> B4[Health Scores]\n B --> B5[Day Rating]\n \n C --> C1[Top 3 Priorities]\n C --> C2[Today's Scheduled Habits]\n C --> C3[Streak Counts]\n```\n\n**Yesterday's Results Section:**\n- Habit scorecard: `X/Y completed` with list of each habit and status\n- Streaks maintained or broken (broken streaks called out explicitly)\n- Health scores from Oura integration\n- Day rating based on habit completion + health scores\n\n**Today's Game Plan Section:**\n- Top 3 priorities from agenda + top priority tasks\n- Habits scheduled for today with streak counts\n\n资料来源：[skills/daily-training-report/SKILL.md:13-24]()\n\n## MCP Tools Reference\n\nThe following MCP tools are used for habit management:\n\n| Tool | Purpose | Used In |\n|------|---------|---------|\n| `get_habits` | Retrieve all habits with streak data | habit-check, daily-training-report |\n| `get_habits_for_date` | Get habits scheduled for a specific date | habit-check, daily-training-report |\n| `check_in_habit` | Mark a habit as completed | habit-check |\n\n### get_habits_for_date Parameters\n\n| Parameter | Type | Required | Description |\n|-----------|------|----------|-------------|\n| `date` | string | Yes | The date to check habits for (ISO format or \"today\"/\"yesterday\") |\n\n### get_habits Response\n\nThe `get_habits` call returns:\n- All defined habits\n- Completion status for the queried date\n- Streak counters for each habit\n- Scheduled frequency (daily, specific days, etc.)\n\n## Accountability Philosophy\n\nThe Habits & Accountability system follows a \"personal trainer\" philosophy:\n\n| Principle | Implementation |\n|-----------|----------------|\n| Direct messaging | No fluff or excessive encouragement |\n| Streak protection | Explicit alerts when streaks are at risk |\n| Immediate feedback | Real-time status updates during check-in |\n| Celebration | Acknowledgment when all habits are completed |\n| Accountability | Call out missed reps directly |\n\nThe tone is described as: \"Direct, like a personal trainer. No fluff. Celebrate wins, call out misses.\"\n\n资料来源：[skills/habit-check/SKILL.md:38-40]()\n\n## Related Skills\n\nThe habit system integrates with several other LifeOS skills:\n\n| Skill | Integration Point |\n|-------|-------------------|\n| `daily-plan` | Habits included in planning context via `include.habits=true` |\n| `weekly-plan` | Habits included in weekly planning context |\n| `sprint-plan` | Habit compliance affects energy/focus capacity |\n| `blind-spot-finder` | Uses habit completion rates to identify patterns |\n| `health-weekly` | Habit data complements health metrics |\n\n资料来源：[skills/daily-plan/SKILL.md:9](), [skills/weekly-plan/SKILL.md:9](), [skills/blind-spot-finder/SKILL.md:10]()\n\n## Data Flow\n\n```mermaid\nsequenceDiagram\n participant User\n participant habit-check\n participant MCP Tools\n participant LifeOS\n \n User->>habit-check: Invoke skill\n habit-check->>MCP Tools: get_habits_for_date(today)\n MCP Tools->>LifeOS: Query habit table\n LifeOS->>MCP Tools: Habit status array\n MCP Tools->>habit-check: Response\n habit-check->>MCP Tools: get_habits\n MCP Tools->>LifeOS: Query all habits with streaks\n LifeOS->>MCP Tools: Full habit list\n MCP Tools->>habit-check: Response\n habit-check->>habit-check: Build dashboard\n habit-check->>User: Display results\n \n alt User marks complete\n User->>habit-check: \"mark X done\"\n habit-check->>MCP Tools: check_in_habit(habitId, today)\n MCP Tools->>LifeOS: Update completion record\n LifeOS->>MCP Tools: Success\n MCP Tools->>habit-check: Confirmation\n habit-check->>User: Updated dashboard\n end\n```\n\n## Best Practices\n\n1. **Daily Check-in** — Run `habit-check` each morning to review and update habit status\n2. **Streak Awareness** — Pay attention to \"streak at risk\" alerts to maintain momentum\n3. **Comprehensive View** — Use `daily-training-report` weekly to see habit patterns in context\n4. **Integration** — Reference habit data in planning sessions for realistic scheduling\n\n---\n\n\n\n## Health Integration (Oura Ring)\n\n### 相关页面\n\n相关主题：[Habits & Accountability](#habits-accountability), [Daily Workflows](#daily-workflows), [Review Workflows](#review-workflows)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [skills/health-check/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/health-check/SKILL.md)\n- [skills/health-weekly/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/health-weekly/SKILL.md)\n- [skills/daily-training-report/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/daily-training-report/SKILL.md)\n- [README.md](https://github.com/starascendin/lifeos-plugin/blob/main/README.md)\n- [AGENTS.md](https://github.com/starascendin/lifeos-plugin/blob/main/AGENTS.md)\n \n\n# Health Integration (Oura Ring)\n\n## Overview\n\nThe Health Integration system in LifeOS plugin provides comprehensive biometric data synchronization with Oura Ring devices. This integration aggregates sleep analysis, activity tracking, readiness scoring, stress measurement, and cardiovascular health metrics into a unified health dashboard accessible through MCP (Model Context Protocol) tools.\n\nThe system serves as the health data layer for 37 workflow skills, enabling AI agents to make informed recommendations based on real-time biometric data. It transforms raw Oura Ring measurements into actionable health insights for daily planning, coaching, and personal optimization workflows.\n\n## Architecture\n\n```mermaid\ngraph TD\n subgraph \"Data Sources\"\n OR[Oura Ring Device]\n end\n \n subgraph \"LifeOS MCP Server\"\n HMC[Health MCP Tools]\n SK[Skills Layer]\n end\n \n subgraph \"Health Data Categories\"\n SL[Sleep]\n AC[Activity]\n RD[Readiness]\n ST[Stress]\n HR[Heart Rate]\n RS[Resilience]\n FT[Fitness]\n OX[Oxygen]\n end\n \n subgraph \"Consuming Skills\"\n HC[health-check]\n HW[health-weekly]\n DT[daily-training-report]\n end\n \n OR --> HMC\n HMC --> SK\n SK --> HC\n SK --> HW\n SK --> DT\n \n HMC --> SL\n HMC --> AC\n HMC --> RD\n HMC --> ST\n HMC --> HR\n HMC --> RS\n HMC --> FT\n HMC --> OX\n```\n\n资料来源：[README.md:1-40]()\n\n## Available Health MCP Tools\n\nThe plugin exposes 10 dedicated health MCP tools that retrieve Oura Ring data. All tools accept a `days` parameter to specify the lookback window.\n\n### Health Data Retrieval Tools\n\n| Tool Name | Purpose | Key Metrics |\n|-----------|---------|-------------|\n| `get_health_sleep` | Sleep quality analysis | Scores, durations, bedtime, breath rate, restless periods |\n| `get_health_activity` | Physical activity tracking | Activity scores, steps, active calories |\n| `get_health_readiness` | Daily readiness assessment | Readiness scores, trends |\n| `get_health_stress` | Stress and recovery balance | Stress levels, recovery data |\n| `get_health_workouts` | Exercise history | Workout type, duration, intensity |\n| `get_health_heart_rate` | Cardiovascular metrics | Resting HR, HRV trends |\n| `get_health_resilience` | Resilience levels | Daily resilience, contributors |\n| `get_health_vo2_max` | Aerobic capacity | VO2 max estimates |\n| `get_health_cardio_age` | Cardiovascular age | Cardiovascular age vs actual |\n| `get_health_spo2` | Blood oxygen | SpO2 levels, breathing disturbance index |\n\n资料来源：[skills/health-check/SKILL.md:1-30]()\n\n## Available Health Skills\n\n### Health Check\n\nA quick daily health overview that pulls 7 days of biometric data.\n\n**Invocation:** `health-check [days]`\n\n**Data Sources Called:**\n1. `get_health_sleep` — 7 days\n2. `get_health_activity` — 7 days\n3. `get_health_readiness` — 7 days\n4. `get_health_heart_rate` — 7 days\n5. `get_health_resilience` — 7 days\n6. `get_health_vo2_max` — 7 days\n7. `get_health_cardio_age` — 7 days\n\n资料来源：[skills/health-check/SKILL.md:1-35]()\n\n**Output Structure:**\n\n| Section | Content |\n|---------|---------|\n| Overall Status | Quick assessment (great / good / needs attention) |\n| Sleep | Average score, duration trend, bedtime consistency, breath rate |\n| Activity | Average score, daily steps, active calories |\n| Readiness | Average score, trend direction |\n| Heart Rate | Resting HR trend, HRV |\n| Resilience | Current level and trend |\n| Fitness | VO2 max trend, cardiovascular age comparison |\n| Insights | 2-3 actionable observations |\n\n```mermaid\ngraph LR\n A[health-check] --> B[7-Day Window]\n B --> C[Aggregate Data]\n C --> D[Trend Analysis]\n D --> E[Concise Dashboard]\n E --> F[Actionable Insights]\n```\n\n### Health Weekly\n\nA comprehensive 7-day rolling health review that analyzes 14 days of data for deeper trend analysis.\n\n**Invocation:** `health-weekly`\n\n**Data Sources Called:**\n1. `get_health_sleep` — 14 days\n2. `get_health_activity` — 14 days\n3. `get_health_readiness` — 14 days\n4. `get_health_stress` — 14 days\n5. `get_health_workouts` — 14 days\n6. `get_health_heart_rate` — 14 days\n7. `get_health_resilience` — 14 days\n8. `get_health_vo2_max` — 14 days\n9. `get_health_cardio_age` — 14 days\n10. `get_health_spo2` — 14 days\n\n资料来源：[skills/health-weekly/SKILL.md:1-45]()\n\n**Output Structure:**\n\n| Section | Metrics |\n|---------|--------|\n| Sleep Quality | Weekly averages, best/worst nights, deep/REM balance, bedtime consistency, breath rate |\n| Activity Patterns | Step averages, active vs rest days, calorie burn |\n| Readiness & Recovery | Score trends, stress vs recovery balance |\n| Resilience | Daily levels trend, contributor breakdown (sleep recovery, daytime recovery, stress) |\n| Fitness | VO2 max trend, cardiovascular age, week-over-week changes |\n| Workouts | Workout history with display names |\n\n```mermaid\ngraph TD\n A[health-weekly] --> B[14-Day Window]\n B --> C[Multi-Source Aggregation]\n C --> D[Category Analysis]\n D --> E[Trend Detection]\n E --> F[Weekly Report]\n F --> G[Recovery Insights]\n F --> H[Fitness Assessment]\n```\n\n### Daily Training Report\n\nA comprehensive daily briefing that combines health data with habit tracking and task management.\n\n**Invocation:** `daily-training-report`\n\n**Workflow:**\n\n```mermaid\ngraph TD\n subgraph \"Data Collection\"\n A1[Yesterday's Habits] --> D[Synthesize Report]\n A2[Today's Habits] --> D\n A3[All Habits] --> D\n A4[Sleep 1 day] --> D\n A5[Readiness 1 day] --> D\n A6[Activity 1 day] --> D\n A7[Today's Agenda] --> D\n A8[Today's Tasks] --> D\n A9[Initiatives] --> D\n A10[Coaching Items] --> D\n end\n \n subgraph \"Synthesis\"\n D --> E[YESTERDAY'S RESULTS]\n D --> F[TODAY'S GAME PLAN]\n D --> G[HABIT SCORECARD]\n D --> H[STREAK STATUS]\n end\n```\n\n**Report Sections:**\n\n| Section | Content |\n|---------|---------|\n| Yesterday's Results | Habit scorecard, streaks, health scores, day rating |\n| Today's Game Plan | Top 3 priorities, scheduled habits with streak counts |\n| Health Integration | Sleep/Readiness/Activity scores from Oura Ring |\n\n资料来源：[skills/daily-training-report/SKILL.md:1-50]()\n\n## Data Flow\n\n```mermaid\nsequenceDiagram\n participant User\n participant Skill\n participant MCP_Tools\n participant Convex\n participant Oura\n\n User->>Skill: Invoke health skill\n Skill->>MCP_Tools: Call get_health_*\n MCP_Tools->>Convex: Fetch data\n Convex->>Oura: Request sync\n Oura-->>Convex: Biometric data\n Convex-->>MCP_Tools: Processed metrics\n MCP_Tools-->>Skill: Health data array\n Skill->>Skill: Aggregate & analyze\n Skill-->>User: Formatted report\n```\n\n## Health Metrics Reference\n\n### Sleep Metrics\n\n| Metric | Description | Used By |\n|--------|-------------|---------|\n| Sleep score | Overall 0-100 quality score | health-check, health-weekly |\n| Duration | Total sleep time in hours | health-check, health-weekly |\n| Bedtime | Sleep onset time | health-weekly |\n| Breath rate | Average breathing during sleep | health-check, health-weekly |\n| Deep sleep | Deep sleep duration | health-weekly |\n| REM sleep | REM duration | health-weekly |\n| Restless periods | Wake episodes during sleep | health-weekly |\n\n### Activity Metrics\n\n| Metric | Description | Used By |\n|--------|-------------|---------|\n| Activity score | Daily activity rating | health-check, health-weekly |\n| Steps | Daily step count | health-check, health-weekly |\n| Active calories | Calories burned through activity | health-check, health-weekly |\n| Active vs rest days | Day type classification | health-weekly |\n\n### Readiness Metrics\n\n| Metric | Description | Used By |\n|--------|-------------|---------|\n| Readiness score | Overall readiness 0-100 | health-check, health-weekly, daily-training-report |\n| Trend direction | Improving/declining/stable | health-check |\n| Temperature trend | Body temperature patterns | health-weekly |\n\n### Cardiovascular Metrics\n\n| Metric | Description | Used By |\n|--------|-------------|---------|\n| Resting heart rate | Minimum HR during rest | health-check, health-weekly |\n| HRV | Heart rate variability | health-check |\n| VO2 max | Maximum oxygen uptake | health-check, health-weekly |\n| Cardiovascular age | Estimated cardiovascular age | health-check, health-weekly |\n| SpO2 | Blood oxygen saturation | health-weekly |\n\n### Resilience Metrics\n\n| Metric | Description | Used By |\n|--------|-------------|---------|\n| Resilience level | Daily resilience score | health-check, health-weekly |\n| Sleep recovery contribution | Sleep's role in resilience | health-weekly |\n| Daytime recovery contribution | Activity's role in resilience | health-weekly |\n| Stress contribution | Stress's impact on resilience | health-weekly |\n\n资料来源：[skills/health-check/SKILL.md:15-30]()\n\n## Configuration\n\nHealth data requires the standard LifeOS MCP server connection configured with:\n\n```json\n{\n \"mcpServers\": {\n \"lifeos\": {\n \"command\": \"npx\",\n \"args\": [\n \"@starascendin/lifeos-mcp@latest\",\n \"--url\", \"YOUR_CONVEX_URL\",\n \"--user-id\", \"YOUR_USER_ID\",\n \"--api-key\", \"YOUR_API_KEY\"\n ]\n }\n }\n}\n```\n\nOr environment variables:\n\n```bash\nexport LIFEOS_CONVEX_URL=https://your-app.convex.site\nexport LIFEOS_USER_ID=your-user-id\nexport LIFEOS_API_KEY=your-api-key\n```\n\n资料来源：[README.md:45-60]()\n\n## Usage Patterns\n\n### Quick Health Check\n\n```\nUser: health-check\n→ Returns 7-day health dashboard with scores, trends, and 2-3 insights\n```\n\n### Extended Health Review\n\n```\nUser: health-check 14\n→ Returns 14-day health overview instead of default 7 days\n```\n\n### Weekly Deep Dive\n\n```\nUser: health-weekly\n→ Returns comprehensive 14-day analysis with recovery insights and fitness trends\n```\n\n### Training Integration\n\n```\nUser: daily-training-report\n→ Combines health data with habits, tasks, and coaching items for complete daily briefing\n```\n\n## Skill Comparison\n\n| Feature | health-check | health-weekly | daily-training-report |\n|---------|--------------|---------------|----------------------|\n| Data window | 7 days (default) | 14 days | 1 day |\n| Sleep analysis | ✓ | ✓✓ | ✓ |\n| Activity analysis | ✓ | ✓✓ | ✓ |\n| Readiness tracking | ✓ | ✓✓ | ✓ |\n| Stress metrics | - | ✓ | - |\n| Heart rate | ✓ | ✓ | - |\n| Resilience | ✓ | ✓✓ | - |\n| VO2 max | ✓ | ✓ | - |\n| Cardio age | ✓ | ✓ | - |\n| SpO2 | - | ✓ | - |\n| Workouts | - | ✓ | - |\n| Habit integration | - | - | ✓✓ |\n| Task integration | - | - | ✓ |\n| Initiative tracking | - | - | ✓ |\n\n## Integration with Other Systems\n\nHealth data flows into multiple LifeOS subsystems:\n\n```mermaid\ngraph LR\n subgraph \"Health Data\"\n H[Oura Ring]\n end\n \n subgraph \"Integrated Systems\"\n D[Daily Planning]\n C[Coaching]\n PP[PPV Life Design]\n T[Task Management]\n end\n \n H --> D\n H --> C\n H --> PP\n H --> T\n \n D -->|Affects| D1[Priority Setting]\n D -->|Affects| D2[Due Dates]\n C -->|Drives| C1[Action Items]\n PP -->|Influences| PP1[Energy Levels]\n T -->|Adjusts| T1[Capacity Planning]\n```\n\n### Daily Training Report Integration\n\nThe `daily-training-report` skill demonstrates deep integration, combining:\n\n- **Habit compliance** data with health scores\n- **Streak tracking** synchronized with biometric trends\n- **Initiative progress** aligned with energy levels\n- **Coaching action items** based on health patterns\n\n资料来源：[skills/daily-training-report/SKILL.md:1-50]()\n\n## Best Practices\n\n1. **Use health-check for daily standups** — Quick 7-day snapshot provides context without overwhelming detail\n\n2. **Reserve health-weekly for planning sessions** — The 14-day window reveals trends better suited for strategic decisions\n\n3. **Incorporate health data into daily-training-report** — Biometric context enhances habit coaching effectiveness\n\n4. **Review resilience metrics weekly** — Sleep recovery, daytime recovery, and stress contributions reveal optimization opportunities\n\n5. **Monitor VO2 max trends monthly** — Cardiovascular fitness changes slowly but meaningfully over 4-week periods\n\n---\n\n\n\n## Project Management\n\n### 相关页面\n\n相关主题：[Client Management](#client-management), [Review Workflows](#review-workflows), [Daily Workflows](#daily-workflows)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [skills/sprint-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/sprint-plan/SKILL.md)\n- [skills/weekly-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/weekly-plan/SKILL.md)\n- [skills/daily-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/daily-plan/SKILL.md)\n- [skills/daily-standup/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/daily-standup/SKILL.md)\n- [AGENTS.md](https://github.com/starascendin/lifeos-plugin/blob/main/AGENTS.md)\n- [README.md](https://github.com/starascendin/lifeos-plugin/blob/main/README.md)\n \n\n# Project Management\n\nProject Management in LifeOS is a comprehensive framework for managing work across projects, sprints (cycles), initiatives, and clients. It integrates with the Convex-powered personal productivity OS to provide full CRUD operations for projects, tasks/issues, cycles, phases, clients, and people/contacts through 126 MCP tools.\n\n## Overview\n\nThe Project Management system operates on multiple levels:\n\n| Level | Scope | Tools Available |\n|-------|-------|-----------------|\n| **Initiative** | Yearly goals by category | Progress tracking, initiative review |\n| **Cycle/Sprint** | Current sprint planning and execution | Cycle goals, backlog pull, due dates, priorities |\n| **Weekly** | Week planning across projects | Task scheduling, cycle assignments, note updates |\n| **Daily** | Day-to-day execution | Top priorities, due dates, daily notes |\n| **Project** | Phase breakdown, task stats, blockers | Status reporting, project metrics |\n| **Client** | Client projects, communications, health | Briefs, health dashboards, triage |\n\n## Core Architecture\n\n```mermaid\ngraph TD\n A[LifeOS Plugin] --> B[Planning Context API]\n A --> C[Planning Patch API]\n B --> D[Convex Backend]\n C --> D\n \n E[get_planning_context] --> F[daily
weekly
currentCycle
backlog
habits
calendar
voiceMemos]\n G[apply_planning_patch] --> H[mode: day|week|cycle]\n H --> I[Mutations]\n I --> J[create_issue
schedule_issue
update_issue
assign_to_cycle
set_top_priority
update_cycle_goals
save_daily_note
save_weekly_note]\n```\n\n## Planning Workflow\n\n### Step 1: Gather Planning Context\n\nThe foundation of all project management operations is `get_planning_context`. This single API call aggregates data across multiple dimensions:\n\n| Parameter | Values | Description |\n|-----------|--------|-------------|\n| `date` | ISO date string | Target date for daily planning |\n| `weekStartDate` | ISO date string | Week start for weekly planning |\n| `include.daily` | `true` | Include daily agenda and tasks |\n| `include.weekly` | `true` | Include weekly view |\n| `include.currentCycle` | `true` | Include active sprint/cycle data |\n| `include.backlog` | `true` | Include backlog items |\n| `include.habits` | `true` | Include habit data |\n| `include.dailyFields` | `true` | Include daily custom fields |\n| `include.calendar` | `true` | Include calendar events |\n| `include.voiceMemos` | `true` | Include voice memos |\n\n资料来源：[skills/daily-plan/SKILL.md:8-18]()\n\n### Step 2: Apply Planning Mutations\n\nAfter analyzing the context, mutations are applied via `apply_planning_patch` with three modes:\n\n| Mode | Use Case | Scope |\n|------|----------|-------|\n| `day` | Daily execution planning | Today's top 3, due dates, daily note |\n| `week` | Week planning | Schedule across week, cycle assignments |\n| `cycle` | Sprint planning | Cycle goals, backlog pull, capacity |\n\n## Project Management Skills\n\n### Sprint Planning (`/sprint-plan`)\n\nThe sprint-plan skill manages the current cycle with mutating operations:\n\n1. Fetch planning context with current cycle and backlog\n2. Build cycle plan with goal updates and backlog prioritization\n3. Apply mutations with `mode=\"cycle\"`\n\n**Key Mutations:**\n\n```javascript\n// Assign work to current cycle\nassign_issue_to_current_cycle(issueId, cycleId)\n\n// Update cycle goals\nupdate_cycle_goals(cycleId, goals)\n\n// Schedule work with due dates\nschedule_issue(issueId, dueDate)\n\n// Set immediate priorities\nset_top_priority([issueId1, issueId2, issueId3])\n```\n\n资料来源：[skills/sprint-plan/SKILL.md:1-45]()\n\n### Weekly Planning (`/weekly-plan`)\n\nWeekly planning operates at a broader scope, scheduling work across multiple days:\n\n```mermaid\ngraph LR\n A[Week Start] --> B[Update Cycle Goals]\n B --> C[Pull Backlog Items]\n C --> D[Schedule Due Dates]\n D --> E[Set Top Priorities]\n E --> F[Save Weekly Note]\n```\n\n**Workflow:**\n1. Call `get_planning_context` with `weekStartDate`\n2. Update active cycle goals when needed\n3. Assign backlog tasks to current cycle\n4. Schedule work across the week using `dueDate`\n5. Set near-term top priorities\n6. Call `apply_planning_patch` with `mode=\"week\"` and `dryRun=false`\n\n资料来源：[skills/weekly-plan/SKILL.md:1-40]()\n\n### Daily Planning (`/daily-plan`)\n\nDaily planning focuses on immediate execution:\n\n| Priority Level | Description |\n|----------------|-------------|\n| Top 3 | Must-complete items for today |\n| Due Today | Tasks with today's due date |\n| Overdue | Late tasks requiring triage |\n| Scheduled | Pre-scheduled calendar work |\n\n**Mutations Available:**\n\n- `create_issue` - New tasks\n- `schedule_issue` - Due date changes\n- `update_issue` - Status, priority, estimate, title\n- `assign_issue_to_current_cycle` - Cycle reassignment\n- `set_top_priority` - Today's focus\n- `update_cycle_goals` - Active cycle changes\n- `save_daily_note` - Write to Agenda Daily Note\n- `add_issue_comment` - Planning rationale\n\n资料来源：[skills/daily-plan/SKILL.md:1-45]()\n\n### Daily Standup (`/daily-standup`)\n\nQuick briefing for daily synchronization:\n\n```mermaid\ngraph TD\n A[Daily Standup] --> B[get_daily_agenda]\n A --> C[get_todays_tasks]\n A --> D[get_overdue_tasks]\n A --> E[get_current_cycle]\n \n B --> F[Today's Focus]\n C --> G[Tasks Due]\n D --> H[Overdue Items]\n E --> I[Sprint Progress]\n```\n\n**Output Sections:**\n- **Today's Focus**: Top 3 priorities\n- **Tasks Due**: Tasks due today with priority\n- **Overdue**: Late tasks needing triage\n- **Sprint Progress**: Cycle completion percentage and stats\n- **Calendar**: Meetings and events\n\n资料来源：[skills/daily-standup/SKILL.md:1-35]()\n\n## Client & Project Reporting\n\n### Project Status (`/project-status`)\n\nProvides phase breakdown, task statistics, and blocker identification:\n\n```mermaid\ngraph TD\n A[Project Status] --> B[Phase Breakdown]\n A --> C[Task Statistics]\n A --> D[Blocker Analysis]\n \n B --> E[Active Phases]\n C --> F[Completion %]\n D --> G[Risk Items]\n```\n\n资料来源：[AGENTS.md:1-30]()\n\n### Client Brief (`/client-brief`)\n\nFull client briefing combining projects and communications:\n\n| Component | Data Source |\n|-----------|-------------|\n| Projects | Active client projects |\n| Communications | Beeper threads, meetings |\n| Open Tasks | Client-related issues |\n| Notes | Recent client notes |\n\n### Client Health (`/client-health`)\n\nDashboard across all clients for relationship health tracking.\n\n### Customer Success Triage (`/customer-success-triage`)\n\nWorkflow for triaging client requests:\n\n1. Call `get_client_success_workspace` with client name\n2. Review workspace output:\n - `recentThreads` - Business chats\n - `recentMeetings` - Fathom and Granola meetings\n - `notes` - Client notes\n - `openTasks` - Active issues\n - `projects` - Client projects\n\n3. Drill down as needed:\n - Chat detail: `get_beeper_thread_messages`\n - Meeting detail: `get_fathom_meeting`, `get_granola_meeting`\n - Transcript: `get_fathom_transcript`, `get_granola_transcript`\n - Note history: `get_client_notes`\n\n4. Classify findings:\n - **New Requirements**: Net-new asks\n - **Follow-Ups**: Items waiting on response\n - **Risks/Blockers**: Scope ambiguity, overdue work, churn risk\n - **Already Tracked**: Existing notes or tasks\n\n资料来源：[skills/customer-success-triage/SKILL.md:1-40]()\n\n## Initiative & Cycle Review\n\n### Initiative Review (`/initiative-review`)\n\nYearly goal progress by category. Tracks progress against annual initiatives with configurable year (e.g., `/initiative-review 2026`).\n\n### Cycle Review (`/sprint-review`)\n\nSprint review with rollover options for managing incomplete work between cycles.\n\n## Data Model Relationships\n\n```mermaid\ngraph TD\n I[Initiative] -->|1:N| C[Cycle]\n I -->|1:N| P[Project]\n \n C -->|1:N| T[Task/Issue]\n P -->|1:N| T\n \n C -->|has| G[Cycle Goals]\n P -->|has| Ph[Phases]\n \n T -->|assigned to| C\n T -->|scheduled on| D[Due Date]\n \n C -->|1:N| C2[Next Cycle]\n \n Cl[Client] -->|1:N| P\n Cl -->|1:N| Co[Contact]\n Cl -->|1:N| N[Notes]\n```\n\n## MCP Tools Summary\n\n| Category | Tools | Operations |\n|----------|-------|------------|\n| Projects | `get_project`, `create_project`, `update_project`, `delete_project` | Full CRUD |\n| Issues/Tasks | `get_issue`, `create_issue`, `update_issue`, `delete_issue`, `schedule_issue` | Full CRUD + scheduling |\n| Cycles | `get_current_cycle`, `get_cycle_goals`, `update_cycle_goals`, `assign_issue_to_current_cycle` | Cycle management |\n| Clients | `get_client_success_workspace`, `create_client_note`, `update_client_note` | Client workspace |\n| Planning | `get_planning_context`, `apply_planning_patch` | Context + mutations |\n\n资料来源：[README.md:1-50]()\n资料来源：[AGENTS.md:1-60]()\n\n## Best Practices\n\n1. **Always fetch context first** - Use `get_planning_context` before any planning mutation to ensure you have the latest data\n2. **Set dryRun=true initially** - Preview changes before applying mutations\n3. **Use appropriate mode** - Match the mutation mode (day/week/cycle) to your planning scope\n4. **Save notes as artifacts** - Use `save_daily_note` and `save_weekly_note` to create readable plan artifacts\n5. **Link existing projects** - When using PPV or other systems, prefer linking to existing projects over creating duplicates\n\n---\n\n\n\n## Client Management\n\n### 相关页面\n\n相关主题：[Project Management](#project-management), [People & Relationships](#people-relationships)\n\n\nRelevant Source Files
\n\n以下源码文件用于生成本页说明：\n\n- [skills/client-brief/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/client-brief/SKILL.md)\n- [skills/client-health/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/client-health/SKILL.md)\n- [skills/customer-success-triage/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md)\n- [skills/inbox-triage/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/inbox-triage/SKILL.md)\n \n\n# Client Management\n\nClient Management in LifeOS provides a comprehensive system for managing client relationships, tracking customer-success work, and maintaining client health across your entire portfolio. It leverages the LifeOS MCP tools to aggregate data from multiple sources including Beeper threads, Fathom/Granola meetings, notes, and open tasks into unified client workspaces.\n\n## Overview\n\nThe Client Management system consists of four primary skills that work together to provide complete client visibility and actionable workflows:\n\n| Skill | Purpose | Invocation |\n|-------|---------|------------|\n| `client-brief` | Full client briefing with projects and communications | `/client-brief \"Acme Corp\"` |\n| `client-health` | Health dashboard across all clients | `/client-health` |\n| `customer-success-triage` | Triage requests using chats, meetings, notes, and open work | `/customer-success-triage \"Acme Corp\"` |\n| `inbox-triage` | Process notes into tasks | `/inbox-triage` |\n\n资料来源：[README.md:28-32](https://github.com/starascendin/lifeos-plugin/blob/main/README.md)\n\n## Architecture\n\n```mermaid\ngraph TD\n A[User Request] --> B{Client Management Skills}\n \n B --> C[client-brief]\n B --> D[client-health]\n B --> E[customer-success-triage]\n B --> F[inbox-triage]\n \n C --> G[get_client_success_workspace]\n D --> H[get_all_clients]\n E --> G\n E --> I[Meeting Tools]\n E --> J[Communication Tools]\n \n G --> K[Projects, Tasks, Notes, Threads]\n I --> L[get_fathom_meeting, get_granola_meeting]\n J --> M[get_beeper_thread_messages]\n \n K --> N[apply_planning_patch]\n L --> N\n M --> N\n \n N --> O[LifeOS Convex Backend]\n```\n\n## Core Skills\n\n### Client Brief\n\nThe `client-brief` skill generates a comprehensive client briefing that includes all projects, communications, and current status information for a specific client. It is invoked with the client name or ID as an argument.\n\n资料来源：[AGENTS.md:24](https://github.com/starascendin/lifeos-plugin/blob/main/AGENTS.md)\n\n**Workflow:**\n1. Call `get_client_success_workspace` with the client identifier\n2. Aggregate all related data: projects, open tasks, notes, recent threads, meetings\n3. Present a structured briefing with actionable insights\n\n### Client Health Dashboard\n\nThe `client-health` skill provides a health dashboard across all clients, allowing you to quickly identify which client relationships need attention and which are performing well.\n\n资料来源：[README.md:29](https://github.com/starascendin/lifeos-plugin/blob/main/README.md)\n\n**Key Metrics Tracked:**\n- Communication frequency\n- Open task counts\n- Blocked or overdue items\n- Recent meeting activity\n- Note activity and recency\n\n### Customer Success Triage\n\nThe `customer-success-triage` skill is designed for reviewing customer asks, checking whether work is already tracked, capturing requirement summaries, and deciding what should become a task.\n\n资料来源：[skills/customer-success-triage/SKILL.md:1-6](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md)\n\n**Input Format:**\n```\n$ARGUMENTS should contain the client name or ID, plus an optional focus area\n```\n\n## Customer Success Triage Workflow\n\n```mermaid\ngraph TD\n A[Start Triage: Client Name/ID] --> B[Call get_client_success_workspace]\n B --> C{Workspace Data}\n \n C --> D[recentThreads]\n C --> E[recentMeetings]\n C --> F[notes]\n C --> G[openTasks]\n C --> H[projects]\n \n D --> I{Drill Down Needed?}\n E --> I\n F --> I\n G --> I\n H --> I\n \n I -->|Threads| J[get_beeper_thread_messages]\n I -->|Fathom| K[get_fathom_meeting
get_fathom_transcript]\n I -->|Granola| L[get_granola_meeting
get_granola_transcript]\n I -->|Notes| M[get_client_notes]\n \n J --> N{Classification}\n K --> N\n L --> N\n M --> N\n \n N --> O[New Requirements]\n N --> P[Follow-Ups]\n N --> Q[Risks / Blockers]\n N --> R[Already Tracked]\n \n O --> S[create_issue
update_issue]\n P --> S\n Q --> S\n R --> S\n \n S --> T[create_client_note
update_client_note]\n T --> U[Present Triage Results]\n```\n\n资料来源：[skills/customer-success-triage/SKILL.md:7-28](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md)\n\n## Classification Framework\n\nWhen triaging customer-success work, findings should be classified into four categories:\n\n| Classification | Description | Action |\n|----------------|-------------|--------|\n| **New Requirements** | Net-new asks or requested changes | Create issues or capture in notes |\n| **Follow-Ups** | Things waiting on you or the team | Track and schedule follow-ups |\n| **Risks / Blockers** | Scope ambiguity, overdue work, delivery risk, churn risk | Prioritize and escalate |\n| **Already Tracked** | Notes or tasks that already cover the request | Link and reference existing work |\n\n资料来源：[skills/customer-success-triage/SKILL.md:17-20](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md)\n\n## MCP Tools Reference\n\n### Client Workspace Tools\n\n| Tool | Purpose | Source |\n|------|---------|--------|\n| `get_client_success_workspace` | Retrieve comprehensive workspace for a client | [customer-success-triage/SKILL.md:8](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md) |\n| `get_client_notes` | Retrieve existing note history for a client | [customer-success-triage/SKILL.md:16](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md) |\n\n### Meeting Integration Tools\n\n| Tool | Purpose | Source |\n|------|---------|--------|\n| `get_fathom_meeting` | Retrieve Fathom meeting details | [customer-success-triage/SKILL.md:14](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md) |\n| `get_fathom_transcript` | Get full Fathom meeting transcript | [customer-success-triage/SKILL.md:14](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md) |\n| `get_granola_meeting` | Retrieve Granola meeting details | [customer-success-triage/SKILL.md:15](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md) |\n| `get_granola_transcript` | Get full Granola meeting transcript | [customer-success-triage/SKILL.md:15](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md) |\n\n### Communication Tools\n\n| Tool | Purpose | Source |\n|------|---------|--------|\n| `get_beeper_thread_messages` | Retrieve Beeper thread communications | [customer-success-triage/SKILL.md:13](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md) |\n\n### Write Operations\n\n| Tool | Purpose | When to Use |\n|------|---------|-------------|\n| `create_client_note` | Save durable account memory | New insights, decisions, context |\n| `update_client_note` | Update existing client notes | Refine or extend existing notes |\n| `create_issue` | Create execution work items | New requirements that need action |\n| `update_issue` | Modify existing issues | Status changes, priority updates |\n\n资料来源：[skills/customer-success-triage/SKILL.md:21-25](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md)\n\n## Inbox Triage Integration\n\nThe `inbox-triage` skill works in conjunction with Client Management to process notes into actionable tasks. When client communications result in notes that need to be converted into work items, this skill provides the bridge between captured information and tracked work.\n\n资料来源：[AGENTS.md:21](https://github.com/starascendin/lifeos-plugin/blob/main/AGENTS.md)\n\n**Typical Flow:**\n1. Customer-success triage identifies new requirements\n2. Client notes are created or updated with requirements\n3. Inbox triage converts notes into issues\n4. Issues are linked to relevant projects and cycles\n\n## Best Practices\n\n### Write Operations\n\nBased on the triage workflow design, follow these guidelines for write operations:\n\n1. **Save durable account memory** with `create_client_note` or `update_client_note` for insights, decisions, and context\n2. **Use `create_issue` or `update_issue`** only for execution work that requires tracking\n3. **Prefer updating existing notes/tasks** over creating duplicates\n4. **Do not delete anything** — maintain complete audit trails of client interactions\n\n资料来源：[skills/customer-success-triage/SKILL.md:22-25](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md)\n\n### Drill-Down Strategy\n\nWhen triaging, follow this prioritized approach:\n\n1. **Review the workspace output first** — examine `recentThreads`, `recentMeetings`, `notes`, `openTasks`, and `projects`\n2. **Drill down only when needed** — not every piece of information requires deep investigation\n3. **Match the drill-down tool to the source** — use the appropriate tool for the data type being investigated\n\n资料来源：[skills/customer-success-triage/SKILL.md:8-16](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md)\n\n## Usage Examples\n\n### Generate a Client Brief\n\n```bash\n/client-brief \"Acme Corp\"\n```\n\n### Check Client Health Across Portfolio\n\n```bash\n/client-health\n```\n\n### Triage Customer Success Work\n\n```bash\n/customer-success-triage \"Acme Corp\"\n```\n\n### Triage with Focus Area\n\n```bash\n/customer-success-triage \"Acme Corp\" --focus \"billing issues\"\n```\n\n## Data Flow Summary\n\n```mermaid\ngraph LR\n A[Beeper Threads] --> D[Client Workspace]\n B[Fathom Meetings] --> D\n C[Granola Meetings] --> D\n E[Open Tasks] --> D\n F[Projects] --> D\n G[Notes] --> D\n \n D --> H{Triage Classification}\n H --> I[New Requirements]\n H --> J[Follow-Ups]\n H --> K[Risks/Blockers]\n H --> L[Already Tracked]\n \n I --> M[Issues + Notes]\n J --> M\n K --> M\n L --> N[Reference Link]\n \n M --> O[LifeOS Backend]\n N --> O\n```\n\n## Related Skills\n\n- **Project Management** — Link client work to specific projects and phases\n- **Sprint Plan** — Assign client work to current cycles\n- **Weekly Review** — Include client health in periodic reviews\n- **Follow-ups** — Track outstanding client communications\n\n---\n\n\n\n## People & Relationships\n\n### 相关页面\n\n相关主题：[Client Management](#client-management)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [skills/contact-lookup/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/contact-lookup/SKILL.md)\n- [skills/relationship-pulse/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/relationship-pulse/SKILL.md)\n- [skills/inbox-triage/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/inbox-triage/SKILL.md)\n- [skills/blind-spot-finder/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/blind-spot-finder/SKILL.md)\n- [AGENTS.md](https://github.com/starascendin/lifeos-plugin/blob/main/AGENTS.md)\n \n\n# People & Relationships\n\nThe People & Relationships module within LifeOS Plugin provides a comprehensive system for managing contacts, tracking interactions, preparing for meetings, and maintaining meaningful professional and personal relationships. This module serves as the social intelligence layer of the productivity OS, connecting human interaction data with actionable workflow skills.\n\n## Overview\n\nThe People & Relationships system integrates with multiple data sources to build complete dossiers on contacts, including Beeper messaging threads, Granola meeting records with AI-generated notes, voice memos, and calendar events. The system enables agents to perform relationship maintenance tasks such as identifying neglected contacts, tracking follow-up obligations, and rapidly switching context between different clients or people.\n\n资料来源：[skills/contact-lookup/SKILL.md:1-5]()\n\nThe core philosophy treats relationships as first-class productivity assets. Rather than siloing contact information in a traditional CRM, LifeOS weaves relationship data into daily workflows, enabling proactive relationship maintenance alongside task and project management.\n\n## Core Skills\n\n### Contact Lookup\n\nThe `contact-lookup` skill provides a complete dossier on any person in the system.\n\n**Entry Point**: `get_contact_dossier` with a name query\n\n**Dossier Components**:\n\n| Component | Data Source | Description |\n|-----------|-------------|-------------|\n| Person Info | LifeOS database | Name, relationship type, contact info, system notes |\n| AI Insights | AI-generated | Communication style, personality indicators, relationship tips |\n| Beeper Threads | Beeper API | Messaging history linked to this contact |\n| Granola Meetings | Granola API | Meeting records with AI notes and calendar events |\n| Voice Memos | Voice memo system | Audio recordings involving or mentioning this person |\n\n资料来源：[skills/contact-lookup/SKILL.md:10-25]()\n\n**Workflow**:\n\n```mermaid\ngraph TD\n A[User Query: Contact Name] --> B[Call get_contact_dossier]\n B --> C{Contact Found?}\n C -->|Yes| D[Extract Data Sources]\n C -->|No| E[Request Valid Name]\n D --> F[Fetch Beeper Threads]\n D --> G[Fetch Granola Meetings]\n D --> H[Fetch Voice Memos]\n F --> I[Aggregate Dossier]\n G --> I\n H --> I\n I --> J[Present Structured Output]\n```\n\n**Output Structure**:\n\n```markdown\n- **Profile**: Name, relationship type, contact info, notes\n- **AI Insights**: Communication style, personality, relationship tips\n- **Recent Interactions**: Last voice memos, meetings, messages sorted by recency\n- **Meeting History**: Granola meetings with key takeaways\n- **Chat Threads**: Beeper conversation threads\n```\n\n资料来源：[skills/contact-lookup/SKILL.md:12-25]()\n\n### Meeting Preparation\n\nThe `meeting-prep` skill aggregates relevant context before scheduled meetings with contacts.\n\n**Data Pulled**:\n\n- Contact dossier from `get_contact_dossier`\n- Recent Beeper threads with the person\n- Granola meeting notes from previous encounters\n- Open tasks or projects related to the person\n- Any pending follow-ups or commitments\n\n**Purpose**: Ensures agents enter meetings with full context, avoiding the need to re-explain background or rediscover relationship history.\n\n### Follow-ups Tracking\n\nThe `follow-ups` skill identifies communication obligations across the network.\n\n**Tracking Criteria**:\n\n| Category | Threshold | Priority |\n|----------|-----------|----------|\n| Active threads | Unreplied messages | High |\n| Scheduled meetings | Confirmed but unheld | Medium |\n| Promised responses | Past commitment date | High |\n| Project updates | Stale status | Medium |\n\n**Output**: Prioritized list of contacts requiring responses, grouped by urgency and relationship type.\n\n资料来源：[AGENTS.md:25-28]()\n\n### Relationship Pulse\n\nThe `relationship-pulse` skill proactively monitors relationship health by analyzing interaction frequency against relationship type expectations.\n\n**Data Sources**:\n\n- `get_people` — All contacts with relationship classifications\n- `get_beeper_threads` — Message activity and recency\n- `get_granola_meetings` — Meeting history\n\n资料来源：[skills/relationship-pulse/SKILL.md:1-10]()\n\n**Neglect Thresholds**:\n\n| Relationship Type | Threshold | Priority Level |\n|-------------------|-----------|----------------|\n| Family / Close friends | 14+ days no contact | Critical |\n| Friends | 30+ days no contact | High |\n| Colleagues / Mentors | 60+ days no contact | Medium |\n| Acquaintances | 90+ days no contact | Low (optional) |\n\n资料来源：[skills/relationship-pulse/SKILL.md:22-28]()\n\n**Output Categories**:\n\n- **Reach out soon**: Prioritized by relationship closeness\n- **Consider reconnecting**: Re-engagement opportunities\n- **Suggested touchpoints**: Quick actions like replying to old threads or scheduling catch-ups\n\n```mermaid\ngraph TD\n A[get_people] --> B[Classify Each Contact]\n A --> C[get_beeper_threads]\n A --> D[get_granola_meetings]\n C --> E[Calculate Last Interaction]\n D --> E\n E --> F{Compare to Thresholds}\n F -->|Exceeded| G[Add to Neglected List]\n F -->|Within bounds| H[Mark as Active]\n G --> I[Prioritize by Relationship]\n I --> J[Generate Action Suggestions]\n```\n\n### Context Switch\n\nThe `context-switch` skill enables rapid context loading for a specific client or person, useful when switching between active workstreams.\n\n**Usage**: When working on multiple clients or projects, agents can invoke context-switch to immediately load relevant data without manual retrieval.\n\n**Loaded Data**:\n\n- Recent client notes\n- Active projects and tasks\n- Meeting history\n- Outstanding communications\n- Project-specific context\n\n资料来源：[AGENTS.md:30-31]()\n\n## Data Models\n\n### Person Entity\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `id` | string | Unique identifier |\n| `name` | string | Full name |\n| `relationshipType` | enum | Family, Friend, Colleague, Mentor, Client, Acquaintance |\n| `contactInfo` | object | Email, phone, social links |\n| `notes` | string | Agent-added notes |\n| `createdAt` | timestamp | Creation date |\n| `updatedAt` | timestamp | Last modification |\n\n### Interaction Record\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `personId` | string | Foreign key to person |\n| `type` | enum | Message, Meeting, VoiceMemo, Note |\n| `timestamp` | timestamp | When interaction occurred |\n| `source` | string | Beeper, Granola, VoiceNotes, etc. |\n| `summary` | string | AI-generated summary |\n| `metadata` | object | Source-specific data |\n\n### Relationship Health Score\n\n| Level | Criteria | Action |\n|-------|----------|--------|\n| Active | Recent interaction within threshold | Maintain |\n| Needs Attention | Approaching threshold | Schedule contact |\n| Neglected | Exceeded threshold | Prioritize outreach |\n| At Risk | Significantly exceeded + commitments pending | Immediate action |\n\n## MCP Tool Integration\n\nThe People & Relationships module leverages the LifeOS MCP server for data operations:\n\n### Read Operations\n\n| Tool | Purpose |\n|------|---------|\n| `get_contact_dossier` | Full person dossier with all data sources |\n| `get_people` | List all contacts |\n| `get_beeper_threads` | Messaging threads, optionally filtered by person |\n| `get_granola_meetings` | Meeting records with AI notes |\n| `get_granola_meeting` | Single meeting details |\n| `get_granola_transcript` | Full meeting transcript |\n| `get_voice_memos_by_labels` | Voice memos filtered by labels |\n| `get_client_notes` | Client-specific notes history |\n\n资料来源：[skills/contact-lookup/SKILL.md:16-22]()\n\n### Write Operations\n\n| Tool | Purpose |\n|------|---------|\n| `create_client_note` | Save durable account memory |\n| `update_client_note` | Update existing note |\n| `link_memo_to_person` | Connect voice memo to contact |\n\n资料来源：[skills/contact-lookup/SKILL.md:25-27]()\n\n## Workflow Integration\n\nThe People & Relationships module connects with other LifeOS workflow skills:\n\n### Integration with Planning\n\nDuring daily and weekly planning, the system can surface:\n\n- Pending follow-ups requiring attention\n- Meeting preparations needed\n- Relationship pulse alerts\n\n```mermaid\ngraph LR\n A[Daily Planning] --> B[get_planning_context]\n B --> C{Include People Data?}\n C -->|Yes| D[Fetch Follow-ups]\n C -->|Yes| E[Fetch Relationship Pulse]\n D --> F[Surface in Day Plan]\n E --> F\n```\n\n### Integration with Reviews\n\nDuring cycle and initiative reviews, contact data informs:\n\n- Client health across projects\n- Communication patterns with stakeholders\n- Meeting frequency analysis\n\n### Integration with Capture\n\nThe `inbox-triage` skill uses person data for:\n\n- Linking captured notes to contacts via `link_memo_to_person`\n- Suggesting contacts when notes mention people\n- Creating tasks tied to relationship obligations\n\n资料来源：[skills/inbox-triage/SKILL.md:10-18]()\n\n## Relationship Intelligence\n\n### AI-Generated Insights\n\nThe system uses AI to generate relationship intelligence:\n\n- **Communication style**: How the person prefers to communicate\n- **Personality indicators**: Extracted from interaction patterns\n- **Relationship tips**: Customized advice for maintaining the relationship\n\nThese insights are generated during `get_contact_dossier` calls and stored as part of the person record.\n\n### Blind Spot Detection\n\nThe `blind-spot-finder` skill incorporates relationship data to identify patterns:\n\n- Screening time analysis vs. relationship investment\n- Say-do gaps in stated priorities vs. actual relationship maintenance\n- Patterns the user cannot see from inside their own behavior\n\n资料来源：[skills/blind-spot-finder/SKILL.md:5-12]()\n\n## Best Practices\n\n### Regular Maintenance\n\n1. Run `relationship-pulse` weekly to identify neglected contacts\n2. Review `follow-ups` daily during planning\n3. Use `contact-lookup` before any significant meeting\n\n### Data Quality\n\n1. Ensure relationship types are accurately set for proper threshold calculation\n2. Add notes during interactions for future context\n3. Link voice memos and meeting notes to relevant contacts\n\n### Avoiding Duplication\n\n- Prefer updating existing notes over creating duplicates\n- Use `update_client_note` instead of `create_client_note` when history exists\n- Link to existing contacts rather than creating new person records\n\n资料来源：[skills/contact-lookup/SKILL.md:26-27]()\n\n## Summary\n\nThe People & Relationships module provides a holistic approach to relationship management within LifeOS. By integrating messaging, meetings, voice notes, and AI-generated insights, it enables proactive relationship maintenance alongside productivity work. The system treats relationships as living data that requires regular attention, not static contacts to be occasionally referenced.\n\nKey capabilities include:\n\n- Complete contact dossiers aggregating all interaction data\n- Proactive neglect detection with customizable thresholds\n- Meeting preparation with full historical context\n- Follow-up tracking across multiple communication channels\n- Rapid context switching for multi-client workflows\n\n---\n\n\n\n## Review Workflows\n\n### 相关页面\n\n相关主题：[Daily Workflows](#daily-workflows), [Project Management](#project-management), [Finance Management](#finance-management)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [skills/weekly-review/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/weekly-review/SKILL.md)\n- [skills/weekly-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/weekly-plan/SKILL.md)\n- [skills/monthly-review/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/monthly-review/SKILL.md)\n- [skills/cycle-review/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/cycle-review/SKILL.md)\n- [skills/initiative-review/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/initiative-review/SKILL.md)\n- [skills/customer-success-triage/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md)\n- [skills/blind-spot-finder/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/blind-spot-finder/SKILL.md)\n- [skills/sprint-plan/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/sprint-plan/SKILL.md)\n \n\n# Review Workflows\n\n## Overview\n\nReview Workflows are periodic assessment and reflection skills that enable users to systematically evaluate their progress across different time horizons—from daily standups to yearly initiative reviews. These workflows pull data from LifeOS via MCP (Model Context Protocol) tools, present structured insights, and in some cases apply mutations to the system.\n\nThe review system follows a temporal hierarchy aligned with typical sprint and goal-setting cadences:\n\n```mermaid\ngraph TB\n subgraph \"Review Hierarchy\"\n DR[Daily Review
daily-plan]\n WR[Weekly Review
weekly-review]\n CR[Cycle Review
cycle-review]\n MR[Monthly Review
monthly-review]\n IR[Initiative Review
initiative-review]\n end\n \n subgraph \"Specialized Reviews\"\n CST[Customer Success
Triage]\n BSF[Blind Spot
Finder]\n end\n \n DR --> WR\n WR --> CR\n CR --> MR\n MR --> IR\n \n WR -.-> CST\n WR -.-> BSF\n```\n\nEach review type serves a distinct purpose in the feedback loop of planning, execution, and reflection.\n\n资料来源：[skills/weekly-review/SKILL.md:1-6](https://github.com/starascendin/lifeos-plugin/blob/main/skills/weekly-review/SKILL.md)\n资料来源：[skills/cycle-review/SKILL.md:1-6](https://github.com/starascendin/lifeos-plugin/blob/main/skills/cycle-review/SKILL.md)\n\n---\n\n## Review Workflow Types\n\n### Comparison Table\n\n| Review Type | Time Horizon | Mutating | Primary Data Sources | Skill File |\n|-------------|--------------|----------|---------------------|------------|\n| Daily Plan | Today | Yes | Planning context, calendar, habits | `daily-plan/SKILL.md` |\n| Weekly Review | This week | No | Weekly agenda, cycle, tasks | `weekly-review/SKILL.md` |\n| Weekly Plan | This week | Yes | Planning context, backlog | `weekly-plan/SKILL.md` |\n| Cycle Review | Current sprint | Partial | Current cycle, tasks | `cycle-review/SKILL.md` |\n| Sprint Plan | Current sprint | Yes | Planning context, backlog | `sprint-plan/SKILL.md` |\n| Monthly Review | This month | No | Monthly agenda, cycles, projects | `monthly-review/SKILL.md` |\n| Initiative Review | This year | No | Yearly initiative rollup | `initiative-review/SKILL.md` |\n| Customer Success Triage | Per client | Partial | Client workspace, threads, meetings | `customer-success-triage/SKILL.md` |\n| Blind Spot Finder | Ad-hoc | Partial | Working memory, health, habits | `blind-spot-finder/SKILL.md` |\n\n资料来源：[skills/weekly-review/SKILL.md:1-20](https://github.com/starascendin/lifeos-plugin/blob/main/skills/weekly-review/SKILL.md)\n资料来源：[skills/monthly-review/SKILL.md:1-25](https://github.com/starascendin/lifeos-plugin/blob/main/skills/monthly-review/SKILL.md)\n资料来源：[skills/initiative-review/SKILL.md:1-15](https://github.com/starascendin/lifeos-plugin/blob/main/skills/initiative-review/SKILL.md)\n\n---\n\n## Weekly Review\n\nThe **weekly-review** skill provides a comprehensive assessment of the current week's work, sprint health, and upcoming priorities.\n\n### Purpose\n\n> \"Run weekly review with completed work, in-progress items, sprint health, and blockers\"\n\n资料来源：[skills/weekly-review/SKILL.md:1-2](https://github.com/starascendin/lifeos-plugin/blob/main/skills/weekly-review/SKILL.md)\n\n### Data Gathering Flow\n\n```mermaid\ngraph LR\n A[get_weekly_agenda] --> B[Present Weekly Review]\n C[get_current_cycle] --> B\n D[get_tasks status=done] --> B\n E[get_tasks status=in_progress] --> B\n F[get_tasks status=todo] --> B\n```\n\n### MCP Tools Used\n\n| Tool | Purpose |\n|------|---------|\n| `get_weekly_agenda` | Week's agenda and AI summary |\n| `get_current_cycle` | Sprint progress |\n| `get_tasks` (status: done) | Completed work this week |\n| `get_tasks` (status: in_progress) | Active work |\n| `get_tasks` (status: todo) | Upcoming work |\n\n### Output Structure\n\nThe weekly review presents:\n- **Completed**: What got done this week\n- **In Progress**: What's still being worked on\n- **Sprint Health**: Cycle progress, burndown status\n- **Blockers**: Anything overdue or stuck\n- **Next Week**: Key items to tackle\n\nThe skill optionally accepts a date argument to review a specific week.\n\n资料来源：[skills/weekly-review/SKILL.md:1-25](https://github.com/starascendin/lifeos-plugin/blob/main/skills/weekly-review/SKILL.md)\n\n---\n\n## Monthly Review\n\nThe **monthly-review** skill provides a broader perspective on accomplishments, project progress, and themes across an entire month.\n\n### Purpose\n\n> \"Run monthly review with accomplishments, project progress, and next month planning\"\n\n资料来源：[skills/monthly-review/SKILL.md:1-2](https://github.com/starascendin/lifeos-plugin/blob/main/skills/monthly-review/SKILL.md)\n\n### Data Gathering Flow\n\n```mermaid\ngraph TB\n A[get_monthly_agenda] --> Z[Monthly Review Output]\n B[get_cycles] --> Z\n C[get_tasks status=done] --> Z\n D[get_projects] --> Z\n E[get_clients] --> Z\n F[get_recent_notes limit=20] --> Z\n```\n\n### MCP Tools Used\n\n| Tool | Purpose | Data Retrieved |\n|------|---------|----------------|\n| `get_monthly_agenda` | Month overview and AI summary | Full month's context |\n| `get_cycles` | All sprints this month | Completion rates |\n| `get_tasks` (status: done) | Everything completed | Accomplishments |\n| `get_projects` | Project progress and health | Status tracking |\n| `get_clients` | Client relationship status | Health of client relationships |\n| `get_recent_notes` (limit: 20) | Captured thoughts | Themes and patterns |\n\n### Output Structure\n\nThe monthly review presents:\n- **Accomplishments**: Major wins and completed work\n- **Projects Progress**: Status of each active project\n- **Sprint Performance**: Average completion rate across cycles\n- **Client Health**: Relationship status per client\n- **Themes**: Patterns from notes and completed work\n- **Carried Forward**: What's rolling into next month\n- **Reflections**: What worked, what didn't\n- **Next Month Focus**: Top 3 priorities\n\nSupports optional month argument (e.g., \"january\" or \"2024-01\").\n\n资料来源：[skills/monthly-review/SKILL.md:1-30](https://github.com/starascendin/lifeos-plugin/blob/main/skills/monthly-review/SKILL.md)\n\n---\n\n## Cycle Review\n\nThe **cycle-review** skill focuses on the current sprint/iteration, providing progress metrics and rollover options for incomplete work.\n\n### Purpose\n\n> \"Review the current cycle/sprint with progress, incomplete items, and rollover options\"\n\n资料来源：[skills/cycle-review/SKILL.md:1-2](https://github.com/starascendin/lifeos-plugin/blob/main/skills/cycle-review/SKILL.md)\n\n### Data Gathering\n\n| Tool | Purpose |\n|------|---------|\n| `get_current_cycle` | Active cycle with progress stats |\n| `get_cycles` (status: upcoming) | What's next |\n| `get_tasks` (status: in_progress) | Active work |\n| `get_tasks` (status: backlog or todo) | Incomplete items in cycle |\n\n### Output Structure\n\n- **Cycle Summary**: Name, dates, days remaining\n- **Progress**: Completion %, issues done vs total\n- **Incomplete Items**: All non-done/non-cancelled issues with status and priority\n- **Next Cycle**: The upcoming cycle (if any)\n- **Recommendations**: Closing suggestions, reprioritization advice\n\n### Cycle Management Actions\n\n| Argument | Action | MCP Call |\n|----------|--------|----------|\n| `close` | Close cycle WITHOUT rollover | `close_cycle` |\n| `rollover` | Close cycle WITH rollover | `close_cycle` with `rolloverIncomplete=true` |\n| None | Prompt user for action | — |\n\n资料来源：[skills/cycle-review/SKILL.md:1-35](https://github.com/starascendin/lifeos-plugin/blob/main/skills/cycle-review/SKILL.md)\n\n---\n\n## Initiative Review\n\nThe **initiative-review** skill provides a yearly perspective on goals, tracking progress across multiple initiative categories.\n\n### Purpose\n\n> \"Review yearly initiative progress with stats per category and highlight stalled initiatives\"\n\n资料来源：[skills/initiative-review/SKILL.md:1-2](https://github.com/starascendin/lifeos-plugin/blob/main/skills/initiative-review/SKILL.md)\n\n### Data Gathering Flow\n\n```mermaid\ngraph TB\n A[get_initiative_yearly_rollup] --> B{Low Progress?}\n B -->|Yes| C[get_initiative_with_stats]\n B -->|No| D[Present Review]\n C --> D\n```\n\n### Output Structure\n\n- **Year Overview**: Total initiatives, active vs completed, average progress\n- **By Category**: Group by (career, health, learning, etc.) with progress\n- **Each Initiative**: Title, status, progress %, tasks completed/total, linked projects, habits\n- **Highlights**: Initiatives at 80%+ progress\n- **Concerns**: Flag 0% progress, no linked projects, or \"paused\" status\n- **Recommendations**: Next actions\n\nSupports optional year argument (e.g., \"2025\").\n\n资料来源：[skills/initiative-review/SKILL.md:1-30](https://github.com/starascendin/lifeos-plugin/blob/main/skills/initiative-review/SKILL.md)\n\n---\n\n## Customer Success Triage\n\nThe **customer-success-triage** skill is a specialized review for customer-facing work, synthesizing communications and tracking across multiple channels.\n\n### Purpose\n\n> \"Triage client requests and customer-success work using the client workspace, business chats, Fathom and Granola meetings, notes, and open tasks.\"\n\n资料来源：[skills/customer-success-triage/SKILL.md:1-5](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md)\n\n### Data Gathering Flow\n\n```mermaid\ngraph TB\n A[get_client_success_workspace] --> B[Review Workspace]\n B --> C[recentThreads]\n B --> D[recentMeetings]\n B --> E[notes]\n B --> F[openTasks]\n B --> G[projects]\n \n C --> H[Drill Down Options]\n D --> H\n E --> H\n \n H --> I[get_beeper_thread_messages]\n H --> J[get_fathom_meeting/transcript]\n H --> K[get_granola_meeting/transcript]\n H --> L[get_client_notes]\n```\n\n### Classification Framework\n\n| Category | Description |\n|----------|-------------|\n| **New Requirements** | Net-new asks or requested changes |\n| **Follow-Ups** | Things waiting on you or the team |\n| **Risks / Blockers** | Scope ambiguity, overdue work, delivery risk, churn risk |\n| **Already Tracked** | Notes or tasks that already cover the request |\n\n### Write Operations\n\n| Operation | When to Use |\n|-----------|-------------|\n| `create_client_note` | Save durable account memory |\n| `update_client_note` | Update existing account memory |\n| `create_issue` | New execution work only |\n| `update_issue` | Modify existing tasks |\n\n**Guidelines**: Prefer updating existing notes/tasks over creating duplicates. Do not delete anything.\n\n资料来源：[skills/customer-success-triage/SKILL.md:1-35](https://github.com/starascendin/lifeos-plugin/blob/main/skills/customer-success-triage/SKILL.md)\n\n---\n\n## Blind Spot Finder\n\nThe **blind-spot-finder** skill uses multi-model AI evaluation to identify self-deceptions, local maxima, and blind spots that the user cannot see from within their own perspective.\n\n### Purpose\n\n> \"Use multiple AI models to find what I'm NOT seeing. This is about the unknown unknowns.\"\n\n资料来源：[skills/blind-spot-finder/SKILL.md:1-3](https://github.com/starascendin/lifeos-plugin/blob/main/skills/blind-spot-finder/SKILL.md)\n\n### Data Gathering (Parallel Calls)\n\n```mermaid\ngraph TB\n subgraph \"Context Gathering\"\n A[get_working_memory] \n B[get_coaching_action_items]\n C[get_habits]\n D[get_screentime_summary]\n E[get_health_sleep]\n F[get_finance_net_worth]\n end\n \n A & B & C & D & E & F --> G[Build Blind Spot Brief]\n G --> H[Multi-Model Council]\n H --> I[Synthesized Insights]\n```\n\n### Multi-Model Council Process\n\n| Round | Focus | Purpose |\n|-------|-------|---------|\n| Round 1 | Blind Spot Detection | Identify top 3-5 blind spots, self-deceptions, local maxima |\n| Round 2 | Peer Evaluation | Models review each other's responses |\n| Round 3 | Synthesis | Chairman's final synthesized perspective |\n\n### Focus Areas for Blind Spot Detection\n\n- Self-deceptions they're maintaining\n- Local maxima they're stuck in\n- Assumptions they haven't questioned\n- Patterns they can't see because they're inside them\n- Things they SAY they want but systematically avoid\n\n资料来源：[skills/blind-spot-finder/SKILL.md:1-50](https://github.com/starascendin/lifeos-plugin/blob/main/skills/blind-spot-finder/SKILL.md)\n\n---\n\n## Planning Integration\n\nReview workflows connect to planning workflows to close the feedback loop between reflection and action.\n\n### Review → Plan Flow\n\n```mermaid\ngraph LR\n WR[Weekly Review] --> WP[Weekly Plan]\n CR[Cycle Review] --> SP[Sprint Plan]\n MR[Monthly Review] --> WP\n \n WP --> AP[apply_planning_patch]\n SP --> AP\n \n AP -->|Creates| NI[new_issue]\n AP -->|Schedules| SI[scheduled_issue]\n AP -->|Assigns| ACI[assign_issue_to_current_cycle]\n AP -->|Updates| UG[update_cycle_goals]\n```\n\n### Mutating Operations Available\n\n| Operation | Purpose | Available In |\n|-----------|---------|---------------|\n| `create_issue` | New work | Weekly Plan, Sprint Plan |\n| `schedule_issue` | Due date changes | Weekly Plan, Sprint Plan |\n| `update_issue` | Status, priority, estimate, title | Weekly Plan, Sprint Plan |\n| `assign_issue_to_current_cycle` | Cycle assignment | Weekly Plan, Sprint Plan |\n| `set_top_priority` | Immediate focus | Weekly Plan, Sprint Plan |\n| `update_cycle_goals` | Cycle focus changes | Weekly Plan, Sprint Plan |\n| `save_weekly_note` | Readable weekly plan artifact | Weekly Plan |\n| `save_daily_note` | Concrete execution plan | Weekly Plan |\n\n资料来源：[skills/weekly-plan/SKILL.md:1-30](https://github.com/starascendin/lifeos-plugin/blob/main/skills/weekly-plan/SKILL.md)\n资料来源：[skills/sprint-plan/SKILL.md:1-30](https://github.com/starascendin/lifeos-plugin/blob/main/skills/sprint-plan/SKILL.md)\n\n---\n\n## MCP Tool Reference\n\n### Commonly Used Tools Across Reviews\n\n| Tool | Returns | Review Types |\n|------|---------|--------------|\n| `get_weekly_agenda` | Week's agenda, AI summary | Weekly Review, Weekly Plan |\n| `get_monthly_agenda` | Month overview, AI summary | Monthly Review |\n| `get_current_cycle` | Active cycle stats | Weekly Review, Cycle Review, Sprint Plan |\n| `get_cycles` | All cycles with status | Cycle Review, Monthly Review |\n| `get_tasks` | Tasks filtered by status | All reviews |\n| `get_projects` | Project list with status | Monthly Review |\n| `get_clients` | Client relationships | Monthly Review |\n| `get_initiative_yearly_rollup` | Initiative stats by year | Initiative Review |\n| `get_working_memory` | User's working memory | Blind Spot Finder |\n\n### Planning Context Tool\n\nThe `get_planning_context` tool is fundamental to planning workflows:\n\n| Parameter | Type | Purpose |\n|-----------|------|---------|\n| `date` | string | Specific date for daily planning |\n| `weekStartDate` | string | Week start for weekly planning |\n| `include.daily` | boolean | Include daily fields |\n| `include.weekly` | boolean | Include weekly context |\n| `include.currentCycle` | boolean | Include current cycle |\n| `include.backlog` | boolean | Include backlog items |\n| `include.habits` | boolean | Include habit data |\n| `include.dailyFields` | boolean | Include daily field values |\n| `include.calendar` | boolean | Include calendar events |\n| `include.voiceMemos` | boolean | Include voice memos |\n\n资料来源：[skills/daily-plan/SKILL.md:1-25](https://github.com/starascendin/lifeos-plugin/blob/main/skills/daily-plan/SKILL.md)\n资料来源：[skills/weekly-plan/SKILL.md:1-30](https://github.com/starascendin/lifeos-plugin/blob/main/skills/weekly-plan/SKILL.md)\n\n---\n\n## Best Practices\n\n### When to Use Each Review Type\n\n| Scenario | Recommended Review |\n|----------|-------------------|\n| Start of week planning | Weekly Plan + Weekly Review (if previous week ended) |\n| Mid-sprint check | Cycle Review |\n| End of sprint | Cycle Review + Sprint Plan (for next) |\n| Month transition | Monthly Review |\n| Quarterly planning | Initiative Review + Monthly Review |\n| New client engagement | Customer Success Triage |\n| Feeling stuck or plateaued | Blind Spot Finder |\n\n### Review Cadence\n\n```mermaid\ngantt\n title Review Cadence\n dateFormat X\n axisFormat %j\n \n section Weekly\n Weekly Review :active, r1, 0, 1d\n Weekly Plan :active, r2, 1, 1d\n \n section Monthly\n Monthly Review :active, m1, 30, 1d\n \n section Cycle\n Cycle Review :active, c1, 14, 1d\n Sprint Plan :active, c2, 14, 1d\n```\n\n### Output Expectations\n\n- **Non-mutating reviews** (Weekly Review, Monthly Review, Initiative Review) present data without changes\n- **Mutating workflows** (Weekly Plan, Sprint Plan) automatically apply changes—do not ask for confirmation\n- **Partial mutating** (Cycle Review, Customer Success Triage) offer options but require user input for destructive actions\n\n资料来源：[skills/cycle-review/SKILL.md:25-35](https://github.com/starascendin/lifeos-plugin/blob/main/skills/cycle-review/SKILL.md)\n资料来源：[skills/weekly-plan/SKILL.md:28-32](https://github.com/starascendin/lifeos-plugin/blob/main/skills/weekly-plan/SKILL.md)\n\n---\n\n## See Also\n\n- [Daily Workflows](README.md#daily-workflows) - Daily planning and standup skills\n- [Project & Client Management](README.md#project--client-management) - Project status and client briefing skills\n- [Skills Index](AGENTS.md) - Complete list of all 37 skills\n\n---\n\n\n\n## Finance Management\n\n### 相关页面\n\n相关主题：[Review Workflows](#review-workflows), [Health Integration (Oura Ring)](#health-integration)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [skills/finance-overview/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/finance-overview/SKILL.md)\n- [skills/finance-spending/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/finance-spending/SKILL.md)\n- [README.md](https://github.com/starascendin/lifeos-plugin/blob/main/README.md)\n- [AGENTS.md](https://github.com/starascendin/lifeos-plugin/blob/main/AGENTS.md)\n \n\n# Finance Management\n\nThe Finance Management module within LifeOS provides a comprehensive suite of tools for tracking, analyzing, and understanding personal finances. It integrates directly with Convex-powered backend services to deliver real-time financial insights through 126 MCP (Model Context Protocol) tools available to AI agents.\n\n## Overview\n\nThe Finance Management system consists of two primary skill workflows that enable users to:\n\n- Monitor net worth, account balances, and financial trends\n- Analyze spending patterns with detailed transaction data\n- Track daily income versus spending\n- Identify financial patterns and anomalies\n\n资料来源：[README.md](https://github.com/starascendin/lifeos-plugin/blob/main/README.md)\n\n## Architecture\n\nThe Finance Management module operates within the broader LifeOS ecosystem, leveraging MCP tools to communicate with the Convex backend. All monetary values are stored in cents and converted to dollars for display.\n\n```mermaid\ngraph TD\n A[User Request] --> B[Finance Skill Workflow]\n B --> C[MCP Tool Calls]\n C --> D[Convex Backend]\n D --> E[(Financial Data)]\n \n C --> F[get_finance_net_worth]\n C --> G[get_finance_accounts]\n C --> H[get_finance_snapshots]\n C --> I[get_finance_daily_spending]\n C --> J[get_finance_transactions]\n \n F --> K[Net Worth Dashboard]\n G --> L[Account Breakdown]\n H --> M[90-Day Trend]\n I --> N[Daily Spending Pattern]\n J --> O[Transaction History]\n```\n\n资料来源：[skills/finance-overview/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/finance-overview/SKILL.md) & [skills/finance-spending/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/finance-spending/SKILL.md)\n\n## Available Skills\n\n### Finance Overview\n\nThe `finance-overview` skill provides a comprehensive financial dashboard including net worth summary, account balances, and net worth trends.\n\n| Component | Description |\n|-----------|-------------|\n| Net Worth | Current total with change over the period |\n| Assets | Total assets by account type (checking, savings, investments, retirement) |\n| Liabilities | Total liabilities by type (credit cards, loans) |\n| Trend | Net worth direction over 90 days (growing/declining/stable) |\n| Accounts | Individual account listing with name, type, and balance |\n| Insights | Notable changes or patterns |\n\n资料来源：[skills/finance-overview/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/finance-overview/SKILL.md)\n\n**Usage:**\n```bash\n/finance-overview\n```\n\n**Custom Days Parameter:**\n```bash\n/finance-overview 30\n```\nWhen a number is provided as an argument, it overrides the default 90-day trend period.\n\n### Finance Spending\n\nThe `finance-spending` skill analyzes spending patterns with daily income/spending aggregation and recent transaction details.\n\n| Component | Description |\n|-----------|-------------|\n| Summary | Total income, total spending, net for the period |\n| Daily Average | Average daily spending calculation |\n| Spending Pattern | High-spending days and behavioral patterns |\n| Recent Transactions | Most notable recent transactions |\n| Insights | Spending trends, unusual activity, suggestions |\n\n资料来源：[skills/finance-spending/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/finance-spending/SKILL.md)\n\n**Usage:**\n```bash\n/finance-spending\n```\n\n**Custom Days Parameter:**\n```bash\n/finance-spending 14\n```\nWhen a number is provided, it overrides the default 30-day analysis period.\n\n## MCP Tool Reference\n\nThe Finance Management system exposes the following MCP tools for programmatic access:\n\n| Tool | Purpose |\n|------|---------|\n| `get_finance_net_worth` | Current net worth and account breakdown |\n| `get_finance_accounts` | All account details |\n| `get_finance_snapshots` | Net worth trend data with configurable days |\n| `get_finance_daily_spending` | Daily income/spending aggregation |\n| `get_finance_transactions` | Recent transaction details |\n\n资料来源：[AGENTS.md](https://github.com/starascendin/lifeos-plugin/blob/main/AGENTS.md)\n\n## Data Models\n\n### Financial Data Types\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `balance` | integer | Monetary value stored in cents |\n| `accountType` | string | Type of account (checking, savings, investment, retirement, credit_card, loan) |\n| `netWorth` | integer | Total net worth in cents |\n| `snapshotDate` | date | Date of the financial snapshot |\n\n> **Note:** All monetary amounts are stored in cents and must be converted to dollars for display purposes.\n\n## Workflow Diagram\n\n```mermaid\ngraph LR\n A[Start: /finance-overview] --> B[get_finance_net_worth]\n A --> C[get_finance_accounts]\n A --> D[get_finance_snapshots days=90]\n \n B --> E[Aggregate Data]\n C --> E\n D --> E\n \n E --> F[Build Dashboard]\n F --> G[Net Worth Display]\n F --> H[Assets Breakdown]\n F --> I[Liabilities Breakdown]\n F --> J[90-Day Trend]\n F --> K[Insights]\n```\n\n## Integration Points\n\nThe Finance Management module integrates with:\n\n- **PPV (Purpose, Pillar, Vision) System** - For linking financial goals to life design\n- **Coaching System** - Financial coaching insights and action items\n- **Habits Tracking** - Financial habit compliance\n- **Initiatives** - Yearly financial goals tracked as initiatives\n\n资料来源：[AGENTS.md](https://github.com/starascendin/lifeos-plugin/blob/main/AGENTS.md)\n\n## Quick Reference\n\n| Command | Description | Default Period |\n|---------|-------------|----------------|\n| `/finance-overview` | Net worth dashboard | 90-day trend |\n| `/finance-spending` | Spending analysis | 30-day analysis |\n\nAll commands support numeric arguments to override default periods (e.g., `/finance-overview 30` or `/finance-spending 14`).\n\n---\n\n\n\n## Coaching System\n\n### 相关页面\n\n相关主题：[Habits & Accountability](#habits-accountability)\n\n\n相关源码文件
\n\n以下源码文件用于生成本页说明：\n\n- [skills/coaching-overview/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/coaching-overview/SKILL.md)\n- [skills/coaching-action-items/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/coaching-action-items/SKILL.md)\n- [skills/coaching-session-review/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/coaching-session-review/SKILL.md)\n- [skills/coach-memory/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/coach-memory/SKILL.md)\n- [skills/blind-spot-finder/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/blind-spot-finder/SKILL.md)\n- [skills/llm-council/SKILL.md](https://github.com/starascendin/lifeos-plugin/blob/main/skills/llm-council/SKILL.md)\n \n\n# Coaching System\n\n## Overview\n\nThe Coaching System is an integrated personal development framework within LifeOS that leverages multiple AI models to provide structured coaching, track action items, maintain coach memory, and help users identify blind spots. The system operates as a multi-layered coaching layer that sits atop the core LifeOS data, utilizing the MCP (Model Context Protocol) interface to access user data and apply mutations.\n\nThe coaching system serves as the \"meta-layer\" for personal growth, distinguishing itself from task management by focusing on identity, behavioral patterns, and sustained development rather than discrete deliverables. It coordinates with other LifeOS features like health data, habits, and finance to provide contextually-aware coaching insights.\n\n**资料来源：** [skills/coaching-overview/SKILL.md:1-4]()\n\n## Architecture\n\nThe Coaching System architecture consists of three primary layers:\n\n```mermaid\ngraph TD\n A[Coaching System] --> B[Skill Layer]\n A --> C[Memory Layer]\n A --> D[Multi-Model Layer]\n \n B --> B1[coaching-overview]\n B --> B2[coaching-action-items]\n B --> B3[coaching-session-review]\n B --> B4[coach-memory]\n \n C --> C1[Working Memory]\n C --> C2[Session Summaries]\n C --> C3[Action Items]\n \n D --> D1[llm-council]\n D --> D2[blind-spot-finder]\n \n C1 --> E[LifeOS Data]\n C2 --> E\n C3 --> E\n```\n\n### Skill Layer\n\nThe skill layer consists of discrete workflow skills that can be invoked individually:\n\n| Skill | Purpose | Mutating |\n|-------|---------|----------|\n| `coaching-overview` | Dashboard of coaches, sessions, and action items | No |\n| `coaching-action-items` | Manage coaching action items | Yes |\n| `coaching-session-review` | Review session summaries and insights | No |\n| `coach-memory` | View and update AI coach's working memory | Yes |\n\n**资料来源：** [skills/coaching-overview/SKILL.md:1-18]()\n\n### Memory Layer\n\nThe memory layer maintains persistent knowledge about the user across coaching interactions:\n\n- **Core Struggles**: Consistent challenges the user faces\n- **Values**: Deeply held principles\n- **Triggers**: Causes of spirals, procrastination, or withdrawal\n- **Breakthroughs**: Moments of clarity or growth\n- **Personality**: Cognitive patterns and characteristics\n- **Communication Style**: Coaching delivery preferences\n- **Patterns**: Recurring behavioral patterns\n- **Energy Sources**: What energizes vs drains\n- **Relationships**: Key relationship dynamics\n- **Context**: Current life circumstances\n\n**资料来源：** [skills/coach-memory/SKILL.md:8-25]()\n\n### Multi-Model Layer\n\nThe multi-model layer employs multiple AI models for deliberation and insight generation:\n\n- **LLM Council**: Structured deliberation with peer review and synthesis\n- **Blind Spot Finder**: Multi-model analysis to identify unknown unknowns\n\n**资料来源：** [skills/llm-council/SKILL.md:1-5]()\n\n## MCP Tools\n\nThe Coaching System exposes its functionality through the following MCP tools:\n\n### Query Tools\n\n| Tool | Returns | Source |\n|------|---------|--------|\n| `get_coaching_profiles` | All coach personas with names, focus areas, session cadence | 资料来源：[skills/coaching-overview/SKILL.md:8]() |\n| `get_coaching_sessions` | Recent sessions grouped by coach | 资料来源：[skills/coaching-session-review/SKILL.md:6]() |\n| `get_coaching_session` | Full session details including summary and action items | 资料来源：[skills/coaching-session-review/SKILL.md:9]() |\n| `get_coaching_action_items` | Action items with status filtering | 资料来源：[skills/coaching-overview/SKILL.md:9]() |\n| `get_working_memory` | All memory sections with confidence levels | 资料来源：[skills/coach-memory/SKILL.md:7]() |\n\n### Mutation Tools\n\n| Tool | Purpose | Source |\n|------|---------|--------|\n| `create_coaching_action_item` | Create new coaching homework/experiments | 资料来源：[skills/blind-spot-finder/SKILL.md:28]() |\n| `update_coaching_action_item` | Update status or content of action items | 资料来源：[skills/coaching-action-items/SKILL.md]() |\n| `update_working_memory` | Update coach's accumulated knowledge | 资料来源：[skills/blind-spot-finder/SKILL.md:29]() |\n\n## Coaching Workflows\n\n### Dashboard Overview\n\nThe `coaching-overview` skill provides a consolidated dashboard by executing three parallel queries:\n\n1. `get_coaching_profiles` — List all coach personas\n2. `get_coaching_sessions` with `limit=10` — Recent sessions across all coaches\n3. `get_coaching_action_items` with `status=\"pending\"` — Outstanding action items\n\n**资料来源：** [skills/coaching-overview/SKILL.md:5-13]()\n\nThe dashboard presents:\n\n- **Coaches**: Each coach profile with name, focus areas, and session cadence\n- **Recent Sessions**: Grouped by coach with title, date, and status\n- **Pending Action Items**: Count per coach with top 3 most urgent items shown\n- **Insights**: Active coaches, overdue items, suggested next sessions\n\n```mermaid\ngraph LR\n A[coaching-overview] --> B[get_coaching_profiles]\n A --> C[get_coaching_sessions]\n A --> D[get_coaching_action_items]\n \n B --> E[Dashboard Output]\n C --> E\n D --> E\n```\n\n**资料来源：** [skills/coaching-overview/SKILL.md:13-18]()\n\n### Session Review\n\nThe `coaching-session-review` skill provides in-depth review of coaching sessions:\n\n1. Find sessions via `get_coaching_sessions` with `limit=5`\n2. Resolve session ID from arguments or find most recent\n3. Fetch full details via `get_coaching_session`\n\n**资料来源：** [skills/coaching-session-review/SKILL.md:4-11]()\n\nThe session review displays:\n\n- **Session Info**: Coach name, date, duration, mood at start\n- **Summary**: AI-generated session summary\n- **Key Insights**: All key insights from the session\n- **Action Items**: All action items with current status\n- **Follow-up**: Suggested next session topics based on insights and pending items\n\n**资料来源：** [skills/coaching-session-review/SKILL.md:11-18]()\n\n### Action Item Management\n\nThe `coaching-action-items` skill manages the coaching homework cycle:\n\n```mermaid\ngraph TD\n A[Create Action Item] --> B[Pending Status]\n B --> C[In Progress]\n C --> D{Complete?}\n D -->|Yes| E[Completed]\n D -->|No| F[Update/Extend]\n F --> C\n \n E --> G[Review in Session]\n G --> A\n```\n\nAction items should be:\n- Specific experiments to test hypotheses\n- Linked to insights from sessions or blind spot discovery\n- Tracked with clear status progression\n\n**资料来源：** [skills/blind-spot-finder/SKILL.md:27-28]()\n\n### Coach Memory Management\n\nThe `coach-memory` skill provides visibility into the AI coach's accumulated knowledge:\n\n```mermaid\ngraph TD\n A[get_working_memory] --> B{All Sections}\n B --> C[Core Struggles]\n B --> D[Values]\n B --> E[Triggers]\n B --> F[Breakthroughs]\n B --> G[Personality]\n B --> H[Communication Style]\n B --> I[Patterns]\n B --> J[Energy Sources]\n B --> K[Relationships]\n B --> L[Context]\n \n M[Offer Update] --> N[update_working_memory]\n```\n\nFor each section, the skill displays:\n- Content of the section\n- Confidence level\n- Flagged sections that are empty or stale\n\n**资料来源：** [skills/coach-memory/SKILL.md:7-25]()\n\n## Multi-Model Deliberation\n\n### LLM Council\n\nThe `llm-council` skill implements a structured multi-model deliberation process:\n\n```mermaid\ngraph TD\n A[Start Council] --> B[Stage 1: Individual Responses]\n B --> C[Each Model Responds]\n C --> D[Stage 2: Peer Review]\n D --> E[Models Evaluate Each Other]\n E --> F[Rankings Generated]\n F --> G[Stage 3: Chairman Synthesis]\n G --> H[Final Authoritative Answer]\n \n H --> I[Optional: Save Summary]\n```\n\n**Execution flow:**\n1. **Stage 1** — Each council member provides an individual response\n2. **Stage 2** — Peer review with rankings table showing average rank per model\n3. **Stage 3** — Chairman synthesizes all perspectives into a final answer\n\n**资料来源：** [skills/llm-council/SKILL.md:35-50]()\n\nThe council uses the `zen consensus` tool for deliberation. Estimated completion:\n- Normal tier: 2-5 minutes\n- Pro tier: 5-10 minutes\n\n**资料来源：** [skills/llm-council/SKILL.md:33-34]()\n\n### Blind Spot Finder\n\nThe `blind-spot-finder` skill uses multi-model council to identify unknown unknowns:\n\n```mermaid\ngraph TD\n A[Context Gathering] --> B[Working Memory]\n A --> C[Pending Action Items]\n A --> D[Habits Completion]\n A --> E[Screen Time 3 Days]\n A --> F[Sleep 14 Days]\n A --> G[Finance Net Worth]\n \n B --> H[Blind Spot Brief]\n C --> H\n D --> H\n E --> H\n F --> H\n G --> H\n \n H --> I[Multi-Model Council]\n I --> J[3-5 Blind Spots Identified]\n \n J --> K[User Chooses ONE]\n K --> L[create_coaching_action_item]\n L --> M[update_working_memory]\n```\n\n**资料来源：** [skills/blind-spot-finder/SKILL.md:8-28]()\n\nThe blind spot brief includes:\n- Working memory patterns and triggers\n- Say-do gaps between stated goals and actual behavior\n- Incomplete action items\n- Screen time vs stated priorities\n- Any visible self-deceptions\n\n**资料来源：** [skills/blind-spot-finder/SKILL.md:15-25]()\n\nThe council focuses on:\n- Self-deceptions being maintained\n- Local maxima being stuck in\n- Unquestioned assumptions\n- Invisible patterns from inside them\n- Things systematically avoided despite stated desire\n\n**资料来源：** [skills/blind-spot-finder/SKILL.md:25-31]()\n\n## Integration with LifeOS\n\nThe Coaching System integrates with other LifeOS modules to provide contextually-aware coaching:\n\n| Module | Integration Point | Purpose |\n|--------|-------------------|---------|\n| Health | Sleep, readiness data via Oura | Correlate well-being with patterns |\n| Habits | Habit completion rates | Track behavior change consistency |\n| Finance | Net worth tracking | Ground goals in financial reality |\n| Projects | Initiative progress | Connect coaching to execution |\n| Working Memory | All memory sections | Persistent coach knowledge |\n\n**资料来源：** [skills/blind-spot-finder/SKILL.md:9-14]()\n\n## Skill Invocation\n\n### Via MCP Protocol\n\nAll coaching skills are exposed as MCP prompts, allowing any MCP client to invoke them:\n\n```bash\n/coaching-overview # Dashboard view\n/coaching-action-items # Manage action items\n/coaching-session-review # Review session\n/coach-memory # View/manage memory\n/blind-spot-finder # Find blind spots\n/llm-council # Multi-model deliberation\n```\n\n**资料来源：** [AGENTS.md:1-45]()\n\n### Via Claude Code\n\n```bash\nclaude plugin add github:starascendin/lifeos-plugin\n```\n\nSkills are then accessible through the Claude Code agent's skill system.\n\n**资料来源：** [README.md:1-35]()\n\n## Data Models\n\n### Coaching Profile\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `id` | string | Unique profile identifier |\n| `name` | string | Coach persona name |\n| `focusAreas` | string[] | Coaching specializations |\n| `sessionCadence` | string | Recommended session frequency |\n\n### Coaching Session\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `id` | string | Session identifier |\n| `coachId` | string | Reference to coach profile |\n| `title` | string | Session title/topic |\n| `date` | datetime | Session date |\n| `duration` | number | Duration in minutes |\n| `moodAtStart` | string | Mood indicator |\n| `summary` | string | AI-generated summary |\n| `keyInsights` | string[] | List of key insights |\n| `status` | string | Session status |\n\n**资料来源：** [skills/coaching-session-review/SKILL.md:11-15]()\n\n### Working Memory Section\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `sectionName` | string | Memory section identifier |\n| `content` | string | Section content |\n| `confidenceLevel` | string | AI confidence in accuracy |\n| `lastUpdated` | datetime | Last modification timestamp |\n\n**资料来源：** [skills/coach-memory/SKILL.md:20-25]()\n\n### Coaching Action Item\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `id` | string | Action item identifier |\n| `title` | string | Brief description |\n| `status` | enum | pending, in_progress, completed |\n| `linkedInsight` | string | Source insight or blind spot |\n| `createdAt` | datetime | Creation timestamp |\n| `dueDate` | datetime | Target completion date |\n\n**资料来源：** [skills/blind-spot-finder/SKILL.md:27-28]()\n\n## Best Practices\n\n### Coach Memory Maintenance\n\n- Review memory sections regularly for accuracy\n- Flag stale sections that need updating\n- Update memory after breakthrough insights\n- Use memory to inform coaching delivery style\n\n**资料来源：** [skills/coach-memory/SKILL.md:24-26]()\n\n### Action Item Creation\n\n- Create specific experiments, not vague goals\n- Link items to identified blind spots or insights\n- Use `create_coaching_action_item` for durable tracking\n- Update working memory when genuinely new insight emerges\n\n**资料来源：** [skills/blind-spot-finder/SKILL.md:28-29]()\n\n### Multi-Model Council Usage\n\n- Be patient for deliberation results (2-10 minutes)\n- Present all three stages for transparency\n- Highlight individual model perspectives of value\n- Offer to save insights via `create_ai_convo_summary`\n\n**资料来源：** [skills/llm-council/SKILL.md:46-52]()\n\n### Session Review\n\n- Always check for pending action items\n- Ground insights in user's specific context\n- Suggest forward-looking next steps\n- Reference working memory for continuity\n\n**资料来源：** [skills/coaching-session-review/SKILL.md:15-18]()\n\n---\n\n---\n\n## Doramagic Pitfall Log\n\nProject: starascendin/lifeos-plugin\n\nSummary: Found 7 potential pitfall items; 0 are high/blocking. Highest priority: configuration - 可能修改宿主 AI 配置.\n\n## 1. configuration · 可能修改宿主 AI 配置\n\n- Severity: medium\n- Evidence strength: source_linked\n- Finding: 项目面向 Claude/Cursor/Codex/Gemini/OpenCode 等宿主，或安装命令涉及用户配置目录。\n- User impact: 安装可能改变本机 AI 工具行为，用户需要知道写入位置和回滚方法。\n- Suggested check: 列出会写入的配置文件、目录和卸载/回滚步骤。\n- Guardrail action: 涉及宿主配置目录时必须给回滚路径，不能只给安装命令。\n- Evidence: capability.host_targets | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | host_targets=mcp_host, claude, claude_code\n\n## 2. capability · 能力判断依赖假设\n\n- Severity: medium\n- Evidence strength: source_linked\n- Finding: README/documentation is current enough for a first validation pass.\n- User impact: 假设不成立时，用户拿不到承诺的能力。\n- Suggested check: 将假设转成下游验证清单。\n- Guardrail action: 假设必须转成验证项；没有验证结果前不能写成事实。\n- Evidence: capability.assumptions | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | README/documentation is current enough for a first validation pass.\n\n## 3. maintenance · 维护活跃度未知\n\n- Severity: medium\n- Evidence strength: source_linked\n- Finding: 未记录 last_activity_observed。\n- User impact: 新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。\n- Suggested check: 补 GitHub 最近 commit、release、issue/PR 响应信号。\n- Guardrail action: 维护活跃度未知时，推荐强度不能标为高信任。\n- Evidence: evidence.maintainer_signals | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | last_activity_observed missing\n\n## 4. security_permissions · 下游验证发现风险项\n\n- Severity: medium\n- Evidence strength: source_linked\n- Finding: no_demo\n- User impact: 下游已经要求复核，不能在页面中弱化。\n- Suggested check: 进入安全/权限治理复核队列。\n- Guardrail action: 下游风险存在时必须保持 review/recommendation 降级。\n- Evidence: downstream_validation.risk_items | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | no_demo; severity=medium\n\n## 5. security_permissions · 存在评分风险\n\n- Severity: medium\n- Evidence strength: source_linked\n- Finding: no_demo\n- User impact: 风险会影响是否适合普通用户安装。\n- Suggested check: 把风险写入边界卡，并确认是否需要人工复核。\n- Guardrail action: 评分风险必须进入边界卡，不能只作为内部分数。\n- Evidence: risks.scoring_risks | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | no_demo; severity=medium\n\n## 6. maintenance · issue/PR 响应质量未知\n\n- Severity: low\n- Evidence strength: source_linked\n- Finding: issue_or_pr_quality=unknown。\n- User impact: 用户无法判断遇到问题后是否有人维护。\n- Suggested check: 抽样最近 issue/PR，判断是否长期无人处理。\n- Guardrail action: issue/PR 响应未知时，必须提示维护风险。\n- Evidence: evidence.maintainer_signals | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | issue_or_pr_quality=unknown\n\n## 7. maintenance · 发布节奏不明确\n\n- Severity: low\n- Evidence strength: source_linked\n- Finding: release_recency=unknown。\n- User impact: 安装命令和文档可能落后于代码，用户踩坑概率升高。\n- Suggested check: 确认最近 release/tag 和 README 安装命令是否一致。\n- Guardrail action: 发布节奏未知或过期时，安装说明必须标注可能漂移。\n- Evidence: evidence.maintainer_signals | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | release_recency=unknown\n\n\n",
"summary": "DeepWiki/Human Wiki output with a Doramagic pitfall appendix.",
"title": "Human Manual"
},
"pitfall_log": {
"asset_id": "pitfall_log",
"filename": "PITFALL_LOG.md",
"markdown": "# Pitfall Log\n\nProject: starascendin/lifeos-plugin\n\nSummary: Found 7 potential pitfall items; 0 are high/blocking. Highest priority: configuration - 可能修改宿主 AI 配置.\n\n## 1. configuration · 可能修改宿主 AI 配置\n\n- Severity: medium\n- Evidence strength: source_linked\n- Finding: 项目面向 Claude/Cursor/Codex/Gemini/OpenCode 等宿主，或安装命令涉及用户配置目录。\n- User impact: 安装可能改变本机 AI 工具行为，用户需要知道写入位置和回滚方法。\n- Suggested check: 列出会写入的配置文件、目录和卸载/回滚步骤。\n- Guardrail action: 涉及宿主配置目录时必须给回滚路径，不能只给安装命令。\n- Evidence: capability.host_targets | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | host_targets=mcp_host, claude, claude_code\n\n## 2. capability · 能力判断依赖假设\n\n- Severity: medium\n- Evidence strength: source_linked\n- Finding: README/documentation is current enough for a first validation pass.\n- User impact: 假设不成立时，用户拿不到承诺的能力。\n- Suggested check: 将假设转成下游验证清单。\n- Guardrail action: 假设必须转成验证项；没有验证结果前不能写成事实。\n- Evidence: capability.assumptions | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | README/documentation is current enough for a first validation pass.\n\n## 3. maintenance · 维护活跃度未知\n\n- Severity: medium\n- Evidence strength: source_linked\n- Finding: 未记录 last_activity_observed。\n- User impact: 新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。\n- Suggested check: 补 GitHub 最近 commit、release、issue/PR 响应信号。\n- Guardrail action: 维护活跃度未知时，推荐强度不能标为高信任。\n- Evidence: evidence.maintainer_signals | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | last_activity_observed missing\n\n## 4. security_permissions · 下游验证发现风险项\n\n- Severity: medium\n- Evidence strength: source_linked\n- Finding: no_demo\n- User impact: 下游已经要求复核，不能在页面中弱化。\n- Suggested check: 进入安全/权限治理复核队列。\n- Guardrail action: 下游风险存在时必须保持 review/recommendation 降级。\n- Evidence: downstream_validation.risk_items | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | no_demo; severity=medium\n\n## 5. security_permissions · 存在评分风险\n\n- Severity: medium\n- Evidence strength: source_linked\n- Finding: no_demo\n- User impact: 风险会影响是否适合普通用户安装。\n- Suggested check: 把风险写入边界卡，并确认是否需要人工复核。\n- Guardrail action: 评分风险必须进入边界卡，不能只作为内部分数。\n- Evidence: risks.scoring_risks | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | no_demo; severity=medium\n\n## 6. maintenance · issue/PR 响应质量未知\n\n- Severity: low\n- Evidence strength: source_linked\n- Finding: issue_or_pr_quality=unknown。\n- User impact: 用户无法判断遇到问题后是否有人维护。\n- Suggested check: 抽样最近 issue/PR，判断是否长期无人处理。\n- Guardrail action: issue/PR 响应未知时，必须提示维护风险。\n- Evidence: evidence.maintainer_signals | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | issue_or_pr_quality=unknown\n\n## 7. maintenance · 发布节奏不明确\n\n- Severity: low\n- Evidence strength: source_linked\n- Finding: release_recency=unknown。\n- User impact: 安装命令和文档可能落后于代码，用户踩坑概率升高。\n- Suggested check: 确认最近 release/tag 和 README 安装命令是否一致。\n- Guardrail action: 发布节奏未知或过期时，安装说明必须标注可能漂移。\n- Evidence: evidence.maintainer_signals | github_repo:1156470663 | https://github.com/starascendin/lifeos-plugin | release_recency=unknown\n",
"summary": "Identity, installation, configuration, runtime, and safety pitfalls before user trial.",
"title": "Pitfall Log"
},
"prompt_preview": {
"asset_id": "prompt_preview",
"filename": "PROMPT_PREVIEW.md",
"markdown": "# lifeos-plugin - Prompt Preview\n\n> Copy the prompt below into your AI host before installing anything.\n> Its purpose is to let you safely feel the project's workflow, not to claim the project has already run.\n\n## Copy this prompt\n\n```text\nYou are using an independent Doramagic capability pack for starascendin/lifeos-plugin.\n\nProject:\n- Name: lifeos-plugin\n- Repository: https://github.com/starascendin/lifeos-plugin\n- Summary: LifeOS plugin - 20 workflow skills and MCP integration for Claude Code, OpenCode, and other AI agents\n- Host target: mcp_host, claude, claude_code\n\nGoal:\nHelp me evaluate this project for the following task without installing it yet: LifeOS plugin - 20 workflow skills and MCP integration for Claude Code, OpenCode, and other AI agents\n\nBefore taking action:\n1. Restate my task, success standard, and boundary.\n2. Identify whether the next step requires tools, browser access, network access, filesystem access, credentials, package installation, or host configuration.\n3. Use only the Doramagic Project Pack, the upstream repository, and the source-linked evidence listed below.\n4. If a real command, install step, API call, file write, or host integration is required, mark it as \"requires post-install verification\" and ask for approval first.\n5. If evidence is missing, say \"evidence is missing\" instead of filling the gap.\n\nPreviewable capabilities:\n- Capability 1: Use the source-backed project context to guide one small, checkable workflow step.\n\nCapabilities that require post-install verification:\n- Capability 1: Use the source-backed project context to guide one small, checkable workflow step.\n- Capability 2: Use the source-backed project context to guide one small, checkable workflow step.\n\nCore service flow:\n1. overview: Overview. Produce one small intermediate artifact and wait for confirmation.\n2. skills-overview: Skills Overview. Produce one small intermediate artifact and wait for confirmation.\n3. daily-workflows: Daily Workflows. Produce one small intermediate artifact and wait for confirmation.\n4. project-management: Project Management. Produce one small intermediate artifact and wait for confirmation.\n5. client-management: Client Management. Produce one small intermediate artifact and wait for confirmation.\n\nSource-backed evidence to keep in mind:\n- https://github.com/starascendin/lifeos-plugin\n- https://github.com/starascendin/lifeos-plugin#readme\n- skills/blind-spot-finder/SKILL.md\n- skills/capture/SKILL.md\n- skills/client-brief/SKILL.md\n- skills/client-health/SKILL.md\n- skills/coach-memory/SKILL.md\n- skills/coaching-action-items/SKILL.md\n- skills/coaching-overview/SKILL.md\n- skills/coaching-session-review/SKILL.md\n\nFirst response rules:\n1. Start Step 1 only.\n2. Explain the one service action you will perform first.\n3. Ask exactly three questions about my target workflow, success standard, and sandbox boundary.\n4. Stop and wait for my answers.\n\nStep 1 follow-up protocol:\n- After I answer the first three questions, stay in Step 1.\n- Produce six parts only: clarified task, success standard, boundary conditions, two or three options, tradeoffs for each option, and one recommendation.\n- End by asking whether I confirm the recommendation.\n- Do not move to Step 2 until I explicitly confirm.\n\nConversation rules:\n- Advance one step at a time and wait for confirmation after each small artifact.\n- Write outputs as recommendations or planned checks, not as completed execution.\n- Do not claim tests passed, files changed, commands ran, APIs were called, or the project was installed.\n- If the user asks for execution, first provide the sandbox setup, expected output, rollback, and approval checkpoint.\n```\n",
"summary": "不安装项目也能感受能力节奏的安全试用 Prompt。",
"title": "Prompt Preview / 安装前试用 Prompt"
},
"quick_start": {
"asset_id": "quick_start",
"filename": "QUICK_START.md",
"markdown": "# Quick Start\n\nProject: starascendin/lifeos-plugin\n\n## Official Entry Points\n\n### Node.js / npm · 官方安装入口\n\n```bash\nnpm install -g @starascendin/lifeos-mcp\n```\n\nSource：https://github.com/starascendin/lifeos-plugin#readme\n\n## Sources\n\n- repo: https://github.com/starascendin/lifeos-plugin\n- docs: https://github.com/starascendin/lifeos-plugin#readme\n",
"summary": "Entry points extracted from official README or installation documentation.",
"title": "Quick Start"
}
},
"validation_id": "dval_2b869867bfa14bf0a0a6e55815a364d2"
}