Back to Details

things-morning-organizer

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Morning Review

晨间回顾

Help the user start their day by organizing their Things todos and providing a clear, prioritized briefing.
帮助用户通过整理其Things待办事项并提供清晰的优先级简报开启新的一天。

Step 0. Load Configuration

步骤0. 加载配置

Check for 
assets/config.json
in this skill's directory.
If config exists → Load it and proceed to Step 1.
If config does NOT exist → Auto-generate it:
  1. Fetch areas (
    things_get_areas
    ) and tags (
    things_get_tags
    )
  2. Fetch todos across all lists (
    things_get_today
    , 
    things_get_anytime
    , 
    things_get_upcoming
    , 
    things_get_someday
    ) to infer what each area and tag is used for
  3. Generate short descriptions and examples for each area and tag based on the todos they contain
  4. Ask the user if they have any daily routine todos (recurring tasks to auto-create on weekdays), or skip if they don't
  5. Present the generated config for confirmation, then save to 
    assets/config.json
  6. Proceed to Step 1
检查此技能目录下的
assets/config.json
文件。
若配置存在 → 加载配置并进入步骤1。
若配置不存在 → 自动生成配置：
  1. 获取区域（
    things_get_areas
    ）和标签（
    things_get_tags
    ）
  2. 获取所有列表中的待办事项（
    things_get_today
    、
    things_get_anytime
    、
    things_get_upcoming
    、
    things_get_someday
    ），以此推断每个区域和标签的用途
  3. 根据区域和标签包含的待办事项，为其生成简短描述和示例
  4. 询问用户是否有日常流程待办事项（工作日自动创建的重复任务），若无则跳过
  5. 展示生成的配置供用户确认，然后保存至
    assets/config.json
  6. 进入步骤1

Config Format

配置格式

json
{
  "areas": {
    "work": {
      "description": "Day job tasks, meetings, team communication",
      "examples": ["Prepare slides for team standup", "Coordinate with project lead"]
    },
    "personal": {
      "description": "Family, home, errands, health",
      "examples": ["Book a doctor appointment", "Handle home admin"]
    }
  },
  "tags": {
    "important": {
      "description": "Has a hard deadline, scheduled meeting, or clear strategic urgency",
      "examples": ["Finish something by a deadline", "Prepare for a scheduled meeting"]
    },
    "waiting": {
      "description": "Explicitly blocked on another person — waiting for someone or pending a response",
      "examples": ["Waiting for a review or approval", "Pending a response"]
    },
    "quick": {
      "description": "Single-step task under 15 minutes — not multi-step work",
      "examples": ["Reply to a message", "Check a status", "Approve a request"]
    }
  },
  "daily_routine": [
    { "title": "Check email", "area": null },
    { "title": "Review calendar", "area": null }
  ]
}
Areas, tags, and daily routines are fully customizable. The examples above are defaults — the user defines what fits their workflow. A 
null
area means uncategorized.
Each area and tag has up to 10 examples. Examples should cover distinct categories without overlap — no need to fill all 10 slots, just enough to represent the range. Area examples should include domain context to distinguish between areas (e.g. "Coordinate with IBM team"). Tag examples should be generic patterns about the nature of the task (e.g. "Reply to a message").
json
{
  "areas": {
    "work": {
      "description": "Day job tasks, meetings, team communication",
      "examples": ["Prepare slides for team standup", "Coordinate with project lead"]
    },
    "personal": {
      "description": "Family, home, errands, health",
      "examples": ["Book a doctor appointment", "Handle home admin"]
    }
  },
  "tags": {
    "important": {
      "description": "Has a hard deadline, scheduled meeting, or clear strategic urgency",
      "examples": ["Finish something by a deadline", "Prepare for a scheduled meeting"]
    },
    "waiting": {
      "description": "Explicitly blocked on another person — waiting for someone or pending a response",
      "examples": ["Waiting for a review or approval", "Pending a response"]
    },
    "quick": {
      "description": "Single-step task under 15 minutes — not multi-step work",
      "examples": ["Reply to a message", "Check a status", "Approve a request"]
    }
  },
  "daily_routine": [
    { "title": "Check email", "area": null },
    { "title": "Review calendar", "area": null }
  ]
}
区域、标签和日常流程完全可自定义。以上示例为默认设置——用户可根据自身工作流定义内容。
null
区域表示未分类。
每个区域和标签最多可包含10个示例。示例应涵盖不同类别且无重叠——无需填满10个位置，足够代表范围即可。区域示例应包含领域背景以区分不同区域（例如"Coordinate with IBM team"）。标签示例应为关于任务性质的通用模式（例如"Reply to a message"）。

