inbox

/inbox

Process GTD inbox items one at a time. This is GTD's Clarify stage — the user decides what each captured thought actually IS. Your job is to make that decision fast by asking the minimum necessary follow-ups per destination.

Flow

0. Sync

git -C ${GTD_VAULT:-$HOME/gtd} pull --rebase --autostash 2>&1 | tail -3

If it reports conflicts, errors, or anything non-trivial, stop and ask the user to resolve before continuing — do not start triage on a dirty or stale tree.

1. List items

ls ${GTD_VAULT:-$HOME/gtd}/gtd/inbox/*.md 2>/dev/null | grep -v /.gitkeep$ | sort

If empty, reply inbox is clean ✨ and exit.

2. Announce

Tell the user: inboxに N件あります。1件ずつ処理します。

3. Per item (in order)

For each file:

1. Read the file. Parse its frontmatter and body.
2. Display:

   [i/N] {filename}
   ---
   {body, no frontmatter}
   

3. Ask:

   これは何ですか？
    1. Next Action (すぐできる1ステップ)
    2. Project (複数ステップ必要)
    3. Waiting-for (他人待ち)
    4. Reference (アクション不要、情報)
    5. Zettel (アイデア・ナレッジ)
    6. 捨てる
   

4. Execute the per-destination procedure below.
5. Print a single-line confirmation like → gtd/next-actions/{filename} and move on. Do NOT ask "続けますか？" — just continue to the next item. (Only stop if the user types "stop", "中断", or similar.)

4. After all items

git -C ${GTD_VAULT:-$HOME/gtd} status --short

Show the summary count (moved / deleted / created). Then ask: コミットしますか？ (y/n) — if yes:

git -C ${GTD_VAULT:-$HOME/gtd} add -A
git -C ${GTD_VAULT:-$HOME/gtd} commit -m "process inbox: {N} items"

Do NOT push. User can push themselves if they want.

Per-destination procedures

All procedures share: keep the filename as-is (it already has a timestamp), keep the body verbatim (do not rephrase), extract the creation date from the original frontmatter's created: field (use the date-only form, e.g. 2026-04-22).

1. Next Action

Ask 3 questions in sequence. Accept empty/"d"/"デフォルト" as "use default":

Context? [@computer / @phone / @errands / @home / @anywhere] (default @computer):
Energy? [low / medium / high] (default low):
Due? [YYYY-MM-DD or empty] (default empty):

Rewrite frontmatter to:

---
type: next-action
status: todo
context: "{context}"
project:
created: {original-date}
due: {due or empty}
energy: {energy}
---

Move: mv gtd/inbox/{filename} gtd/next-actions/{filename}

2. Project

Ask:

目的・成功イメージを1文で:
最初のNext Actionは何？ (空でskip):

Rewrite frontmatter:

---
type: project
status: active
created: {original-date}
target:
area:
---

Rewrite body to:

## 目的

{purpose}

## Next Action

- [ ] {first_na or "(未設定)"}

## Notes

{original body verbatim}

Move: mv gtd/inbox/{filename} gtd/projects/{filename}

If first_na is non-empty, additionally create gtd/next-actions/{TS}-{slug}.md where TS is from TZ=Asia/Tokyo date +%Y-%m-%d-%H%M and slug is a 3-4 word English slug of first_na. Content:

---
type: next-action
status: todo
context: "@computer"
project: "[[{project-filename-without-ext}]]"
created: {today}
energy: low
---

{first_na}

3. Waiting-for

Ask:

誰 待ち？:
いつまで？ [YYYY-MM-DD or empty]:

Rewrite frontmatter:

---
type: waiting-for
waiting_on: "{who}"
expected_by: {date or empty}
created: {original-date}
---

Body verbatim. Move to gtd/waiting-for/.

4. Reference

No questions. Rewrite frontmatter type: to reference, keep other fields. Move to gtd/reference/.

5. Zettel (fleeting)

No questions. Rewrite frontmatter type: to fleeting, keep other fields. Move to zettelkasten/fleeting/. (A future /zettel skill will later promote fleeting → permanent.)

6. Trash

Ask 本当に削除？ (y/n). If yes: rm gtd/inbox/{filename}.

Rules

• Never modify a file without moving (or deleting) it. If the user cancels mid-item, leave the inbox file unchanged.
• Preserve body content verbatim in all destinations except Project (where you restructure into sections but keep the original text under ## Notes).
• Don't touch .gitkeep — always skip.
• Respect interruption. On "stop" / "中断" / Ctrl+C, summarize what's been processed and offer to commit the partial progress.
• Don't push. Commit only. Pushing is the user's call.
• Don't auto-classify. Always ask the 6-choice menu, even if the content seems obvious.