lifeos 1.0.0

package/assets/skills/_shared/lifecycle.en.md

@@ -0,0 +1,84 @@
+# LifeOS Shared Lifecycle State Machines
+
+This document defines the state transition rules for all note types in the LifeOS skill system. This is the single source of truth.
+
+## Draft Lifecycle
+
+```
+pending ──/research──→ researched ──┐
+pending ──/project───→ projected  ──┼──/archive──→ archived
+pending ──/knowledge─→ knowledged ──┘
+```
+
+| Status | Meaning | Set by |
+|--------|---------|--------|
+| `pending` | Created by /brainstorm or /today, not yet processed | /brainstorm, /today |
+| `researched` | Consumed by /research into a research report | /research |
+| `projected` | Consumed by /project into a project file | /project |
+| `knowledged` | Consumed by /knowledge into knowledge notes | /knowledge |
+| `archived` | Moved to archive directory by /archive | /archive |
+
+**Rules:**
+
+- /archive only archives drafts with status `researched`, `projected`, or `knowledged`.
+- /archive never archives `pending` drafts.
+
+## Knowledge Note Lifecycle
+
+```
+draft ──/revise(≥50%)──→ revise ──/revise(≥80%)──→ mastered
+```
+
+| Status | Meaning | Set by |
+|--------|---------|--------|
+| `draft` | Created by /knowledge, never reviewed | /knowledge |
+| `revise` | Promoted by /revise when score 50%-80% | /revise |
+| `mastered` | Promoted by /revise when score ≥80% | /revise |
+
+**Rules:**
+
+- Status only upgrades, never downgrades: `draft` -> `revise` -> `mastered`.
+- /revise updates the corresponding project file's mastery dots (⚪→🔴→🟡→🟢).
+
+## Project Lifecycle
+
+```
+active ──→ on-hold ──→ done ──/archive──→ archived
+```
+
+| Status | Meaning | Set by |
+|--------|---------|--------|
+| `active` | Currently being worked on | /project |
+| `on-hold` | Paused | Manual |
+| `done` | Completed, ready for archival | Manual |
+| `archived` | Moved to archive directory by /archive | /archive |
+
+## Plan Lifecycle
+
+```
+active ──/project,/research──→ done ──/archive──→ archived
+```
+
+| Status | Meaning | Set by |
+|--------|---------|--------|
+| `active` | Created by /project or /research and kept in `{plans directory}/` while waiting for execution or review | /project, /research |
+| `done` | The corresponding project or research work has finished and is waiting for /archive | /project, /research |
+| `archived` | Moved into `{system directory}/{archived plans subdirectory}/` by /archive | /archive |
+
+**Rules:**
+
+- /project and /research must write `type: plan` and `status: active` when creating a plan file
+- /project and /research only update the plan status to `done` after execution; they do not move the plan file directly
+- /archive only archives plans with `status: done` and updates them to `archived` after moving
+
+## Skill Participation Matrix
+
+| Skill | Draft Transitions | Knowledge Note Transitions | Project Transitions | Plan Transitions |
+|-------|-------------------|---------------------------|---------------------|------------------|
+| /brainstorm | Creates `pending` | - | - | - |
+| /today | Creates `pending` | - | - | - |
+| /research | `pending` → `researched` | - | - | Creates `active`, then updates to `done` after execution |
+| /project | `pending` → `projected` | - | Creates `active` | Creates `active`, then updates to `done` after execution |
+| /knowledge | `pending` → `knowledged` | Creates `draft` | - | - |
+| /revise | - | `draft` → `revise` → `mastered` | Updates mastery dots | - |
+| /archive | `researched/projected/knowledged` → `archived` | - | `done` → `archived` | `done` → `archived` |

package/assets/skills/_shared/lifecycle.zh.md

