菜单
daodao Notion→Issue→Plan→PR 自動化 pipeline 的 routine 行為規範。Use when running Routine A/B, implementing an auto issue, opening a pipeline PR, or writing pipeline comments. Triggered by keywords: routine, pipeline, auto issue, handler, agentic phase, notion-sync, dispatch.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
PR merge 後的收尾流程：歸檔 openspec change、更新 docs/product 功能狀態、校準地圖文件。Use when a PR is merged, the user says 合併了/merged/上線了, or after confirming a PR's merge status.
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.
| name | notion-pipeline |
| description | daodao Notion→Issue→Plan→PR 自動化 pipeline 的 routine 行為規範。Use when running Routine A/B, implementing an auto issue, opening a pipeline PR, or writing pipeline comments. Triggered by keywords: routine, pipeline, auto issue, handler, agentic phase, notion-sync, dispatch. |
daodao 自動化 pipeline 行為規範。Routine A/B 在 agentic phase 前必須載入此 skill。
Monorepo root: /Users/xiaoxu/Projects/daodao
NOTION_API_KEY / NOTION_DB_ID / GITHUB_TOKEN），缺任一 → abort.automation-paused 不存在，否則 exit 0flock -n /tmp/notion-sync.lock pnpm tsx bin/notion-sync/sync.ts.omc/logs/notion-sync-latest.log 後 80 行pnpm tsx bin/pipeline-status.ts → commit + push（[skip ci]）Issue body 模板 → 見 references/templates.md#issue-body
階段 0：cd monorepo root；確認 .automation-paused 不存在
階段 1：pnpm tsx bin/routine-dispatch/spec-merged-scan.ts
成功 → 更新 state-store.json:last_scan_at；失敗 → 跳過 timestamp 更新，繼續
階段 2：對 8 個 sub-repo 掃 auto issue（最多 3 個）
gh issue list --repo daodaoedu/<repo> --label auto --state open --json number,labels --limit 3
對每個 issue：bash bin/routine-dispatch/main.sh <repo> <issue-num>
階段 3：PR patrol（verbatim 保留既有 trig_01KATY 邏輯）
Sub-repos: daodao-server / daodao-f2e / daodao-ai-backend / daodao-storage / daodao-admin-ui / daodao-infra / daodao-mcp / daodao-worker
高風險（storage / infra）：state.ts 規則 0 強制 plan-only，不論 issue label
執行前讀取：
openspec/changes/{change_id}/docs/adr/（grep 關鍵字）auto/{issue_num}-{slug}依 scope 執行流程 → 見 references/agentic-flows.md
PR body 模板 → 見 references/templates.md#pr-body
留言時直接套用 → 見 references/templates.md#comments
{type}({area}): {description}
Co-Authored-By: daodao-pipeline <noreply@daodaoedu.github.com>
type: feat / fix / test / plan / chore
不使用 format-commit skill（那是互動式的）
| 情況 | 處置 |
|---|---|
| token 超 cap | 加 human-coding label，留 comment，exit |
偵測到 human-driving | 呼叫 handoff.sh，不繼續 |
| verification 2 次失敗 | 加 human-coding，留 comment，exit |
| tool 被 blocklist 擋 | log BLOCKED，exit 3 |
| openspec-headless exit 2 | 留 comment 說明缺什麼，exit |
詳細 ADR 與架構 → docs/automation/architecture.md
執行：pnpm tsx bin/routine-c/sync-done.ts [--dry-run] [--hours <n>]
流程：
.automation-paused 不存在，否則 exit 0auto label PRNotion page ID: \...``Done建議在 Routine B 跑完後接著執行，或在確認 PR 已 merge 時手動觸發。