Step 1. Gather Data

步骤1. 收集数据

Call in parallel: 
things_get_today
, 
things_get_inbox
, 
things_get_areas
, 
things_get_anytime
Check day of week with 
date
(working days Mon-Fri have daily habits).
并行调用：
things_get_today
、
things_get_inbox
、
things_get_areas
、
things_get_anytime
使用
date
工具检查星期几（工作日周一至周五包含日常习惯任务）。

Step 2. Categorize, Move & Tag

步骤2. 分类、移动与标记

Process items from Today, Inbox, and Anytime that are missing an area or tags. Skip items that already have them.
处理来自Today、Inbox和Anytime中缺少区域或标签的项目。跳过已包含区域或标签的项目。

A. Categorize Uncategorized Items

A. 分类未分类项目

For items without an area, use the config area descriptions and examples to determine the best fit and move with 
things_update_todo
. If a todo doesn't clearly fit any area, flag it in the briefing.
对于没有区域的项目，使用配置中的区域描述和示例确定最佳匹配，并通过
things_update_todo
移动项目。若待办事项无法明确匹配任何区域，在简报中标记出来。

B. Tag Untagged Items

B. 标记未标记项目

For items without tags, use the config tag descriptions and examples to determine which apply. Be conservative — only apply a tag when the todo title clearly and obviously matches the tag description and is similar to the examples. Do not infer or guess.
Wait for all 
things_update_todo
calls to complete before proceeding.
对于没有标签的项目，使用配置中的标签描述和示例确定适用的标签。请保持谨慎——仅当待办事项标题明确且明显匹配标签描述，且与示例相似时才应用标签。请勿推断或猜测。
等待所有
things_update_todo
调用完成后再继续。

Step 3. Create Daily Routine Todos (Weekdays Only)

步骤3. 创建日常流程待办事项（仅工作日）

Check if the todos from 
daily_routine
in config exist in Today. If missing, create each with 
things_add_todo
set to today, with the area from config.
Match flexibly (case-insensitive, similar wording counts). Skip on weekends.
检查配置中
daily_routine
里的待办事项是否存在于Today列表中。若缺失，使用
things_add_todo
创建每个待办事项并设置为今日，同时应用配置中的区域。
灵活匹配（不区分大小写，相似表述即可）。周末跳过此步骤。

Step 4. Prioritize & Brief

步骤4. 优先级排序与简报

Use Peter Drucker's "Effective Executive" lens — prioritize by contribution, not busyness. "First things first, second things not at all."
🔴 Must do — Deadlines, meetings, items tagged as important. "What can only I do that, if done really well, will make a real difference?" 🟡 Should do — High-impact strategic work. "What is the greatest contribution I can make?" 🟢 Could do — Non-urgent items, learning, low-priority personal. 📋 Daily Routine — Items from 
daily_routine
in config.
Output brief summary:
Good morning! [weekend note if applicable]

> "[Relevant Drucker quote for the day]"

🔴 Must do (X)
- **[item]** — [why this matters today]

🟡 Should do (X)
- **[item]**

🟢 Could do (X)
- **[item]**

📋 Daily Routine
- [routine items from config]

Categorized: X items moved
[Ambiguous items if any]
[Drucker-inspired closing nudge — e.g. "You have 3 must-dos. Protect your morning for the one that only you can do." or "Heavy list today — what can you delegate or defer?"]
Keep it tight. 30 seconds to read max.
以彼得·德鲁克《卓有成效的管理者》的视角——按贡献而非忙碌程度确定优先级。“要事第一，次要的事干脆不做。”
🔴 必须完成——截止日期、会议、标记为important的项目。“只有我能做的、且做好后会产生真正影响的事情是什么？” 🟡 应该完成——高影响力的战略工作。“我能做出的最大贡献是什么？” 🟢 可以完成——非紧急事项、学习、低优先级个人任务。 📋 日常流程——配置中
daily_routine
里的项目。
输出简要摘要：
Good morning! [weekend note if applicable]

> "[Relevant Drucker quote for the day]"

🔴 Must do (X)
- **[item]** — [why this matters today]

🟡 Should do (X)
- **[item]**

🟢 Could do (X)
- **[item]**

📋 Daily Routine
- [routine items from config]

