メニュー
每日早晨任務看板：整合 gsheet / GitHub / Heptabase Sprint whiteboard + week tag 三處任務狀態，自動建卡、合併狀態、寫入 Heptabase 當日 journal。 觸發詞：「start-day」「每日任務看板」「今日任務」「我要開始工作」 「daily task board」「整理今日任務」。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | start-day |
| description | 每日早晨任務看板：整合 gsheet / GitHub / Heptabase Sprint whiteboard + week tag 三處任務狀態，自動建卡、合併狀態、寫入 Heptabase 當日 journal。 觸發詞：「start-day」「每日任務看板」「今日任務」「我要開始工作」 「daily task board」「整理今日任務」。 |
| allowed-tools | ["Bash","Bash(heptabase *)","Bash(gh *)","Bash(uv run *)","Bash(python *)","mcp__heptabase__get_whiteboard_with_objects"] |
| model | claude-sonnet-4.6 |
幫使用者跑每日任務看板。
確認在 fstack repo 根目錄，確認 Heptabase desktop 在跑：
heptabase --version
若失敗，請使用者執行 heptabase start 後再試。
計算當週週號：
TZ=Asia/Taipei date +%G-W%V
使用 mcp__heptabase__get_whiteboard_with_objects 讀取 Sprint whiteboard（whiteboard ID: 79f11368-17a3-4263-8cb3-2028c0b4b005）。
從回傳結果中找到 section title == 當週週號（例如 2026-W18）的 section，取出其 objectIds。
⚠️ Sprint whiteboard 尚無 {week_id} section，略過 並繼續（不 abort）將 sprint whiteboard 的卡片轉為 normalized task schema，寫入 /tmp/sprint_cards.json：
[
{
"name": "<normalized title>",
"name_raw": "<original card title>",
"status": "unknown",
"sources": [{"kind": "heptabase", "id": "<card_id>", "url": null, "status_raw": "sprint_board", "last_updated": ""}],
"conflict": null,
"depends_on": [],
"card_id": "<card_id>",
"multi_match_warning": null,
"progress_note": "<從卡片內容 ## Progress / ## Goal section 抽取，無則留空>"
}
]
TZ=Asia/Taipei uv run python skills/start-day/scripts/start_day.py --sprint-json /tmp/sprint_cards.json
加 --dry-run 可預覽 markdown 不寫 journal。
從 stdout 解析 summary，回 chat：
Document codebase as-is via parallel sub-agents. Use when researching how code works, mapping architecture, or answering questions about existing systems. Auto-detects thoughts/ directory — if present, integrates historical context and syncs; if absent, skips those steps.
Create the Questions artifact before codebase research, design, planning, or implementation. Use for feature tickets, architecture changes, unclear code work, CRISPY/QRSPI Questions phase, or when the agent needs to define code-answerable unknowns and human questions before researching or planning.
Create a concise Design Concept artifact after questions and codebase research are available. Use for CRISPY/QRSPI Design phase, architecture alignment, feature design discussion, or turning current-state research into a small human-reviewable proposed shape before detailed planning.
Create an interface-first Structure Outline before detailed planning or implementation. Use for CRISPY/QRSPI Structure Outline phase, vertical planning, method signatures, type contracts, API/component boundaries, or converting an accepted design concept into end-to-end slices with verification checkpoints.
Create comprehensive handoff documents for transferring work to another agent session. Use when the user requests to create a handoff, end a session, or document work-in-progress for future continuation.
Create detailed implementation plans through interactive research and iteration. Use when starting a new feature or ticket that needs a comprehensive technical plan. Saves plans to the repo-appropriate plans location and emits Personal Knowledge events when applicable.