القائمة
Convert an idea or Inbox note into a structured DeepOrbit project. Use when the user wants to start, scope, or turn an idea into a project with a reviewable plan and C.A.P. project note.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Batched proactive check-in over vault state — silence by default, propose-approve. Use when the user asks "今天该干什么", "帮我看看有什么要做的", "有什么要我处理的", "巡检一下", "anything I should deal with", "what needs my attention", or when a scheduled heartbeat job wakes you up. Also use for evaluating WHEN rules in 99_System/Rules.
Daily planning - run a recap of yesterday's knowledge, review most recent diary, plan today, connect projects. News summaries included.
Act as the user's mentor for project and knowledge management. Use when the user asks for guidance on how to manage projects, which method to use (GTD, Zettelkasten, PARA, Atomic Habits), how to use DeepOrbit tools, asks for a vault health diagnosis, a weekly review, or wants a recipe designed for a recurring workflow.
Build a current agenda from DeepOrbit Markdown tasks. Use when the user asks what to do today, what is overdue, what is upcoming, for a task review, or for a daily planning summary across Inbox, Diary, and Projects.
Export dated DeepOrbit Markdown tasks to a portable iCalendar file. Use when the user asks to link tasks to a calendar, export ICS, or view due and scheduled tasks in Apple, Google, Outlook, or another calendar app.
Install and explain DeepOrbit's local reminder delivery for timed Markdown tasks. Use when the user says "remind me", "提醒我", "到点叫我", "定时任务", mentions cron-based reminders, asks why a notification did not fire, or wants macOS notifications for tasks carrying a due date and time.
| name | do.kickoff |
| description | Convert an idea or Inbox note into a structured DeepOrbit project. Use when the user wants to start, scope, or turn an idea into a project with a reviewable plan and C.A.P. project note. |
Keep the workflow portable. Use the current runtime's native Goal or Tracker when it exists, but keep the Markdown plan as the durable source of truth. Do not require subagents or an external self-invoking loop.
Accept an Inbox path, inline idea, or—when no input is given—offer the notes in
00_Inbox/. Read deeporbit.json for paths and language. Search related context with:
deeporbit --vault "<vault-path>" rag "<project subject>"
If semantic search is unavailable, use deeporbit ... rag --lexical-only or the
runtime's file search. Identify overlapping projects before creating a duplicate.
Create 90_Plans/Plan_YYYY-MM-DD_Kickoff_<ProjectName>.md containing:
Open it with do.obsidian-open when available. Ask for confirmation before turning
the plan into a project note because this step can reorganize the user's Inbox.
Create 20_Projects/<ProjectName>.md for a small project or
20_Projects/<ProjectName>/<ProjectName>.md for a larger one. Use frontmatter:
---
title: Project Name
type: project
created: YYYY-MM-DD
status: active
area: "[[AreaName]]"
due:
priority: P2
tags: [project]
---
Use C.A.P. sections: Context, Actions, and Progress. Link it from today's
Daily Note. Move the completed plan to 90_Plans/Archive/. For an Inbox source, set
status: processed and archived: YYYY-MM-DD, then move it to
99_System/Archive/Inbox/YYYY/MM/ without overwriting an existing file.
author: ai in frontmatter for every note you create; switch to author: mixed when substantially rewriting a human-authored note. Authorship lives in frontmatter only — never add visible badges.
Report created and moved paths plus the next concrete action. Opening a note through
Obsidian is useful but never a condition for success.