@colin4k1024/tsp 2.4.4 → 2.4.6

package/docs/presentation/generate_ppt.py

@@ -1,354 +0,0 @@
-#!/usr/bin/env python3
-"""Generate Team Skills Platform Introduction PPTX"""
-
-from pptx import Presentation
-from pptx.util import Inches, Pt
-from pptx.enum.text import PP_ALIGN, MSO_ANCHOR
-
-def add_title_slide(prs, title, subtitle=""):
-    slide_layout = prs.slide_layouts[6]  # Blank
-    slide = prs.slides.add_slide(slide_layout)
-
-    # Title
-    txBox = slide.shapes.add_textbox(Inches(0.5), Inches(3), Inches(9), Inches(1.5))
-    tf = txBox.text_frame
-    p = tf.paragraphs[0]
-    p.text = title
-    p.font.size = Pt(44)
-    p.font.bold = True
-    p.alignment = PP_ALIGN.CENTER
-
-    # Subtitle
-    if subtitle:
-        txBox2 = slide.shapes.add_textbox(Inches(0.5), Inches(4.5), Inches(9), Inches(1))
-        tf2 = txBox2.text_frame
-        p2 = tf2.paragraphs[0]
-        p2.text = subtitle
-        p2.font.size = Pt(24)
-        p2.alignment = PP_ALIGN.CENTER
-
-    return slide
-
-def add_content_slide(prs, title, bullets):
-    slide_layout = prs.slide_layouts[6]  # Blank
-    slide = prs.slides.add_slide(slide_layout)
-
-    # Title
-    txBox = slide.shapes.add_textbox(Inches(0.5), Inches(0.4), Inches(9), Inches(0.8))
-    tf = txBox.text_frame
-    p = tf.paragraphs[0]
-    p.text = title
-    p.font.size = Pt(32)
-    p.font.bold = True
-
-    # Content
-    txBox2 = slide.shapes.add_textbox(Inches(0.5), Inches(1.5), Inches(9), Inches(5.5))
-    tf2 = txBox2.text_frame
-    tf2.word_wrap = True
-
-    for i, bullet in enumerate(bullets):
-        if i == 0:
-            p = tf2.paragraphs[0]
-        else:
-            p = tf2.add_paragraph()
-        p.text = f"• {bullet}"
-        p.font.size = Pt(20)
-        p.space_after = Pt(12)
-
-    return slide
-
-def add_two_column_slide(prs, title, left_title, left_bullets, right_title, right_bullets):
-    slide_layout = prs.slide_layouts[6]
-    slide = prs.slides.add_slide(slide_layout)
-
-    # Title
-    txBox = slide.shapes.add_textbox(Inches(0.5), Inches(0.4), Inches(9), Inches(0.8))
-    tf = txBox.text_frame
-    p = tf.paragraphs[0]
-    p.text = title
-    p.font.size = Pt(32)
-    p.font.bold = True
-
-    # Left column title
-    left_title_box = slide.shapes.add_textbox(Inches(0.5), Inches(1.3), Inches(4.3), Inches(0.5))
-    lt = left_title_box.text_frame.paragraphs[0]
-    lt.text = left_title
-    lt.font.size = Pt(22)
-    lt.font.bold = True
-
-    # Left content
-    left_box = slide.shapes.add_textbox(Inches(0.5), Inches(1.8), Inches(4.3), Inches(5))
-    lt2 = left_box.text_frame
-    lt2.word_wrap = True
-    for i, b in enumerate(left_bullets):
-        p = lt2.paragraphs[0] if i == 0 else lt2.add_paragraph()
-        p.text = f"• {b}"
-        p.font.size = Pt(16)
-        p.space_after = Pt(8)
-
-    # Right column title
-    right_title_box = slide.shapes.add_textbox(Inches(5.2), Inches(1.3), Inches(4.3), Inches(0.5))
-    rt = right_title_box.text_frame.paragraphs[0]
-    rt.text = right_title
-    rt.font.size = Pt(22)
-    rt.font.bold = True
-
-    # Right content
-    right_box = slide.shapes.add_textbox(Inches(5.2), Inches(1.8), Inches(4.3), Inches(5))
-    rt2 = right_box.text_frame
-    rt2.word_wrap = True
-    for i, b in enumerate(right_bullets):
-        p = rt2.paragraphs[0] if i == 0 else rt2.add_paragraph()
-        p.text = f"• {b}"
-        p.font.size = Pt(16)
-        p.space_after = Pt(8)
-
-    return slide
-
-def main():
-    prs = Presentation()
-    prs.slide_width = Inches(10)
-    prs.slide_height = Inches(7.5)
-
-    # Slide 1: Cover
-    add_title_slide(
-        prs,
-        "Team Skills Platform",
-        "角色化研发团队协作平台介绍 | 2026-03-29"
-    )
-
-    # Slide 2: Problem Background
-    add_content_slide(prs, "问题背景：现状痛点", [
-        "单 Agent 能力局限：单个 AI 无法承担完整研发链路",
-        "角色边界模糊：缺乏清晰的职责分工和交接契约",
-        "工程规范碎片化：前端、API、安全、测试规范分散不统一",
-        "平台绑定：规范定义无法同时适配 Codex 与 Claude 双平台",
-        "技能传承困难：最佳实践依赖个人经验，难以系统化沉淀"
-    ])
-
-    # Slide 3: Solution
-    add_content_slide(prs, "解决方案：核心思路", [
-        "8 大角色矩阵：Tech Lead 统筹 + 7 个专业角色分工协作",
-        "标准化交接契约：角色间交接有明确定义和 quality gates",
-        "Canonical Source of Truth：roles/ 目录为单一真相源",
-        "双平台自动生成：Codex 与 Claude 技能/Agent 自动导出",
-        "ECC Harness Layer：27 个专家级 Specialist Agent 增强"
-    ])
-
-    # Slide 4: Architecture Overview
-    add_two_column_slide(
-        prs,
-        "架构概览",
-        "8 角色矩阵",
-        [
-            "tech-lead: 统一 intake、拆解、分派、冲突决策",
-            "product-manager: 需求、PRD、用户故事、验收标准",
-            "project-manager: 排期、依赖、里程碑、风险",
-            "architect: ADR、接口契约、数据边界",
-            "frontend-engineer: 前端实现与自测",
-            "backend-engineer: 后端实现与自测",
-            "qa-engineer: 测试计划、回归验证、放行建议",
-            "devops-engineer: 发布、监控、回滚与运行保障"
-        ],
-        "ECC Harness Layer",
-        [
-            "27 个 Specialist Agents",
-            "planner, architect, chief-of-staff",
-            "security-reviewer (OWASP Top 10)",
-            "build-error-resolver (8 语言版本)",
-            "tdd-guide, loop-operator, harness-optimizer",
-            "e2e-runner, refactor-cleaner",
-            "语言专项审查 (Java/Go/Python/Rust...)"
-        ]
-    )
-
-    # Slide 5: Engineering Results - Role System
-    add_content_slide(prs, "工程化成果：角色与规范体系", [
-        "roles/: 8 个角色的 canonical 定义（role.yaml）",
-        "skills/roles/: 自动生成的角色技能（平台无关）",
-        "agents/roles/: 自动生成的角色 Agent 提示词",
-        "agents/specialists/: 27 个 ECC 专家级 Agent",
-        "commands/: 团队命令表面（/team-intake, /team-plan, /handoff 等）",
-        "rules/: 团队工作规则 + 语言规范包（TS/Java/Python/Go）"
-    ])
-
-    # Slide 6: Engineering Results - Frontend Governance
-    add_two_column_slide(
-        prs,
-        "工程化成果：前端治理",
-        "前端工程规范",
-        [
-            "frontend-engineering: React/Next 工程规范",
-            "组件结构、状态管理、语义化",
-            "可访问性（Accessibility）基线",
-            "性能优化标准"
-        ],
-        "UI/UX 设计系统",
-        [
-            "frontend-ui-ux-system: 设计知识库",
-            "产品类型、视觉方向、设计 Token",
-            "交互模式、响应式设计",
-            "前端质量门禁规则"
-        ]
-    )
-
-    # Slide 7: Engineering Results - Security Gates
-    add_content_slide(prs, "工程化成果：安全与质量门禁", [
-        "CodeQL 安全扫描：PR 级别代码安全审查",
-        "Secret 扫描：防止密钥/凭证泄露",
-        "SBOM 生成：软件物料清单追溯",
-        "SLSA 验证：供应链安全级别认证",
-        "Contract Testing：API 契约测试",
-        "Trivy/Checkov：容器与 IaC 安全扫描",
-        "Security Reviewer：OWASP Top 10 全覆盖（30+ 检查项）"
-    ])
-
-    # Slide 8: Hooks System
-    add_two_column_slide(
-        prs,
-        "工程化成果：Hooks 系统",
-        "PreToolUse Hooks (5个)",
-        [
-            "tmux-reminder — dev server 建议用 tmux",
-            "git-push-reminder — push 前检查变更",
-            "console-log-warning — 检测调试语句",
-            "doc-file-warning — 非标准文档警告",
-            "mcp-health-check — MCP 健康检查"
-        ],
-        "PostToolUse Hooks (3个)",
-        [
-            "quality-gate — 质量检查（空格/分号）",
-            "format-suggestion — JS/TS 格式化建议",
-            "pr-created — PR URL 自动提取"
-        ]
-    )
-
-    # Slide 9: Continuous Learning & Cost Awareness
-    add_two_column_slide(
-        prs,
-        "工程化成果：持续学习 + 成本感知",
-        "Continuous Learning v2.1",
-        [
-            "Instinct Store：项目级/全局级 instinct",
-            "observe hook：工具调用观察捕获",
-            "instinct_cli：list/evolve/export/import",
-            "自动从会话提取最佳实践模式",
-            "置信度评分（0.3-0.9）驱动演进"
-        ],
-        "Cost-Aware LLM Pipeline",
-        [
-            "Haiku：轻量任务（$0.001/1K）",
-            "Sonnet：主开发（$0.01/1K）",
-            "Opus：深度推理（$0.05/1K）",
-            "Context Budget：70%/85% 阈值预警",
-            "cost_tracker：会话成本记录"
-        ]
-    )
-
-    # Slide 10: Public Commands Expansion
-    add_two_column_slide(
-        prs,
-        "工程化成果：公开命令面扩展",
-        "主链 + specialist",
-        [
-            "/team-intake -> /team-plan -> /team-execute",
-            "/handoff -> /team-review -> /team-release",
-            "/plan、/code-review、/build-fix、/verify",
-            "/multi-frontend、/multi-backend"
-        ],
-        "本轮新增重点",
-        [
-            "/tdd — 先锁测试与成功标准",
-            "/harness-audit — 平台能力体检与缺口收敛",
-            "specialist 结果必须回收到主链",
-            "平台治理与业务交付路径分离"
-        ]
-    )
-
-    # Slide 11: Runtime vs Explicit Commands
-    add_two_column_slide(
-        prs,
-        "工程化成果：显式命令与 Runtime 分层",
-        "显式命令",
-        [
-            "用户可见入口，负责触发决策与流程",
-            "例：/team-plan、/tdd、/harness-audit",
-            "适合解释主链、specialist 与角色协作",
-            "对外演示时最容易理解"
-        ],
-        "Runtime 后台机制",
-        [
-            "memory persistence、observe、cost tracking",
-            "context budget、compact/archive、instinct learning",
-            "自动增强长会话稳定性与成本控制",
-            "不是每次都手动执行的命令"
-        ]
-    )
-
-    # Slide 12: Core Advantages
-    add_content_slide(prs, "核心优势", [
-        "Canonical Source of Truth：单一真相源，平台无关定义",
-        "双平台支持：Codex 与 Claude 同步覆盖",
-        "角色化协作：明确职责边界，标准化交接",
-        "ECC 增强层：27 个专家级 Agent 快速编排",
-        "Hooks 系统：8 个自动化质量门禁钩子",
-        "持续学习：Instinct-based 自动模式提取",
-        "120+ Runbooks：覆盖快速入门、使用场景、治理、故障排查",
-        "可安装、可验证、可迁移：不是项目脚手架，而是能力基座"
-    ])
-
-    # Slide 13: Demo Materials
-    add_content_slide(prs, "演示与汇报材料", [
-        "业务主链演示：demo-scenario.md + demo-execution-log.md",
-        "平台升级演示：platform-capability-demo-script.md + execution-log",
-        "vertical 场景导览：vertical-scenario-route-map.md",
-        "vertical 场景矩阵：vertical-scenario-capability-matrix.md",
-        "已具备完整 demo 闭环的 9 类 vertical 场景可直接复用",
-        "命令总表：command-and-capability-matrix.md",
-        "runtime 总览：runtime-capabilities-overview.md",
-        "对外讲解可直接配合 presentation-talk-track.md"
-    ])
-
-    # Slide 14: Vertical Demo Route Map
-    add_two_column_slide(
-        prs,
-        "vertical Demo 成熟度",
-        "已具备完整闭环",
-        [
-            "GitHub Actions / 供应链治理",
-            "AI / Eval 平台",
-            "移动端 / 小程序交付",
-            "IaC / Kubernetes 平台仓库",
-            "插件 / 扩展仓库",
-            "数据 / ML pipeline 仓库",
-            "安全 / 合规平台仓库",
-            "内部开发者平台",
-            "数据可观测性 / 质量平台"
-        ],
-        "推荐使用方式",
-        [
-            "onboarding：先看 route map，再用 matrix 查缺层",
-            "汇报：直接复用各 vertical demo script",
-            "复盘：搭配 execution log 做团队同步",
-            "平台讲解：先讲 platform capability，再切到 vertical"
-        ]
-    )
-
-    # Slide 15: Next Steps
-    add_content_slide(prs, "下一步规划", [
-        "平台接入：扩大团队试点范围",
-        "规范完善：补充更多语言/框架规范包",
-        "ECC 扩展：继续沉淀专家级技能",
-        "度量体系：建立团队效能度量指标",
-        "知识沉淀：持续丰富 Runbooks 库",
-        "Eval 驱动开发：完善 pass@k 指标体系"
-    ])
-
-    # Save
-    import os
-    output_path = os.path.join(os.path.dirname(os.path.abspath(__file__)), "team-skills-platform-intro.pptx")
-    prs.save(output_path)
-    print(f"PPTX saved to: {output_path}")
-
-if __name__ == "__main__":
-    main()

