git:20260606.b0f0051 to git:20260608.0b5a87c

24 added, 24 removed. Audit A to A.

---

name: seo-outline-designer

sheetId: "1.22"

- description: "SEO 流程第八棒：把 SEO Brief 變成文章大綱與 FAQ 區塊，輸出與 article-drafter 相容的交棒摘要。對應 v2 流程圖「架構文章：大綱設計」與「建立 FAQ」。當使用者交出 Brief 交棒包、說「設計大綱」、「做 FAQ」時觸發。只做大綱與 FAQ，實際撰寫交給 article-drafter。"

+ description: "Stage 8 of the SEO pipeline: turn the SEO Brief into an article outline and FAQ section, outputting a handoff summary compatible with article-drafter. Corresponds to the v2 flow diagram's 'Structure article: outline design' and 'Build FAQ'. Triggers when the user hands over a Brief handoff packet and says '設計大綱' or '做 FAQ'. Only handles the outline and FAQ; the actual writing is handed off to article-drafter."

category: brand-marketing

project: seo-outline-designer

platform: claude

status: WIP

author: Peter Tu

- input: "seo-brief-writer 的 SEO_PACKET ▸ Brief；可選：是否補充資訊（其他參考文章）、業主第一手資訊"

- process: "依 outline-patterns 設計 H2/H3 大綱（answer-first 開場）→ 由 Brief 的必答題建 FAQ → 決定是否補資訊 → 人工審核 → 輸出 article-drafter 相容交棒摘要"

- output: "文章大綱 + FAQ + 目標關鍵字的交棒摘要，交給 article-drafter（1.06）撰寫"

+ input: "seo-brief-writer's SEO_PACKET ▸ Brief; optional: whether to supplement information (other reference articles), client first-hand information"

+ process: "Design the H2/H3 outline per outline-patterns (answer-first opening) → build the FAQ from the Brief's must-answer questions → decide whether to supplement information → human review → output an article-drafter-compatible handoff summary"

+ output: "Article outline + FAQ + handoff summary of target keywords, handed off to article-drafter (1.06) for writing"

synergy: ["article-drafter"]

---

# SEO Outline Designer

```bash

npx skills add https://github.com/peter-tu-zynkr/zynkr-skill-builder --skill seo-outline-designer

```

- SEO 流程第八棒，對應流程圖「架構文章」與「建立 FAQ」。它是 SEO 前半段與既有寫作管線的**接點**：產出的交棒摘要刻意做成 `article-drafter`（1.06）能直接吃的格式（架構 + 各章節要點），並額外帶上目標關鍵字、FAQ 與 AEO 要求。

+ Stage 8 of the SEO pipeline, corresponding to the flow diagram's 'Structure article' and 'Build FAQ'. It is the **junction** between the front half of the SEO pipeline and the existing writing pipeline: the handoff summary it produces is deliberately formatted so `article-drafter` (1.06) can consume it directly (structure + per-section talking points), and additionally carries the target keywords, FAQ, and AEO requirements.

---

## Resources you'll use

- > **知識來源**：本 skill 用到的 rubric/範本優先從 SEO Knowledge Base 的「01 Rubrics & Templates」(Drive，google-workspace MCP，依名稱 search) 讀取；取不到時 fallback 本地 `./references/`。對照表見 `seo-article-pipeline/seo-pipeline-config.md`。

+ > **Knowledge source**: The rubrics/templates this skill uses are read preferentially from the SEO Knowledge Base's "01 Rubrics & Templates" (Drive, google-workspace MCP, search by name); when unavailable, fall back to the local `./references/`. See the mapping table in `seo-article-pipeline/seo-pipeline-config.md`.

- - **大綱型態**：`./references/outline-patterns.md`

- - **下游**：`article-drafter`（1.06）撰寫、`article-title-suggester`（1.09）下標題、`article-editor`（1.07）校稿

- - **SEO 知識庫資料夾 ID**：`<your-seo-kb-folder-id>`

+ - **Outline patterns**: `./references/outline-patterns.md`

