メニュー
功能完成後的收尾三連發：commit+PR → gsheet 進度同步 → (選配) Slack 通知。 觸發詞：「work-wrap-up」、「收尾」、「功能做完了」、「幫我收尾」、「wrap up」、 「wrap」、「做完了」、「push 完了」、「收工」。 依序執行：commit-commands:commit-push-pr → gsheet-progress-sync → (選配) slack-message。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | work-wrap-up |
| description | 功能完成後的收尾三連發：commit+PR → gsheet 進度同步 → (選配) Slack 通知。 觸發詞：「work-wrap-up」、「收尾」、「功能做完了」、「幫我收尾」、「wrap up」、 「wrap」、「做完了」、「push 完了」、「收工」。 依序執行：commit-commands:commit-push-pr → gsheet-progress-sync → (選配) slack-message。 |
| allowed-tools | ["Bash","mcp__slack__*","mcp__google_sheets__*"] |
| model | claude-opus-4-6 |
幫使用者完成功能開發後的標準收尾流程，步驟固定，依序執行：
使用 /commit-commands:commit-push-pr 執行：
若使用者已有 PR 或已 merge，跳過此步驟直接進行 Step 2。
使用 /gsheet-progress-sync 更新工作進度：
詢問使用者是否要發送 Slack 通知。
/slack-message 撰寫並預覽訊息後發送/brief-mode 規範，並控制在 20 秒內可讀完此 skill 需要以下 skills 已安裝：
commit-commands（本 repo 提供）gsheet-progress-sync（本 repo 提供）slack-message（本 repo 提供）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.