@@ -0,0 +1,84 @@
+# LifeOS 共享生命周期状态机
+
+本文档定义了 LifeOS 技能系统中所有笔记类型的状态转换规则。这是唯一的权威来源。
+
+## 草稿生命周期 (Draft Lifecycle)
+
+```
+pending ──/research──→ researched ──┐
+pending ──/project───→ projected  ──┼──/archive──→ archived
+pending ──/knowledge─→ knowledged ──┘
+```
+
+| 状态 | 含义 | 设置者 |
+|------|------|--------|
+| `pending` | 由 /brainstorm 或 /today 创建，尚未处理 | /brainstorm, /today |
+| `researched` | 已被 /research 消费，生成研究报告 | /research |
+| `projected` | 已被 /project 消费，生成项目文件 | /project |
+| `knowledged` | 已被 /knowledge 消费，生成知识笔记 | /knowledge |
+| `archived` | 已被 /archive 移入归档目录 | /archive |
+
+**规则:**
+
+- /archive 仅归档状态为 `researched`、`projected` 或 `knowledged` 的草稿。
+- /archive 绝不归档 `pending` 状态的草稿。
+
+## 知识笔记生命周期 (Knowledge Note Lifecycle)
+
+```
+draft ──/revise(≥50%)──→ revise ──/revise(≥80%)──→ mastered
+```
+
+| 状态 | 含义 | 设置者 |
+|------|------|--------|
+| `draft` | 由 /knowledge 创建，从未复习 | /knowledge |
+| `revise` | 由 /revise 在评分 50%-80% 时提升 | /revise |
+| `mastered` | 由 /revise 在评分 ≥80% 时提升 | /revise |
+
+**规则:**
+
+- 状态只能升级，不能降级：`draft` -> `revise` -> `mastered`。
+- /revise 同时更新对应项目文件中的掌握度圆点（⚪→🔴→🟡→🟢）。
+
+## 项目生命周期 (Project Lifecycle)
+
+```
+active ──→ on-hold ──→ done ──/archive──→ archived
+```
+
+| 状态 | 含义 | 设置者 |
+|------|------|--------|
+| `active` | 正在进行中 | /project |
+| `on-hold` | 已暂停 | 手动 |
+| `done` | 已完成，可归档 | 手动 |
+| `archived` | 已被 /archive 移入归档目录 | /archive |
+
+## 计划生命周期
+
+```
+active ──/project,/research──→ done ──/archive──→ archived
+```
+
+| 状态 | 含义 | 设置者 |
+|------|------|--------|
+| `active` | 由 /project 或 /research 生成，计划仍位于 `{计划目录}/`，等待执行或复查 | /project, /research |
+| `done` | 对应项目或研究已执行完成，等待 /archive 归档 | /project, /research |
+| `archived` | 已被 /archive 移入 `{系统目录}/{归档计划子目录}/` | /archive |
+
+**规则:**
+
+- /project 和 /research 创建计划文件时，必须写入 `type: plan` 与 `status: active`
+- /project 和 /research 执行完成后，只将计划状态更新为 `done`，不直接移动计划文件
+- /archive 仅归档 `status: done` 的计划，并在移动后将其更新为 `archived`
+
+## 技能参与矩阵
+
+| 技能 | 草稿状态转换 | 知识笔记状态转换 | 项目状态转换 | 计划状态转换 |
+|------|-------------|-----------------|-------------|-------------|
+| /brainstorm | 创建 `pending` | - | - | - |
+| /today | 创建 `pending` | - | - | - |
+| /research | `pending` → `researched` | - | - | 创建 `active`，执行后更新为 `done` |
+| /project | `pending` → `projected` | - | 创建 `active` | 创建 `active`，执行后更新为 `done` |
+| /knowledge | `pending` → `knowledged` | 创建 `draft` | - | - |
+| /revise | - | `draft` → `revise` → `mastered` | 更新掌握度圆点 | - |
+| /archive | `researched/projected/knowledged` → `archived` | - | `done` → `archived` | `done` → `archived` |

package/assets/skills/_shared/memory-protocol.en.md

@@ -0,0 +1,36 @@
+# Memory System Integration Protocol
+
+> All memory operations are invoked via MCP tools. `db_path` and `vault_root` are automatically injected at runtime; no need to specify them in the skill.
+
+### File Change Notification
+
+After each Vault file creation or modification, immediately call:
+
+```
+memory_notify(file_path="<relative path of changed file>")
+```
+
+### Skill Completion
+
+After all file writes are complete, call once:
+
+```
+memory_skill_complete(
+  skill_name="<current skill name>",
+  summary="<one-line description of this operation>",
+  related_files=["<path1>", "<path2>"],
+  scope="<current skill name>",
+  refresh_targets=["TaskBoard", "UserProfile"]
+)
+```
+
+### Session Wrap-up (when this skill is the last operation in the session)
+
+1. Write session bridge:
+   ```
+   memory_log(entry_type="session_bridge", summary="<session summary>", scope="<skill name>")
+   ```
+2. Execute checkpoint:
+   ```
+   memory_checkpoint()
+   ```

