startup

Start-work continuation assistant (three-tier)

When a new conversation begins, help the user quickly get into the context of "where did we leave off", avoiding explaining from scratch.

Core principles

1. Starting work is "read", wrapping up is "write"—this skill only reads and reports, it does not modify any files
2. Do not proactively git pull(to avoid overwriting local uncommitted changes, only remind "do you want to pull")
3. Skip if fetched within 30 minutes(to avoid redundancy across multiple conversations on a single machine)
4. Read Obsidian only when needed—L3 notes are detailed background material; by default, starting work does not read them, only lists the paths
5. With the shutdown skill it is adual relationship: shutdown saves in, start-work reads out

Tier detection (at start of work, see which tier "this project" has been built up to)

• L1: the project has AGENTS.md／handoff.md → read
• L2: the project has .git → do a git check
• L3：AGENTS.md The sync tier table has an Obsidian path registered, andthere are currently available Obsidian MCP tools(for example, tools that can list vault directories and read/write notes) → list the note paths (do not proactively read)

When determining L3, look at "what tools you actually have on hand", and do not assume specific tool names—different Obsidian MCPs have different names. Note: the basis for detection is "what the project has", not "what the computer has". When a lower-tier computer opens a higher-tier project, do what can be done and note what cannot (graceful degradation).

Start-work SOP (execute in order)

L1: Read the blueprint and handoff file (always execute)

1. Read AGENTS.md: project goals, roadmap progress, work conventions (summary, do not dump the full text)
2. Read handoff.md: where we left off last time, current status, next step, notes
3. Check the "Last updated" field：
   • Get this computer's name—Windows (PowerShell) uses $env:COMPUTERNAME; Mac/Linux uses hostname
   • Ifthe updater's computer name ≠ this computer → specially mark "⚠️ Last time work was wrapped up on another computer (name)", and confirm that cloud drive sync has completed (check whether the file timestamp of handoff.md matches the time written in the handoff file; if the local file is obviously too old, remind to wait for cloud sync to finish before starting work)
   • If handoff.md is much older than AGENTS.md → remind that "work may not have been formally wrapped up last time"

Fallback (legacy project compatibility): if the project does not have AGENTS.md／handoff.md：

• Has Obsidian MCP → instead read <你的 vault>/<專案資料夾名>/專案工作流程.md or 工作筆記.md 's "where we left off" section
• After reading, suggest: "This project does not yet have AGENTS.md + handoff.md. Do you want to use 'Initialize Project' to add them?" (suggest only, do not proactively create)

L2: git check (only if the project has .git )

1. Local status：git status --short
   • clean → "local working tree is clean"
   • There are uncommitted changes → list them, and remind: "There were unfinished changes last time—do you want to continue or discard them?"
2. Remote status (30-minute rule)：
   1. First check the last modified time of .git/FETCH_HEAD (just read the timestamp with the file tool you have on hand;do not use shell syntax that only exists on a certain platform）
   2. The file does not exist, or it ismore than 30 minutes from now → run:

      git fetch origin
      

   3. Then check how many commits behind it is:

      git rev-list --count "HEAD..@{u}"
      

      The quotes cannot be omitted: PowerShell will treat unquoted @{...} as hashtable syntax and report an error. If it reports an error like "no upstream branch" → treat it as 0, and note "upstream branch not yet configured" in the report.

   4. Behind > 0 → remind: "There are N new commits on the remote, do you want to git pull ?"do not pull proactively
3. Cross-checking safeguard: if handoff.md says "Git push: ✅" but the remote has no corresponding new commit → warn: "The last shutdown may not have pushed successfully; it is recommended to confirm before starting work"

L3: Obsidian notes (only list if registered; do not read proactively)

1. List the note paths in the report (e.g.,<專案資料夾名>/專案工作流程.md), and note "I will read them when detailed background is needed"
2. Read proactively only in two cases:handoff.md 's "Next step" explicitly points to the note content, or the user requests it

Report + suggested next step

Give the usera structured summary(do not be verbose):

📂 專案：<資料夾名>（第 N 層級）
📘 上次做到哪：<handoff 摘要 1-2 句>（<時間>，<更新者> @ <電腦名>）
🔧 本地 git：<clean｜有 N 個未 commit 變動｜—（L1 專案）>
🌐 遠端：<最新｜落後 N commits，建議 git pull｜—>
🧠 Obsidian：<筆記路徑，需要時再讀｜—>
➡️ 建議下一步：
   1. <handoff「下一步」第 1 項>
   2. <可選：第 2 項>

要從哪個方向開始？

Finallywait for the user to choose a direction, do not continue on your own without permission.

Things you should not do

• ❌ Proactively git pull(it will conflict with local uncommitted changes)
• ❌ Modify AGENTS.md／handoff.md/ Obsidian notes (that is shutdown work)
• ❌ Force-create one when there is no handoff file (ask the user first)
• ❌ Read the full Obsidian note at the start of work (violates the layered design of "read only when needed")
• ❌ Dump the full contents of the blueprint and handoff filein full(summarize and keep it concise)

Dual relationship with shutdown

Aspect	Shutdown	Startup
Main action	Summarize what was done today	Summarize what was done last time
AGENTS.md / handoff.md	Write	Read
Git action	add + commit + push	status + fetch (no pull)
Obsidian	Write detailed records	Only list paths, read only when needed
External side effects	Push to GitHub, modify files	None(read-only, report-only)

Notes

• All messages useTraditional Chinese
• The project blueprint filename is fixed asall uppercase AGENTS.md(cross-Agent open standard). Mac/Linux are case-sensitive; writing it in lowercase will result in "the file exists, but the Agent cannot read it"