lifeos 1.0.0

package/assets/skills/project/references/execution-agent-prompt.en.md

@@ -0,0 +1,148 @@
+---
+name: execution-agent-prompt
+description: Execution Agent prompt for the Project skill
+role: execution
+parent_skill: project
+---
+# Project Execution Agent Instructions
+
+> Path logical names (e.g., `{projects directory}`, `{drafts directory}`) are resolved by the Orchestrator from `lifeos.yaml` and injected into context. See the main skill file `project/SKILL.md` for the mapping.
+
+> This file is read by the `project/SKILL.md` Orchestrator after the user confirms the plan, and used as the complete prompt for the Task tool.
+> Replace `[plan file path]` with the actual plan file path when using.
+
+---
+
+Execute the project plan at the following path: [plan file path]
+
+## Step 1: Read the Plan File
+
+Carefully read the plan file and note:
+
+- Project category (learning / development / creative / general)
+- Knowledge domain (Domain)
+- Source draft field (for subsequent status update)
+
+## Step 2: Obtain Template (Critical)
+
+**Before generating any content**, read `{system directory}/{templates subdirectory}/Project_Template.md`.
+
+Do not guess the structure. Remember:
+
+- Exact Obsidian Callouts format (e.g., `> [!info]`, `> [!note]`)
+- Frontmatter field structure
+
+## Step 3: Create Project Note
+
+Path rules:
+
+- `development`: must create `{projects directory}/ProjectName/ProjectName.md`
+- `learning / creative / general`: may create `{projects directory}/ProjectName.md`, or use `{projects directory}/ProjectName/ProjectName.md` when there are many files
+
+### Development Project Directory Convention (Mandatory)
+
+If the project category is `development`, the following rules must be followed during execution:
+
+1. There can only be one main project file: `{projects directory}/ProjectName/ProjectName.md`
+2. If supporting documents are needed, place them in `{projects directory}/ProjectName/Docs/`
+3. Supporting documents must use `type: project-doc`
+4. Supporting documents must include `project: "[[{projects directory}/ProjectName/ProjectName]]"`
+5. Do not create versioned main project files like `ProjectNameV0.2.md`, `ProjectNameV0.3.md`
+6. If the plan includes a version roadmap, write version information in the main project's fields or body, not in filenames
+
+**Frontmatter specification:**
+
+```yaml
+---
+type: project
+status: active
+domain: "[[DomainName]]"
+created: "YYYY-MM-DD"
+tags: [project]
+aliases: []
+---
+```
+
+If the project category is `development` and the plan has an explicit version roadmap, you may add:
+
+```yaml
+current_version: V0.1
+target_version: V0.2
+```
+
+**C.A.P. Structure (learning projects use mastery table):**
+
+```markdown
+## Background
+
+[Project objective and background]
+
+## Content Plan
+
+### Mastery Overview
+
+| Chapter | Mastery | Notes | Wiki |
+|---------|---------|-------|------|
+| Chapter 1 [Name] | ⚪ Not started | — | — |
+| Chapter 2 [Name] | ⚪ Not started | — | — |
+
+<!-- Mastery dot mapping: ⚪ Not started 🔴 Not reviewed (draft) 🟡 Needs reinforcement (revise) 🟢 Mastered (mastered) -->
+<!-- /revise will automatically update this table after grading -->
+
+### 📖 Chapter 1: [Chapter Name]
+
+> **Objective:** [What you can do after completing this chapter]
+
+**Reference:** [[{resources directory}/Books/<ResourceName>]] Chapter 1
+
+**Core content:** [3-5 sentence summary]
+
+**Output paths:**
+- 📝 Knowledge note: [[{knowledge directory}/{notes subdirectory}/<Domain>/<BookName>/<ChapterName>/<ChapterName>]]
+- 📝 Wiki: [[{knowledge directory}/{wiki subdirectory}/<Domain>/ConceptName]]
+
+## Progress
+
+[Progress log area, left empty for user to fill]
+```
+
+**Formatting rules:**
+
+- Use wikilinks `[[NoteName]]` to connect all related notes and resources
+- Fill in all chapters/phases according to the outline draft in the plan file, do not truncate
+- Content must be in English
+- Development projects must include a "Project Documents" section in the main project body, stating that supporting documents are stored in the `Docs/` directory
+
+## Step 4: Update Draft Status (Critical)
+
+Check the "Source Draft" field in the plan file:
+
+- If a draft file path is listed (not "None"): update the `status` in that draft file's frontmatter to `projected`
+- This marks the draft as processed, allowing `/archive` to identify and archive it
+
+## Step 5: Update Plan Status (Critical)
+
+- After the project is created, update the plan file frontmatter `status` to `done`
+- Keep the plan file at `{plans directory}/Plan_YYYY-MM-DD_Project_ProjectName.md`
+- `/archive` later moves plans with `status: done` into `{system directory}/{archived plans subdirectory}/`
+
+---
+
+## Completion Report
+
+After completion, report in English:
+
+```
+## Project Creation Complete
+
+**Project:** [[ProjectName]] has been created
+**Knowledge domain:** [Domain]
+**Linked Vault resources:** [List actually linked notes and resources]
+**Source draft status:** [{drafts directory}/filename.md → status updated to projected, or "No source draft"]
+**Plan status:** {plans directory}/Plan_YYYY-MM-DD_Project_ProjectName.md → `status: done` (waiting for `/archive` to move it into `{system directory}/{archived plans subdirectory}/`)
+
+If it is a development project, also include:
+
+**Main project path:** `{projects directory}/ProjectName/ProjectName.md`
+**Supporting documents directory:** `{projects directory}/ProjectName/Docs/`
+```

package/assets/skills/project/references/execution-agent-prompt.zh.md

@@ -0,0 +1,148 @@
+---
+name: execution-agent-prompt
+description: Project 技能的执行 Agent 提示词
+role: execution
+parent_skill: project
+---
+# 项目执行 Agent 指令
+
+> 路径逻辑名（如 `{项目目录}`、`{草稿目录}`）由 Orchestrator 从 `lifeos.yaml` 解析后注入上下文。映射关系见主技能文件 `project/SKILL.md` 的配置块。
+
+> 此文件由 `project/SKILL.md` 的 Orchestrator 在用户确认计划后读取，作为 Task 工具的完整 prompt 使用。
+> 使用时将 `[计划文件路径]` 替换为实际计划文件路径。
+
+---
+
+执行以下路径的项目计划：[计划文件路径]
+
+## 步骤一：读取计划文件
+
+仔细读取计划文件，记录：
+
+- 项目类别（learning / development / creative / general）
+- 知识领域（Domain）
+- 来源草稿字段（用于后续状态更新）
+
+## 步骤二：获取模板（关键）
+
+**在生成任何内容之前**，读取 `{系统目录}/{模板子目录}/Project_Template.md`。
+
+禁止猜测结构。记住：
+
+- 精确的 Obsidian Callouts 格式（如 `> [!info]`, `> [!note]`）
+- frontmatter 字段结构
+
+## 步骤三：创建项目笔记
+
+路径规则：
+
+- `development`：必须创建 `{项目目录}/ProjectName/ProjectName.md`
+- `learning / creative / general`：可创建 `{项目目录}/ProjectName.md`，或在文件较多时使用 `{项目目录}/ProjectName/ProjectName.md`
+
+### 开发类项目目录规范（强制）
+
+若项目类别为 `development`，执行时必须遵守以下规则：
+
+1. 主项目文件只能有一个：`{项目目录}/ProjectName/ProjectName.md`
+2. 若需要配套文档，统一放在 `{项目目录}/ProjectName/文档/`
+3. 配套文档必须使用 `type: project-doc`
+4. 配套文档必须写 `project: "[[{项目目录}/ProjectName/ProjectName]]"`
+5. 禁止创建 `ProjectNameV0.2.md`、`ProjectNameV0.3.md` 之类的版本化主项目文件
+6. 若计划中包含版本路线，版本信息写在主项目字段或正文中，不写入文件名
+
+**Frontmatter 规范：**
+
+```yaml
+---
+type: project
+status: active
+domain: "[[DomainName]]"
+created: "YYYY-MM-DD"
+tags: [project]
+aliases: []
+---
+```
+
+若项目类别为 `development` 且计划中有明确版本路线，可增加：
+
+```yaml
+current_version: V0.1
+target_version: V0.2
+```
+
+**C.A.P. 结构（学习类项目使用掌握度表格）：**
+
+```markdown
+## 背景
+
+[项目目标与背景]
+
+## 内容规划
+
+### 掌握度总览
+
+| 章节 | 掌握度 | 笔记 | 百科 |
+|------|--------|------|------|
+| 第1章 [章节名] | ⚪ 未学 | — | — |
+| 第2章 [章节名] | ⚪ 未学 | — | — |
+
+<!-- 掌握度小圆点映射：⚪未学 🔴未复习(draft) 🟡待巩固(revise) 🟢已掌握(mastered) -->
+<!-- /revise 批改完成后会自动回写此表格 -->
+
+### 📖 第1章: [章节名称]
+
+> **目标:** [学完这个章节后能做什么]
+
+**参考:** [[{资源目录}/Books/<资源名>]] 第1章
+
+**核心内容:** [3-5句话概括]
+
+**产出路径:**
+- 📝 体系笔记: [[{知识目录}/{笔记子目录}/<Domain>/<BookName>/<ChapterName>/<ChapterName>]]
+- 📝 百科: [[{知识目录}/{百科子目录}/<Domain>/概念名称]]
+
+## 进展
+
+[进展记录区，留空供用户填写]
+```
+
+**格式规范：**
+
+- 使用 wikilinks `[[NoteName]]` 连接所有相关笔记和资源
+- 按计划文件中的大纲草案填充所有章节/阶段，不截断
+- 内容必须为中文
+- 开发类项目必须在主项目正文中写明“项目文档”区块，说明配套文档统一存放在 `文档/` 目录
+
+## 步骤四：更新草稿状态（关键）
+
+检查计划文件中的「来源草稿」字段：
+
+- 若列出了草稿文件路径（非"无"）：将该草稿文件的 frontmatter 中 `status` 更新为 `projected`
+- 这标记该草稿已被处理，使 `/archive` 可识别并归档
+
+## 步骤五：更新计划状态（关键）
+
+- 项目创建完成后，将计划文件的 frontmatter 中 `status` 更新为 `done`
+- 保持计划文件仍位于 `{计划目录}/Plan_YYYY-MM-DD_Project_ProjectName.md`
+- 后续由 `/archive` 统一将 `status: done` 的计划移动到 `{系统目录}/{归档计划子目录}/`
+
+---
+
+## 完成报告
+
+完成后用中文汇报：
+
+```
+## 项目创建完成
+
+**项目:** [[ProjectName]] 已创建
+**知识领域:** [Domain]
+**已链接的 Vault 资源:** [列出实际链接到的笔记和资源]
+**来源草稿状态:** [{草稿目录}/文件名.md → status 已更新为 projected，或"无来源草稿"]
+**计划状态:** {计划目录}/Plan_YYYY-MM-DD_Project_ProjectName.md → `status: done`（待 `/archive` 归档到 `{系统目录}/{归档计划子目录}/`）
+
+若为开发类项目，再补充：
+
+**主项目路径:** `{项目目录}/ProjectName/ProjectName.md`
+**配套文档目录:** `{项目目录}/ProjectName/文档/`
+```