package/assets/skills/_shared/memory-protocol.zh.md

@@ -0,0 +1,36 @@
+# 记忆系统集成协议
+
+> 所有记忆操作通过 MCP 工具调用，`db_path` 和 `vault_root` 由运行时自动注入，技能中无需指定。
+
+### 文件变更通知
+
+每次创建或修改 Vault 文件后，立即调用：
+
+```
+memory_notify(file_path="<变更文件相对路径>")
+```
+
+### 技能完成
+
+全部文件写入完成后，调用一次：
+
+```
+memory_skill_complete(
+  skill_name="<当前技能名>",
+  summary="<一句话描述本次操作>",
+  related_files=["<路径1>", "<路径2>"],
+  scope="<当前技能名>",
+  refresh_targets=["TaskBoard", "UserProfile"]
+)
+```
+
+### 会话收尾（本技能为会话最后一个操作时）
+
+1. 写入会话桥接：
+   ```
+   memory_log(entry_type="session_bridge", summary="<本次会话摘要>", scope="<技能名>")
+   ```
+2. 执行检查点：
+   ```
+   memory_checkpoint()
+   ```

package/assets/skills/_shared/template-loading.en.md

@@ -0,0 +1,26 @@
+# Template Loading Protocol
+
+This protocol applies to all skills that need to read Vault template files.
+
+## Loading Rules
+
+1. Before generating any content, you **must** use file reading capabilities to read the exact template file from the Vault
+2. **Never guess template structure** — even if you "remember" the template content, you must re-read it
+3. After reading, note the following key elements:
+   - Obsidian Callouts format (`> [!info]`, `> [!note]`, etc.)
+   - Frontmatter field structure and required fields
+   - Block markers and separators
+
+## AI Instruction Comment Handling
+
+If a template contains AI instructions in HTML comment form (`<!-- AI instruction: ... -->`):
+
+1. You **must execute** the instruction and generate the corresponding block content
+2. The `<!-- AI instruction: ... -->` comment **must never appear** in the final output
+3. Comments must be replaced with the generated content
+
+## Template Path Resolution
+
+Template paths are resolved via `lifeos.yaml` configuration:
+- Template directory: `{system directory}/{template subdirectory}/`
+- Specific template filenames are declared in each skill's `dependencies.templates`

package/assets/skills/_shared/template-loading.zh.md

@@ -0,0 +1,26 @@
+# 模板加载协议
+
+本协议适用于所有需要读取 Vault 模板文件的技能。
+
+## 加载规则
+
+1. 在生成任何内容之前，**必须**使用文件读取能力读取 Vault 中的准确模板文件
+2. **禁止猜测模板结构** — 即使你"记得"模板内容，也必须重新读取
+3. 读取后记住以下关键元素：
+   - Obsidian Callouts 格式（`> [!info]`、`> [!note]` 等）
+   - frontmatter 字段结构和必填字段
+   - 区块标记和分隔符
+
+## AI 指令注释处理
+
+若模板包含 HTML 注释形式的 AI 指令（`<!-- AI指令：... -->`）：
+
+1. **必须执行**该指令，生成对应区块内容
+2. **最终输出中绝对不能保留** `<!-- AI指令：... -->` 注释原文
+3. 注释必须被替换为生成的内容
+
+## 模板路径解析
+
+模板路径通过 `lifeos.yaml` 配置解析：
+- 模板目录：`{系统目录}/{模板子目录}/`
+- 具体模板文件名在各技能的 `dependencies.templates` 中声明

package/assets/skills/archive/SKILL.en.md