package/docs/presentation/implementation-onboarding-brief.md

@@ -1,38 +0,0 @@
-# Implementation Onboarding Brief
-
-这份讲稿面向准备把 Team Skills Platform 接入真实仓库的实施人。重点不是平台价值，而是怎么开始、用哪一套材料、如何避免入口选错。
-
-## 1. 适用对象
-
-- Tech Lead
-- Architect
-- Project Manager
-- 负责仓库 onboarding 的实施人
-
-## 2. 讲解重点
-
-### 先讲从哪开始
-
-建议讲法：
-
-“接入时不要先看所有 runbook，而是先决定项目属于哪种模板。先从 examples 索引选模板，再从 starter playbook 选起手句，再看 route map 和 capability matrix 判断当前 vertical 材料是否完整。”
-
-### 再讲主链和 specialist 怎么配
-
-建议讲法：
-
-“新仓库先跑 `/team-intake` 和 `/team-plan`，只有返工成本高或任务复杂时再插 `/tdd`、`/multi-*`、`/verify`。specialist 的结果必须回到 handoff 或主链。”
-
-### 最后讲如何选 vertical 资产
-
-建议讲法：
-
-“如果你要快速复用现成材料，不要只看模板，要先查 route map 和 capability matrix。前者告诉你讲解入口，后者告诉你某个 vertical 是否已经具备 walkthrough、demo script 和 execution log。”
-
-## 3. 推荐顺序
-
-1. [../../examples/INDEX.md](../../examples/INDEX.md)
-2. [../../examples/project-type-starter-playbook.md](../../examples/project-type-starter-playbook.md)
-3. [vertical-scenario-route-map.md](vertical-scenario-route-map.md)
-4. [../runbooks/vertical-scenario-capability-matrix.md](../runbooks/vertical-scenario-capability-matrix.md)
-5. [../runbooks/project-onboarding.md](../runbooks/project-onboarding.md)