package/assets/skills/project/references/planning-agent-prompt.en.md

@@ -0,0 +1,162 @@
+---
+name: planning-agent-prompt
+description: Planning Agent prompt for the Project skill
+role: planning
+parent_skill: project
+---
+
+# Project Planning Agent Instructions
+
+> Path logical names (e.g., `{projects directory}`, `{drafts directory}`) are resolved by the Orchestrator from `lifeos.yaml` and injected into context. See the main skill file `project/SKILL.md` for the mapping.
+
+> This file is read by the `project/SKILL.md` Orchestrator and used as the complete prompt for the Task tool.
+> Replace `[user's idea/draft note]` with the user's actual input when using.
+
+---
+
+Create a project launch plan for the following: [user's idea/draft note]
+
+Execute the following steps:
+
+## Step 1: Gather Context (Broad Search)
+
+- If the input is a draft file path in `{drafts directory}/`: read its full content as the project seed idea
+- Search `{projects directory}/` for any related existing projects
+- Search `{resources directory}/` (Books, Papers, Courses, Links)
+- Record the source draft file path (if any) — the Execution Agent will need it to update the draft status later
+
+Summarize all related content already in the Vault.
+
+## Step 2: Project Classification
+
+- **Project category**: learning / development / creative / general
+- **Knowledge domain** (required for learning): Math / AI / CS / Art / History / Other
+
+If the project category is `development`, the plan must include directory structure design following these rules:
+
+- Main project path is fixed at `{projects directory}/<ProjectName>/<ProjectName>.md`
+- Supporting documents directory is fixed at `{projects directory}/<ProjectName>/Docs/`
+- Main project filename must not contain version numbers
+- If version information exists, write it in the main project's fields or body; do not generate separate `V0.2`, `V0.3` project files
+
+## Step 3: Create Plan File
+
+Path: `{plans directory}/Plan_YYYY-MM-DD_Project_ProjectName.md`
+
+```markdown
+---
+title: "Plan: [Project Name]"
+type: plan
+status: active
+created: "YYYY-MM-DD"
+source: project
+project: "[Project Name]"
+tags: [plan, project]
+aliases: []
+---
+
+# Launch Plan: [Project Name]
+
+## Classification
+
+- Project category: [learning / development / creative / general]
+- Knowledge domain (Domain): [e.g., Math, AI — determines knowledge base subdirectory]
+- Difficulty: [Beginner / Intermediate / Advanced] (required for learning)
+- Estimated effort: [X hours/week × Y weeks] or [approx. X hours total]
+
+## Objective
+
+[One-sentence summary of the project goal]
+
+## Target Directory Structure (Required for Development Projects)
+
+- Main project file: `{projects directory}/<ProjectName>/<ProjectName>.md`
+- Supporting documents directory: `{projects directory}/<ProjectName>/Docs/`
+- Single main project rule: there is only one main project; requirements, design, implementation, testing, etc. are all managed as supporting documents
+- Version rule: version information goes in the main project, not in filenames
+
+## Source Draft
+
+[{drafts directory}/filename.md, or "None (direct input)"]
+
+## Existing Resources in the Vault
+
+### Existing Projects
+
+- [List related existing project wikilinks, or "None"]
+
+### Existing Learning Resources
+
+- Books: [List related wikilinks in {resources directory}/Books/]
+- Papers: [List related wikilinks in {resources directory}/Papers/]
+- Courses: [List related wikilinks in {resources directory}/Courses/]
+
+## Project Outline Draft
+
+### Background
+
+[What problem does it solve / why is it important]
+
+### Prerequisites (Required for Learning)
+
+- [ ] [Concepts/skills that need to be mastered first, wikilink to existing notes]
+
+### Content Plan
+```
+
+**Key rule: Chapter coverage requirement (Learning projects)**
+
+When generating chapter structure:
+
+- Must include **every chapter** from the source resource, never truncate
+- Count the chapters before writing, verify the count matches after writing
+- Never use "..." or "remaining chapters follow the same pattern"
+- Must use the exact, complete filename of the resource (including extension .pdf/.epub etc.)
+
+```markdown
+**Learning project — chapter structure:**
+
+#### Chapter 1: [Chapter Name]
+
+- Objective: [What you can do after completing this chapter]
+- Reference resource: [[{resources directory}/Books/ExactResourceName.pdf]] Chapter 1
+- Expected knowledge note: [[{knowledge directory}/{notes subdirectory}/Domain/BookName/Chapter1NoteName/Chapter1NoteName]] (chapter directory structure)
+- Expected Wiki: [[{knowledge directory}/{wiki subdirectory}/Domain/ConceptName]]
+
+#### Chapter 2: [Chapter Name]
+
+...(exhaustively list all chapters)
+
+**Development project — phase structure:**
+
+#### Phase 1: [Phase Name]
+
+- Deliverables: [...]
+- Reference resources: [if applicable]
+
+> For development projects, if requirements, design, implementation, testing, or refactoring documents are expected, the plan must explicitly state these documents will be stored in `{projects directory}/<ProjectName>/Docs/`.
+
+**Creative/General project — phase structure:**
+
+#### Phase 1: [Phase Name]
+
+- Deliverables: [...]
+- Reference resources: [if applicable]
+
+---
+
+## Missing Resources Alert
+
+- [List needed but missing resources, or "None"]
+
+## Clarification Questions
+
+- What is the timeline/deadline for this project?
+- What is the priority? (P0=Urgent, P1=High, P2=Medium, P3=Low, P4=Later)
+- How many hours per week do you plan to invest?
+- Do you have a preferred learning resource or method? (video/books/hands-on/mixed)
+```
+
+## Step 4: Return Result
+
+Return the path to the plan file.

package/assets/skills/project/references/planning-agent-prompt.zh.md

@@ -0,0 +1,162 @@
+---
+name: planning-agent-prompt
+description: Project 技能的规划 Agent 提示词
+role: planning
+parent_skill: project
+---
+
+# 项目规划 Agent 指令
+
+> 路径逻辑名（如 `{项目目录}`、`{草稿目录}`）由 Orchestrator 从 `lifeos.yaml` 解析后注入上下文。映射关系见主技能文件 `project/SKILL.md` 的配置块。
+
+> 此文件由 `project/SKILL.md` 的 Orchestrator 读取，作为 Task 工具的完整 prompt 使用。
+> 使用时将 `[用户输入的想法或草稿]` 替换为用户实际输入内容。
+
+---
+
+为以下内容创建项目启动计划：[用户输入的想法或草稿]
+
+按以下步骤执行：
+
+## 步骤一：收集上下文（广泛搜索）
+
+- 若输入为 `{草稿目录}/` 中的草稿文件路径：读取其完整内容作为项目种子想法
+- 搜索 `{项目目录}/` 中是否有相关的已有项目
+- 搜索 `{资源目录}/`（Books、Papers、Courses、Links）
+- 记录来源草稿文件路径（如有）——后续 Execution Agent 需用此路径更新草稿状态
+
+汇总 Vault 中已有的相关内容。
+
+## 步骤二：项目分类
+
+- **项目类别**：learning / development / creative / general
+- **知识领域**（学习类必填）：Math / AI / CS / Art / History / 其他
+
+若项目类别为 `development`，规划时必须同时设计目录结构，并遵守以下规则：
+
+- 主项目路径固定为 `{项目目录}/<项目名>/<项目名>.md`
+- 配套文档目录固定为 `{项目目录}/<项目名>/文档/`
+- 主项目文件名不得包含版本号
+- 版本信息若存在，写入主项目字段或正文，不单独生成 `V0.2`、`V0.3` 项目文件
+
+## 步骤三：创建计划文件
+
+路径：`{计划目录}/Plan_YYYY-MM-DD_Project_ProjectName.md`
+
+```markdown
+---
+title: "Plan: [项目名称]"
+type: plan
+status: active
+created: "YYYY-MM-DD"
+source: project
+project: "[项目名称]"
+tags: [plan, project]
+aliases: []
+---
+
+# 启动计划: [项目名称]
+
+## 分类
+
+- 项目类别: [learning / development / creative / general]
+- 知识领域 (Domain): [如 Math, AI 等，决定知识库子目录]
+- 难度: [入门 / 进阶 / 高级]（学习类必填）
+- 预估投入: [X小时/周 × Y周] 或 [总计约X小时]
+
+## 目标
+
+[一句话总结项目目标]
+
+## 目标目录结构（开发类项目必填）
+
+- 主项目文件：`{项目目录}/<项目名>/<项目名>.md`
+- 配套文档目录：`{项目目录}/<项目名>/文档/`
+- 单主项目规则：主项目只有一个，需求、设计、实施、测试等都作为配套文档管理
+- 版本规则：版本信息写入主项目，不写入文件名
+
+## 来源草稿
+
+[{草稿目录}/文件名.md，或"无（直接输入）"]
+
+## Vault 中的已有资源
+
+### 已有项目
+
+- [列出相关的已有项目 wikilinks，或"无"]
+
+### 已有学习资源
+
+- 书籍: [列出 {资源目录}/Books/ 中相关 wikilinks]
+- 论文: [列出 {资源目录}/Papers/ 中相关 wikilinks]
+- 课程: [列出 {资源目录}/Courses/ 中相关 wikilinks]
+
+## 项目大纲草案
+
+### 背景
+
+[解决什么问题 / 为什么重要]
+
+### 前置依赖（学习类必填）
+
+- [ ] [需要先掌握的概念/技能，wikilink 到已有笔记]
+
+### 内容规划
+```
+
+**关键规则：章节覆盖要求（学习类项目）**
+
+生成章节结构时：
+
+- 必须包含来源资源的**每一章**，绝不截断
+- 写之前先数章节数，写完后验证数量一致
+- 禁止使用"..."或"其余章节同上"
+- 必须使用资源的精确完整文件名（含扩展名 .pdf/.epub 等）
+
+```markdown
+**学习类项目——章节结构：**
+
+#### 第1章: [章节名称]
+
+- 目标: [学完能做什么]
+- 参考资源: [[{资源目录}/Books/ExactResourceName.pdf]] 第1章
+- 预计产出体系笔记: [[{知识目录}/{笔记子目录}/Domain/BookName/第1章笔记名/第1章笔记名]]（章节目录结构）
+- 预计产出百科: [[{知识目录}/{百科子目录}/Domain/概念名]]
+
+#### 第2章: [章节名称]
+
+...（对所有章节穷尽列出）
+
+**开发项目——阶段结构：**
+
+#### 阶段1: [阶段名称]
+
+- 交付物: [...]
+- 参考资源: [如适用]
+
+> 对开发项目，若预计会产生需求、设计、实施、测试或重构文档，必须在计划中明确这些文档将存放于 `{项目目录}/<项目名>/文档/`。
+
+**创作/通用项目——阶段结构：**
+
+#### 阶段1: [阶段名称]
+
+- 交付物: [...]
+- 参考资源: [如适用]
+
+---
+
+## 缺失资源提醒
+
+- [列出需要但缺失的资源，或"暂无"]
+
+## 澄清问题
+
+- 这个项目的时间线/截止日期是什么？
+- 优先级是多少？（P0=紧急, P1=高, P2=中, P3=低, P4=以后）
+- 每周计划投入多少时间？
+- 有偏好的学习资源或方式吗？（视频/书籍/实践/混合）
+```
+
+## 步骤四：返回结果
+
+返回计划文件的路径。