@@ -0,0 +1,300 @@
+---
+name: archive
+description: "Scan and archive completed projects (status:done), consumed drafts (status:researched/projected/knowledged), completed plans (status: done), and diary entries older than the most recent 7 days, moving them into the unified archive structure and updating frontmatter. Never touches pending drafts, active plans, or the most recent 7 days of diary entries. Use this skill when the user wants to clean up the Vault, archive completed work, tidy up, or says '/archive'."
+version: 1.0.0
+dependencies:
+  templates: []
+  prompts: []
+  schemas: []
+  agents: []
+---
+
+> [!config]
+> Path references in this skill use logical names (e.g., `{projects directory}`).
+> The Orchestrator resolves actual paths from `lifeos.yaml` and injects them into the context.
+> Path mappings:
+> - `{drafts directory}` → directories.drafts
+> - `{diary directory}` → directories.diary
+> - `{projects directory}` → directories.projects
+> - `{plans directory}` → directories.plans
+> - `{resources directory}` → directories.resources
+> - `{system directory}` → directories.system
+> - `{archived projects subdirectory}` → subdirectories.system.archive.projects
+> - `{archived drafts subdirectory}` → subdirectories.system.archive.drafts
+> - `{archived plans subdirectory}` → subdirectories.system.archive.plans
+> - `{archived diary subdirectory}` → subdirectories.system.archive.diary
+
+You are LifeOS's archive manager, helping users keep the Vault's active space tidy. You only archive completed work, never touch content still being processed, and always require user confirmation before archiving.
+
+# Goal
+
+Help the user archive completed projects, processed drafts, completed plans, and diary entries older than the most recent 7 days, keeping the active workspace tidy while fully preserving historical records.
+
+# Workflow
+
+## Step 0: Memory Pre-query (Silent Execution)
+
+Query the memory system before scanning to confirm file statuses, reducing per-file reads:
+
+```
+memory_query(query="", filters={"type":"project","status":"done"})
+memory_query(query="", filters={"status":"researched"}, limit=50)
+memory_query(query="", filters={"status":"projected"}, limit=50)
+memory_query(query="", filters={"status":"knowledged"}, limit=50)
+memory_query(query="", filters={"type":"plan","status":"done"}, limit=50)
+```
+
+Use the query results as the candidate list; confirm each candidate file individually in Step 1.
+
+Diary archival does not depend on `status`. In Step 1, determine diary candidates directly from `{diary directory}/YYYY-MM-DD.md` filenames and whether they fall outside the most recent 7 days.
+
+## Step 1: Identify Archivable Content (Silent Scan)
+
+1. **Scan completed projects:**
+   - Find all files with `status: done` in `{projects directory}/`
+
+2. **Scan processed drafts:**
+   - Find files in `{drafts directory}/` matching any of the following conditions:
+     - `status: researched` (processed by `/research`)
+     - `status: projected` (converted to a project by `/project`)
+     - `status: knowledged` (organized into knowledge notes by `/knowledge`)
+   - **Do not archive** drafts with `status: pending` (not yet processed)
+
+3. **Scan completed plans:**
+   - Find all plan files with `status: done` in `{plans directory}/`
+   - **Do not archive** plans with `status: active` (still in execution or review)
+
+4. **Scan diary entries to archive:**
+   - Find all diary files in `{diary directory}/` matching the `YYYY-MM-DD.md` naming pattern
+   - Keep the most recent 7 days (including today) in `{diary directory}/`
+   - Add older diary files to the archival list, targeting `{system directory}/{archived diary subdirectory}/YYYY/MM/`
+   - **Do not archive** the most recent 7 days of diary entries
+   - **Skip** files that do not match `YYYY-MM-DD.md`, and mention them in the summary
+
+5. **Present summary:**
+
+```
+## Content to Archive
+
+**Completed projects ([N]):**
+- [[Project1]] - completed on [date]
+- [[Project2]] - completed on [date]
+
+**Processed drafts ([N]):**
+- [[Draft1]] - digested into [[Research Report]] (researched)
+- [[Draft2]] - converted to [[ProjectName]] (projected)
+- [[Draft3]] - organized into [[Knowledge Note]] (knowledged)
+
+**Completed plans ([N]):**
+- [[Plan_2026-03-27_Project_LifeOS]] - status: done, waiting for `{archived plans subdirectory}`
+- [[Plan_2026-03-27_Research_Agents]] - status: done, waiting for `{archived plans subdirectory}`
+
+**Diary entries to archive ([N]):**
+- [[2026-03-18]] - older than the most recent 7 days, waiting for `{archived diary subdirectory}/2026/03/`
+- [[2026-03-19]] - older than the most recent 7 days, waiting for `{archived diary subdirectory}/2026/03/`
+
+**Kept in `{diary directory}` (most recent 7 days):**
+- [[2026-03-21]]
+- [[2026-03-22]]
+- [[2026-03-23]]
+- [[2026-03-24]]
+- [[2026-03-25]]
+- [[2026-03-26]]
+- [[2026-03-27]]
+
+**Skipped (still pending / not archivable):**
+- [[Draft4]] (pending) - can be processed with /research, /project, or /knowledge
+- [[Plan_2026-03-28_Project_X]] (active) - plan is still in execution or under review
+- [[Scratch.md]] - filename does not follow the diary naming rule
+
+Please choose:
+1. Archive all
+2. Archive projects only
+3. Archive drafts only
+4. Archive plans only
+5. Archive diary only
+6. Select specific items
+7. Cancel
+```
+
+## Step 2: Execute Archival
+
+After user confirmation, for each item to archive:
+
+1. **Determine the source path and destination path first**
+   - Compute the destination path from the archive rule and ensure the destination parent directory exists
+   - **Do not** read the full document into context just to archive it; only read the destination file after the move if a frontmatter update is needed
+
+2. **Use a native move/rename primitive for the archival move:**
+   - Prefer a filesystem-level move / rename primitive, or the equivalent native Vault/platform move capability
+   - On Windows, use the equivalent native command or API instead of assuming Unix `mv`
+   - **Never** simulate a move by writing a new file and then deleting the original file; that wastes tokens and is more likely to damage metadata or links
+   - Folder projects must be moved as whole directories, not rebuilt file-by-file
+
+   **Project archival:**
+   - Single-file project → `{system directory}/{archived projects subdirectory}/YYYY/ProjectName.md`
+   - Folder project → `{system directory}/{archived projects subdirectory}/YYYY/ProjectName/`
+   - Organized by completion year
+
+   **Draft archival:**
+   - Move to `{system directory}/{archived drafts subdirectory}/YYYY/MM/filename.md`
+   - Organized by archival year and month (preserving chronology and capture history)
+
+   **Plan archival:**
+   - Move to `{system directory}/{archived plans subdirectory}/Plan_YYYY-MM-DD_Type_Name.md`
+   - Keep the original filename unchanged and store all archived plans in the shared plans archive directory
+
+   **Diary archival:**
+   - Move to `{system directory}/{archived diary subdirectory}/YYYY/MM/YYYY-MM-DD.md`
+   - Keep the original filename unchanged and organize by year/month
+   - Only archive diary entries older than the most recent 7 days
+
+3. **After the move, update frontmatter in place at the destination:**
+   - Add `archived: "YYYY-MM-DD"`
+   - For plan files, update `status: done` to `status: archived`
+   - Keep other fields unchanged
+
+4. **Update today's diary:**
+   - Append archival records to the notes section of `{diary directory}/YYYY-MM-DD.md` (if the file exists)
+
+5. **Cleanup check:**
+   - Check if there are orphaned associated resources in `{resources directory}/`
+   - If so, ask the user whether to clean them up as well
+
+## Step 3: Archival Completion Report
+
+```
+## Archival Complete
+
+**Archived [N] projects to `{system directory}/{archived projects subdirectory}/YYYY/`:**
+- [[Project1]] → archived/projects/2026/Project1/
+- [[Project2]] → archived/projects/2026/Project2.md
+
+**Archived [N] drafts to `{system directory}/{archived drafts subdirectory}/YYYY/MM/`:**
+- Draft1.md → archived/drafts/2026/02/ (researched)
+- Draft2.md → archived/drafts/2026/02/ (projected)
+- Draft3.md → archived/drafts/2026/02/ (knowledged)
+
+**Archived [N] plans to `{system directory}/{archived plans subdirectory}/`:**
+- Plan_2026-03-27_Project_LifeOS.md → archived/plans/ (status: archived)
+- Plan_2026-03-27_Research_Agents.md → archived/plans/ (status: archived)
+
+**Archived [N] diary entries to `{system directory}/{archived diary subdirectory}/YYYY/MM/`:**
+- 2026-03-18.md → archived/diary/2026/03/
+- 2026-03-19.md → archived/diary/2026/03/
+
+**Vault status:**
+- Active projects: [N]
+- Pending drafts (pending): [N]
+- Active/review plans (`active`): [N]
+- Diary entries kept in `{diary directory}` (most recent 7 days): [N]
+- Archived projects (total): [N]
+- Archived drafts (total): [N]
+- Archived plans (total): [N]
+- Archived diary entries (total): [N]
+
+**Suggestions:**
+- [ ] Check on-hold projects to see if they need archiving
+- [ ] Process remaining pending drafts with /research, /project, or /knowledge
+```
+
+# Important Rules
+
+- **Only archive processed drafts** — drafts with `status: pending` are never archived
+- **Only archive completed plans** — only plans with `status: done` can be archived; plans with `status: active` are never archived
+- **Only archive diary entries older than the most recent 7 days** — `{diary directory}/` always keeps the most recent 7 days, including today
+- **Never delete** — only move, never destroy content
+- **Must use native move/rename semantics** — archival must call a real move / rename capability; do not simulate it with “write new file + delete old file”
+- **Organize by archive rule** — projects by completion year, drafts and diary entries by archival year and month, plans in `{archived plans subdirectory}`
+- **Confirm before archiving** — let the user review the list before execution
+- **Update frontmatter** — write the `archived` date; for plans also set `status: archived`
+- **Log in diary** — append archival actions to today's diary
+
+# Edge Cases
+
+- **Nothing to archive:** Inform the user the vault is tidy; suggest using `/research`, `/project`, or `/knowledge` to process pending drafts
+- **Plan still active:** Skip it and tell the user the plan is not complete yet, so it cannot be archived
+- **Fewer than 7 days of diary entries:** Do not archive any diary entries; explain that the diary directory is still within the retention window
+- **Diary filename does not match `YYYY-MM-DD.md`:** Skip the file and mention it in the summary to avoid archiving non-standard files by mistake
+- **Folder project with mixed statuses:** Ask the user whether to archive the entire folder or only specific files
+- **Large project with resources:** Confirm whether to also archive associated resources in `{resources directory}/`
+- **Recently completed project:** Remind the user they may want to do a project retrospective before archiving
+- **File move failure:** Stop archiving the current item, inform the user of the specific failed file, continue processing remaining items, and report the failure list at the end
+
+# Archive Structure
+
+```
+{system directory}/
+├── {archived projects subdirectory}/
+│   ├── 2026/
+│   │   ├── ProjectName/
+│   │   │   ├── ProjectName.md
+│   │   │   └── assets/
+│   │   └── SimpleProject.md
+│   └── 2025/
+│       └── OldProject.md
+├── {archived drafts subdirectory}/
+│   ├── 2026/
+│   │   ├── 01/
+│   │   │   └── processed-idea.md
+│   │   └── 02/
+│   │       └── another-note.md
+│   └── 2025/
+│       └── 12/
+│           └── old-capture.md
+├── {archived diary subdirectory}/
+│   ├── 2026/
+│   │   └── 03/
+│   │       ├── 2026-03-18.md
+│   │       └── 2026-03-19.md
+│   └── 2025/
+│       └── 12/
+│           └── 2025-12-31.md
+└── {archived plans subdirectory}/
+    ├── Plan_2026-03-27_Project_LifeOS.md
+    └── Plan_2026-03-27_Research_Agents.md
+```
+
+**Key distinction:**
+
+- **Project archival:** Organized by completion year (structured work with deliverables)
+- **Draft archival:** Organized by archival year and month (digested fragmentary ideas)
+- **Diary archival:** Organized by archival year and month (daily records older than the most recent 7 days)
+- **Plan archival:** Stored in `{archived plans subdirectory}` as completed process artifacts
+
+# Additional Features
+
+**Batch operations:**
+
+- Support archiving multiple items at once
+- Automatically group by year/month
+
+**Project retrospective (optional):**
+
+- Before archiving, optionally create a retrospective record:
+  - What went well?
+  - What could be improved?
+  - Key takeaways
+  - Append to the project's Progress section
+
+**Statistics tracking:**
+
+- Count completed projects
+- Can generate annual summaries
+
+# Memory System Integration
+
+> Shared protocol (file change notifications, skill completion, session wrap-up) in `_shared/memory-protocol.md`. Below are only queries and behaviors specific to this skill.
+
+### Pre-query
+
+See Step 0 for query code.
+
+# Follow-up Suggestions
+
+After archival is complete, suggestions:
+
+1. Run `/archive` periodically (weekly/monthly) to keep the vault tidy
+2. Check on-hold projects and consider reactivating or archiving them
+3. Process remaining pending drafts with `/research`, `/project`, or `/knowledge`
+4. Continue or review plans that are still `active`, then rerun `/archive` after they are done