④段整套同步（六节 ＋ P/S/F/J ＋ 模板）＋ open-design 移到技能根

一、④段整套同步（用户选候选 A）
- 新增 `references/stage-proto-doc/assets/产品文档模板.html`（16 KB／247 行，从备份拷、转 LF）。
- ④段 SKILL.md 换成备份 15:28 那版，并按模板口径改齐：
  · 「产品文档框架」从「四块＋一附录」改成**六节** —— 页面结构／功能清单／使用场景／操作流程／
    跨页与界面状态／待确认与偏离；与模板同构，⛔ 不从空白页重写结构。
  · 编号从 R/S/F 改成 **P 页面／S 场景／F 功能／J 二级功能**，各自唯一、按展示顺序通排。
  · 保留旧版有价值的要求：每项功能补齐 做什么／入口在哪／输入边界／异常与恢复；重点功能三处标红；
    横向流程图每步写清页面／功能／操作／完成判据。
  · 完成标准「七节」→「六节」，自查清单同步换掉「需求」那批条目，补模板与配图两条。
  · 路径 `designs/<项目>/` → `docs/pm/<项目>/ui/`（2 处）。
  · 补回本机那条「每份产出文档开头都要有一张图」的引用（指向主 skill，段内不复述）。
- 主 skill 同步：四段结构表④行、④段沿革、画图小节（④段画页面结构图 ＋ 用户路径）。

二、open-design 移到技能根（用户选候选 A）
- `git mv product-planning/references/stage-delivery/assets/open-design → open-design/`（4178 文件）。
- `.gitignore` 白名单加 `!/open-design/` —— 否则移出去就不再纳入版本控制。
- 引用改 11 处：路径形态 `assets/open-design/...` → `<技能根>/open-design/...`；
  「随段携带的自带件」改称「同根技能」；「路径怎么找」那条改成自带件（段内相对路径）与
  同根技能（`<技能根>/<技能名>/`）两类分开写。
- open-design 自己的 ATTRIBUTION.md 两处同步（它现在与 oil-ui-pro 同层）。
- 副作用（有益）：命名闸门读数由 2063 降到 225 —— 此前它把 open-design 里 919 个第三方 md
  当成规则一起扫了；现在只扫本包 23 个 md。已确认④段的 H1 与 4a/4b/4c 子步仍在检查范围内。

三、验收
- check_naming.py --ws E:/ProgramData/AIProject/contentm_agent ＝ 通过 225 / 失败 0 / 提示 27。
- 活文件里 `assets/open-design` 残留 0；工作区 CRLF 文件 0。

open-design/design-templates/pricing-page/SKILL.md

@@ -0,0 +1,79 @@
+---
+name: pricing-page
+description: |
+  A standalone pricing page — header, plan tiers, feature comparison table,
+  and an FAQ. Use when the brief asks for "pricing", "plans",
+  "subscription tiers", or a "compare plans" page.
+triggers:
+  - "pricing"
+  - "pricing page"
+  - "plans"
+  - "subscription"
+  - "compare plans"
+  - "定价"
+  - "套餐"
+od:
+  mode: prototype
+  platform: desktop
+  scenario: sales
+  preview:
+    type: html
+    entry: index.html
+  design_system:
+    requires: true
+    sections: [color, typography, layout, components]
+  craft:
+    requires: [laws-of-ux]
+---
+
+# Pricing Page Skill
+
+Produce a single-screen pricing page that respects the active DESIGN.md.
+
+## Workflow
+
+1. **Read the active DESIGN.md** (injected above). Use only its colors, type
+   tokens, and component patterns.
+2. **Classify** the product from the brief and pick a tier shape:
+   - 3-tier (most common): Free / Pro / Team or Starter / Growth / Enterprise.
+   - 4-tier when the brief says "scale" or "enterprise plus".
+   - 2-tier when it says "individual / business" or "personal / pro".
+3. **Sections**, in order:
+   1. **Hero** — page title (e.g. "Pricing"), one-line subhead, optional
+      monthly/annual toggle.
+   2. **Plan cards** — one card per tier. Each card: tier name, price (use the
+      display font + larger scale for the number), 1-line positioning, 4–6
+      bullet features, primary CTA. Mark the recommended tier with the DS
+      accent border or a small badge.
+   3. **Comparison table** — feature rows × tier columns, ✓ / — / value cells.
+      Group features into 2–3 logical sections (Core, Collaboration,
+      Support, Security…). Sticky header.
+   4. **FAQ** — 4–6 collapsible Q&A items. Use `<details><summary>` for the
+      collapse — no JS.
+   5. **Footer CTA** — single line + button, accent band sparingly.
+4. **Write** one self-contained HTML document:
+   - `<!doctype html>` through `</html>`, CSS in one inline `<style>`.
+   - CSS Grid for the plan-card row; CSS Grid for the comparison table.
+   - `data-od-id` on each tier card and each table row.
+5. **Money rendering**: use the display font for the big number, body for the
+   currency and "/mo" — sizes per DESIGN.md scale.
+6. **Self-check**:
+   - Prices are plausible for the product (not "$X / month").
+   - Accent is on the recommended tier and one CTA only.
+   - Comparison table renders cleanly at 1024px and stacks readably below
+     768px (rotate column headers or scroll-x).
+   - No fake feature names — every row reads as something a real product
+     would actually offer.
+
+## Output contract
+
+Emit between `<artifact>` tags:
+
+```
+<artifact identifier="pricing-slug" type="text/html" title="Pricing — Product Name">
+<!doctype html>
+<html>...</html>
+</artifact>
+```
+
+One sentence before the artifact, nothing after.