Menu
PR merge 後的收尾流程：歸檔 openspec change、更新 docs/product 功能狀態、校準地圖文件。Use when a PR is merged, the user says 合併了/merged/上線了, or after confirming a PR's merge status.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
PRD 快速生成、需求補洞、優化顧問三合一工具。從需求產出完整 PRD，多角色檢視缺漏，再優化成工程師友善文件。Use when writing a new PRD, reviewing an existing PRD for gaps, or optimizing PRD readability. Triggered by keywords: PRD, 需求文件, 產品規格, 規格書, user story, acceptance criteria, 驗收條件.
依島島 GTM 策略產出 TA 導向的行銷內容——部落格文章、社群貼文（Threads/IG/FB）、回覆別人的文案。Use when user says "寫一篇文章"、"寫貼文"、"幫我回覆這篇"、"招生文"、"揪團文"、"寫 threads"、"content"、"文案"。自動套用語氣鐵律、TA 痛點語言與模板 CTA。
規劃或實作任何 product 功能前，先用程式碼驗證 docs/product 的狀態標示是否為真。docs/product 的 PRD/FRD 狀態普遍落後於程式碼——直接照文件規劃會重做一個早就上線的功能。Use before planning a feature, estimating scope, writing an OpenSpec change, or answering "這功能做了沒". Triggered by keywords: PRD, FRD, 規劃, 這功能, 還沒做, 規劃中, roadmap, scope, plan feature.
Use when asked to summarize or analyze monthly user activity and interaction data. Queries DB for MAU, DAU trends, check-in counts, reactions, comments, follows, retention rate, and top users/practices. Generates narrative insights via daodao-ai-backend LLM and outputs a markdown report or writes to Notion.
Use when sending personalized congratulation emails to users who completed a practice. Queries the DB for completed practices, generates personalized email content via daodao-ai-backend LLM, previews samples for confirmation, then sends via email API. Always runs in dry-run mode first.
在 daodao 任務 Notion DB 建立新卡片。Use when user says "開 Notion 卡"、"建 notion 單"、"新增任務"、"create notion card"、"開一張卡"、"記到 notion"。從對話或報告自動推斷欄位，互動確認後建立。
| name | post-merge-wrapup |
| description | PR merge 後的收尾流程：歸檔 openspec change、更新 docs/product 功能狀態、校準地圖文件。Use when a PR is merged, the user says 合併了/merged/上線了, or after confirming a PR's merge status. |
PR merge 不是流程終點。少了收尾，openspec change 會堆積、docs/product 的狀態標示會腐爛（文件寫「規劃中」但功能早已上線）。本 skill 把收尾變成機械步驟。
pull_request_read 或 gh pr view；使用者親口說 merged 也算）openspec/changes/ 下有進行中的 change）.claude/skills/openspec-archive-change/SKILL.mddocs/product 位於 daodao repo。這步是根治「文件說規劃中、程式碼已上線」的關鍵，不可跳過不提。
狀態：已上線（2026-07-18））codebase-map，並更新頂部「最後校準」日期system-map（複製式共用，改一份要同步六份）以 checklist 回報每一步的實際結果，如實標注未執行的項目與原因：
## Merge 收尾報告
- [x] openspec change 已歸檔 / [ ] 無對應 change
- [x] docs/product 狀態已更新：<文件路徑> / [ ] 不涉及 product 文件 / [ ] ⚠️ 需在 daodao repo 手動更新：<文件>
- [x] 地圖已校準 / [ ] 無結構性變更