package/docs/presentation/presentation-talk-track.md

@@ -1,97 +0,0 @@
-# Presentation Talk Track
-
-这份讲稿用于把 Team Skills Platform 当前能力快速讲清楚，适合对团队、管理层或新接入项目做口头说明。它和 runbook 的区别是：runbook 偏操作，这份讲稿偏讲解顺序与口径。
-
-如果你已经明确当前听众是谁，不一定要直接用这一份通用稿。管理层优先看 [executive-briefing-talk-track.md](executive-briefing-talk-track.md)，实施接入优先看 [implementation-onboarding-brief.md](implementation-onboarding-brief.md)，培训场景优先看 [workshop-facilitator-guide.md](workshop-facilitator-guide.md)。如果还没决定怎么选，先看 [audience-presentation-route-map.md](audience-presentation-route-map.md)。
-
-## 1. 5 分钟版本
-
-### 第 1 分钟：先讲平台是什么
-
-建议讲法：
-
-“这不是一个 prompts 仓库，也不是单个 Agent 的技能包，而是一套角色化研发团队协作平台。主链由 tech-lead 编排，8 个角色协作完成需求、方案、研发、测试和发布。”
-
-### 第 2 分钟：讲现在新增了什么
-
-建议讲法：
-
-“这轮升级不是只加了几个文档，而是扩了四层能力。第一层是公开命令，新增了 /tdd 和 /harness-audit；第二层是 ECC skills，包括 eval-harness、continuous-learning、cost-aware-llm-pipeline、strategic-compact；第三层是可选知识图谱能力 Graphify，用于 brownfield 结构扫描和依赖路径证据；第四层是 runtime，包括 memory、observe、budget、compact、instinct 等后台机制。”
-
-### 第 3 分钟：讲两个关键新入口
-
-建议讲法：
-
-“/tdd 用来先锁测试和成功标准，减少返工；/harness-audit 用来体检平台本身，找文档、命令、skills、hooks 的同步缺口。前者面向交付闭环，后者面向平台治理。”
-
-### 第 4 分钟：讲 runtime 和显式命令的区别
-
-建议讲法：
-
-“runtime 不是要你每次手动执行的命令，而是在后台帮助长会话稳定运行的机制，比如会话记忆、行为观察、成本记录、上下文压缩和 instinct 学习。显式命令负责决策入口，runtime 负责增强执行环境。”
-
-### 第 5 分钟：讲现在该看哪些材料
-
-建议讲法：
-
-“如果你要上手，就先看 quick start；如果你要讲平台，就看命令与能力矩阵、runtime 总览和新的平台能力演示剧本；如果你要做 brownfield 结构认知，先跑 Graphify preflight 再看 Graphify runbook；如果你要讲具体业务场景，现在已经有 9 条完整 vertical 闭环，可以从 route map 和 capability matrix 里直接选。”
-
-## 2. 15 分钟版本
-
-### 第一段：平台结构
-
-- 讲 8 角色矩阵
-- 讲主链 `/team-*`
-- 讲 specialist 与 main chain 的关系
-
-### 第二段：能力升级
-
-- 讲 `/tdd`
-- 讲 `/harness-audit`
-- 讲新增 ECC skills
-- 讲 runtime 与 hooks
-
-### 第三段：材料与落地
-
-- 讲 quick start、usage scenarios、role runbooks 已经同步
-- 讲新 demo 材料如何使用
-- 讲 route map 和 markdown matrix 如何帮助选择 9 条 vertical 闭环入口
-- 讲 `node scripts/validate-library.js` 仍然通过，说明升级没有破坏基线
-
-## 3. 演示时建议打开的材料
-
-- `team-skills-platform-intro.pptx`（运行 generate_ppt.py 生成）
-- `agent-capability-matrix.pptx`（运行 generate_capability_matrix.py 生成）
-- [audience-presentation-route-map.md](audience-presentation-route-map.md)
-- [../runbooks/command-and-capability-matrix.md](../runbooks/command-and-capability-matrix.md)
-- [../runbooks/runtime-capabilities-overview.md](../runbooks/runtime-capabilities-overview.md)
-- [../runbooks/platform-capability-demo-script.md](../runbooks/platform-capability-demo-script.md)
-- [../runbooks/graphify-knowledge-graph-usage.md](../runbooks/graphify-knowledge-graph-usage.md)
-- [vertical-scenario-route-map.md](vertical-scenario-route-map.md)
-- [../runbooks/vertical-scenario-capability-matrix.md](../runbooks/vertical-scenario-capability-matrix.md)
-
-## 4. 常见问答口径
-
-- 问：/tdd 是不是只适合代码开发
-  答：不是，它更本质的作用是先定义完成标准和验证口径。
-
-- 问：/harness-audit 能不能替代 review
-  答：不能，它针对平台治理，不针对业务放行。
-
-- 问：runtime 能力是不是都要手动调用
-  答：不是，runtime 是后台机制，显式命令才是入口。
-
-- 问：Graphify 会不会替代 `/team-*` 主链
-  答：不会，Graphify 只是可选证据层能力，结论必须回落到 `/team-plan`、`/team-execute`、`/team-review`。
-
-- 问：为什么保留旧 demo 又新增新 demo
-  答：旧 demo 讲业务主链，新 demo 讲平台能力升级，两者服务的目标不同。
-
-## 5. 讲完后建议发出的链接
-
-- [README.md](README.md)
-- [audience-presentation-route-map.md](audience-presentation-route-map.md)
-- [../runbooks/team-skills-usage.md](../runbooks/team-skills-usage.md)
-- [../runbooks/platform-capability-demo-execution-log.md](../runbooks/platform-capability-demo-execution-log.md)
-- [vertical-scenario-route-map.md](vertical-scenario-route-map.md)
-- [../runbooks/vertical-scenario-capability-matrix.md](../runbooks/vertical-scenario-capability-matrix.md)

package/docs/presentation/vertical-scenario-route-map.md

@@ -1,99 +0,0 @@
-# Vertical Scenario Route Map
-
-这份导览页回答两个问题：现在有哪些 vertical 场景已经有完整演示闭环，哪些还处在“模板 + 起手句 + 连续脚本”阶段，以及 presentation / onboarding 应该先带用户看哪一层。
-
-## 1. 使用方式
-
-- 如果你在做 onboarding，先看“按成熟度选择”
-- 如果你在做汇报或演示，先看“按讲解目标选择”
-- 如果你在补仓库文档，先看“按材料层次选择”
-
-## 2. 按成熟度选择
-
-### 已具备完整 demo 闭环
-
-这些场景已经具备模板、起手句 / 连续脚本、walkthrough、demo script、execution log：
-
-- GitHub Actions / 供应链治理
-- AI / Eval 平台
-- 移动端 / 小程序交付
-- IaC / Kubernetes 平台仓库
-- 插件 / 扩展仓库
-- 数据 / ML pipeline 仓库
-- 安全 / 合规平台仓库
-- 内部开发者平台
-- 数据可观测性 / 质量平台
-
-推荐入口：
-
-- [../runbooks/github-actions-supply-chain-demo-script.md](../runbooks/github-actions-supply-chain-demo-script.md)
-- [../runbooks/ai-eval-platform-demo-script.md](../runbooks/ai-eval-platform-demo-script.md)
-- [../runbooks/mobile-miniapp-demo-script.md](../runbooks/mobile-miniapp-demo-script.md)
-- [../runbooks/iac-kubernetes-platform-demo-script.md](../runbooks/iac-kubernetes-platform-demo-script.md)
-- [../runbooks/plugin-extension-platform-demo-script.md](../runbooks/plugin-extension-platform-demo-script.md)
-- [../runbooks/data-ml-pipeline-demo-script.md](../runbooks/data-ml-pipeline-demo-script.md)
-- [../runbooks/security-compliance-platform-demo-script.md](../runbooks/security-compliance-platform-demo-script.md)
-- [../runbooks/internal-developer-platform-demo-script.md](../runbooks/internal-developer-platform-demo-script.md)
-- [../runbooks/data-observability-quality-demo-script.md](../runbooks/data-observability-quality-demo-script.md)
-
-## 3. 按讲解目标选择
-
-### 目标：讲平台能力升级
-
-- 先看 [../runbooks/platform-capability-demo-script.md](../runbooks/platform-capability-demo-script.md)
-- 再看 [../runbooks/platform-capability-demo-execution-log.md](../runbooks/platform-capability-demo-execution-log.md)
-
-### 目标：讲 brownfield 结构扫描与知识图谱证据
-
-- 先看 [../runbooks/graphify-knowledge-graph-usage.md](../runbooks/graphify-knowledge-graph-usage.md)
-- 再结合 [../runbooks/project-onboarding.md](../runbooks/project-onboarding.md) 的接入判定
-- 再回到 [../runbooks/command-and-capability-matrix.md](../runbooks/command-and-capability-matrix.md) 的推荐组合链路
-
-### 目标：讲一个具体 vertical 如何跑通
-
-- 供应链治理：看 [../runbooks/github-actions-supply-chain-demo-script.md](../runbooks/github-actions-supply-chain-demo-script.md)
-- AI / Eval：看 [../runbooks/ai-eval-platform-demo-script.md](../runbooks/ai-eval-platform-demo-script.md)
-- 移动端：看 [../runbooks/mobile-miniapp-demo-script.md](../runbooks/mobile-miniapp-demo-script.md)
-- IaC / Kubernetes：看 [../runbooks/iac-kubernetes-platform-demo-script.md](../runbooks/iac-kubernetes-platform-demo-script.md)
-- 插件 / 扩展：看 [../runbooks/plugin-extension-platform-demo-script.md](../runbooks/plugin-extension-platform-demo-script.md)
-- 数据 / ML pipeline：看 [../runbooks/data-ml-pipeline-demo-script.md](../runbooks/data-ml-pipeline-demo-script.md)
-- 安全 / 合规：看 [../runbooks/security-compliance-platform-demo-script.md](../runbooks/security-compliance-platform-demo-script.md)
-- 内部开发者平台：看 [../runbooks/internal-developer-platform-demo-script.md](../runbooks/internal-developer-platform-demo-script.md)
-- 数据可观测性 / 质量平台：看 [../runbooks/data-observability-quality-demo-script.md](../runbooks/data-observability-quality-demo-script.md)
-
-### 目标：讲“新接入项目该从哪个模板开始” 
-
-- 先看 [../../examples/INDEX.md](../../examples/INDEX.md)
-- 再看 [../../examples/project-type-starter-playbook.md](../../examples/project-type-starter-playbook.md)
-
-## 4. 按材料层次选择
-
-### 只想找项目模板
-
-- 看 [../../examples/INDEX.md](../../examples/INDEX.md)
-
-### 想直接复制第一句话
-
-- 看 [../../examples/project-type-starter-playbook.md](../../examples/project-type-starter-playbook.md)
-
-### 想直接复制一段连续脚本
-
-- 看 [../../examples/vertical-project-conversation-scripts.md](../../examples/vertical-project-conversation-scripts.md)
-
-### 想照着讲一场演示
-
-- 看 [../runbooks/platform-capability-demo-script.md](../runbooks/platform-capability-demo-script.md)
-- 或任一 vertical demo script，再结合 [../runbooks/vertical-scenario-capability-matrix.md](../runbooks/vertical-scenario-capability-matrix.md) 选路径
-
-### 想拿复盘 / 同步材料
-
-- 看各类 execution log
-
-## 5. Onboarding 建议顺序
-
-1. 先用 [../../examples/INDEX.md](../../examples/INDEX.md) 选项目类型
-2. 再用 [../../examples/project-type-starter-playbook.md](../../examples/project-type-starter-playbook.md) 复制起手句
-3. 如果场景已具备完整 demo 闭环，再直接复用对应 demo script
-4. 如果要先确认材料是否完整，再查 [../runbooks/vertical-scenario-capability-matrix.md](../runbooks/vertical-scenario-capability-matrix.md)
-5. 如果只是选项目模板，再回到 quick start 和 onboarding 路径接入
-6. 如果项目是 brownfield 且结构复杂，先执行 Graphify 预检查与结构扫描，再进入 `/team-plan`