+ - **Downstream**: `article-drafter` (1.06) writes, `article-title-suggester` (1.09) titles, `article-editor` (1.07) proofreads

+ - **SEO Knowledge Base folder ID**: `<your-seo-kb-folder-id>`

- ## Step 1 — 接收 Brief

+ ## Step 1 — Receive the Brief

- 讀取 `SEO_PACKET ▸ Brief`。

+ Read `SEO_PACKET ▸ Brief`.

- ## Step 2 — 決定是否補充資訊（HITL 決策）

+ ## Step 2 — Decide whether to supplement information (HITL decision)

- 對應流程圖菱形「是否要補充資訊？」。若 Brief 標了 `[需 Peter 補]` 或缺第一手素材：

- - 是 → 請使用者提供其他參考文章 / 業主第一手資訊（「詢問業主第一手資訊」），補進來。

- - 否 → 直接設計大綱。

+ Corresponds to the flow diagram's diamond "Need to supplement information?". If the Brief is marked `[需 Peter 補]` or is missing first-hand material:

+ - Yes → ask the user to provide other reference articles / client first-hand information ("ask the client for first-hand information") and add it in.

+ - No → design the outline directly.

- ## Step 3 — 設計大綱（answer-first）

+ ## Step 3 — Design the outline (answer-first)

- 依 `./references/outline-patterns.md`：開場即答（搶 AEO）→ H2/H3 骨架，每個 H2 標一個要點方向＋對應目標/輔助關鍵字落點。**每章給 3 個可寫要點**（沿用 article-style-selector 的交棒慣例，讓 drafter 能直接寫）。

+ Per `./references/outline-patterns.md`: answer up front in the opening (to capture AEO) → H2/H3 skeleton, with each H2 marking one talking-point direction plus the placement of the corresponding target/supporting keywords. **Give 3 writable talking points per section** (following article-style-selector's handoff convention, so the drafter can write directly).

- ## Step 4 — 建立 FAQ

+ ## Step 4 — Build the FAQ

- 把 Brief 的必答題（3–5 題）寫成 FAQ 區塊，答案精簡可被 AI 引用（給 schema 用）。對應「根據大綱和 Brief 建立 FAQ」。

+ Write the Brief's must-answer questions (3–5 questions) into an FAQ section, with concise answers that can be cited by AI (for schema use). Corresponds to "build the FAQ from the outline and Brief".

- ## Step 5 — 人工審核大綱與 FAQ（HITL）

+ ## Step 5 — Human review of the outline and FAQ (HITL)

- 對應「審核大綱和 FAQ」。確認後存「文章大綱」「FAQ」工作檔。

+ Corresponds to "review the outline and FAQ". Once confirmed, save the "article outline" and "FAQ" working files.

- ## Step 6 — 輸出 article-drafter 相容交棒摘要

+ ## Step 6 — Output an article-drafter-compatible handoff summary

```

✅ 大綱與 FAQ 已確認（SEO）

**選定架構：** <對應 article-style-selector 的某型，如思維流程型>

**目標關鍵字：** 主 <...> ｜輔 <...>

**章節要點：**

**第一章：<H2>**（關鍵字落點：<...>）

1. <要點>

2. <要點>

3. <要點>

**第二章：…**

…

**FAQ（供 AEO / schema）：**

- Q：… / A：…（精簡）

**AEO 要求：** 開頭即答句「<...>」；命名框架「<...>」

**CTA：** <B2B discovery / lead magnet>

大綱與要點已確認，可交棒給 article-drafter 進行段落撰寫。

```

## Outputs

- 文章大綱 + FAQ + 交棒摘要（與 `article-drafter` 相容）。

+ Article outline + FAQ + handoff summary (compatible with `article-drafter`).

## Limitations

- 不撰寫段落、不下標題、不校稿——交給既有 1.06 / 1.09 / 1.07。

+ Does not write paragraphs, set titles, or proofread — those go to the existing 1.06 / 1.09 / 1.07.