Categorized: X items moved
[Ambiguous items if any]
[Drucker-inspired closing nudge — e.g. "You have 3 must-dos. Protect your morning for the one that only you can do." or "Heavy list today — what can you delegate or defer?"]
保持简洁，最多30秒即可读完。

Creating Todos

创建待办事项

If no config exists yet, run Step 0 first.
When the user asks to add a todo to Things:
  1. Rephrase for clarity — Convert the user's message into a clear, actionable todo title in English
  2. Assign to area — Use config area descriptions and examples to pick the best fit; default to the first area if ambiguous
  3. Schedule appropriately — Use 
    when="today"
    by default, or adjust based on context
  4. Extract details — If the message contains specific information (names, numbers, deadlines), include them in the title or notes
若配置尚未存在，先执行步骤0。
当用户要求在Things中添加待办事项时：
  1. 重新表述以确保清晰——将用户的消息转换为清晰、可执行的英文待办事项标题
  2. 分配区域——使用配置中的区域描述和示例选择最佳匹配；若不明确则默认选择第一个区域
  3. 合理安排时间——默认使用
    when="today"
    ，或根据上下文调整
  4. 提取细节——若消息包含特定信息（姓名、数字、截止日期），将其包含在标题或备注中

Silent Mode

静默模式

Activate when the argument is "silent" (e.g. 
/things-morning-organizer silent
). Designed for automated/headless execution via 
-p
mode.
Requirements:
  • Config MUST already exist — if 
    assets/config.json
    is missing, output an error message and exit
  • Skip Step 0 entirely (no configuration, no questions)
  • Execute Steps 1 → 2 → 3 → 4 in a single pass
  • Do NOT ask any questions or wait for user input
  • Do NOT use 
    AskUserQuestion
    tool
  • Output ONLY the final briefing from Step 4 (no intermediate status messages)
当参数为"silent"时激活（例如
/things-morning-organizer silent
）。专为通过
-p
模式进行的自动化/无头执行设计。
要求：
  • 配置必须已存在——若
    assets/config.json
    缺失，输出错误信息并退出
  • 完全跳过步骤0（无配置操作，无问题询问）
  • 一次性执行步骤1 → 2 → 3 → 4
  • 请勿询问任何问题或等待用户输入
  • 请勿使用
    AskUserQuestion
    工具
  • 仅输出步骤4中的最终简报（无中间状态消息）

Learning Mode

学习模式

Activate when the user asks to run in learning mode (e.g. "learning mode", "learn", "improve config").
  1. Load 
    assets/config.json
  2. Fetch todos across all lists (
    things_get_today
    , 
    things_get_anytime
    , 
    things_get_upcoming
    , 
    things_get_someday
    )
  3. Compare todos against the current config and identify gaps:
    • Todos that don't fit any existing area well
    • Todos where no tag description clearly applies but a tag probably should
    • Area or tag descriptions that are too narrow to cover the todos they contain
  4. Propose config updates — refine area and tag descriptions, add/rotate examples, add new areas or tags if needed
  5. Present the diff to the user for confirmation, then save to 
    assets/config.json
  6. Ask the user if they want to proceed with the normal morning review (Steps 1-4)
当用户要求以学习模式运行时激活（例如"learning mode"、"learn"、"improve config"）。
  1. 加载
    assets/config.json
  2. 获取所有列表中的待办事项（
    things_get_today
    、
    things_get_anytime
    、
    things_get_upcoming
    、
    things_get_someday
    ）
  3. 将待办事项与当前配置进行比较，找出差距：
    • 无法很好匹配现有区域的待办事项
    • 没有明确适用的标签描述但可能需要标签的待办事项
    • 区域或标签描述过于狭窄，无法涵盖其包含的待办事项
  4. 提出配置更新建议——优化区域和标签描述，添加/轮换示例，必要时添加新区域或标签
  5. 向用户展示差异供确认，然后保存至
    assets/config.json
  6. 询问用户是否要继续进行常规晨间回顾（步骤1-4）

Principles

原则

  • Don't change scheduling (today/tomorrow/someday) — but inbox items without a clear schedule should be moved to Today if actionable, or flagged in the briefing
  • NEVER delete or mark todos complete unless user explicitly requests it
  • Be opinionated about priority
  • Focus on contribution and impact
  • 不要更改日程安排（今日/明日/某天）——但收件箱中无明确日程的可执行项目应移至Today，或在简报中标记
  • 除非用户明确要求，否则绝不删除或标记待办事项为已完成
  • 对优先级要有明确的判断
  • 专注于贡献和影响