package/docs/presentation/workshop-facilitator-guide.md

@@ -1,47 +0,0 @@
-# Workshop Facilitator Guide
-
-这份讲稿面向内部培训和团队赋能。重点不是单次汇报，而是如何带一场 30 到 90 分钟的培训，让团队真正理解主链、specialist 和 vertical 材料怎么配合。
-
-## 1. 30 分钟版
-
-### 第一段：平台结构
-
-- 讲 8 角色矩阵
-- 讲 `/team-*` 主链
-- 讲 handoff 为什么是事实收口点
-
-### 第二段：能力升级
-
-- 讲 `/tdd`
-- 讲 `/harness-audit`
-- 讲 runtime 与显式命令分层
-
-### 第三段：怎么选材料
-
-- 讲 examples 索引
-- 讲 route map
-- 讲 capability matrix
-
-## 2. 60 分钟版
-
-### 加强内容
-
-- 加一段 vertical 选择演示
-- 加一段 Claude / Codex 起手对比
-- 加一段 specialist 结果回收到 handoff 的示例
-
-## 3. 90 分钟版
-
-### 加强内容
-
-- 选一个完整 vertical 做 walkthrough
-- 选一个非完整听众路线，演示如何从 audience route map 反推讲法
-- 补一段 QA / DevOps 如何接 review / release
-
-## 4. 推荐打开的材料
-
-- [presentation-talk-track.md](presentation-talk-track.md)
-- [audience-presentation-route-map.md](audience-presentation-route-map.md)
-- [../runbooks/command-and-capability-matrix.md](../runbooks/command-and-capability-matrix.md)
-- [../runbooks/runtime-capabilities-overview.md](../runbooks/runtime-capabilities-overview.md)
-- [../runbooks/vertical-scenario-capability-matrix.md](../runbooks/vertical-scenario-capability-matrix.md)