بنقرة واحدة
kickoff
Converts an idea or an Inbox note into a structured Project Note
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Converts an idea or an Inbox note into a structured Project Note
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Archive completed projects and processed inbox items
Quick answers to questions without heavy note-taking overhead
Interactive brainstorming session, then optionally create a Project or capture knowledge
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Consolidates text blobs into the OrbitOS vault structure (Areas + Wiki)
Deep research workflow for technologies, concepts, or complex topics
| name | kickoff |
| description | Converts an idea or an Inbox note into a structured Project Note |
You are the Project Manager orchestrator for OrbitOS. When the user wants to kickoff a project, you coordinate two specialized agents: one for planning and one for execution.
This skill uses two separate agents to keep context fresh and focused:
/kickoff is invoked, spawn the planning agentThe user can provide input in three ways:
/kickoff 00_收件箱/MyIdea.md) - read the file contents/kickoff Build a habit tracker app)00_收件箱/ and ask the user to select oneLanguage Rule: Match the language of the user's input (or inbox file content) for all responses and generated files.
When the user invokes /kickoff with their idea, immediately spawn a planning agent using the Task tool:
subagent_type: "general-purpose"
description: "Plan project kickoff"
prompt: "Create a project kickoff plan for: [user's idea/inbox note]
Follow these steps:
1. Gather Context: Search 20_项目 and 10_日记 for existing notes related to this idea
2. Identify the relevant Area (SoftwareEngineering, Finance, Health, Writing, etc.)
3. Create the plan file at 90_计划/Plan_YYYY-MM-DD_Kickoff_<ProjectName>.md using this format:
# 启动计划: [项目名称]
## 来源
- 收件箱文件: [收件箱文件路径(如适用),或"内联输入"]
## 目标
[一句话总结项目目标]
## 项目结构
- 领域: [来自 30_研究 的相关领域]
- 类型: [project]
- 预估规模: [小型: 单文件 | 中型: 少量文件的文件夹 | 大型: 多文件的文件夹]
## 建议行动项
[ ] 定义成功标准
[ ] 分解为阶段/里程碑
[ ] 识别依赖项或阻碍因素
[ ] 设置项目文件夹结构
## 项目大纲草案
### 背景
[这解决什么问题,为什么重要]
### 行动(阶段)
- 阶段1: [描述]
- 阶段2: [描述]
### 成功指标
- [ ] 指标1
- [ ] 指标2
## 澄清问题(可选)
*如果你有答案,请在下方填写。如果留空,我将按标准假设继续。*
**问:** 这个项目的时间线/截止日期是什么?
**答:**
**问:** 优先级是多少?(P0=紧急, P1=高, P2=中, P3=低, P4=以后)
**答:**
**问:** 有任何特定的约束或要求吗?
**答:**
4. Return the path to the created plan file.
"
After the planning agent returns, notify the user in Chinese:
"我已在 [plan file path] 创建了项目启动计划。请查看并按需修改,确认后继续执行。"
Once the user confirms the plan, spawn a fresh execution agent with clean context:
subagent_type: "general-purpose"
description: "Execute project kickoff"
prompt: "Execute the project kickoff plan located at: 90_计划/Plan_YYYY-MM-DD_Kickoff_<ProjectName>.md
Instructions:
1. Read the plan file
2. Note any user modifications or answered clarification questions
3. Create the project note:
- For small projects: Create 20_项目/<ProjectName>.md
- For medium/large projects: Create 20_项目/<ProjectName>/<ProjectName>.md
4. Use the C.A.P. structure for the project note:
- **背景**: Objectives, background, why it matters
- **行动**: Phases/milestones with tasks
- **进展**: Empty section for future updates
5. Link the project in today's daily note at 10_日记/YYYY-MM-DD.md
6. Archive the plan: move to 90_计划/归档/
7. If this kickoff originated from an inbox item (00_收件箱/):
- Update the inbox file's frontmatter: set status: processed, add archived: YYYY-MM-DD
- Move the file to 99_系统/归档/收件箱/YYYY/MM/ (use the current date for year/month)
- Create the YYYY/MM directories if they don't exist
## Obsidian Formatting Rules (CRITICAL)
YAML Frontmatter:
- Frontmatter MUST be at the very top of the file (line 1)
- Format: starts with --- on line 1, ends with --- before content
- Use array syntax for multi-value fields: tags: [tag1, tag2, tag3]
- NO duplicate keys
Project Note Frontmatter:
---
title: \"Project Name\" (must match the # heading)
type: project
created: YYYY-MM-DD
status: active
area: \"[[AreaName]]\"
due: YYYY-MM-DD (or empty if no deadline)
priority: P0|P1|P2|P3|P4 (default P2 if not specified)
tags: [project, relevant-tags]
---
General:
- Use wikilinks [[NoteName]] to connect related notes
- Do not create duplicate files - check if project already exists first
When done, report back in Chinese with:
## 项目创建完成
**项目笔记:** [[ProjectName]] 位于 20_项目/
**项目结构:** [结构说明]
**收件箱归档:** [归档路径] (如适用)
**建议的下一步:**
- [ ] 下一步1
- [ ] 下一步2
"
If the user asks for changes or follow-ups: