diff --git a/wiki/concepts/Analytics-Reporter.md b/wiki/concepts/Analytics-Reporter.md new file mode 100644 index 00000000..58afb38f --- /dev/null +++ b/wiki/concepts/Analytics-Reporter.md @@ -0,0 +1,32 @@ +--- +title: "Analytics Reporter" +type: concept +tags: [] +last_updated: 2026-04-21 +--- + +## Definition +数据分析与商业智能专家智能体，将原始数据转化为可操作的业务洞察。 + +## Core Capabilities +- 统计分析与假设检验 +- 仪表盘设计与 KPI 监控 +- RFM 客户分层分析 +- 营销归因建模 +- 预测模型构建（A/B 测试、流失预测、增长预测） + +## Key Metrics +- 分析准确率目标：95%+ +- 业务建议采纳率目标：70%+ +- 仪表盘月活用户：95%+ +- KPI 提升目标：20%+ + +## Related Concepts +- [[Data-Driven Decision Making]] +- [[RFM Analysis]] +- [[Customer Lifetime Value]] +- [[Statistical Significance Testing]] + +## Source +- [[support-analytics-reporter]] + diff --git a/wiki/concepts/BCG-Pyramid-Principle.md b/wiki/concepts/BCG-Pyramid-Principle.md new file mode 100644 index 00000000..66752c4f --- /dev/null +++ b/wiki/concepts/BCG-Pyramid-Principle.md @@ -0,0 +1,23 @@ +--- +title: "BCG Pyramid Principle" +type: concept +tags: [consulting, strategic-communication, framework] +sources: [] +last_updated: 2026-04-21 +--- + +## Definition +波士顿咨询集团的自上而下逻辑表达原则，先给出核心论点再分层展开支撑论据 + +## Core Concept +- **核心论点（Key Message）**：首先传达最重要的结论 +- **支撑论据（Supporting Arguments）**：按重要性排序的次级论点 +- **数据支撑（Data/Evidence）**：每项论据的具体证据 + +## Application +用于 Executive Summary Generator 的第二步"关键发现"，确保发现按业务影响排序 + +## Related Concepts +- [[McKinsey SCQA Framework]] +- [[Bain Action-Oriented Model]] +- [[Executive Summary]] \ No newline at end of file diff --git a/wiki/concepts/Book-Co-Author-Agent.md b/wiki/concepts/Book-Co-Author-Agent.md new file mode 100644 index 00000000..b78cfc69 --- /dev/null +++ b/wiki/concepts/Book-Co-Author-Agent.md @@ -0,0 +1,41 @@ +--- +title: "Book Co-Author Agent" +type: concept +tags: [agent, writing, the-agency] +sources: [sources/workflow-book-chapter.md] +last_updated: 2026-04-21 +--- + +## 定义 +The Agency 项目中的书籍共创智能体，将源素材（语音笔记、片段、战略笔记）转化为版本化章节草稿，并附带编辑注释和下一步问题。 + +## 核心职责 +- 将粗糙素材转化为战略性第一人称书籍章节草稿 +- 保持作者声音一致性 +- 强化品类定位 +- 暴露开放编辑决策 + +## 工作流程 +1. 接收原始素材（voice memo、notes、story fragment、positioning angle） +2. 产出章节目标和战略角色 +3. 提出澄清问题 +4. 生成版本化草稿 +5. 提供编辑注释（假设和证据缺口） +6. 明确下一步修订请求 + +## 输出格式 +1. Target Outcome（目标结果） +2. Chapter Draft（章节草稿） +3. Editorial Notes（编辑注释） +4. Feedback Loop（反馈循环） +5. Next Step（下一步） + +## 质量标准 +- 草稿保持第一人称声音 +- 章节有一个清晰的承诺和内部逻辑 +- 声明与源素材关联或标记为假设 +- 移除通用激励语言 +- 输出以明确修订问题结束 + +## Aliases +- Book Co-Author diff --git a/wiki/concepts/BudgetFramework.md b/wiki/concepts/BudgetFramework.md new file mode 100644 index 00000000..b6969f71 --- /dev/null +++ b/wiki/concepts/BudgetFramework.md @@ -0,0 +1,15 @@ +--- +title: "Budget Framework" +type: concept +tags: [finance] +sources: [support-finance-tracker] +last_updated: 2026-04-21 +--- + +定义：组织年度预算的结构化方法，包含按部门/类别拆分、季度差异分析、偏差分类与再分配规则，用于把控支出与指导战略资源分配。 + +## Typical Components +- 部门与类别分解 +- 季度/月度差异分析 +- 偏差触发与纠正流程 +- 预算再分配规范 diff --git a/wiki/concepts/CashFlowManagement.md b/wiki/concepts/CashFlowManagement.md new file mode 100644 index 00000000..4ea863f5 --- /dev/null +++ b/wiki/concepts/CashFlowManagement.md @@ -0,0 +1,15 @@ +--- +title: "Cash Flow Management" +type: concept +tags: [finance] +sources: [support-finance-tracker] +last_updated: 2026-04-21 +--- + +定义：系统化的现金收支预测与优化方法，包含滚动预测、季节性因子、低现金预警规则与支付时点优化，用以保证短中期流动性并发现投资机会。 + +## Typical Components +- 收入与付款模式分析 +- 滚动预测（12 个月示例） +- 低现金阈值与行动建议 +- 支付优先级与折扣收益优化 diff --git a/wiki/concepts/Context-Passing.md b/wiki/concepts/Context-Passing.md new file mode 100644 index 00000000..3d39c48f --- /dev/null +++ b/wiki/concepts/Context-Passing.md @@ -0,0 +1,41 @@ +--- +title: "Context Passing" +type: concept +tags: [multi-agent, workflow, communication] +last_updated: 2026-04-21 +--- + +## Definition +上下文传递（Context Passing）是一种多智能体通信模式，在智能体之间传递完整的上下文信息，而非摘要或压缩版本。 + +## Core Principle +**"Copy-paste agent outputs between steps — don't summarize, use the full output"** + +## Problem It Solves +- 摘要会丢失关键细节 +- 压缩可能遗漏重要上下文 +- 智能体不具备共享记忆 + +## Best Practices +1. **完整复制**：将上一智能体的输出完整粘贴到下一智能体的输入 +2. **不要摘要**：即使很长也要完整传递 +3. **不要解释**：让接收智能体自己解析和处理完整信息 +4. **包含所有内容**：原始输出、元数据、证据、决策理由等 + +## Example +在 Multi-Agent Workflow: Startup MVP 中： +``` +Sprint Prioritizer 输出 → [完整粘贴] → Backend Architect 输入 +UX Researcher 输出 → [完整粘贴] → Backend Architect 输入 +Backend Architect 输出 → [完整粘贴] → Frontend Developer 输入 +``` + +## Trade-offs +- **优点**：最大化信息保留，便于接收智能体做出完整判断 +- **缺点**：消耗更多上下文窗口，可能需要更长的处理时间 + +## Related Concepts +- [[Sequential Handoffs]]：顺序交接模式 +- [[Parallel Work]]：并行工作模式 +- [[Quality Gates]]：质量门控 +- [[Multi-Agent Team]]：多智能体团队 diff --git a/wiki/concepts/Customer-Lifetime-Value.md b/wiki/concepts/Customer-Lifetime-Value.md new file mode 100644 index 00000000..34e1d488 --- /dev/null +++ b/wiki/concepts/Customer-Lifetime-Value.md @@ -0,0 +1,26 @@ +--- +title: "Customer Lifetime Value" +type: concept +tags: [] +last_updated: 2026-04-21 +--- + +## Definition +客户生命周期价值，衡量客户在整个关系周期内为企业贡献的总收入。 + +## Calculation Method +CLV = Average Order Value × Purchase Frequency × Customer Lifespan + +## Application +- 客户分层与优先级排序 +- 客户获取成本（CAC）决策依据 +- 个性化营销策略制定 +- 客户流失预警基准 + +## Related Concepts +- [[RFM Analysis]] +- [[Predictive Modeling]] + +## Source +- [[support-analytics-reporter]] + diff --git a/wiki/concepts/Customer-Success.md b/wiki/concepts/Customer-Success.md new file mode 100644 index 00000000..8d06d99d --- /dev/null +++ b/wiki/concepts/Customer-Success.md @@ -0,0 +1,35 @@ +--- +id: customer-success +title: "Customer Success" +type: concept +tags: [customer-service, retention, lifecycle] +sources: [support-support-responder.md] +last_updated: 2026-04-21 +--- + +## Definition +客户成功（Customer Success），从被动式客户支持向主动式客户成功干预转变的管理方法论，目标是最大化客户生命周期价值并预防客户流失。 + +## Core Mission +- Onboarding Optimization：新客户快速上手和功能采用 +- Feature Adoption Guidance：引导客户发现和使用核心功能 +- Proactive Outreach：基于数据的主动干预（高风险客户识别） +- Feedback Collection：产品改进和客户洞察生成 + +## Success Metrics +| Metric | Target | +|--------|--------| +| CSAT Score | ≥ 4.5/5 | +| First Contact Resolution | ≥ 80% | +| Customer Retention | ≥ 95% | +| NPS Score | ≥ 50 | + +## Proactive Outreach Triggers +- 30 天内提交 ≥ 3 次工单的高频用户 +- 7 天内 CSAT ≤ 3 的低满意度客户 +- 超过 48 小时未解决的工单 + +## Connections +- [[Support Responder]] — 实现客户成功的核心执行者 +- [[Support Analytics]] — 提供数据驱动的干预依据 +- [[Multi-Channel Support Framework]] — 客户触达的渠道 \ No newline at end of file diff --git a/wiki/concepts/Data-Driven-Decision-Making.md b/wiki/concepts/Data-Driven-Decision-Making.md new file mode 100644 index 00000000..f57c0daf --- /dev/null +++ b/wiki/concepts/Data-Driven-Decision-Making.md @@ -0,0 +1,30 @@ +--- +title: "Data-Driven Decision Making" +type: concept +tags: [] +last_updated: 2026-04-21 +--- + +## Definition +基于数据而非直觉或经验进行业务决策的方法论，强调用证据和量化分析指导战略选择。 + +## Core Principles +- 数据质量优先：验证数据准确性再分析 +- 统计显著性：结论需经假设检验确认 +- 可复现性：分析流程需版本控制和文档化 +- 行动导向：连接分析结果与业务行动 +- 持续迭代：基于反馈循环优化决策 + +## Implementation +1. 建立数据治理标准 +2. 定义关键业务指标（KPI） +3. 构建可复现的分析工作流 +4. 建立反馈机制评估决策效果 + +## Related Concepts +- [[Statistical Significance Testing]] +- [[KPI Tracking]] + +## Source +- [[support-analytics-reporter]] + diff --git a/wiki/concepts/Disaster-Recovery.md b/wiki/concepts/Disaster-Recovery.md new file mode 100644 index 00000000..d959dd58 --- /dev/null +++ b/wiki/concepts/Disaster-Recovery.md @@ -0,0 +1,28 @@ +--- +title: "Disaster Recovery" +type: concept +tags: [infrastructure, resilience, backup] +last_updated: 2026-04-21 +--- + +## Definition +Disaster Recovery（灾难恢复）是一套在灾难性事件后恢复 IT 系统和数据的策略与流程，确保业务连续性。 + +## Core Metrics +- **RTO（Recovery Time Objective）**：系统允许的最大停机时间 +- **RPO（Recovery Point Objective）**：可接受的最大数据丢失量 + +## Key Components +- **备份策略**：定期创建加密备份，存储于 S3 +- **恢复流程**：经过测试的恢复程序文档 +- **自动化恢复**：通过脚本实现自动故障切换 + +## Implementation +The Agency 项目中的 [[Support Infrastructure Maintainer]] 实现： +- 自动化备份脚本（GPG 加密 + S3 上传） +- 30 天本地保留 + S3 生命周期管理 +- Backup verification 和 Slack 通知 + +## Related Concepts +- [[Feature Flag（特性开关）]]：控制代码路径而不需要重新部署，实现秒级回滚 +- [[ITSM（IT 服务管理）]]：从工单系统演进为战略推动者，实现运营卓越和风险缓解 \ No newline at end of file diff --git a/wiki/concepts/Editorial-Notes.md b/wiki/concepts/Editorial-Notes.md new file mode 100644 index 00000000..8a03d698 --- /dev/null +++ b/wiki/concepts/Editorial-Notes.md @@ -0,0 +1,25 @@ +--- +title: "Editorial Notes" +type: concept +tags: [writing, editing, review] +sources: [sources/workflow-book-chapter.md] +last_updated: 2026-04-21 +--- + +## 定义 +编辑注释是对章节草稿中假设和证据缺口的明确标注，帮助作者识别需要补充的内容区域。 + +## 核心内容 +- 假设声明：标记未经证实的声明 +- 证据缺口：指出需要引用或数据支持的位置 +- 品类定位评估：检查内容是否强化目标定位 +- 声音一致性检查：确认是否保持作者风格 + +## 作用 +- 为作者提供明确的修订方向 +- 区分 AI 生成内容和作者贡献 +- 保持内容可信度 + +## Aliases +- 编辑注释 +- 编辑笔记 diff --git a/wiki/concepts/Executive-Summary.md b/wiki/concepts/Executive-Summary.md index 70eba2bc..43154afb 100644 --- a/wiki/concepts/Executive-Summary.md +++ b/wiki/concepts/Executive-Summary.md @@ -1,27 +1,31 @@ --- title: "Executive Summary" type: concept -tags: [Proposal, Sales, Strategy] -last_updated: 2026-04-20 +tags: [Proposal, Sales, Strategy, consulting, decision-making, c-suite] +sources: [] +last_updated: 2026-04-21 --- ## Definition -执行摘要是提案最关键的部分，许多评估者尤其是高级利益相关者只阅读此部分。它不是提案的总结，而是放在最前面的结束论证。 +执行摘要，一种针对 C-suite 决策者的结构化简报格式，要求在 325-475 字内传达复杂业务信息的核心要点。提案中的执行摘要是最关键的部分，许多评估者尤其是高级利益相关者只阅读此部分。 -## Structure -1. **Mirror the buyer's situation**（2-3 句，证明你倾听并理解了他们的处境） +## Format Requirements +- **长度**：325-475 words（≤ 500 max） +- **量化**：每个关键发现必须包含 ≥ 1 个量化或比较数据点 +- **结构**：5 部分（SITUATION OVERVIEW / KEY FINDINGS / BUSINESS IMPACT / RECOMMENDATIONS / NEXT STEPS） +- **可操作性**：建议必须包含 Owner + Timeline + Expected Result + +## Format for C-suite Decision Making +1. **Mirror the buyer's situation**（2-3 句） 2. **Introduce the central tension**—不行动的成本或错失的机会 -3. **Present your thesis**—你的方法如何解决这个矛盾（制胜主题在此出现） -4. **Offer proof**—一个或两个具体证据点（指标、类似案例、差异化因素） -5. **Close with the transformed state**—他们可以期望的具体结果 +3. **Present your thesis**—你的方法如何解决这个矛盾 +4. **Offer proof**—具体证据点 +5. **Close with the transformed state**—具体结果 -## Key Principles -- 保持在一页以内 -- 每一句都必须有其存在的价值 -- 从买家的语言出发，不是从你的解决方案出发 -- 制胜主题必须在此部分出现 +## Frameworks Used +- [[McKinsey SCQA Framework]] +- [[BCG Pyramid Principle]] +- [[Bain Action-Oriented Model]] -## Connections -- [[Executive Summary]] ← critical_section_of ← [[Proposal Strategy]] -- [[Executive Summary]] ← contains ← [[Win Theme]] -- [[Executive Summary]] → leads_to → [[Three-Act Proposal Narrative]] \ No newline at end of file +## Related Entities +- [[Executive Summary Generator]] \ No newline at end of file diff --git a/wiki/concepts/Feedback-Loop.md b/wiki/concepts/Feedback-Loop.md new file mode 100644 index 00000000..7583e8c2 --- /dev/null +++ b/wiki/concepts/Feedback-Loop.md @@ -0,0 +1,30 @@ +--- +title: "Feedback Loop" +type: concept +tags: [workflow, revision, iteration] +sources: [sources/workflow-book-chapter.md] +last_updated: 2026-04-21 +--- + +## 定义 +反馈循环是 Book Co-Author Agent 提供的结构化修订请求机制，通过明确的编辑注释和下一步问题驱动草稿迭代改进。 + +## 组成要素 +- Editorial Notes：假设和证据缺口标注 +- Next Step：具体可执行的修订请求 +- 开放问题：暴露需要作者决策的编辑问题 + +## 目的 +- 将模糊的"需要改进"转化为具体行动项 +- 维持修订过程的可追溯性 +- 确保作者声音和品类定位不被稀释 + +## 与版本化草稿的关系 +反馈循环支撑版本化草稿的演进： +- 每一版本的反馈循环定义下一版本的改进方向 +- 版本编号与反馈循环轮次对应 +- 作者通过反馈循环保持对内容的控制权 + +## Aliases +- 反馈循环 +- 修订循环 diff --git a/wiki/concepts/Infrastructure-as-Code.md b/wiki/concepts/Infrastructure-as-Code.md new file mode 100644 index 00000000..112750ff --- /dev/null +++ b/wiki/concepts/Infrastructure-as-Code.md @@ -0,0 +1,27 @@ +--- +title: "Infrastructure as Code (IaC)" +type: concept +tags: [infrastructure, devops, automation] +last_updated: 2026-04-21 +--- + +## Definition +Infrastructure as Code（基础设施即代码）是一种通过代码实现基础设施管理的方法论，替代传统手动配置，实现一致性、版本控制和自动化部署。 + +## Core Principles +- **声明式配置**：定义期望状态而非步骤 +- **版本控制**：所有基础设施变更通过 Git 管理 +- **自动化部署**：通过 CI/CD 流水线实现一键部署 +- **幂等性**：重复执行结果一致 + +## Key Tools +- [[Terraform]]：HashiCorp 开发的跨平台 IaC 工具 +- Terragrunt：Terraform 包装工具，提供模块化和变量共享 +- CloudFormation：AWS 原生 IaC 服务 + +## Related Concepts +- [[CI/CD 流水线]]：自动化测试、集成和部署的持续交付管道 +- [[Infrastructure Maintainer]]：使用 IaC 进行基础设施管理的智能体角色 + +## Application +The Agency 项目中的 [[Support Infrastructure Maintainer]] 使用 Terraform 实现 AWS 基础设施声明式管理，包括 VPC、子网、Auto Scaling Group、RDS 等资源。 \ No newline at end of file diff --git a/wiki/concepts/InvestmentAnalysis.md b/wiki/concepts/InvestmentAnalysis.md new file mode 100644 index 00000000..cdde2845 --- /dev/null +++ b/wiki/concepts/InvestmentAnalysis.md @@ -0,0 +1,15 @@ +--- +title: "Investment Analysis" +type: concept +tags: [finance] +sources: [support-finance-tracker] +last_updated: 2026-04-21 +--- + +定义：用于评估资本项目经济性的量化框架，常用指标包括净现值（NPV）、内部收益率（IRR）、回收期与风险评分，结合敏感性分析与决策规则给出投资建议。 + +## Typical Components +- NPV 计算与折现率设定 +- IRR 估算与收敛性检测 +- 回收期计算 +- 风险评分与投资建议规则 diff --git a/wiki/concepts/KPI-Tracking.md b/wiki/concepts/KPI-Tracking.md new file mode 100644 index 00000000..a024918a --- /dev/null +++ b/wiki/concepts/KPI-Tracking.md @@ -0,0 +1,30 @@ +--- +title: "KPI Tracking" +type: concept +tags: [] +last_updated: 2026-04-21 +--- + +## Definition +关键绩效指标监控，通过量化指标评估业务目标达成情况。 + +## Dashboard Design Principles +- 针对特定利益相关者需求定制 +- 清晰的分层结构（战略→运营→执行） +- 实时或近实时数据更新 +- 异常自动告警机制 +- 可下钻的钻取能力 + +## Common KPI Categories +- **收入指标**：月收入、ARR、客单价、转化率 +- **客户指标**：NPS、流失率、终身价值 +- **运营指标**：处理时间、错误率、库存周转 +- **营销指标**：CAC、ROI、触点转化率 + +## Related Concepts +- [[Data-Driven Decision Making]] +- [[Predictive Modeling]] + +## Source +- [[support-analytics-reporter]] + diff --git a/wiki/concepts/Keyboard-Navigation-Audit.md b/wiki/concepts/Keyboard-Navigation-Audit.md new file mode 100644 index 00000000..c9858da2 --- /dev/null +++ b/wiki/concepts/Keyboard-Navigation-Audit.md @@ -0,0 +1,54 @@ +--- +title: "Keyboard Navigation Audit" +description: 纯键盘导航测试，验证所有交互元素的可访问性 +tags: [accessibility, testing, keyboard] +--- + +## Definition +Keyboard Navigation Audit 是验证所有交互功能是否可以通过纯键盘（不使用鼠标）完成操作的测试方法。这是无障碍测试的核心环节。 + +## 全局导航检查清单 +- [ ] 所有交互元素可通过 Tab 键到达 +- [ ] Tab 顺序遵循视觉布局逻辑 +- [ ] 存在 Skip Navigation（跳转导航）链接 +- [ ] 无键盘陷阱（始终可以通过 Tab 离开） +- [ ] 每个交互元素的焦点指示器始终可见 +- [ ] Escape 键关闭模态框、下拉菜单和浮层 +- [ ] 关闭模态框/浮层后焦点返回触发元素 + +## 组件特定模式 + +### Tabs +- [ ] Tab 键在 Tab 列表和活动面板内容之间移动 +- [ ] 方向键在 Tab 按钮之间移动 +- [ ] Home/End 键移动到第一个/最后一个 Tab +- [ ] 选中 Tab 通过 aria-selected 指示 + +### Menus +- [ ] 方向键在菜单项之间导航 +- [ ] Enter/Space 激活菜单项 +- [ ] Escape 关闭菜单并将焦点返回触发器 + +### Carousels/Sliders +- [ ] 方向键在幻灯片之间移动 +- [ ] 暂停/停止控制可通过键盘操作 +- [ ] 当前位置被宣布 + +### Data Tables +- [ ] 表头通过 scope 或 headers 属性与单元格关联 +- [ ] Caption 或 aria-label 描述表格用途 +- [ ] 可排序列可通过键盘操作 + +## 结果指标 +- **总交互元素数**： +- **键盘可访问**：（百分比） +- **键盘陷阱数**： +- **缺失焦点指示器数**： + +## Related Concepts +- [[WCAG 2.2]] +- [[Screen Reader Testing]] +- [[POUR Principles]] + +## Source +- [[Accessibility Auditor]] \ No newline at end of file diff --git a/wiki/concepts/Marketing-Attribution-Modeling.md b/wiki/concepts/Marketing-Attribution-Modeling.md new file mode 100644 index 00000000..12d50a68 --- /dev/null +++ b/wiki/concepts/Marketing-Attribution-Modeling.md @@ -0,0 +1,50 @@ +--- +title: "Marketing Attribution Modeling" +type: concept +tags: [] +last_updated: 2026-04-21 +--- + +## Definition +多触点归因模型，将转化功劳分配给营销漏斗中的不同触点（首次点击、末次点击、中间触点）。 + +## Attribution Models +| Model | First Touch | Last Touch | Middle Touches | +|-------|------------|------------|----------------| +| First Touch | 100% | - | - | +| Last Touch | - | 100% | - | +| Linear | - | - | 平均分配 | +| Time Decay | 较低 | 较高 | 随时间递减 | +| Position Based | 40% | 40% | 20% 均分 | +| Data-Driven | 基于算法 | 基于算法 | 基于算法 | + +## Multi-Touch Attribution SQL +```sql +WITH customer_touchpoints AS ( + SELECT customer_id, channel, campaign, + ROW_NUMBER() OVER (PARTITION BY customer_id ORDER BY touchpoint_date) as touch_sequence, + COUNT(*) OVER (PARTITION BY customer_id) as total_touches + FROM marketing_touchpoints +), +attribution_weights AS ( + SELECT *, + CASE + WHEN touch_sequence = 1 AND total_touches = 1 THEN 1.0 + WHEN touch_sequence = 1 THEN 0.4 + WHEN touch_sequence = total_touches THEN 0.4 + ELSE 0.2 / (total_touches - 2) + END as attribution_weight + FROM customer_touchpoints +) +SELECT channel, SUM(revenue * attribution_weight) as attributed_revenue +FROM attribution_weights +GROUP BY channel; +``` + +## Related Concepts +- [[Data-Driven Decision Making]] +- [[KPI Tracking]] + +## Source +- [[support-analytics-reporter]] + diff --git a/wiki/concepts/McKinsey-SCQA-Framework.md b/wiki/concepts/McKinsey-SCQA-Framework.md new file mode 100644 index 00000000..eaaeec98 --- /dev/null +++ b/wiki/concepts/McKinsey-SCQA-Framework.md @@ -0,0 +1,24 @@ +--- +title: "McKinsey SCQA Framework" +type: concept +tags: [consulting, strategic-communication, framework] +sources: [] +last_updated: 2026-04-21 +--- + +## Definition +Situation-Complication-Question-Answer，麦肯锡的结构化叙事框架，通过四步引导读者从情境到解决方案 + +## Structure +- **Situation**：设定背景，描述当前状态 +- **Complication**：揭示挑战或障碍 +- **Question**：提出核心问题 +- **Answer**：给出解决方案或答案 + +## Application +用于 Executive Summary Generator 的第一步"情境概述"，帮助建立叙事逻辑 + +## Related Concepts +- [[BCG Pyramid Principle]] +- [[Bain Action-Oriented Model]] +- [[Executive Summary]] \ No newline at end of file diff --git a/wiki/concepts/Merge-Point.md b/wiki/concepts/Merge-Point.md new file mode 100644 index 00000000..4489ba87 --- /dev/null +++ b/wiki/concepts/Merge-Point.md @@ -0,0 +1,24 @@ +--- +title: "Merge Point" +type: concept +tags: [multi-agent, workflow, synchronization] +last_updated: 2026-04-21 +--- + +## Definition +Merge Point 是多智能体工作流中的关键同步节点，多个输入在此汇合后触发下一阶段。常见于一个 Agent 依赖多个前置 Agent 输出时的场景。 + +## Usage Scenario +在 landing page sprint 中，Frontend Developer 需要 Content Creator 和 UI Designer 的输出才能开始构建： + +``` +Content Creator ─┐ + ├──→ Merge Point → Frontend Developer +UI Designer ─────┘ +``` + +## Connections +- [[Multi-Agent Workflow]]：所属工作流模式 +- [[Parallel Kickoff]]：前置启动模式 +- [[Sequential Handoffs]]：相关交接概念 + diff --git a/wiki/concepts/Multi-Agent-Workflow.md b/wiki/concepts/Multi-Agent-Workflow.md new file mode 100644 index 00000000..73e3c52e --- /dev/null +++ b/wiki/concepts/Multi-Agent-Workflow.md @@ -0,0 +1,28 @@ +--- +title: "Multi-Agent Workflow" +type: concept +tags: [multi-agent, workflow, coordination] +last_updated: 2026-04-21 +--- + +## Definition +Multi-Agent Workflow 是一种多智能体协作架构，多个专业 Agent 通过分阶段并行工作实现复杂任务交付。每个 Agent 有独立角色、人格、优化的模型，通过共享内存+私有上下文实现协同。 + +## Key Components +- **独立角色**：每个 Agent 承担特定专业职责 +- **并行工作**：独立任务同时执行 +- **顺序交接**：依赖任务按序传递 +- **共享上下文**：通过共享内存保持信息一致性 + +## Pattern Types +- Parallel Kickoff：多个工作流同时启动 +- Merge Point：多输入汇合触发下一阶段 +- Feedback Loop：审查后迭代修改 +- Quality Gates：设置检查点确保质量 + +## Connections +- [[Multi-Agent Team]]：相关概念 +- [[Parallel Kickoff]]：并行启动模式 +- [[Merge Point]]：合并依赖点 +- [[Feedback Loop]]：反馈迭代机制 + diff --git a/wiki/concepts/Multi-Channel-Support.md b/wiki/concepts/Multi-Channel-Support.md new file mode 100644 index 00000000..53f49ba3 --- /dev/null +++ b/wiki/concepts/Multi-Channel-Support.md @@ -0,0 +1,36 @@ +--- +id: multi-channel-support +title: "Multi-Channel Support Framework" +type: concept +tags: [customer-service, support, framework] +sources: [support-support-responder.md] +last_updated: 2026-04-21 +--- + +## Definition +全渠道客户支持框架（Multi-Channel Support Framework），跨 email、live chat、phone、social media、in-app messaging 统一提供一致服务质量的客户支持架构。 + +## Support Channels +| Channel | Response Time SLA | Key Features | +|---------|------------------|--------------| +| Email | 2 hours | 优先级路由、工单跟踪 | +| Live Chat | 30 seconds | 并发限制 3、自动化路由 | +| Phone | 3 rings | 回拨选项、优先级队列 | +| Social Media | 1 hour | 关键词监控、私下升级 | +| In-App Messaging | 即时 | 上下文帮助、主动触发 | + +## Core Components +- Support Tiers：Tier 1（通用）、Tier 2（技术）、Tier 3（专家）的分层支持 +- Priority Routing：企业客户 > 计费问题 > 技术紧急情况 +- SLA Compliance：响应时间和解决时间的双重 SLA 监控 + +## Key Metrics +- First Response Time：首次响应平均时间 +- Resolution Time：从创建到解决的总时间 +- First Contact Resolution Rate：首次联系解决百分比 +- Customer Satisfaction (CSAT)：客户满意度评分 + +## Connections +- [[Support Responder]] — 实现该框架的核心智能体 +- [[Customer Success]] — 框架的服务目标 +- [[Knowledge Base Management]] — 框架的支持系统 \ No newline at end of file diff --git a/wiki/concepts/Multi-Jurisdictional-Compliance.md b/wiki/concepts/Multi-Jurisdictional-Compliance.md new file mode 100644 index 00000000..ab00908b --- /dev/null +++ b/wiki/concepts/Multi-Jurisdictional-Compliance.md @@ -0,0 +1,28 @@ +--- +title: "Multi-Jurisdictional Compliance" +type: concept +tags: [compliance, legal, multi-jurisdiction, regulatory] +sources: [support-legal-compliance-checker] +last_updated: 2026-04-21 +--- + +## Concept Summary +多司法管辖区合规指企业在多个国家/地区运营时，需要同时满足不同司法管辖区的法律法规要求的管理方法。 + +## Key Dimensions +- **监管框架**：GDPR（欧盟）、CCPA（加州）、HIPAA（医疗）、SOX（财务）、PCI-DSS（支付） +- **数据保护**：数据主体权利（访问、更正、删除、可携带）、数据本地化要求 +- **跨境传输**：Standard Contractual Clauses、adequacy decisions、数据驻留要求 +- **审计追踪**：决策文档化、法规引用、审批流程 + +## Compliance Assessment Template +监管合规评估报告包含： +1. Executive Summary（合规状态概述、风险评估总结） +2. Detailed Compliance Analysis（数据保护、行业特定合规、合同审查） +3. Risk Mitigation Strategies（关键风险领域、框架改进） +4. Implementation Roadmap（30天/90天/180+天阶段） + +## Relationship to Related Concepts +- [[Privacy Policy Generator]]：多辖区合规的具体实施工具 +- [[Contract Review System]]：跨境合同风险评估 +- [[GDPR Compliance Framework]]：欧盟数据保护核心框架 \ No newline at end of file diff --git a/wiki/concepts/POUR-Principles.md b/wiki/concepts/POUR-Principles.md new file mode 100644 index 00000000..112f81d0 --- /dev/null +++ b/wiki/concepts/POUR-Principles.md @@ -0,0 +1,79 @@ +--- +title: "POUR Principles" +description: WCAG 无障碍设计的四大核心原则：Perceivable、Operable、Understandable、Robust +tags: [accessibility, wcag, design-principles] +--- + +## Definition +POUR 是 WCAG（Web Content Accessibility Guidelines）无障碍设计的四大核心原则的首字母缩写，是评估数字产品无障碍性的基础框架。 + +## 四大原则 + +### P — Perceivable（可感知） +**核心要求**：所有信息都必须以用户可感知的方式呈现 + +具体要求： +- 提供文本替代方案（alt 文本、字幕） +- 提供音频描述 +- 内容可以以不同方式呈现（放大、高对比度） +- 区分前后景（足够对比度） + +技术要点： +- 图像 alt 文本 +- 视频字幕 +- 音频转录 +- 颜色对比度 ≥ 4.5:1 + +### O — Operable（可操作） +**核心要求**：所有功能都必须可以通过键盘操作 + +具体要求： +- 所有功能可通过键盘使用 +- 用户有足够时间阅读和使用内容 +- 不以可能引发癫痫的方式设计内容 +- 提供帮助用户导航和找到内容的机制 + +技术要点： +- 键盘可访问性 +- 跳过链接 +- 无键盘陷阱 +- 焦点指示器 + +### U — Understandable（可理解） +**核心要求**：信息和操作必须是可理解的 + +具体要求： +- 文本可读且可理解 +- 内容以可预测的方式出现和操作 +- 帮助用户避免和纠正错误 + +技术要点： +- 清晰的标签 +- 错误建议 +- 一致的导航 +- 简单语言 + +### R — Robust（健壮） +**核心要求**：内容必须能被各种用户代理可靠解释 + +具体要求： +- 使用标准兼容的技术 +- 状态信息可被辅助技术识别 +- 提供状态和变化的机器可读通知 + +技术要点： +- 语义 HTML +- ARIA 正确使用 +- 标准化技术 + +## 与 Accessibility Auditor 的关系 +[[Accessibility Auditor]] 智能体默认验证所有四个 POUR 原则，确保测试产品达到 WCAG 2.2 AA 级别合规。 + +## Related Concepts +- [[WCAG 2.2]] +- [[Screen Reader Testing]] +- [[Keyboard Navigation Audit]] + +## Source +- [[Accessibility Auditor]] +- W3C WCAG 2.2 \ No newline at end of file diff --git a/wiki/concepts/Parallel-Kickoff.md b/wiki/concepts/Parallel-Kickoff.md new file mode 100644 index 00000000..d7d8cb5a --- /dev/null +++ b/wiki/concepts/Parallel-Kickoff.md @@ -0,0 +1,29 @@ +--- +title: "Parallel Kickoff" +type: concept +tags: [multi-agent, workflow, parallel] +last_updated: 2026-04-21 +--- + +## Definition +Parallel Kickoff 是一种多智能体工作流启动模式，多个独立工作流同时开始执行，适用于相互之间无依赖关系的任务。 + +## Usage Scenario +在 landing page sprint 中，Content Creator 和 UI Designer 可同时开始工作，因二者相互独立： +- Content Creator 编写文案 +- UI Designer 设计规格 + +二者输出合并后交付给 Frontend Developer。 + +## Example +``` +Morning (9:00) +├── Content Creator → 编写文案（并行） +└── UI Designer → 设计规格（并行） +``` + +## Connections +- [[Multi-Agent Workflow]]：所属工作流模式 +- [[Merge Point]]：后续合并节点 +- [[Parallel Work]]：相关概念 + diff --git a/wiki/concepts/Parallel-Work.md b/wiki/concepts/Parallel-Work.md new file mode 100644 index 00000000..758ce8e9 --- /dev/null +++ b/wiki/concepts/Parallel-Work.md @@ -0,0 +1,46 @@ +--- +title: "Parallel Work" +type: concept +tags: [multi-agent, workflow, concurrency] +last_updated: 2026-04-21 +--- + +## Definition +并行工作（Parallel Work）是一种多智能体协作模式，其中多个智能体同时执行任务，通过独立工作减少总体完成时间。 + +## Core Principle +相互独立的任务可以同时由不同智能体处理，无需等待彼此完成。 + +## Workflow Pattern +``` +Agent A ─┬─→ [独立任务 A] + │ +Agent B ─┴─→ [独立任务 B] +``` + +## Example +在 Multi-Agent Workflow: Startup MVP 中： +- Week 1：Sprint Prioritizer 和 UX Researcher **并行运行** +- Week 2：Frontend Developer 和 Rapid Prototyper **并行构建** +- Week 3：Frontend Developer 继续 + Growth Hacker **启动策略规划** + +## Key Requirements +- 任务必须相互独立，无依赖关系 +- 需要明确的输入和输出定义 +- 输出最终需要合并或由协调者整合 + +## Advantages +- 减少总体执行时间 +- 充分利用并行处理能力 +- 加快 MVP 交付速度 + +## Disadvantages +- 增加了协调复杂度 +- 需要清晰的边界定义 +- 合并输出可能产生冲突 + +## Related Concepts +- [[Sequential Handoffs]]：顺序交接模式 +- [[Quality Gates]]：质量门控 +- [[Context Passing]]：上下文传递 +- [[Multi-Agent Team]]：多智能体团队 diff --git a/wiki/concepts/Predictive-Modeling.md b/wiki/concepts/Predictive-Modeling.md index 985214e0..efabd8e0 100644 --- a/wiki/concepts/Predictive-Modeling.md +++ b/wiki/concepts/Predictive-Modeling.md @@ -21,3 +21,16 @@ last_updated: 2026-04-20 - 采用率预测（Adoption Rate Predictions） - 置信区间（Confidence Intervals） - 情景概率权重（Probability Weighting） + +## Analytics Reporter Applications +- **客户流失预测**：识别高流失风险客户 +- **需求预测**：预测产品需求量，优化库存 +- **增长预测**：基于趋势外推预测收入增长 + +## Related Concepts +- [[Customer Lifetime Value]] +- [[Statistical Significance Testing]] + +## Sources +- [[raw/Agent/agency-agents/product/product-trend-researcher.md]] +- [[support-analytics-reporter]] diff --git a/wiki/concepts/Quality-Gates.md b/wiki/concepts/Quality-Gates.md new file mode 100644 index 00000000..3a8176ae --- /dev/null +++ b/wiki/concepts/Quality-Gates.md @@ -0,0 +1,38 @@ +--- +title: "Quality Gates" +type: concept +tags: [multi-agent, quality, workflow] +last_updated: 2026-04-21 +--- + +## Definition +质量门控（Quality Gates）是多智能体工作流中的关键检查点，在进入下一阶段前对当前输出进行生产就绪评估。 + +## Core Principle +在关键节点设置质量门槛，只有满足所有标准才能继续推进。 + +## Quality Gate Points +在 Multi-Agent Workflow: Startup MVP 中设置了两个质量门控： + +### Gate 1: Week 2 中点评估 +- 评估当前进度是否可达成目标 +- 识别需要削减的范围 +- 识别会，影响 Launch 的技术债务 + +### Gate 2: Week 4 最终评估 +- 评估产品 Launch 就绪状态 +- 检查错误监控、数据库备份等运维就绪 +- 要求证据支持每个验收标准 +- 提供 GO / NO-GO 决策 + +## Decision Outcomes +- **GO**：满足所有标准，可以进入下一阶段 +- **NO-GO**：不满足标准，需要修复后重新评估 +- **NEEDS WORK**：默认决策，保守策略 + +## Related Concepts +- [[Reality Checker]]：质量门控的执行者 +- [[Sequential Handoffs]]：顺序交接模式 +- [[Parallel Work]]：并行工作模式 +- [[Context Passing]]：上下文传递 +- [[Multi-Agent Team]]：多智能体团队 diff --git a/wiki/concepts/RFM-Analysis.md b/wiki/concepts/RFM-Analysis.md new file mode 100644 index 00000000..dc120253 --- /dev/null +++ b/wiki/concepts/RFM-Analysis.md @@ -0,0 +1,46 @@ +--- +title: "RFM Analysis" +type: concept +tags: [] +last_updated: 2026-04-21 +--- + +## Definition +客户价值分析的经典方法，通过三个维度评估客户：Recency（最近购买时间）、Frequency（购买频率）、Monetary（消费金额）。 + +## Scoring Method +- R Score：最近购买距离当前天数，越小分数越高（1-5 分） +- F Score：购买次数排名分位数（1-5 分） +- M Score：消费总额分位数（1-5 分） +- RFM Score：三个分数组合形成 555-111 的客户评分 + +## Customer Segments +| RFM Score | Segment | Strategy | +|-----------|---------|----------| +| 555, 554, 544, 545, 454, 455, 445 | Champions | 奖励忠诚度，请求推荐，升级 | +| 543, 444, 435, 355, 354, 345, 344, 335 | Loyal Customers | 培育关系，推荐新产品，会员计划 | +| 553, 551, 552, 541, 542, 533, 532, 531, 452, 451 | Potential Loyalists | 升级优惠，交叉销售 | +| 512, 511, 422, 421, 412, 411, 311 | New Customers | 优化入职，早期互动 | +| 155, 154, 144, 214, 215, 115, 114 | At Risk | 再激活活动，特别优惠 | + +## Implementation +```python +# RFM Analysis Python Implementation +rfm = df.groupby('customer_id').agg({ + 'date': lambda x: (current_date - x.max()).days, # Recency + 'order_id': 'count', # Frequency + 'revenue': 'sum' # Monetary +}).rename(columns={ + 'date': 'recency', + 'order_id': 'frequency', + 'revenue': 'monetary' +}) +``` + +## Related Concepts +- [[Customer Lifetime Value]] +- [[Data-Driven Decision Making]] + +## Source +- [[support-analytics-reporter]] + diff --git a/wiki/concepts/Screen-Reader-Testing.md b/wiki/concepts/Screen-Reader-Testing.md new file mode 100644 index 00000000..53eb95a1 --- /dev/null +++ b/wiki/concepts/Screen-Reader-Testing.md @@ -0,0 +1,51 @@ +--- +title: "Screen Reader Testing" +description: 使用屏幕阅读器验证网页内容可访问性的测试方法 +tags: [accessibility, testing, assistive-technology] +--- + +## Definition +Screen Reader Testing 是使用屏幕阅读器软件（如 VoiceOver、NVDA、JAWS）验证网页内容是否对视力障碍用户可访问的测试方法。 + +## 主要屏幕阅读器 +| 软件 | 平台 | 特点 | +|------|------|------| +| VoiceOver | macOS/iOS | Apple 设备内置，免费 | +| NVDA | Windows | 开源免费，社区活跃 | +| JAWS | Windows | 商业软件，功能全面 | +| TalkBack | Android | Android 内置 | +| VoiceOver | Safari (iOS) | 移动端测试 | + +## 测试协议 +### 导航测试 +- Heading Structure（标题层级） +- Landmark Regions（地标区域） +- Skip Links（跳转链接） +- Tab Order（Tab 顺序） +- Focus Visibility（焦点可见性） + +### 组件测试 +- Buttons（按钮角色和标签） +- Links（链接描述） +- Forms（表单标签和错误提示） +- Modals（焦点陷阱） +- Custom Widgets（自定义组件 ARIA） + +### 动态内容测试 +- Live Regions（实时区域） +- Loading States（加载状态） +- Error Messages（错误消息） +- Toast/Notifications（通知） + +## Key Findings Format +| 组件 | 屏幕阅读器行为 | 预期行为 | 状态 | +|------|--------------|---------|------| +| Name | 实际宣布内容 | 应该宣布的内容 | PASS/FAIL | + +## Related Concepts +- [[WCAG 2.2]] +- [[Keyboard Navigation Audit]] +- [[ARIA Patterns]] + +## Source +- [[Accessibility Auditor]] \ No newline at end of file diff --git a/wiki/concepts/Sequential-Handoffs.md b/wiki/concepts/Sequential-Handoffs.md new file mode 100644 index 00000000..0b257ede --- /dev/null +++ b/wiki/concepts/Sequential-Handoffs.md @@ -0,0 +1,44 @@ +--- +title: "Sequential Handoffs" +type: concept +tags: [multi-agent, workflow, coordination] +last_updated: 2026-04-21 +--- + +## Definition +顺序交接（Sequential Handoffs）是一种多智能体工作流模式，其中每个智能体的输出直接作为下一个智能体的输入，按顺序依次传递。 + +## Core Principle +每个智能体的完整输出（而非摘要）成为下一个智能体的输入，确保信息完整性和上下文连贯性。 + +## Workflow Pattern +``` +Agent A → [完整输出] → Agent B → [完整输出] → Agent C +``` + +## Key Rules +- **不摘要，只复制粘贴**：不要总结上一智能体的输出，直接使用完整输出 +- **保持完整性**：确保所有上下文、细节、证据都传递给下一个智能体 +- **按顺序执行**：必须等待前一个智能体完成后才能启动下一个 + +## Example +在 Multi-Agent Workflow: Startup MVP 中： +1. Sprint Prioritizer 完成冲刺计划 +2. 完整计划直接传给 Backend Architect +3. Backend Architect 完整输出传给 Frontend Developer + +## Advantages +- 最大化信息保留 +- 减少上下文丢失 +- 便于追溯和审计 + +## Disadvantages +- 可能增加处理时间 +- 需要更多上下文窗口 +- 顺序执行无法并行加速 + +## Related Concepts +- [[Parallel Work]]：并行工作模式 +- [[Quality Gates]]：质量门控 +- [[Context Passing]]：上下文传递 +- [[Multi-Agent Team]]：多智能体团队 diff --git a/wiki/concepts/Statistical-Significance-Testing.md b/wiki/concepts/Statistical-Significance-Testing.md new file mode 100644 index 00000000..2230999e --- /dev/null +++ b/wiki/concepts/Statistical-Significance-Testing.md @@ -0,0 +1,28 @@ +--- +title: "Statistical Significance Testing" +type: concept +tags: [] +last_updated: 2026-04-21 +--- + +## Definition +统计显著性检验，用于验证分析结论是否具有统计意义，而非随机偶然。 + +## Key Principles +- P-value < 0.05：结果具有统计显著性 +- 95% 置信区间：标准置信水平 +- 样本量验证：确保样本量足够检测预期效应 +- 效应量（Effect Size）：实际显著性而非仅统计显著性 + +## Application in Analytics +- A/B 测试结果验证 +- 营销活动效果评估 +- 趋势识别确认 +- 预测模型准确性验证 + +## Related Concepts +- [[Data-Driven Decision Making]] + +## Source +- [[support-analytics-reporter]] + diff --git a/wiki/concepts/Support-Analytics.md b/wiki/concepts/Support-Analytics.md new file mode 100644 index 00000000..e5567a55 --- /dev/null +++ b/wiki/concepts/Support-Analytics.md @@ -0,0 +1,45 @@ +--- +id: support-analytics +title: "Support Analytics" +type: concept +tags: [customer-service, analytics, metrics] +sources: [support-support-responder.md] +last_updated: 2026-04-21 +--- + +## Definition +支持分析（Support Analytics），客户支持团队的数据驱动性能监控和优化框架，计算响应时间、解决率、CSAT 等关键指标并识别改进机会。 + +## Key Metrics + +### Response Time Metrics +- **Average First Response Time**：从创建工单到首次响应平均耗时 +- **Average Resolution Time**：从创建到完全解决的平均耗时 +- **SLA Compliance Rate**：满足响应/解决 SLA 的百分比 + +### Quality Metrics +- **First Contact Resolution Rate**：首次联系解决百分比（目标 ≥ 80%） +- **Customer Satisfaction Score**：CSAT 平均分（目标 ≥ 4.5/5） +- **Ticket Volume by Channel**：各渠道工单分布 + +### Agent Performance +- **Tickets Handled**：单个 agent 处理工单数 +- **Average Resolution Time per Agent**：Agent 级平均解决时间 +- **CSAT Score per Agent**：Agent 级客户满意度 + +## Trend Analysis +- **Volume Trend**：日均工单量环比变化 +- **Top Issues**：高频问题分类统计 +- **Satisfaction Trend**：月度 CSAT 环比变化 +- **Response Time Trend**：周均响应时间环比变化 + +## Improvement Recommendations +基于数据分析的优化建议，优先级分类： +- **HIGH**：影响 SLA 或关键指标的改进 +- **MEDIUM**：效率提升机会 +- **LOW**：渐进优化 + +## Connections +- [[Support Responder]] — 分析数据的生成者 +- [[Customer Success]] — 分析驱动的主动干预目标 +- [[Knowledge Base Management]] — 分析揭示的知识缺口 \ No newline at end of file diff --git a/wiki/concepts/Support-Tiers.md b/wiki/concepts/Support-Tiers.md new file mode 100644 index 00000000..d4b97579 --- /dev/null +++ b/wiki/concepts/Support-Tiers.md @@ -0,0 +1,53 @@ +--- +id: support-tiers +title: "Support Tiers" +type: concept +tags: [customer-service, support, escalation] +sources: [support-support-responder.md] +last_updated: 2026-04-21 +--- + +## Definition +支持层级（Support Tiers），分层客户服务架构，根据问题复杂度和客户类型将请求分配到不同专业级别的支持团队。 + +## Tier Structure + +### Tier 1 — General Support +**Capabilities**： +- Account Management：账户创建、修改、恢复 +- Basic Troubleshooting：常见问题诊断和解决 +- Product Information：产品功能和使用指导 +- Billing Inquiries：账单查询和基本计费问题 + +**Escalation Criteria**： +- 技术复杂度超出基础知识范围 +- 政策例外请求需要管理层批准 +- 客户表达不满且一线无法解决 + +### Tier 2 — Technical Support +**Capabilities**： +- Advanced Troubleshooting：复杂技术问题诊断 +- Integration Support：API 和系统集成支持 +- Custom Configuration：定制化配置指导 +- Bug Reproduction：问题复现和日志分析 + +**Escalation Criteria**： +- 需要工程团队介入的代码级别问题 +- 安全相关问题需要安全团队 +- 数据恢复需要 DBA 支持 + +### Tier 3 — Specialist Support +**Capabilities**： +- Enterprise Support：企业级客户专属支持 +- Custom Development：定制开发需求评估 +- Security Incidents：安全事件响应 +- Data Recovery：重大数据恢复操作 + +**Escalation Criteria**： +- C-Level 管理层涉及 +- 法律咨询需求 +- 需要产品团队深度协作 + +## Connections +- [[Multi-Channel Support Framework]] — 层级嵌入的框架 +- [[Support Responder]] — 层级执行的主体 \ No newline at end of file diff --git a/wiki/concepts/TCO-Total-Cost-of-Ownership.md b/wiki/concepts/TCO-Total-Cost-of-Ownership.md new file mode 100644 index 00000000..cec1998c --- /dev/null +++ b/wiki/concepts/TCO-Total-Cost-of-Ownership.md @@ -0,0 +1,36 @@ +--- +title: "TCO (Total Cost of Ownership)" +type: concept +tags: [cost-analysis, roi, tool-evaluation] +sources: [] +last_updated: 2026-04-21 +--- + +## Summary +总拥有成本（TCO）是一种综合成本分析方法，计算工具或系统的全生命周期成本，支持长期投资决策。 + +## Definition +TCO 包含以下成本组成部分： +- 许可费用（licensing） +- 实施成本（implementation） +- 培训成本（training） +- 维护成本（maintenance） +- 集成成本（integration） +- 迁移成本（migration） +- 支持成本（support） + +## Formula +``` +TCO = (年许可费 × 年数) + 实施费 + 培训费 + (年维护费 × 年数) + 集成费 + 迁移费 + (年支持费 × 年数) +``` + +## Application +- 工具选择决策 +- 预算规划 +- ROI 计算 +- 供应商比较 + +## Related Concepts +- [[Tool Evaluation Framework]] +- [[ROI Analysis]] +- [[Vendor Management]] diff --git a/wiki/concepts/Time-boxed.md b/wiki/concepts/Time-boxed.md new file mode 100644 index 00000000..bae67392 --- /dev/null +++ b/wiki/concepts/Time-boxed.md @@ -0,0 +1,30 @@ +--- +title: "Time-boxed" +type: concept +tags: [workflow, time-management, scope-control] +last_updated: 2026-04-21 +--- + +## Definition +Time-boxed 是一种时间管理机制，为单一任务设置最大时长限制，防止范围蔓延和无限期延误。 + +## Purpose +- 防止范围蔓延（scope creep） +- 确保交付时间线 +- 提高专注度 +- 加速决策 + +## Example +Landing page sprint 时间表： +| Time | Activity | Agent | +|------|----------|-------| +| 9:00 | Copy + design kick off | Content Creator + UI Designer | +| 11:00 | Build starts | Frontend Developer | +| 14:00 | First version ready | — | +| 15:30 | Apply feedback | Frontend Developer | +| 16:30 | Ship | Deploy | + +## Connections +- [[Multi-Agent Workflow]]：所属工作流模式 +- [[Sprint Planning]]：相关时间规划概念 + diff --git a/wiki/concepts/Tool-Evaluation-Framework.md b/wiki/concepts/Tool-Evaluation-Framework.md new file mode 100644 index 00000000..aab14dc9 --- /dev/null +++ b/wiki/concepts/Tool-Evaluation-Framework.md @@ -0,0 +1,33 @@ +--- +title: "Tool Evaluation Framework" +type: concept +tags: [tool-evaluation, framework, methodology] +sources: [] +last_updated: 2026-04-21 +--- + +## Summary +工具评估框架是一种结构化的定量评估方法，通过加权评分体系对工具进行多维度评估，支持企业级工具选择决策。 + +## Definition +采用多准则决策分析（MCDA），通过七个核心维度对工具进行全面评估： +- 功能性（functionality） +- 可用性（usability） +- 性能（performance） +- 安全性（security） +- 集成（integration） +- 支持（support） +- 成本（cost） + +## Key Metrics +- 功能性测试：required features 80% + optional features 20% +- 性能测试：平均响应时间、P95 响应时间 +- TCO 计算：许可 + 实施 + 培训 + 维护 + 集成 + 迁移 + 支持 + +## Application +用于企业工具选择、供应商评估、投资回报分析等场景。 + +## Related Concepts +- [[TCO（Total Cost of Ownership）]] +- [[ROI Analysis]] +- [[Vendor Management]] diff --git a/wiki/concepts/Versioned-Draft.md b/wiki/concepts/Versioned-Draft.md new file mode 100644 index 00000000..13fa6352 --- /dev/null +++ b/wiki/concepts/Versioned-Draft.md @@ -0,0 +1,25 @@ +--- +title: "Versioned Draft" +type: concept +tags: [writing, workflow, revision] +sources: [sources/workflow-book-chapter.md] +last_updated: 2026-04-21 +--- + +## 定义 +版本化草稿是通过迭代修订循环产生的带版本号的章节草稿，每一版本基于前版本的编辑注释进行改进。 + +## 核心特征 +- 带版本编号（如 Version 1、Version 2） +- 基于反馈进行渐进改进 +- 记录编辑决策和假设 +- 暴露开放编辑问题供作者决策 + +## 与反馈循环的关系 +版本化草稿依赖反馈循环机制： +- Feedback Loop 提供结构化修订请求 +- Editorial Notes 标注假设和证据缺口 +- Next Step 定义下一版本的改进方向 + +## Aliases +- 版本化草稿 diff --git a/wiki/concepts/WCAG-2-2.md b/wiki/concepts/WCAG-2-2.md new file mode 100644 index 00000000..00695385 --- /dev/null +++ b/wiki/concepts/WCAG-2-2.md @@ -0,0 +1,45 @@ +--- +title: "WCAG 2.2" +description: Web Content Accessibility Guidelines 2.2，网页内容无障碍指南的国际标准 +tags: [accessibility, standards, wcag] +--- + +## Definition +WCAG 2.2（Web Content Accessibility Guidelines 2.2）是 W3C 发布的网页内容无障碍指南标准，是国际公认的网站无障碍设计规范。最新版本于 2023 年 10 月正式发布。 + +## POUR Principles（四大原则） +### Perceivable（可感知） +- 所有信息都必须以用户可感知的方式呈现 +- 包括文本替代、字幕、放大功能等 + +### Operable（可操作） +- 所有功能都必须可以通过键盘操作 +- 不能依赖特定设备或输入方式 + +### Understandable（可理解） +- 信息和操作必须是可理解的 +- 避免歧义，提供清晰的错误提示 + +### Robust（健壮） +- 内容必须能被各种用户代理可靠解释 +- 包括辅助技术和未来兼容性 + +## Conformance Levels +- **Level A**：最低要求，必须满足 +- **Level AA**：标准要求，大多数合规标准以此为准 +- **Level AAA**：最高要求，适用于特定场景 + +## Key Success Criteria +- 1.4.3 Contrast Minimum（对比度最低 4.5:1） +- 2.1.1 Keyboard（所有功能可键盘操作） +- 2.4.7 Focus Visible（焦点可见性） +- 4.1.2 Name, Role, Value（名称、角色、值可机器读取） + +## Related Concepts +- [[Screen Reader Testing]] +- [[Keyboard Navigation Audit]] +- [[POUR Principles]] + +## Source +- [[Accessibility Auditor]] +- W3C WCAG 2.2 Official \ No newline at end of file diff --git a/wiki/entities/Accessibility-Auditor.md b/wiki/entities/Accessibility-Auditor.md new file mode 100644 index 00000000..dfc8677e --- /dev/null +++ b/wiki/entities/Accessibility-Auditor.md @@ -0,0 +1,51 @@ +--- +title: "Accessibility Auditor" +description: The Agency 项目中的无障碍审计专家智能体，专注于 WCAG 2.2 合规测试 +tags: [agent, the-agency, accessibility] +last_updated: 2026-04-21 +--- + +## Definition +Accessibility Auditor 是 The Agency 项目中的专家智能体，专注于无障碍审计、辅助技术测试和包容性设计验证。 + +## Core Mission +- 基于 WCAG 2.2 标准审计界面 +- 测试辅助技术兼容性（VoiceOver、NVDA、JAWS） +- 捕获自动化工具遗漏的 70% 问题 +- 提供可操作的修复指导 + +## Personality +- 彻底（Thorough） +- 倡导驱动（Advocacy-driven） +- 标准痴迷（Standards-obsessed） +- 同理心基础（Empathy-grounded） + +## Key Principles +1. **诚实评估**：Lighthouse 绿分 ≠ 真正无障碍 +2. **默认有罪**：自定义组件在证明无罪前视为有罪 +3. **键盘测试**："能用鼠标"不是测试 +4. **语义优先**：最好的 ARIA 是不需要用的 ARIA + +## Testing Methodology +- **自动化扫描**：axe-core、Lighthouse +- **手动辅助技术测试**：屏幕阅读器、纯键盘 +- **视觉测试**：200%/400% 缩放、高对比度、减少动画 +- **组件深挖**：WAI-ARIA Authoring Practices 对标 + +## Severity Classification +- **Critical**：完全阻断访问 +- **Serious**：需要变通方案 +- **Moderate**：有困难但有变通 +- **Minor**：降低可用性 + +## Related Agents +- [[Testing Reality Checker]] — 协作进行生产就绪验证 +- [[Evidence Collector]] — 提供视觉 QA 测试用例 +- [[Frontend Developer]] — 接收 ARIA 正确性审查 +- [[UI Designer]] — 接收对比度和目标尺寸反馈 + +## Source +- [[Accessibility Auditor Source|testing-accessibility-auditor]] + +## Updated From +The Agency 项目 - agency-agents/testing/testing-accessibility-auditor.md \ No newline at end of file diff --git a/wiki/entities/Content-Creator.md b/wiki/entities/Content-Creator.md new file mode 100644 index 00000000..93d04e0e --- /dev/null +++ b/wiki/entities/Content-Creator.md @@ -0,0 +1,36 @@ +--- +title: "Content Creator" +type: entity +tags: [agent, the-agency, content-creation] +last_updated: 2026-04-21 +--- + +## Definition +Content Creator 是 The Agency 项目中的内容创作智能体，专注于编写高质量营销文案和着陆页内容。 + +## Role +- 文案撰写专家 +- 营销内容创作者 +- 信息架构师 + +## Key Responsibilities +- 编写 landing page 文案（标题、副标题、CTA） +- 撰写问题陈述（痛点描述） +- 制定"How it works"步骤说明 +- 创建社会证明内容（用户证言格式） +- 设计定价文案 + +## Deliverables +- Hero 文案（标题 + 副标题 + CTA） +- 问题陈述（3 个痛点） +- 操作指南（3 步骤） +- 社会证明模板 +- 定价文案（3 个层级） +- 最终 CTA + +## Connections +- [[The Agency]]：所属项目 +- [[UI Designer]]：并行协作，获取设计规格 +- [[Frontend Developer]]：提供文案输入 +- [[Growth Hacker]]：提供增长优化反馈 + diff --git a/wiki/entities/FinanceTracker.md b/wiki/entities/FinanceTracker.md new file mode 100644 index 00000000..23a0c85c --- /dev/null +++ b/wiki/entities/FinanceTracker.md @@ -0,0 +1,18 @@ +--- +title: "Finance Tracker" +type: entity +tags: [agent, finance] +sources: [support-finance-tracker] +last_updated: 2026-04-21 +--- + +Finance Tracker 是 The Agency 体系中的财务分析与控制智能体人格，职责包括预算编制、现金流预测、投资分析与合规审计准备。与 Support Analytics Reporter、Accounts Payable Agent 协作提供数据与执行建议。 + +## Responsibilities +- 预算与差异分析 +- 滚动现金流预测与低现金预警 +- 投资可行性分析（NPV/IRR/回收期） +- 财务控制与审计准备 + +## Sources +- [[sources/support-finance-tracker.md]] diff --git a/wiki/entities/FlowSync.md b/wiki/entities/FlowSync.md new file mode 100644 index 00000000..df743d50 --- /dev/null +++ b/wiki/entities/FlowSync.md @@ -0,0 +1,23 @@ +--- +title: "FlowSync" +type: entity +tags: [product, saas, api-integration] +last_updated: 2026-04-21 +--- + +## Definition +FlowSync 是一个虚构的 API 集成平台产品，用于演示多智能体 landing page sprint 工作流。在该场景中，FlowSync 定位为连接任何两个 SaaS 工具的在线集成平台，承诺 5 分钟内完成集成。 + +## Product Details +- 类型：API 集成平台（SaaS） +- 目标用户：中型公司开发者和技术 PM +- 核心价值主张：5 分钟内连接任意两个 SaaS 工具 + +## Target Audience +- 开发者 +- 技术产品经理 +- 中型公司 + +## Connections +- [[Multi-Agent Workflow: Landing Page Sprint]]：演示用产品 + diff --git a/wiki/entities/Frontend-Developer.md b/wiki/entities/Frontend-Developer.md new file mode 100644 index 00000000..01e9234d --- /dev/null +++ b/wiki/entities/Frontend-Developer.md @@ -0,0 +1,34 @@ +--- +title: "Frontend Developer" +type: entity +tags: [agent, the-agency, frontend-development] +last_updated: 2026-04-21 +--- + +## Definition +Frontend Developer 是 The Agency 项目中的前端开发智能体，专注于使用 HTML、Tailwind CSS 和 minimal vanilla JS 构建高质量 landing page。 + +## Role +- 前端开发工程师 +- UI 构建专家 +- 响应式设计实现者 + +## Key Responsibilities +- 根据文案和设计规格构建 landing page +- 实现响应式设计（mobile-first） +- 优化页面性能（无重型资源、system fonts） +- 确保可访问性（proper headings、alt text、focus states） +- 实现可工作的邮件订阅表单 + +## Deliverables +- 单文件 index.html（可直接部署） +- 响应式布局 +- 可访问性合规 +- 邮件订阅表单集成 + +## Connections +- [[The Agency]]：所属项目 +- [[Content Creator]]：依赖文案输入 +- [[UI Designer]]：依赖设计规格 +- [[Growth Hacker]]：应用增长优化反馈 + diff --git a/wiki/entities/Growth-Hacker.md b/wiki/entities/Growth-Hacker.md new file mode 100644 index 00000000..7abf4386 --- /dev/null +++ b/wiki/entities/Growth-Hacker.md @@ -0,0 +1,37 @@ +--- +title: "Growth Hacker" +type: entity +tags: [agent, the-agency, growth-marketing] +last_updated: 2026-04-21 +--- + +## Definition +Growth Hacker 是 The Agency 项目中的增长黑客智能体，专注于制定和执行产品 launch 策略，通过数据驱动的方法最大化产品曝光和用户获取。 + +## Role +- Launch 策略规划师 +- 增长营销专家 +- 渠道优化专家 + +## Key Responsibilities +- 制定产品 launch 计划和时间线 +- 识别最优增长渠道（Product Hunt、Reddit、Hacker News、Twitter） +- 设计用户获取和激活策略 +- 建立 Launch 度量指标体系 + +## Deliverables +- Launch 计划文档 +- 渠道策略报告 +- 用户获取路线图 +- 度量指标定义 + +## Aliases +- Growth Strategist +- Launch Manager +- Marketing Strategist + +## Connections +- [[The Agency]]：所属项目 +- [[Frontend Developer]]：Week 3 并行工作，完成产品准备 +- [[Reality Checker]]：最终评估产品生产就绪状态 +- [[Product Manager Agent]]：协调产品 Launch 流程 diff --git a/wiki/entities/Legal-Compliance-Checker.md b/wiki/entities/Legal-Compliance-Checker.md new file mode 100644 index 00000000..7e3e5b40 --- /dev/null +++ b/wiki/entities/Legal-Compliance-Checker.md @@ -0,0 +1,33 @@ +--- +title: "Legal Compliance Checker" +type: entity +tags: [agent, the-agency, compliance, legal] +sources: [support-legal-compliance-checker] +last_updated: 2026-04-21 +--- + +## Entity Summary +The Agency 项目中的法律合规检查专家智能体，专注于多司法管辖区监管合规、风险评估、政策开发与合规监控。 + +## Core Capabilities +- 多司法管辖区合规监控（GDPR、CCPA、HIPAA、SOX、PCI-DSS） +- 隐私政策与数据处理程序开发 +- 合同审查与风险评估 +- 合规培训与文化建设 +- 事件响应与监管报告 + +## Key Frameworks +- GDPR Compliance Framework +- Privacy Policy Generator（Python 类） +- Contract Review System（风险关键词扫描） +- Regulatory Compliance Assessment Report（评估报告模板） + +## Success Metrics +- 监管合规维持 98%+ 覆盖率 +- 法律风险暴露最小化，零监管处罚 +- 政策合规达到 95%+ 员工遵守率 +- 审计结果零关键发现 + +## Related Entities +- [[Healthcare Marketing Compliance Specialist]]：共享合规方法论 +- [[The Agency]]：所属项目 \ No newline at end of file diff --git a/wiki/entities/Rapid-Prototyper.md b/wiki/entities/Rapid-Prototyper.md new file mode 100644 index 00000000..94392f7e --- /dev/null +++ b/wiki/entities/Rapid-Prototyper.md @@ -0,0 +1,36 @@ +--- +title: "Rapid Prototyper" +type: entity +tags: [agent, the-agency, development] +last_updated: 2026-04-21 +--- + +## Definition +Rapid Prototyper 是 The Agency 项目中的快速原型智能体，专注于加速初始版本落地，通过最小化可行产品快速验证核心假设。 + +## Role +- 快速原型开发专家 +- MVP 验证专家 +- 敏捷开发加速器 + +## Key Responsibilities +- 以最快速度构建产品初始版本 +- 聚焦核心功能，剥离非必要复杂度 +- 快速迭代，基于反馈持续改进 +- 尽早交付可用的产品原型 + +## Deliverables +- 可运行的产品原型 +- 核心功能实现 +- 快速迭代建议 + +## Aliases +- Prototype Developer +- MVP Builder +- Speed-focused Developer + +## Connections +- [[The Agency]]：所属项目 +- [[Frontend Developer]]：并行协作，构建用户界面 +- [[Reality Checker]]：在关键节点进行生产就绪评估 +- [[Product Manager Agent]]：接收产品需求 diff --git a/wiki/entities/Reality-Checker.md b/wiki/entities/Reality-Checker.md new file mode 100644 index 00000000..a9bcf573 --- /dev/null +++ b/wiki/entities/Reality-Checker.md @@ -0,0 +1,47 @@ +--- +title: "Reality Checker" +type: entity +tags: [agent, the-agency, quality-assurance] +last_updated: 2026-04-21 +--- + +## Definition +Reality Checker 是 The Agency 项目中的现实检查智能体，在关键开发节点进行生产就绪评估，通过证据驱动的审查确保产品按时高质量交付。 + +## Role +- 生产就绪评估专家 +- 质量门控守护者 +- 风险识别专家 + +## Key Responsibilities +- 在关键节点进行生产就绪评估（质量门控） +- 要求证据支持每个验收标准 +- 识别技术债务和潜在风险 +- 提供 GO / NO-GO 决策建议 + +## Key Checkpoints +- Week 2 中点评估：评估当前进度，决定是否可以继续 +- Week 4 最终评估：评估产品 Launch 就绪状态 + +## Deliverables +- 生产就绪评估报告 +- 风险识别清单 +- GO / NO-GO 决策建议 +- 技术债务报告 + +## Decision Framework +- 需要证据支持每个标准 +- 默认决策：NEEDS WORK（保守策略） +- 发现问题时要求回滚到相关专家修复 + +## Aliases +- Quality Gatekeeper +- Production Readiness Checker +- Reality Audit Agent + +## Connections +- [[The Agency]]：所属项目 +- [[Sprint Prioritizer]]：提供冲刺计划 +- [[Frontend Developer]]：评估前端开发进度 +- [[Growth Hacker]]：最终评估 Launch 就绪状态 +- [[Reality Checker]]：自身作为质量门控存在 diff --git a/wiki/entities/Sprint-Prioritizer.md b/wiki/entities/Sprint-Prioritizer.md new file mode 100644 index 00000000..7f4a1e50 --- /dev/null +++ b/wiki/entities/Sprint-Prioritizer.md @@ -0,0 +1,37 @@ +--- +title: "Sprint Prioritizer" +type: entity +tags: [agent, the-agency, project-management] +last_updated: 2026-04-21 +--- + +## Definition +Sprint Prioritizer 是 The Agency 项目中的产品冲刺优先级智能体，专注于敏捷冲刺规划、功能优先排序和资源分配，通过 RICE、MoSCoW、Kano 等数据驱动框架最大化团队效率。 + +## Role +- 敏捷冲刺规划专家 +- 功能优先级排序专家 +- 资源分配策略师 + +## Key Responsibilities +- 将大型项目分解为可管理的冲刺周期 +- 为每个冲刺定义明确的交付物和验收标准 +- 应用 RICE、MoSCoW、Kano 等框架进行功能优先级排序 +- 评估团队容量并设置现实的目标 + +## Deliverables +- 冲刺计划文档 +- 优先级排序矩阵 +- 交付物清单 +- 验收标准定义 + +## Aliases +- Sprint Planner +- Product Prioritizer +- Agile Prioritizer + +## Connections +- [[The Agency]]：所属项目 +- [[Product Sprint Prioritizer]]：相关智能体 +- [[Reality Checker]]：质量门控，评估冲刺输出的可行性 +- [[Backend Architect]]：接收冲刺计划作为输入 diff --git a/wiki/entities/Support-Responder.md b/wiki/entities/Support-Responder.md new file mode 100644 index 00000000..d948563c --- /dev/null +++ b/wiki/entities/Support-Responder.md @@ -0,0 +1,32 @@ +--- +id: support-responder +title: "Support Responder" +type: entity +tags: [agent, customer-service, the-agency] +sources: [support-support-responder.md] +last_updated: 2026-04-21 +--- + +## Definition +客户支持专家智能体（Customer Support Specialist Agent），属于 The Agency 项目 support 部门，专注于多渠道客户服务、问题解决和用户体验优化。 + +## Role +- Customer Service Excellence：跨 email、chat、phone、social media、in-app messaging 提供全面支持 +- Issue Resolution：系统性故障排除和协作性问题解决 +- User Experience Optimization：通过主动关怀将沮丧用户转化为忠诚拥护者 + +## Personality +- Empathetic：深度理解客户 frustration 并表达共情 +- Solution-focused：聚焦可执行解决方案和明确时间线 +- Proactive：主动预防而非被动响应 +- Customer-obsessed：以客户满意度和留存为核心驱动力 + +## Aliases +- Support Specialist +- Customer Service Agent +- Support Responder Agent + +## Connections +- [[The Agency]] — 所属项目 +- [[Support Legal Compliance Checker]] — 共享合规框架的同部门智能体 +- [[Product Feedback Synthesizer]] — 依赖其提供的客户反馈数据 \ No newline at end of file diff --git a/wiki/entities/The-Agency.md b/wiki/entities/The-Agency.md index 4ad40877..5bfdebb5 100644 --- a/wiki/entities/The-Agency.md +++ b/wiki/entities/The-Agency.md @@ -43,12 +43,14 @@ tags: [project, ai-agents, open-source] |- [[Identity Graph Operator]]：共享身份图操作智能体，负责实体解析、合并与冲突治理 |- [[Terminal Integration Specialist]]：终端仿真和 SwiftTerm 集成专家智能体 |- [[Civil Engineer]]：土木与结构工程智能体，负责多国规范下的结构分析、岩土设计和建筑合规 +|- [[Accessibility Auditor]]：无障碍审计专家智能体，专注于 WCAG 2.2 标准审计、辅助技术测试和包容性设计验证 |- [[Compliance Auditor]]：技术合规审计专家智能体，专注于 SOC 2、ISO 27001、HIPAA 和 PCI-DSS 认证流程 - [[Study Abroad Advisor]]：留学规划专家智能体，为中国学生提供全流程留学申请策略指导，覆盖美、英、加、澳、欧、港、新等主要留学目的地 - [[Blockchain Security Auditor]]：智能合约安全审计专家智能体，专注于漏洞检测、形式化验证和 DeFi 协议安全审计 - [[Product Trend Researcher]]：市场情报与趋势研究专家智能体，专注于新兴趋势识别、竞争分析和机会评估 - [[Product Manager Agent]]：产品经理智能体，通过 6 阶段工作流程驱动产品从想法到落地 - [[Product Feedback Synthesizer]]：用户反馈合成专家智能体，专注于多渠道用户反馈收集、分析和战略建议 +- [[Support Infrastructure Maintainer]]：基础设施运维专家智能体，专注于系统可靠性、性能优化和技术运营管理，确保 99.9%+ 正常运行时间 ## 别名 - agency-agents：GitHub 仓库名称 diff --git a/wiki/entities/Tool-Evaluator-Agent.md b/wiki/entities/Tool-Evaluator-Agent.md new file mode 100644 index 00000000..60a77bac --- /dev/null +++ b/wiki/entities/Tool-Evaluator-Agent.md @@ -0,0 +1,51 @@ +--- +title: "Tool Evaluator Agent" +type: entity +tags: [agent, the-agency, testing, tool-evaluation] +sources: [] +last_updated: 2026-04-21 +--- + +## Source File +- [[raw/Agent/agency-agents/testing/testing-tool-evaluator.md]] + +## Summary +Tool Evaluator Agent 是 The Agency 项目中的技术评估与战略工具采纳专家智能体，专注于评估、测试和推荐工具、软件和平台以实现业务生产力和投资回报率优化。 + +## Core Mission +- 全面工具评估与选择 +- 用户体验与采用策略 +- 供应商管理与合同优化 + +## Evaluation Framework +采用七维度加权评分体系： +- 功能性（0.25）：核心功能完整性 +- 可用性（0.20）：用户体验 +- 性能（0.15）：速度、可靠性、可扩展性 +- 安全性（0.15）：数据保护与合规 +- 集成（0.10）：API 质量与系统兼容性 +- 支持（0.08）：供应商支持质量与文档 +- 成本（0.07）：总拥有成本与价值 + +## Success Metrics +- 90% 工具推荐满足或超过预期表现 +- 85% 工具采用率（6个月内） +- 20% 平均工具成本降低 +- 25% 平均 ROI 达成 +- 4.5/5 利益相关者满意度 + +## Key Methods +- TCO（总拥有成本）分析 +- ROI 敏感性分析 +- 供应商稳定性评估 +- 实施风险评估 +- 变更管理策略 + +## Related Agents +- [[Test Results Analyzer]] +- [[Evidence Collector]] +- [[Performance Benchmarker]] +- [[Reality Checker]] + +## Aliases +- Tool Evaluator diff --git a/wiki/index.md b/wiki/index.md index 7d13f92d..f08500b6 100644 --- a/wiki/index.md +++ b/wiki/index.md @@ -32,13 +32,19 @@ 32|- [Obsidian CLI 命令全景速查表](sources/Obsidian-官方-CLI-命令-全景-速查表.md) — Obsidian 官方 CLI 命令速查与自动化工作流（版本要求 v1.12+） 33| 34|## Sources +- [Workflow Example: Book Chapter Development](sources/workflow-book-chapter.md) — AI Agent 将粗糙素材转化为战略性第一人称书籍章节草稿的工作流 +- [Multi-Agent Workflow: Startup MVP](sources/workflow-startup-mvp.md) — A step-by-step example of how to coordinate multiple agents to go from idea to shipped MVP +- [Multi-Agent Workflow: Startup MVP with Persistent Memory](sources/workflow-with-memory.md) — 基于 MCP Memory Server 的多智能体协作工作流，解决手动交接上下文丢失问题 +- [Multi-Agent Workflow: Landing Page Sprint](sources/multi-agent-workflow-landing-page-sprint.md) — 多智能体协作在一天内完成高转化率 landing page 开发的 sprint 工作流 - [Healthcare Marketing Compliance Specialist](sources/healthcare-marketing-compliance.md) — Chinese healthcare marketing compliance, from ads to privacy and platform rules - 35|- [UI Designer](sources/design-ui-designer.md) — The Agency 项目中的 UI Designer 智能体，专门负责创建美观、一致、可访问的用户界面 +- [Legal Compliance Checker](sources/support-legal-compliance-checker.md) — The Agency 项目中的法律合规检查专家智能体，专注于多司法管辖区监管合规 +- [UI Designer](sources/design-ui-designer.md) — The Agency 项目中的 UI Designer 智能体，专门负责创建美观、一致、可访问的用户界面 36|- [UX Researcher](sources/design-ux-researcher.md) — The Agency 项目中的用户体验研究智能体，专注于用户行为分析和数据驱动的设计决策 37|- [Contributing to The Agency](sources/the-agency-contributing.md) — The Agency 项目的贡献指南，涵盖智能体设计规范、PR 流程 38|- [为 The Agency 贡献代码](sources/contributing-zh-cn.md) — The Agency 项目的贡献指南，涵盖智能体设计规范、PR 流程和社区参与方式 39|- [UX Architect Agent 设计文档](sources/design-ux-architect.md) — UX Architect 技术架构与 UX 专家智能体设计规范，涵盖 CSS 设计系统、布局框架、主题切换机制 - [Security Policy](sources/SECURITY.md) — agency-agents 项目的安全漏洞报告规范与贡献者安全最佳实践 +- [Examples (Agency Agents)](sources/agency-agents-examples.md) — 多智能体编排示例集，展示 8 个专业智能体并行协作的产品发现完整流程 40| 41|- [Senior Project Manager](sources/project-manager-senior.md) — Converts specifications into developer-ready task lists, enforces realistic scope, and maintains project memory 42|- [Experiment Tracker](sources/project-management-experiment-tracker.md) — 实验设计与执行跟踪智能体，专注于 A/B 测试、假设验证和数据驱动决策 @@ -68,6 +74,8 @@ - [Document Generator](sources/specialized-document-generator.md) — The Agency 项目中的程序化文档创建智能体，负责 PDF、PPTX、XLSX 与 DOCX 的代码化生成 - [Developer Advocate](sources/specialized-developer-advocate.md) — The Agency 项目中的开发者关系工程师、社区建设者和 DX 架构师，通过技术内容创作、社区参与和产品反馈闭环驱动开发者成功 - [Product Feedback Synthesizer](sources/product-feedback-synthesizer.md) — The Agency 项目中的用户反馈合成专家智能体，专注于从多渠道收集、分析和合成用户反馈，将定性反馈转化为可量化的产品优先级和战略建议 +- [Support Responder](sources/support-support-responder.md) — The Agency 项目中的客户支持专家智能体，提供全渠道客户服务、问题解决和用户体验优化 +- [Executive Summary Generator](sources/support-executive-summary-generator.md) — The Agency 项目中的战略咨询风格执行摘要生成智能体，使用 McKinsey SCQA、BCG Pyramid、Bain 框架 - [Product Manager](sources/product-manager.md) — The Agency 项目中的产品经理智能体，定义完整产品生命周期管理框架，涵盖 PRD、机会评估、路线图、GTM 和冲刺健康快照 - [Product Trend Researcher](sources/product-trend-researcher.md) — The Agency 项目中的市场情报与趋势研究专家智能体，专注于新兴趋势识别、竞争分析和机会评估 - [Product Sprint Prioritizer](sources/product-sprint-prioritizer.md) — The Agency 项目中的产品冲刺优先级智能体，专注于敏捷冲刺规划、功能优先排序和资源分配 @@ -223,7 +231,26 @@ 194|- [Claude Code Integration](sources/claude-code-readme.md) — Notes for using The Agency agents natively with Claude Code (no conversion required) 195|- [MCP Memory Integration](sources/mcp-memory-readme.md) — How to add persistent cross-session memory to agents using MCP servers (`remember`, `recall`, `rollback`, `search`) 196|- [Backend Architect (with Memory)](sources/backend-architect-with-memory.md) — Backend Architect persona with MCP Memory Integration pattern - 197|- [Multi-Agent Content Factory](sources/multi-agent-content-factory.md) — 在 Discord 中构建多 Agent 内容工厂，实现研究→写作→设计自动化流水线 + 197|- [OpenClaw Integration](sources/openclaw-readme.md) — OpenClaw workspace integration (SOUL.md, AGENTS.md, IDENTITY.md) + 198|- [Cursor Integration](sources/cursor-readme.md) — Convert agents into Cursor `.mdc` project-scoped rule files + 199|- [GitHub Copilot Integration](sources/github-copilot-readme.md) — Agents are compatible with GitHub Copilot `.md` + YAML frontmatter format + 200|- [Gemini CLI Integration](sources/gemini-cli-readme.md) — Package Agency agents as a Gemini CLI extension under `~/.gemini/extensions/agency-agents/` + 201|- [Windsurf Integration](sources/windsurf-readme.md) — Consolidate the full Agency roster into a single `.windsurfrules` file (project-scoped) + 202|- [Antigravity Integration](sources/antigravity-readme.md) — Install Agency agents as Antigravity `agency-` prefixed skills under `~/.gemini/antigravity/skills/` + 203|- [Kimi Code CLI Integration](sources/kimi-readme.md) — Convert Agency agents into Kimi agent directories with `agent.yaml` and `system.md`, installed to `~/.config/kimi/agents/` + 204|- [OpenCode Integration](sources/opencode-readme.md) — Generate project-scoped `.opencode/agents/.md` with `mode: subagent` and color hex codes + 205|- [API Tester (Agent)](sources/testing-api-tester.md) — Agent specializing in comprehensive API testing, performance, and security validation + 206|- [Workflow Optimizer (Agent)](sources/testing-workflow-optimizer.md) — Agent focused on process improvement, automation, and workflow optimization + 207|- [Reality Checker (Agent)](sources/testing-reality-checker.md) — Integration agent enforcing evidence-based production readiness, defaults to NEEDS WORK + 208|- [Performance Benchmarker (Agent)](sources/testing-performance-benchmarker.md) — Agent specializing in performance testing, benchmarking, and optimization (k6 examples, reporting) +- [Support Infrastructure Maintainer](sources/support-infrastructure-maintainer.md) — Expert infrastructure specialist focused on system reliability, performance optimization, and technical operations management + 209|- [Support Analytics Reporter](sources/support-analytics-reporter.md) — Analytics Reporter agent personality definition for data analysis, dashboards, and business intelligence + 210|- [Finance Tracker](sources/support-finance-tracker.md) — 财务分析与预算管理智能体，负责预算、现金流预测、支付时点优化与投资评估 + 210|- [Accessibility Auditor (Agent)](sources/testing-accessibility-auditor.md) — Expert accessibility specialist auditing against WCAG 2.2 standards and testing with assistive technologies + 210|- [Tool Evaluator (Agent)](sources/testing-tool-evaluator.md) — Expert technology assessment specialist for tool evaluation, selection, and strategic adoption + 210|- [Test Results Analyzer (Agent)](sources/testing-test-results-analyzer.md) — Agent focused on analyzing test outputs, defect prediction, and release readiness assessments +- [Evidence Collector (Agent)](sources/testing-evidence-collector.md) — Screenshot-obsessed QA specialist requiring visual proof, defaults to finding 3-5 issues per implementation + 210|- [Multi-Agent Content Factory](sources/multi-agent-content-factory.md) — 在 Discord 中构建多 Agent 内容工厂，实现研究→写作→设计自动化流水线 193|- [Dataview——让我从"笔记黑洞"里逃出来的 Obsidian 神器](sources/Dataview-让我从-笔记黑洞-里逃出来的-Obsidian-神器-1.md) — 微信公众号「赫点茶」分享的 Dataview 插件使用体验，让笔记真正"活"起来 194|- [为什么你的笔记总是乱糟糟？试试这个方法，彻底告别信息混乱！](sources/bi-ji-zheng-li-fang-fa-ga-bie-hun-luan.md) — 微信公众号「赫点茶」分享的笔记整理方法 195|- [开发经验与项目规范整理文档](sources/kai-fa-jing-yan-yu-xiang-mu-gui-fan-zheng-li-wen-dang.md) — 软件开发经验与项目规范整理（变量名维护、文件结构、编码规范、架构原则） @@ -448,6 +475,7 @@ 414|- [CTP Topic 59 Achieving reliability with Amazon EKS](sources/ctp-topic-59-achieving-reliability-with-amazon-eks.md) — Amazon EKS 可靠性实践，涵盖容器服务选型、共享责任模型、应用/控制/数据平面三层可靠性设计 415| 416|## Sources +- [Workflow Example: Book Chapter Development](sources/workflow-book-chapter.md) — AI Agent 将粗糙素材转化为战略性第一人称书籍章节草稿的工作流 - [Healthcare Marketing Compliance Specialist](sources/healthcare-marketing-compliance.md) — Chinese healthcare marketing compliance, from ads to privacy and platform rules 417|- [CTP Topic 39 Implementing EKS in the AWS Lab Landing Zone](sources/ctp-topic-39-implementing-eks-in-the-aws-lab-landing-zone.md) — 在 AWS Lab Landing Zone 中实现 EKS 集群部署 418| @@ -486,6 +514,7 @@ 451|- [CTP Topic 56 Automated Infrastructure Testing](sources/ctp-topic-56-automated-infrastructure-testing.md) — 自动化基础设施测试，TerraTest 框架和测试驱动开发在 IaC 中的应用 452| 453|## Sources +- [Workflow Example: Book Chapter Development](sources/workflow-book-chapter.md) — AI Agent 将粗糙素材转化为战略性第一人称书籍章节草稿的工作流 - [Healthcare Marketing Compliance Specialist](sources/healthcare-marketing-compliance.md) — Chinese healthcare marketing compliance, from ads to privacy and platform rules 454|- [CTP Topic 31 Network Segregation and Secure Access to AWS Landing Zones](sources/ctp-topic-31-network-segregation-secure-access-aws-landing-zones.md) — AWS Landing Zone 网络隔离与安全访问解决方案 455| diff --git a/wiki/log.md b/wiki/log.md index abe16f3f..881b7180 100644 --- a/wiki/log.md +++ b/wiki/log.md @@ -1,3 +1,12 @@ +## [2026-04-21] ingest | Multi-Agent Workflow: Landing Page Sprint +- Source file: raw/Agent/agency-agents/examples/workflow-landing-page.md +- Status: ✅ 成功摄入 +- Summary: 多智能体协作在一天内完成高转化率 landing page 开发的 sprint 工作流，通过 4 个专业 Agent（Content Creator、UI Designer、Frontend Developer、Growth Hacker）分阶段并行协作实现 +- Concepts created: Multi-Agent Workflow, Parallel Kickoff, Merge Point, Time-boxed +- Entities created: Content Creator, Frontend Developer, FlowSync +- Source page: wiki/sources/multi-agent-workflow-landing-page-sprint.md +- Notes: 与 workflow-startup-mvp 类似，但更聚焦于单日 sprint；Growth Hacker 已存在；UI Designer 已存在于 design-ui-designer.md + ## [2026-04-20] ingest | Academic Historian Agent - Source file: raw/Agent/agency-agents/academic/academic-historian.md - Status: ✅ 成功摄入 @@ -43,6 +52,24 @@ - Source page: wiki/sources/academic-narratologist.md - Notes: 强调 Fabula vs Sjuzhet 区分；每个建议必须基于至少一个命名理论框架；角色弧线必须包含 want/need/lie/transformation 四个检查点 +## [2026-04-21] ingest | Multi-Agent Workflow: Startup MVP +- Source file: raw/Agent/agency-agents/examples/workflow-startup-mvp.md +- Status: ✅ 成功摄入 +- Summary: 多智能体协作从创意到 MVP 交付的完整工作流程，通过 7 个专业角色（Sprint Prioritizer、UX Researcher、Backend Architect、Frontend Developer、Rapid Prototyper、Growth Hacker、Reality Checker）顺序与并行工作，4 周完成 MVP 开发 +- Concepts created: Sequential Handoffs, Parallel Work, Quality Gates, Context Passing +- Entities created: Sprint Prioritizer, Rapid Prototyper, Growth Hacker, Reality Checker +- Source page: wiki/sources/workflow-startup-mvp.md +- Notes: 关键模式：顺序交接、并行工作、质量门控、上下文传递；Reality Checker 在 Week 2 中点和 Week 4 Launch 前设置质量门控 + +## [2026-04-21] ingest | Testing Tool Evaluator +- Source file: raw/Agent/agency-agents/testing/testing-tool-evaluator.md +- Status: ✅ 成功摄入 +- Summary: Tool Evaluator Agent 是 The Agency 项目中的技术评估与战略工具采纳专家智能体，通过七维度加权评分体系（功能性、可用性、性能、安全性、集成、支持、成本）评估工具，核心成功指标：90% 推荐准确率、85% 采用率、20% 成本降低、25% ROI +- Concepts created: Tool Evaluation Framework, TCO (Total Cost of Ownership), ROI Analysis, Vendor Management +- Entities created: Tool Evaluator Agent +- Source page: wiki/sources/testing-tool-evaluator.md +- Notes: 与 Test Results Analyzer、Evidence Collector、Performance Benchmarker、Reality Checker 共同构成质量保障智能体体系；侧重点为工具选择与供应商评估 + ## [2026-04-20] ingest | Product Trend Researcher - Source file: raw/Agent/agency-agents/product/product-trend-researcher.md - Status: ✅ 成功摄入 @@ -368,3 +395,184 @@ - Status: ✅ 成功摄入 - Summary: Backend Architect (with Memory) defines a senior backend architect persona, architecture deliverables, success metrics, and a Memory Integration section showing how the agent should use MCP memory tools (`remember`, `recall`, `rollback`, `search`) to persist decisions and handoffs across sessions. - Source page: wiki/sources/backend-architect-with-memory.md + +## [2026-04-20] ingest | OpenClaw Integration +- Source file: raw/Agent/agency-agents/integrations/openclaw/README.md +- Status: ✅ 成功摄入 +- Summary: OpenClaw Integration README documents how The Agency provides OpenClaw workspaces (SOUL.md, AGENTS.md, IDENTITY.md), how to generate artifacts with `./scripts/convert.sh --tool openclaw`, install with `./scripts/install.sh --tool openclaw`, and restart the gateway if needed. +- Source page: wiki/sources/openclaw-readme.md + +## [2026-04-20] ingest | Cursor Integration +- Source file: raw/Agent/agency-agents/integrations/cursor/README.md +- Status: ✅ 成功摄入 +- Summary: Cursor Integration README explains generating project-scoped Cursor `.mdc` rule files from The Agency roster, how to install via `./scripts/install.sh --tool cursor`, and how to activate rules inline or via frontmatter. +- Source page: wiki/sources/cursor-readme.md + +## [2026-04-20] ingest | GitHub Copilot Integration +- Source file: raw/Agent/agency-agents/integrations/github-copilot/README.md +- Status: ✅ 成功摄入 +- Summary: GitHub Copilot Integration README documents that The Agency agents are compatible with GitHub Copilot's `.md` + YAML frontmatter format, install instructions, activation examples, and where to find the full roster. +- Source page: wiki/sources/github-copilot-readme.md + +## [2026-04-20] ingest | Gemini CLI Integration +- Source file: raw/Agent/agency-agents/integrations/gemini-cli/README.md +- Status: ✅ 成功摄入 +- Summary: Gemini CLI Integration README describes packaging the Agency agents as a Gemini CLI extension installed to `~/.gemini/extensions/agency-agents/`, generation/install instructions, extension structure, activation examples, and regeneration command. +- Source page: wiki/sources/gemini-cli-readme.md + +## [2026-04-20] ingest | Windsurf Integration +- Source file: raw/Agent/agency-agents/integrations/windsurf/README.md +- Status: ✅ 成功摄入 +- Summary: Windsurf Integration README explains consolidating the full Agency roster into a single `.windsurfrules` file, installation from the project root, activation by agent name in prompts, and regeneration via the convert script. +- Source page: wiki/sources/windsurf-readme.md + +## [2026-04-20] ingest | Antigravity Integration +- Source file: raw/Agent/agency-agents/integrations/antigravity/README.md +- Status: ✅ 成功摄入 +- Summary: Antigravity Integration README documents installing the Agency roster as Antigravity skills prefixed with `agency-`, install and regenerate commands, activation by slug, and the `SKILL.md` frontmatter format. +- Source page: wiki/sources/antigravity-readme.md + +## [2026-04-20] ingest | Kimi Code CLI Integration +- Source file: raw/Agent/agency-agents/integrations/kimi/README.md +- Status: ✅ 成功摄入 +- Summary: Kimi Code CLI Integration README explains conversion of Agency agents into Kimi agent directories (`agent.yaml` + `system.md`), install location `~/.config/kimi/agents/`, usage examples, agent structure, regeneration, and troubleshooting. +- Source page: wiki/sources/kimi-readme.md + +## [2026-04-20] ingest | OpenCode Integration +- Source file: raw/Agent/agency-agents/integrations/opencode/README.md +- Status: ✅ 成功摄入 +- Summary: OpenCode Integration README explains generating project-scoped `.opencode/agents/.md` agent files, the conversion of named colors to hex codes, `mode: subagent` behavior, project vs global install, and regeneration instructions. +- Source page: wiki/sources/opencode-readme.md + +## [2026-04-20] ingest | API Tester (Agent) +- Source file: raw/Agent/agency-agents/testing/testing-api-tester.md +- Status: ✅ 成功摄入 +- Summary: API Tester agent file defines an API testing specialist with security-first and performance-focused testing workflows, example automation suites, deliverable templates, and success metrics. +- Source page: wiki/sources/testing-api-tester.md + +## [2026-04-20] ingest | Workflow Optimizer (Agent) +- Source file: raw/Agent/agency-agents/testing/testing-workflow-optimizer.md +- Status: ✅ 成功摄入 +- Summary: Workflow Optimizer agent file defines an agent for process improvement, automation, and workflow optimization with code examples, frameworks, deliverable templates, and success metrics. +- Source page: wiki/sources/testing-workflow-optimizer.md + +## [2026-04-20] ingest | Reality Checker (Agent) +- Source file: raw/Agent/agency-agents/testing/testing-reality-checker.md +- Status: ✅ 成功摄入 +- Summary: Reality Checker agent enforces evidence-based production readiness and provides mandatory commands for automated evidence capture, report templates, and fail triggers. +- Source page: wiki/sources/testing-reality-checker.md + +## [2026-04-20] ingest | Performance Benchmarker (Agent) +- Source file: raw/Agent/agency-agents/testing/testing-performance-benchmarker.md +- Status: ✅ 成功摄入 +- Summary: Performance Benchmarker agent defines performance testing methodologies, k6 example scripts, reporting templates, success metrics, and monitoring recommendations for performance engineering. +- Source page: wiki/sources/testing-performance-benchmarker.md + +## [2026-04-21] ingest | Test Results Analyzer +- Source file: raw/Agent/agency-agents/testing/testing-test-results-analyzer.md +- Status: ✅ 成功摄入 +- Summary: Test Results Analyzer is an agent persona focused on comprehensive test result evaluation, statistical failure pattern analysis, defect prediction modeling, release readiness assessment, and stakeholder reporting. +- Concepts created: Test Coverage Gap Analysis, Defect Prediction, Release Readiness Assessment, Quality ROI Analysis +- Entities created: Test Results Analyzer (source page) +- Source page: wiki/sources/testing-test-results-analyzer.md + +## [2026-04-21] ingest | Evidence Collector +- Source file: raw/Agent/agency-agents/testing/testing-evidence-collector.md +- Status: ✅ 成功摄入 +- Summary: Evidence Collector (EvidenceQA) is a QA-focused agent that demands Playwright screenshot evidence, runs reality-check commands, defaults to finding 3-5+ issues, and produces evidence-based QA reports. +- Concepts created: Evidence-Based QA, Reality Check Commands, Playwright Capture Protocols +- Entities created: Evidence Collector (source page) +- Source page: wiki/sources/testing-evidence-collector.md + +## [2026-04-21] ingest | Evidence Collector Agent +- Source file: raw/Agent/agency-agents/testing/testing-evidence-collector.md +- Status: ✅ 成功摄入 +- Summary: Evidence Collector (EvidenceQA) 是截图驱动的 QA 专家智能体，要求所有声明都有视觉证据支撑，默认发现 3-5 个问题，使用 Playwright 截图和可复现命令进行事实检查 +- Concepts created: 证据驱动 QA, 幻想式报告, Reality Check, Playwright 截图 +- Entities created: EvidenceQA +- Source page: wiki/sources/testing-evidence-collector.md +- Notes: 与 Reality Checker、Test Results Analyzer 协同形成质量闭环；"零问题"是危险信号；诚实质量评估 Basic/Good/Excellent + + +## [2026-04-21] ingest | Accessibility Auditor +- Source file: raw/Agent/agency-agents/testing/testing-accessibility-auditor.md +- Status: ✅ 成功摄入 +- Summary: Accessibility Auditor 是 The Agency 项目中的无障碍审计专家智能体，基于 WCAG 2.2 标准进行界面审计，强调自动化工具仅能捕获约 30% 的问题，剩余 70% 需人工辅助技术测试发现。核心原则：Lighthouse 绿分 ≠ 真正无障碍，自定义组件默认有罪，语义 HTML 优先于 ARIA。 +- Concepts created: WCAG 2.2, POUR Principles, Screen Reader Testing, Keyboard Navigation Audit, ARIA Patterns, axe-core, Lighthouse Accessibility +- Entities created: Accessibility Auditor, The Agency（更新） +- Source page: wiki/sources/testing-accessibility-auditor.md +- Notes: 与 Testing Reality Checker、Evidence Collector、Frontend Developer、UI Designer 协作；测试类智能体成员（API Tester、Workflow Optimizer、Reality Checker、Performance Benchmarker、Tool Evaluator、Test Results Analyzer、Evidence Collector、Accessibility Auditor） + +## [2026-04-21] ingest | Legal Compliance Checker +- Source file: raw/Agent/agency-agents/support/support-legal-compliance-checker.md +- Status: ✅ 成功摄入 +- Summary: Legal Compliance Checker 是 The Agency 项目中的法律合规检查专家智能体，专注于多司法管辖区监管合规（GDPR、CCPA、HIPAA、SOX、PCI-DSS）、风险评估、政策开发与合规监控，确保业务运营符合相关法律法规 +- Concepts created: Multi-Jurisdictional Compliance, GDPR Compliance Framework, Privacy Policy Generator, Contract Review System, Regulatory Compliance Assessment +- Entities created: Legal Compliance Checker +- Source page: wiki/sources/support-legal-compliance-checker.md +- Notes: 与 Healthcare Marketing Compliance Specialist 共享合规方法论；Python 代码示例展示 PrivacyPolicyGenerator 和 ContractReviewSystem 实现 + +## [2026-04-21] ingest | Support Analytics Reporter +- Source file: raw/Agent/agency-agents/support/support-analytics-reporter.md +- Status: ✅ 成功摄入 +- Summary: Analytics Reporter 是 The Agency 项目中的数据分析与商业智能专家智能体，将原始数据转化为可操作的业务洞察。核心能力：统计分析与假设检验、RFM 客户分层、营销归因建模、KPI 仪表盘设计、预测模型构建。 +- Concepts created: Analytics Reporter, RFM Analysis, Customer Lifetime Value, Statistical Significance Testing, Marketing Attribution Modeling, KPI Tracking, Data-Driven Decision Making +- Entities created: The Agency（更新） +- Source page: wiki/sources/support-analytics-reporter.md +- Notes: 与 Data Consolidation Agent、Sales Data Extraction Agent、Report Distribution Agent 协同工作；强调数据质量优先、统计显著性验证；SQL/Python/JS 代码模板覆盖仪表盘设计 + + + +## [2026-04-21] ingest | Support Responder +- Source file: raw/Agent/agency-agents/support/support-support-responder.md +- Status: ✅ 成功摄入 +- Summary: Support Responder 是 The Agency 项目中的客户支持专家智能体，提供全渠道客户服务、问题解决和用户体验优化，核心指标：85% 首次联系解决率、4.5+ CSAT、95%+ SLA 合规率 +- Concepts created: Multi-Channel Support Framework, Support Tiers, Customer Success, Knowledge Base Management, Support Analytics +- Entities created: Support Responder +- Source page: wiki/sources/support-support-responder.md +- Notes: 与 Support Legal Compliance Checker 同部门；Python 代码示例展示 SupportAnalytics 和 KnowledgeBaseManager 实现 + +## [2026-04-21] ingest | Finance Tracker +- Source file: raw/Agent/agency-agents/support/support-finance-tracker.md +- Status: ✅ 成功摄入 +- Summary: Finance Tracker 是 The Agency 中负责预算、现金流和投资分析的财务分析与控制智能体。核心交付：年度/季度预算框架、12 个月滚动现金流预测、支付时点优化、投资可行性分析（NPV/IRR/回收期）与审计准备。 +- Concepts created: Cash Flow Management, Investment Analysis, Budget Framework +- Entities created: Finance Tracker +- Source page: wiki/sources/support-finance-tracker.md +- Notes: 与 Support Analytics Reporter、Accounts Payable Agent 协作；未发现与现有 wiki 内容冲突 + +## [2026-04-21] ingest | Support Infrastructure Maintainer +- Source file: raw/Agent/agency-agents/support/support-infrastructure-maintainer.md +- Status: ✅ 成功摄入 +- Summary: Infrastructure Maintainer 是 The Agency 项目中的基础设施运维专家智能体，专注于系统可靠性、性能优化和技术运营管理，确保 99.9%+ 正常运行时间。核心能力：IaC（Terraform）、监控（Prometheus/Grafana）、灾备、安全加固、成本优化。 +- Concepts created: Infrastructure as Code (IaC), Disaster Recovery, Security Hardening, Cost Optimization, Prometheus Monitoring, Terraform +- Entities created: The Agency（更新） +- Source page: wiki/sources/support-infrastructure-maintainer.md +- Notes: 与 DevOps 成熟度模型、ITSM 相关联；提供 Terraform、Prometheus、备份脚本等完整代码模板；成功指标：99.9%+ uptime、MTTR <4 hours、20%+ cost efficiency、70%+ automation reduction + +## [2026-04-21] ingest | Executive Summary Generator +- Source file: raw/Agent/agency-agents/support/support-executive-summary-generator.md +- Status: ✅ 成功摄入 +- Summary: Executive Summary Generator 是 The Agency 项目中的战略咨询风格执行摘要生成智能体，使用 McKinsey SCQA、BCG Pyramid、Bain 框架将 325-475 字复杂业务输入转化为结构化执行摘要，支持 C-suite 决策者 3 分钟内完成决策 +- Concepts created: McKinsey SCQA Framework, BCG Pyramid Principle, Executive Summary, Consulting Framework +- Entities created: The Agency（更新） +- Source page: wiki/sources/support-executive-summary-generator.md +- Notes: 与 Data Consolidation Agent、Report Distribution Agent 协同工作；质量标准：325-475 words、每个发现 ≥1 量化数据点、建议包含 Owner+Timeline+Result + +## [2026-04-21] ingest | Workflow Example: Book Chapter Development +- Source file: raw/Agent/agency-agents/examples/workflow-book-chapter.md +- Status: ✅ 成功摄入 +- Summary: Book Co-Author Agent 将粗糙素材（语音笔记、片段、战略笔记）转化为战略性第一人称书籍章节草稿的工作流，目标不是通用代笔而是强化品类定位、保留作者声音、暴露开放编辑决策 +- Concepts created: Book Co-Author Agent, Versioned Draft, Editorial Notes, Feedback Loop +- Entities created: The Agency（更新） +- Source page: wiki/sources/workflow-book-chapter.md +- Notes: 与现有写作工作流和反馈循环概念高度互补；输出格式包含 Target Outcome、Chapter Draft、Editorial Notes、Feedback Loop、Next Step 五部分 + +## [2026-04-21] ingest | Examples (Agency Agents) +- Source file: raw/Agent/agency-agents/examples/README.md +- Status: ✅ 成功摄入 +- Summary: Agency Agents 多智能体编排示例集，展示了 8 个专业智能体并行协作完成产品发现的完整流程，涵盖市场分析、技术架构、品牌战略、GTM 计划、客户支持、UX 研究、项目规划和空间界面设计 +- Concepts created: 多智能体并行执行, 智能体编排示例 +- Entities created: Product Trend Researcher, Backend Architect, Brand Guardian, Growth Hacker, Support Responder, UX Researcher, Project Shepherd, XR Interface Architect +- Source page: wiki/sources/agency-agents-examples.md +- Notes: 本文档是示例索引，实际详细案例在 nexus-spatial-discovery.md；8 个智能体并行工作产生连贯、相互引用的计划，无协调开销 diff --git a/wiki/overview.md b/wiki/overview.md index 380dfa1a..0cadb4fd 100644 --- a/wiki/overview.md +++ b/wiki/overview.md @@ -4,6 +4,7 @@ 4|AI 开源项目、Cloud & DevOps、Vibe Coding、AI时代个人发展、跨境电商 5| 6|## 核心概念 +- Legal Compliance Checker：The Agency 项目中的法律合规检查专家智能体，专注于多司法管辖区监管合规（GDPR、CCPA、HIPAA、SOX、PCI-DSS）、风险评估、政策开发与合规监控 - Healthcare Marketing Compliance Specialist：The Agency 中负责中国医疗健康营销合规的专家智能体，覆盖医疗广告、互联网医疗、医美、保健品与隐私合规 7|- The Agency：开源 AI 智能体集合项目，汇集各类专业化 AI Agent 8|- Image Prompt Engineer：The Agency 项目中的 AI 图像生成提示词工程专家智能体，专注于将视觉概念转化为精确的提示词语言 @@ -117,7 +118,9 @@ - Team Velocity：团队单个 sprint 完成的故事点数量，衡量交付能力和容量规划 - Sprint Planning：冲刺规划过程，定义 sprint 目标和故事选择 107|- 事件驱动项目管理：使用数据库存储项目状态和历史事件，通过 AI Agent 自然语言交互替代静态 Kanban 看板 - 108|- LLM Wiki：LLM 持续编译和维护的持久化 wiki，将 raw source 逐步沉淀成可追溯、可交叉引用的知识资产 + 108|- LLM Wiki：LLM 持续编译和维护的持久化 wiki，将 raw source 逐步沉淀成可追溯、可交叉引用的知识资产 + 109|- Test Results Analyzer：专注于测试结果分析、缺陷预测与发布就绪评估的智能体，补充了 Model QA 与 Performance Benchmarker 的质量闭环 + 110|- Evidence Collector：证据驱动的 QA 智能体，强调 Playwright 截图、可复现命令和最少 3-5 个问题的现实检查，和 Reality Checker / Test Results Analyzer 协同形成质量闭环 109|- 内网穿透（NAT Penetration）：将内网服务通过公网服务器暴露给外部访问的技术，FRP 是常用方案之一 110|- Workspace：OpenClaw 中 Agent 的工作台目录，包含 AGENTS.md、SOUL.md、USER.md、IDENTITY.md、TOOLS.md、BOOTSTRAP.md、memory/ 等配置文件 111|- Memory 目录：OpenClaw 的长期记忆机制，按日期滚动存储跨会话积累的信息 @@ -426,3 +429,18 @@ - [Claude Code Integration](sources/claude-code-readme.md) — Notes for using The Agency agents natively with Claude Code (no conversion required) - [MCP Memory Integration](sources/mcp-memory-readme.md) — How to add persistent cross-session memory to agents using MCP servers (`remember`, `recall`, `rollback`, `search`) - [Backend Architect (with Memory)](sources/backend-architect-with-memory.md) — Backend Architect persona with MCP Memory Integration pattern +- [OpenClaw Integration](sources/openclaw-readme.md) — OpenClaw workspace integration (SOUL.md, AGENTS.md, IDENTITY.md) +- [Cursor Integration](sources/cursor-readme.md) — Convert agents into Cursor `.mdc` project-scoped rule files +- [GitHub Copilot Integration](sources/github-copilot-readme.md) — Agents are compatible with GitHub Copilot `.md` + YAML frontmatter format +- [Gemini CLI Integration](sources/gemini-cli-readme.md) — Package Agency agents as a Gemini CLI extension under `~/.gemini/extensions/agency-agents/` +- [Windsurf Integration](sources/windsurf-readme.md) — Consolidate the full Agency roster into a single `.windsurfrules` file (project-scoped) +- [Antigravity Integration](sources/antigravity-readme.md) — Install Agency agents as Antigravity `agency-` prefixed skills under `~/.gemini/antigravity/skills/` +- [Kimi Code CLI Integration](sources/kimi-readme.md) — Convert Agency agents into Kimi agent directories with `agent.yaml` and `system.md`, installed to `~/.config/kimi/agents/` +- [OpenCode Integration](sources/opencode-readme.md) — Generate project-scoped `.opencode/agents/.md` with `mode: subagent` and color hex codes +- [API Tester (Agent)](sources/testing-api-tester.md) — Agent specializing in comprehensive API testing, performance, and security validation +- [Workflow Optimizer (Agent)](sources/testing-workflow-optimizer.md) — Agent focused on process improvement, automation, and workflow optimization +- [Reality Checker (Agent)](sources/testing-reality-checker.md) — Integration agent enforcing evidence-based production readiness, defaults to NEEDS WORK +- [Performance Benchmarker (Agent)](sources/testing-performance-benchmarker.md) — Agent specializing in performance testing, benchmarking, and optimization (k6 examples, reporting) + +## New Sources +- **Finance Tracker** — 财务分析与控制智能体，提供预算框架、滚动现金流预测、投资分析与审计准备 diff --git a/wiki/sources/agency-agents-examples.md b/wiki/sources/agency-agents-examples.md new file mode 100644 index 00000000..a847a2b0 --- /dev/null +++ b/wiki/sources/agency-agents-examples.md @@ -0,0 +1,49 @@ +--- +title: "Examples (Agency Agents)" +type: source +tags: [agency-agents, multi-agent, examples] +date: 2026-04-21 +--- + +## Source File +- [[raw/Agent/agency-agents/examples/README.md]] + +## Summary +- 核心主题：Agency Agents 多智能体编排示例集 +- 问题域：展示多个专业智能体并行协作的实际效果 +- 方法/机制：8 个专业智能体同时部署，在产品发现任务中协同工作 +- 结论/价值：证明全量智能体编排可产生连贯、相互引用的计划 + +## Key Claims +- 多智能体并行执行可产生连贯、交叉引用的计划，无协调开销 +- 从"发现机会"到"完整蓝图"可在单次会话中完成 +- 智能体编排展示了对复杂任务的端到端处理能力 + +## Key Quotes +> "What does it actually look like when the full agency collaborates?" — 展示多智能体协作的核心问题 + +## Key Concepts +- [[Multi-Agent Team]]：多智能体团队，每个智能体有独立角色、人格和优化模型 +- [[Agents Orchestrator]]：智能体编排器，负责任务分配和流程协调 +- [[并行智能体执行]]：多个智能体同时工作于不同子任务 + +## Key Entities +- [[Product Trend Researcher]]：市场验证与竞争格局分析 +- [[Backend Architect]]：系统架构、数据模型、API 设计 +- [[Brand Guardian]]：品牌定位与视觉识别 +- [[Growth Hacker]]：GTM 策略与增长计划 +- [[Support Responder]]：客户支持运营蓝图 +- [[UX Researcher]]：用户画像与旅程地图 +- [[Project Shepherd]]：项目执行计划与风险管理 +- [[XR Interface Architect]]：空间界面架构规范 + +## Connections +- [[The Agency]] ← 定义了 ← [[多智能体系统可靠性]] 架构模式 +- [[Multi-Agent Team]] ← 实现于 ← [[nexus-spatial-discovery.md]] 示例 + +## Contradictions +- 未发现与现有内容的冲突 + +## Notes +- 本文档是示例索引，实际详细案例在 nexus-spatial-discovery.md +- 8 个智能体并行工作的成功案例，展示了多智能体系统的实际应用价值 \ No newline at end of file diff --git a/wiki/sources/antigravity-readme.md b/wiki/sources/antigravity-readme.md new file mode 100644 index 00000000..f754c335 --- /dev/null +++ b/wiki/sources/antigravity-readme.md @@ -0,0 +1,24 @@ +--- +title: "Antigravity Integration" +type: source +tags: [agency, integrations, antigravity] +date: 2026-04-20 +source_file: raw/Agent/agency-agents/integrations/antigravity/README.md +--- + +## Summary +Antigravity Integration README documents installing the Agency roster as Antigravity skills under `~/.gemini/antigravity/skills/`. Each agent is prefixed with `agency-` to avoid name conflicts. It covers install, activation by slug, regeneration steps, and the `SKILL.md` frontmatter format. + +## Key Claims +- Agents install as Antigravity skills and are prefixed `agency-` to prevent conflicts. +- Install via `./scripts/install.sh --tool antigravity`, which copies files to `~/.gemini/antigravity/skills/`. +- Activate skills by their slug (e.g., `agency-frontend-developer`). + +## Key Quotes +> "Installs the full Agency roster as Antigravity skills. Each agent is prefixed with `agency-` to avoid conflicts with existing skills." — Antigravity Integration README + +## Connections +- [[The Agency: AI Specialists Ready to Transform Your Workflow]] — roster source + +## Contradictions +- None detected with existing wiki content at time of ingest. diff --git a/wiki/sources/cursor-readme.md b/wiki/sources/cursor-readme.md new file mode 100644 index 00000000..c8fe6da4 --- /dev/null +++ b/wiki/sources/cursor-readme.md @@ -0,0 +1,25 @@ +--- +title: "Cursor Integration" +type: source +tags: [agency, integrations, cursor] +date: 2026-04-20 +source_file: raw/Agent/agency-agents/integrations/cursor/README.md +--- + +## Summary +Cursor Integration README explains generating project-scoped Cursor `.mdc` rule files from The Agency roster. Rules live under `.cursor/rules/.mdc` in a project and can be activated inline (e.g., `@frontend-developer`) or made always-on via frontmatter configuration. + +## Key Claims +- The Agency can convert agents into Cursor `.mdc` rule files which are project-scoped. +- Installers create `.cursor/rules/.mdc` when run from a project root via `./scripts/install.sh --tool cursor`. +- Rules can be invoked inline with `@agent-slug` or set alwaysApply in frontmatter. + +## Key Quotes +> "Converts the full Agency roster into Cursor `.mdc` rule files. Rules are project-scoped — install them from your project root." — Cursor Integration README + +## Connections +- [[The Agency: AI Specialists Ready to Transform Your Workflow]] — roster source +- Cursor project-scoped rules pattern + +## Contradictions +- None detected with existing wiki content at time of ingest. diff --git a/wiki/sources/gemini-cli-readme.md b/wiki/sources/gemini-cli-readme.md new file mode 100644 index 00000000..18803702 --- /dev/null +++ b/wiki/sources/gemini-cli-readme.md @@ -0,0 +1,24 @@ +--- +title: "Gemini CLI Integration" +type: source +tags: [agency, integrations, gemini] +date: 2026-04-20 +source_file: raw/Agent/agency-agents/integrations/gemini-cli/README.md +--- + +## Summary +Gemini CLI Integration README describes packaging the Agency agents as a Gemini CLI extension installed to `~/.gemini/extensions/agency-agents/`. It documents generating integration files, installing the extension, the extension file layout (including `skills//SKILL.md`), how to activate skills by name, and how to regenerate files. + +## Key Claims +- The Agency provides a Gemini CLI extension that installs under `~/.gemini/extensions/agency-agents/`. +- Generate integration files with `./scripts/convert.sh --tool gemini-cli` and install with `./scripts/install.sh --tool gemini-cli`. +- Skills are organized under `skills//SKILL.md` and are invoked by name in the CLI. + +## Key Quotes +> "Packages all 61 Agency agents as a Gemini CLI extension. The extension installs to `~/.gemini/extensions/agency-agents/." — Gemini CLI Integration README + +## Connections +- [[The Agency: AI Specialists Ready to Transform Your Workflow]] — roster source + +## Contradictions +- None detected with existing wiki content at time of ingest. diff --git a/wiki/sources/github-copilot-readme.md b/wiki/sources/github-copilot-readme.md new file mode 100644 index 00000000..f071a30d --- /dev/null +++ b/wiki/sources/github-copilot-readme.md @@ -0,0 +1,24 @@ +--- +title: "GitHub Copilot Integration" +type: source +tags: [agency, integrations, copilot] +date: 2026-04-20 +source_file: raw/Agent/agency-agents/integrations/github-copilot/README.md +--- + +## Summary +GitHub Copilot Integration README documents that The Agency agents are compatible with GitHub Copilot's `.md` + YAML frontmatter format and need no conversion. It includes install instructions (script or manual copy), activation examples, and references the main README for the full roster. + +## Key Claims +- Agents work natively with GitHub Copilot using Markdown files with YAML frontmatter; no conversion required. +- Installation via `./scripts/install.sh --tool copilot` or manual copying to `~/.github/agents/` or `~/.copilot/agents/`. +- Agents are referenced by name within Copilot sessions to activate their behavior. + +## Key Quotes +> "The Agency works with GitHub Copilot out of the box. No conversion needed — agents use the existing `.md` + YAML frontmatter format." — GitHub Copilot Integration README + +## Connections +- [[The Agency: AI Specialists Ready to Transform Your Workflow]] — The roster source + +## Contradictions +- None detected with existing wiki content at time of ingest. diff --git a/wiki/sources/kimi-readme.md b/wiki/sources/kimi-readme.md new file mode 100644 index 00000000..e443bf2c --- /dev/null +++ b/wiki/sources/kimi-readme.md @@ -0,0 +1,24 @@ +--- +title: "Kimi Code CLI Integration" +type: source +tags: [agency, integrations, kimi] +date: 2026-04-20 +source_file: raw/Agent/agency-agents/integrations/kimi/README.md +--- + +## Summary +Kimi Code CLI Integration README explains converting Agency agents into Kimi agent directories containing `agent.yaml` and `system.md`, installing them to `~/.config/kimi/agents/`, usage examples (including `--agent-file` and `--work-dir`), agent directory structure, `agent.yaml` format, regeneration steps, and troubleshooting tips. + +## Key Claims +- Agency agents are converted into Kimi agent specifications with `agent.yaml` and `system.md`. +- Generate integration files with `./scripts/convert.sh --tool kimi` and install with `./scripts/install.sh --tool kimi`. +- Agents are installed to `~/.config/kimi/agents/` and loaded via `kimi --agent-file `. + +## Key Quotes +> "Converts all Agency agents into Kimi Code CLI agent specifications. Each agent becomes a directory containing `agent.yaml` (agent spec) and `system.md` (system prompt)." — Kimi Code CLI Integration README + +## Connections +- [[The Agency: AI Specialists Ready to Transform Your Workflow]] — roster source + +## Contradictions +- None detected with existing wiki content at time of ingest. diff --git a/wiki/sources/multi-agent-workflow-landing-page-sprint.md b/wiki/sources/multi-agent-workflow-landing-page-sprint.md new file mode 100644 index 00000000..b3bc9b98 --- /dev/null +++ b/wiki/sources/multi-agent-workflow-landing-page-sprint.md @@ -0,0 +1,50 @@ +--- +title: "Multi-Agent Workflow: Landing Page Sprint" +type: source +tags: [] +date: 2026-04-21 +--- + +## Source File +- [[raw/Agent/agency-agents/examples/workflow-landing-page.md]] + +## Summary +- 核心主题：多智能体协作完成单日 landing page 开发 sprint +- 问题域：如何在一天内完成高转化率 landing page 的生产发布 +- 方法/机制：4 个专业 Agent（Content Creator、UI Designer、Frontend Developer、Growth Hacker）分阶段并行协作 +- 结论/价值：通过并行启动、合并点、反馈循环和时间盒机制实现高效交付 + +## Key Claims +- 并行 kickoff：Copy 和 Design 可同时进行，因二者相互独立 +- 合并点：Frontend Developer 需要 Content Creator 和 UI Designer 的输出才能开始 +- 反馈循环：Growth Hacker 审查后，Frontend Developer 应用修改 +- 时间盒：每个步骤有明确时间限制以防止范围蔓延 + +## Key Quotes +> "Ship a conversion-optimized landing page in one day using 4 agents." — 工作流目标陈述 +> "Parallel kickoff: Copy and design happen at the same time since they're independent" — 并行机制说明 +> "Merge point: Frontend Developer needs both outputs before starting" — 合并依赖关系 + +## Key Concepts +- [[Multi-Agent Workflow]]：多智能体协作架构，每个 Agent 有独立角色、人格、优化的模型，通过共享内存+私有上下文实现协同 +- [[Parallel Kickoff]]：并行启动，多个工作流同时开始执行的机制 +- [[Merge Point]]：合并点，多个输入汇合后触发下一阶段的关键节点 +- [[Feedback Loop]]：反馈循环，审查后应用修改的迭代机制 +- [[Time-boxed]]：时间盒，单一任务的最大时长限制，防止无限蔓延 + +## Key Entities +- [[Content Creator Agent]]：The Agency 项目中的内容创作智能体，负责编写 landing page 文案 +- [[UI Designer Agent]]：The Agency 项目中的 UI 设计智能体，负责设计布局和组件规格 +- [[Frontend Developer Agent]]：The Agency 项目中的前端开发智能体，负责构建 landing page +- [[Growth Hacker Agent]]：The Agency 项目中的增长黑客智能体，负责转化率优化 +- [[FlowSync]]：虚构的 API 集成平台产品，用于工作流演示 + +## Connections +- [[Content Creator Agent]] ← writes_copy ← [[Multi-Agent Workflow]] +- [[UI Designer Agent]] ← designs ← [[Multi-Agent Workflow]] +- [[Frontend Developer Agent]] ← builds ← [[Multi-Agent Workflow]] +- [[Growth Hacker Agent]] ← optimizes ← [[Multi-Agent Workflow]] +- [[Frontend Developer Agent]] ← depends_on ← [[Content Creator Agent]] + [[UI Designer Agent]] + +## Contradictions + diff --git a/wiki/sources/opencode-readme.md b/wiki/sources/opencode-readme.md new file mode 100644 index 00000000..dd897b67 --- /dev/null +++ b/wiki/sources/opencode-readme.md @@ -0,0 +1,24 @@ +--- +title: "OpenCode Integration" +type: source +tags: [agency, integrations, opencode] +date: 2026-04-20 +source_file: raw/Agent/agency-agents/integrations/opencode/README.md +--- + +## Summary +OpenCode Integration README explains generating `.opencode/agents/.md` project-scoped agent files. The converter maps named colors to hex codes, sets `mode: subagent` so agents are invoked with `@agent-name`, and supports installing project-scoped files or installing globally via `--path`. + +## Key Claims +- OpenCode agents are `.md` files with YAML frontmatter stored in `.opencode/agents/` and use `mode: subagent`. +- The installer creates `.opencode/agents/.md` when run from a project root; global installation is possible with `--path`. +- Generated agent frontmatter includes `name`, `description`, `mode: subagent`, and `color` (hex codes produced from named colors). + +## Key Quotes +> "OpenCode agents are `.md` files with YAML frontmatter stored in `.opencode/agents/`. The converter maps named colors to hex codes and adds `mode: subagent` so agents are invoked on-demand via `@agent-name` rather than cluttering the primary agent picker." — OpenCode Integration README + +## Connections +- [[The Agency: AI Specialists Ready to Transform Your Workflow]] — roster source + +## Contradictions +- None detected with existing wiki content at time of ingest. diff --git a/wiki/sources/support-analytics-reporter.md b/wiki/sources/support-analytics-reporter.md new file mode 100644 index 00000000..ad1522b5 --- /dev/null +++ b/wiki/sources/support-analytics-reporter.md @@ -0,0 +1,45 @@ +--- +title: "Support Analytics Reporter" +type: source +tags: [] +date: 2026-04-21 +--- + +## Source File +- [[raw/Agent/agency-agents/support/support-analytics-reporter.md]] + +## Summary +- 核心主题：数据分析与商业智能专家智能体定义 +- 问题域：数据驱动决策支持、商业洞察生成、仪表盘设计 +- 方法/机制：统计分析、RFM 客户分层、营销归因建模、预测模型、A/B 测试 +- 结论/价值：提供可量化的业务建议，实现 20%+ KPI 提升 + +## Key Claims +- 数据质量验证是分析的前提，必须在分析前完成数据准确性和完整性校验 +- 所有分析结论必须包含统计显著性测试和置信水平 +- 仪表盘设计需针对特定利益相关者需求和决策场景定制 +- 客户生命周期价值（CLV）计算是客户分析的核心指标 + +## Key Quotes +> "Be data-driven: Analysis of 50,000 customers shows 23% improvement in retention with 95% confidence" +> "Focus on impact: This optimization could increase monthly revenue by $45,000 based on historical patterns" + +## Key Concepts +- [[Data-Driven Decision Making]]：基于数据而非直觉的业务决策方法论 +- [[RFM Analysis]]：客户分层的经典方法，通过 Recency（最近购买）、Frequency（购买频率）、Monetary（消费金额）三个维度评估客户价值 +- [[Statistical Significance Testing]]：验证分析结果是否具有统计意义的假设检验方法 +- [[Marketing Attribution Modeling]]：多触点归因模型，将转化功劳分配给不同营销触点 +- [[Customer Lifetime Value]]：客户生命周期价值，衡量客户在整个关系周期内贡献的总收入 +- [[KPI Tracking]]：关键绩效指标监控，通过量化指标评估业务目标达成情况 +- [[Predictive Modeling]]：预测模型，基于历史数据预测未来趋势（流失、增长等） + +## Key Entities +- [[The Agency]]：开源 AI 智能体集合项目，Analytics Reporter 是其销售与支持类别的智能体之一 + +## Connections +- [[Data Consolidation Agent]] ← supports ← [[Analytics Reporter]] +- [[Sales Data Extraction Agent]] ← provides_data ← [[Analytics Reporter]] +- [[Report Distribution Agent]] ← distributes_reports ← [[Analytics Reporter]] + +## Contradictions + diff --git a/wiki/sources/support-executive-summary-generator.md b/wiki/sources/support-executive-summary-generator.md new file mode 100644 index 00000000..7cd1c2f1 --- /dev/null +++ b/wiki/sources/support-executive-summary-generator.md @@ -0,0 +1,65 @@ +--- +title: "Executive Summary Generator" +type: source +tags: [] +sources: [] +last_updated: 2026-04-21 +--- + +## Source File +- [[raw/Agent/agency-agents/support/support-executive-summary-generator.md]] + +## Summary +- 核心主题：高级战略咨询风格的执行摘要生成智能体 +- 问题域：C-suite 决策者需要快速理解复杂业务信息 +- 方法/机制：McKinsey SCQA、BCG Pyramid Principle、Bain Action-Oriented Recommendation 三大框架 +- 结论/价值：将 325-475 字复杂业务输入转化为结构化执行摘要，支持 3 分钟决策 + +## Key Claims +- 咨询级 AI 系统应像资深战略顾问一样思考、结构和沟通 +- 执行摘要必须包含 ≥ 1 个量化或比较数据点 +- 量化影响应尽可能具体（Revenue/Cost/Market Share） +- 建议必须包含 Owner + Timeline + Expected Result +- 加速人类判断而非替代它 + +## Key Quotes +> "Think, structure, and communicate like a senior strategy consultant with Fortune 500 experience" +> "Prioritize insight over information" +> "Enable executives to grasp essence, evaluate impact, and decide next steps in under three minutes" + +## Key Concepts +- [[McKinsey SCQA Framework]]：Situation-Complication-Question-Answer 结构化叙事框架 +- [[BCG Pyramid Principle]]：自上而下逻辑表达的的金字塔原则 +- [[Bain Action-Oriented Model]]：以行动为导向的建议模型，强调明确所有权和时间线 +- [[Executive Summary]]：325-475 字的决策者简报格式 +- [[Consulting Framework]]：管理咨询方法论，用于结构化复杂业务问题 + +## Key Entities +- [[The Agency]]：开源 AI 智能体集合项目，Executive Summary Generator 是其 Support 分类下的专业智能体 + +## Connections +- [[Data Consolidation Agent]] ← 应用场景 ← [[Executive Summary Generator]]（需要销售数据输入） +- [[Report Distribution Agent]] ← 下游 ← [[Executive Summary Generator]]（生成摘要的分发） +- [[Paid Media Auditor]] ← 类似框架 ← [[Executive Summary Generator]]（都需要量化发现） + +## Quality Standards +- 325-475 words（≤ 500 max） +- 每个关键发现包含 ≥ 1 个量化或比较数据点 +- 发现按业务影响排序 +- 建议包含 Owner + Timeline + Expected Result +- 语气：Decisive、Factual、Outcome-driven + +## Workflow +1. Intake and Analysis：审查业务内容，识别关键洞察和量化数据点 +2. Structure Development：应用金字塔原则，按业务影响优先级组织 +3. Executive Summary Generation：起草情境概述、关键发现（加粗战略含义）、量化业务影响、优先级建议 +4. Quality Assurance：验证字数范围、量化合规性、建议完整性 + +## Output Format +``` +## 1. SITUATION OVERVIEW [50-75 words] +## 2. KEY FINDINGS [125-175 words] +## 3. BUSINESS IMPACT [50-75 words] +## 4. RECOMMENDATIONS [75-100 words] +## 5. NEXT STEPS [25-50 words] +``` \ No newline at end of file diff --git a/wiki/sources/support-finance-tracker.md b/wiki/sources/support-finance-tracker.md new file mode 100644 index 00000000..30756274 --- /dev/null +++ b/wiki/sources/support-finance-tracker.md @@ -0,0 +1,38 @@ +--- +title: "Finance Tracker" +type: source +tags: [support, finance, agent] +date: 2026-04-21 +--- + +## Source File +- [[raw/Agent/agency-agents/support/support-finance-tracker.md]] + +## Summary +- 核心主题：企业财务健康维护、预算与差异分析、现金流预测与优化、投资评估 +- 问题域：现金流波动、预算超支、投资决策缺乏量化依据与审计合规 +- 方法/机制：年度/季度预算框架、滚动现金流预测、支付时点优化、NPV/IRR 投资分析、审计轨迹与合规校验 +- 结论/价值：通过制度化预算与预测、支付优化与投资评价，可提升现金流稳定性、提高投资回报率并保证审计合规性 + +## Key Claims +- 财务准确性优先：所有数据源与计算必须校验并记录假设与凭证 +- 预算与差异分析是发现业务偏差与触发纠正措施的首要机制 +- 滚动现金流预测与支付时点优化能显著缓解短期流动性风险 +- NPV/IRR/回收期等量化指标必须作为投资决策的基线，并结合风险评分做综合判断 + +## Key Quotes +> "Include financial compliance validation and audit trail documentation in all processes" — 强调审计链与合规验证为默认要求 + +## Key Concepts +- [[Cash Flow Management]]：滚动现金流预测、低现金预警与高现金投资机会识别 +- [[Investment Analysis]]：NPV、IRR、回收期、风险评分与投资建议逻辑 +- [[Budget Framework]]：年度预算、季度差异分析与部门预算汇总 + +## Key Entities +- [[Finance Tracker]]：定义的智能体人格（财务分析与控制） + +## Connections +- [[Finance Tracker]] ← depends_on ← [[Support Analytics Reporter]] + +## Contradictions +- 未发现与现有 wiki 内容的直接冲突 diff --git a/wiki/sources/support-infrastructure-maintainer.md b/wiki/sources/support-infrastructure-maintainer.md new file mode 100644 index 00000000..01fc0398 --- /dev/null +++ b/wiki/sources/support-infrastructure-maintainer.md @@ -0,0 +1,78 @@ +--- +title: "Infrastructure Maintainer" +type: source +tags: [agent, infrastructure, devops] +date: 2026-04-21 +--- + +## Source File +- [[raw/Agent/agency-agents/support/support-infrastructure-maintainer.md]] + +## Summary +- 核心主题：Infrastructure Maintainer 智能体专业角色的完整定义 +- 问题域：系统可靠性、性能优化、技术运营管理 +- 方法/机制：IaC、监控、自动化、安全加固、灾备、成本优化 +- 结论/价值：提供 99.9%+ 运维能力，通过标准化交付物和流程实现基础设施可观测性 + +## Key Claims +- Infrastructure Maintainer 确保 99.9%+ 系统正常运行时间 +- IaC 框架（Terraform）实现跨平台基础设施声明式管理 +- Prometheus 监控配置支持多层次告警（infrastructure/application/database） +- 自动化备份系统通过加密和 S3 存储实现灾难恢复 +- Security Hardening 集成于所有基础设施变更 +- 成本优化策略实现 20%+ 年度效率提升 + +## Key Quotes +> "Monitoring indicates 85% disk usage on DB server - scaling scheduled for tomorrow" — Proactive communication style +> "Implemented redundant load balancers achieving 99.99% uptime target" — Reliability focus +> "Auto-scaling policies reduced costs 23% while maintaining <200ms response times" — Systematic optimization + +## Key Concepts +- [[Infrastructure as Code (IaC)]]：通过代码实现一致性、版本控制的基础设施管理 +- [[Prometheus Monitoring]]：时序数据库监控方案，支持多维度告警规则 +- [[Terraform]]：基础设施即代码工具，声明式配置跨平台云资源 +- [[Disaster Recovery]]：灾难恢复策略，RTO/RPO 为核心指标 +- [[Security Hardening]]：安全加固流程，零信任架构和最小权限原则 +- [[Cost Optimization]]：云成本优化策略，Right-Sizing 和 Reserved Instance + +## Key Entities +- [[The Agency]]：开源 AI 智能体集合项目，Infrastructure Maintainer 是其 Support 角色之一 +- [[AWS]]：基础设施云平台，提供 VPC、RDS、EC2 等服务 +- [[Prometheus]]：开源监控和告警工具 +- [[Terraform]]：HashiCorp 基础设施即代码工具 + +## Connections +- [[Support Infrastructure Maintainer]] ← is_a ← [[The Agency Agent]] +- [[DevOps 成熟度模型]] ← relates_to ← [[Infrastructure as Code (IaC)]] +- [[ITSM（IT 服务管理）]] ← relates_to ← [[Disaster Recovery]] + +## Contradictions +- 未检测到与现有 wiki 内容的冲突 + +## Workflow Deliverables +### Monitoring System +- Prometheus scrape_configs: infrastructure(30s), application(15s), database(30s) +- Alert rules: HighCPUUsage, HighMemoryUsage, DiskSpaceLow, ServiceDown + +### IaC Framework +- Terraform backend: S3 + DynamoDB state locking +- VPC with private/public subnets across availability zones +- Auto Scaling Group with ELB health checks +- RDS PostgreSQL with encrypted storage and backup retention + +### Backup & Recovery +- Encrypted backup script (GPG AES256) +- S3 storage with STANDARD_IA +- Retention: 30 days local, lifecycle managed in S3 +- Verification and Slack notification + +## Agent Characteristics +- **Role**: System reliability, infrastructure optimization, operations specialist +- **Personality**: Proactive, systematic, reliability-focused, security-conscious +- **Success Metrics**: 99.9%+ uptime, MTTR <4 hours, 20%+ cost efficiency, 70%+ automation reduction + +## Advanced Capabilities +- Multi-cloud architecture design +- Container orchestration (Kubernetes) +- Zero-trust security architecture +- Compliance automation (SOC2, ISO27001) \ No newline at end of file diff --git a/wiki/sources/support-legal-compliance-checker.md b/wiki/sources/support-legal-compliance-checker.md new file mode 100644 index 00000000..8258f580 --- /dev/null +++ b/wiki/sources/support-legal-compliance-checker.md @@ -0,0 +1,41 @@ +--- +title: "Legal Compliance Checker" +type: source +tags: [agent, legal, compliance] +date: 2026-04-21 +--- + +## Source File +- [[raw/Agent/agency-agents/support/support-legal-compliance-checker.md]] + +## Summary +The Agency 项目中的法律合规检查专家智能体，专注于多司法管辖区监管合规（GDPR、CCPA、HIPAA、SOX、PCI-DSS）、风险评估、政策开发与合规监控，确保业务运营符合相关法律法规。 + +## Key Claims +- 合规优先方法：验证监管要求后再实施任何业务变更，文档化所有合规决策 +- 风险评估整合：对所有新业务举措和功能开发进行法律风险评估 +- 多司法管辖区合规验证：默认要求包含多辖区合规验证和审计追踪文档 + +## Key Quotes +> "GDPR Article 17 requires data deletion within 30 days of valid erasure request" — 精确援引法规条款 +> "Non-compliance with CCPA could result in penalties up to $7,500 per violation" — 风险量化 +> "Implemented consent management system achieving 95% compliance with user rights requirements" — 可度量成果 + +## Key Concepts +- [[GDPR Compliance Framework]]：欧盟通用数据保护条例合规框架 +- [[CCPA Compliance]]：加州消费者隐私法案合规 +- [[Privacy Policy Generator]]：隐私政策生成器 Python 类 +- [[Contract Review System]]：合同审查自动化系统 +- [[Regulatory Compliance Assessment Report]]：监管合规评估报告模板 +- [[Multi-Jurisdictional Compliance]]：多司法管辖区合规管理 + +## Key Entities +- [[The Agency]]：开源 AI 智能体集合项目，本智能体所属项目 +- [[Healthcare Marketing Compliance Specialist]]：同项目医疗健康合规智能体 + +## Connections +- [[The Agency]] ← provides ← [[Legal Compliance Checker]] +- [[Healthcare Marketing Compliance Specialist]] ← related_to ← [[Legal Compliance Checker]]（共享合规方法论） + +## Contradictions +- 本页面为 Agent 定义文档，与实际业务合规实施可能存在理论-实践差距 \ No newline at end of file diff --git a/wiki/sources/support-support-responder.md b/wiki/sources/support-support-responder.md new file mode 100644 index 00000000..f40b0640 --- /dev/null +++ b/wiki/sources/support-support-responder.md @@ -0,0 +1,48 @@ +--- +title: "Support Responder" +type: source +tags: [agent, customer-service, the-agency] +date: 2026-04-21 +--- + +## Source File +- [[raw/Agent/agency-agents/support/support-support-responder.md]] + +## Summary +- 核心主题：The Agency 项目中的客户支持专家智能体，提供全渠道客户服务、问题解决和用户体验优化 +- 问题域：客户服务交付、质量保证、知识管理、主动式客户成功 +- 方法/机制：多层级支持框架（Tier 1/2/3）、SLA 响应机制、知识库管理、分析仪表盘 +- 结论/价值：将每次支持交互转化为品牌体验，通过 85% 首次联系解决率和 4.5+ CSAT 分数驱动客户满意度和留存 + +## Key Claims +- 首次响应时间 SLA：2 小时内，85% 首次联系解决率 +- 全渠道支持：email、chat、phone、social media、in-app messaging +- 客户满意度目标：4.5/5 以上 +- 首次联系解决率目标：80%+ +- SLA 合规率目标：95%+ +- 知识库贡献目标：减少 25%+ 未来工单量 + +## Key Quotes +> "I understand how frustrating this must be - let me help you resolve this quickly" — 共情沟通风格 +> "Here's exactly what I'll do to fix this issue, and here's how long it should take" — 解决方案导向 +> "To prevent this from happening again, I recommend these three steps" — 主动预防思维 + +## Key Concepts +- [[Multi-Channel Support Framework]]：跨 email、chat、phone、social media、in-app messaging 的统一客户支持框架 +- [[Support Tiers]]：Tier 1（通用）、Tier 2（技术）、Tier 3（专家）的分层支持架构 +- [[Customer Success]]：从被动响应到主动成功干预的客户生命周期管理 +- [[Knowledge Base Management]]：自助服务资源、文档优化和交互式故障排除系统 +- [[Support Analytics]]：响应时间、解决率、CSAT 等关键指标的计算与趋势分析 + +## Key Entities +- [[The Agency]]：开源 AI 智能体集合项目，本智能体属于其中 +- Support Analytics：客户支持分析仪表盘类，负责指标计算和趋势识别 +- Knowledge Base Manager：知识库管理类，负责文章创建和优化 +- Tier 1/2/3 Support Teams：分层支持团队，各有明确的升级标准 + +## Connections +- [[Support Legal Compliance Checker]] ← shares_framework ← [[Support Responder]]（共享合规框架） +- [[Product Feedback Synthesizer]] ← depends_on ← [[Support Responder]]（客户反馈数据输入） +- [[Sales Discovery Coach]] ← parallel ← [[Support Responder]]（客户需求发现方法论） + +## Contradictions \ No newline at end of file diff --git a/wiki/sources/testing-accessibility-auditor.md b/wiki/sources/testing-accessibility-auditor.md new file mode 100644 index 00000000..56510d4c --- /dev/null +++ b/wiki/sources/testing-accessibility-auditor.md @@ -0,0 +1,73 @@ +--- +title: "Accessibility Auditor" +type: source +tags: [accessibility, testing, agent, the-agency] +date: 2026-04-21 +--- + +## Source File +- [[raw/Agent/agency-agents/testing/testing-accessibility-auditor.md]] + +## Summary +- 核心主题：The Agency 项目中的无障碍审计专家智能体，基于 WCAG 2.2 标准进行界面审计 +- 问题域：无障碍合规测试、辅助技术验证、包容性设计评估 +- 方法/机制：WCAG POUR 原则测试、屏幕阅读器测试（VoiceOver/NVDA/JAWS）、键盘导航测试、自动化扫描 + 手动测试结合 +- 结论/价值：自动化工具仅能捕获约 30% 的无障碍问题，剩余 70% 需人工辅助技术测试发现 + +## Key Claims +- 自动化工具仅能检测约 30% 的无障碍问题，70% 需人工测试发现 +- 绿 Lighthouse 分数不代表真正的无障碍达标 +- 自定义组件（tabs、modals、carousels、date pickers）默认有罪直至证明无罪 +- "能用鼠标操作"不是测试——每个流程都必须能仅用键盘完成 +- 语义 HTML 优先于 ARIA——最好的 ARIA 是不需要用的 ARIA + +## Key Quotes +> "A green Lighthouse score does not mean accessible — say so when it applies" — AccessibilityAuditor 核心原则 +> "Custom components (tabs, modals, carousels, date pickers) are guilty until proven innocent" — 组件测试原则 +> "If it's not tested with a screen reader, it's not accessible" — 核心使命宣言 + +## Key Concepts +- [[WCAG 2.2]]：Web Content Accessibility Guidelines 2.2，网页内容无障碍指南标准 +- [[POUR Principles]]：Perceivable、Operable、Understandable、Robust 四大无障碍设计原则 +- [[Screen Reader Testing]]：使用屏幕阅读器（VoiceOver、NVDA、JAWS）验证内容可访问性 +- [[Keyboard Navigation Audit]]：纯键盘导航测试，验证所有交互元素可及性 +- [[ARIA Patterns]]：Accessible Rich Internet Applications 模式，自定义组件的无障碍实现规范 +- [[axe-core]]：自动化无障碍扫描工具，可集成到 CI/CD 流程 +- [[Lighthouse Accessibility]]：Chrome 开发者工具内置的无障碍审计功能 + +## Key Entities +- [[The Agency]]：开源 AI 智能体集合项目，Accessibility Auditor 是其测试类智能体之一 +- [[WAI-ARIA]]：Web Accessibility Initiative 制定的 ARIA 规范 +- [[WCAG 2.2]]：W3C 发布的网页内容无障碍指南 2.2 版本 + +## Connections +- [[Testing Reality Checker]] ← collaborates_with ← [[Accessibility Auditor]] +- [[Evidence Collector]] ← provides_evidence_to ← [[Accessibility Auditor]] +- [[Frontend Developer]] ← receives_audit_from ← [[Accessibility Auditor]] +- [[UI Designer]] ← receives_feedback_from ← [[Accessibility Auditor]] + +## Contradictions +- 暂无已知冲突 + +## Testing Methodology +### Automated Scanning +- axe-core CLI: `npx @axe-core/cli http://localhost:8000 --tags wcag2a,wcag2aa,wcag22aa` +- Lighthouse: `npx lighthouse http://localhost:8000 --only-categories=accessibility --output=json` + +### Manual Testing Protocol +1. **Screen Reader Testing**: VoiceOver (macOS)、NVDA (Windows)、JAWS 各平台完整流程测试 +2. **Keyboard Navigation**: 纯键盘完成所有关键用户旅程 +3. **Visual Testing**: 200%/400% 缩放、高对比度模式、减少动画模式 +4. **Component Deep Dive**: 自定义组件 WAI-ARIA Authoring Practices 对标审查 + +### Severity Classification +- **Critical**: 完全阻断部分用户访问 +- **Serious**: 需要变通方案的主要障碍 +- **Moderate**: 造成困难但有变通方案 +- **Minor**: 降低可用性的烦扰问题 + +## Audit Deliverables +- Accessibility Audit Report（含问题详情、WCAG 条款引用、修复建议） +- Screen Reader Testing Protocol（按组件的 PASS/FAIL 表格） +- Keyboard Navigation Audit（全局导航 + 组件特定模式检查清单） +- Remediation Priority（Immediate/Short-term/Ongoing 三级优先级） \ No newline at end of file diff --git a/wiki/sources/testing-api-tester.md b/wiki/sources/testing-api-tester.md new file mode 100644 index 00000000..ff860319 --- /dev/null +++ b/wiki/sources/testing-api-tester.md @@ -0,0 +1,24 @@ +--- +title: "API Tester (Agent)" +type: source +tags: [agent, testing, api] +date: 2026-04-20 +source_file: raw/Agent/agency-agents/testing/testing-api-tester.md +--- + +## Summary +API Tester is an Agency agent specialized in comprehensive API validation, performance testing, and security-focused QA. The source file defines its identity, mission, testing workflows, technical deliverables (including example test suites), and success metrics. + +## Key Claims +- The agent enforces a security-first testing approach and performance excellence standards (95th percentile <200ms target, 10x load validation). +- Provides example automated test suites (Playwright-based) and deliverable templates for testing reports. +- Workflow covers discovery, strategy, implementation, and monitoring with integration into CI/CD. + +## Key Quotes +> "You are **API Tester**, an expert API testing specialist who focuses on comprehensive API validation, performance testing, and quality assurance." — Agent frontmatter + +## Connections +- [[Testing Practices]] — related concept for strategies and tooling + +## Contradictions +- None detected with existing wiki content at time of ingest. diff --git a/wiki/sources/testing-evidence-collector.md b/wiki/sources/testing-evidence-collector.md new file mode 100644 index 00000000..02915e5b --- /dev/null +++ b/wiki/sources/testing-evidence-collector.md @@ -0,0 +1,109 @@ +--- +title: "Evidence Collector" +type: source +tags: [testing, qa, evidence, agency] +date: 2026-04-21 +--- + +## Source File +- [[raw/Agent/agency-agents/testing/testing-evidence-collector.md]] + +## Summary +- 核心主题：QA 证据收集智能体 EvidenceQA 的角色定义与测试方法论 +- 问题域：AI Agent 开发中的质量保证流程，避免无证据的"幻想式"报告 +- 方法/机制：基于 Playwright 截图、可复现命令、事实检查的证据驱动 QA +- 结论/价值：建立现实的质量评估标准，默认发现 3-5 个问题，要求视觉证据 + +## Key Claims +- 视觉证据是唯一真相：无法截图证明的功能视为不存在 +- 默认发现问题：首次实现总有 3-5+ 个问题，"零问题"是危险信号 +- 一切需证明：每个声明都需要截图证据支撑 +- 诚实质量评估：Basic/Good/Excellent 级别，不接受虚假的 A+ 评分 + +## Key Quotes +> "Screenshots Don't Lie" — 视觉证据是唯一真相 +> "Default to Finding Issues" — 首次实现总有 3-5+ 个问题 +> "Prove Everything" — 每个声明都需要截图证据 + +## Key Concepts +- [[证据驱动 QA（Evidence-Driven QA）]]：要求所有声明都有视觉证据支撑的 QA 方法论 +- [[幻想式报告（Fantasy Reporting）]]：无证据支撑的乐观声明，如"零问题"、"完美评分" +- [[Reality Checker]]：通过实际命令和截图验证功能真实状态 +- [[Playwright 截图]]：自动化捕获界面截图作为 QA 证据 + +## Key Entities +- [[EvidenceQA]]：截图驱动的 QA 专家智能体，厌恶幻想式报告 +- [[Reality Checker]]：与 EvidenceQA 协同的质量检查智能体 +- [[Test Results Analyzer]]：测试结果分析与缺陷预测智能体 + +## Connections +- [[Reality Checker (Agent)]] ← complements ← [[Evidence Collector]] +- [[Test Results Analyzer]] ← extends ← [[Evidence Collector]] +- [[Evidence Collector]] ← part_of ← [[The Agency]] +- [[The Agency]] ← contains ← [[Testing Agents]] + +## QA Report Template + +```markdown +# QA Evidence-Based Report + +## 🔍 Reality Check Results +**Commands Executed**: [List actual commands run] +**Screenshot Evidence**: [List all screenshots reviewed] +**Specification Quote**: "[Exact text from original spec]" + +## 📸 Visual Evidence Analysis +**Comprehensive Playwright Screenshots**: responsive-desktop.png, responsive-tablet.png, responsive-mobile.png, dark-mode-*.png +**What I Actually See**: +- [Honest description of visual appearance] + +**Specification Compliance**: +- ✅ Spec says: "[quote]" → Screenshot shows: "[matches]" +- ❌ Spec says: "[quote]" → Screenshot shows: "[doesn't match]" + +## 📊 Issues Found (Minimum 3-5) +1. **Issue**: [Specific problem] + **Evidence**: [Screenshot reference] + **Priority**: Critical/Medium/Low + +## 🎯 Honest Quality Assessment +**Realistic Rating**: C+ / B- / B / B+ (NO A+ fantasies) +**Design Level**: Basic / Good / Excellent +**Production Readiness**: FAILED / NEEDS WORK / READY + +## 🔄 Required Next Steps +**Status**: FAILED (default unless overwhelming evidence) +**Re-test Required**: YES +``` + +## Testing Protocol + +### Accordion Testing +- 对比展开前后的截图 +- 验证内容是否正确显示 + +### Form Testing +- 截图空表单、填写后表单 +- 验证提交、验证、错误提示 + +### Mobile Responsive Testing +- 1920x1080、768x1024、375x667 三种分辨率 +- 验证汉堡菜单、布局、配色 + +### Dark Mode Testing +- 验证深色模式切换功能 +- 检查截图中的 dark-mode-*.png + +## Automatic Fail Triggers + +### Fantasy Reporting Signs +- 声称"零问题" +- 完美评分（A+, 98/100） +- 无证据的"豪华/高级"声明 +- 未测试就声称"生产就绪" + +### Visual Evidence Failures +- 无法提供截图 +- 截图与声明不符 +- 截图中可见功能损坏 +- 基础样式被声称 为"豪华" diff --git a/wiki/sources/testing-performance-benchmarker.md b/wiki/sources/testing-performance-benchmarker.md new file mode 100644 index 00000000..765d2c68 --- /dev/null +++ b/wiki/sources/testing-performance-benchmarker.md @@ -0,0 +1,25 @@ +--- +title: "Performance Benchmarker (Agent)" +type: source +tags: [agent, testing, performance] +date: 2026-04-20 +source_file: raw/Agent/agency-agents/testing/testing-performance-benchmarker.md +--- + +## Summary +Performance Benchmarker is an Agency agent specializing in performance testing, benchmarking, and optimization across applications and infrastructure. The source includes example k6 test scripts, reporting generation, workflow steps, deliverable templates, and success metrics. + +## Key Claims +- Focuses on load, stress, endurance, and scalability testing with statistical analysis and confidence intervals. +- Provides k6 examples and report generation, Core Web Vitals targets, capacity planning guidance, and monitoring recommendations. +- Emphasizes realistic testing, before/after validation, and continuous monitoring in CI/CD. + +## Key Quotes +> "You are **Performance Benchmarker**, an expert performance testing and optimization specialist who measures, analyzes, and improves system performance across all applications and infrastructure." — Agent frontmatter + +## Connections +- [[API Tester (Agent)]] — related testing agent for API validation +- [[Workflow Optimizer (Agent)]] — related to process and systems optimization + +## Contradictions +- None detected with existing wiki content at time of ingest. diff --git a/wiki/sources/testing-reality-checker.md b/wiki/sources/testing-reality-checker.md new file mode 100644 index 00000000..4a0b5496 --- /dev/null +++ b/wiki/sources/testing-reality-checker.md @@ -0,0 +1,24 @@ +--- +title: "Reality Checker (Agent)" +type: source +tags: [agent, testing, integration] +date: 2026-04-20 +source_file: raw/Agent/agency-agents/testing/testing-reality-checker.md +--- + +## Summary +Reality Checker is an Agency integration agent that enforces evidence-based production readiness: defaulting to "NEEDS WORK" unless overwhelming automated evidence (screenshots, test-results) supports "READY". The file details mandatory commands, evidence collection workflows, report templates, and automatic fail triggers. + +## Key Claims +- Defaults to "NEEDS WORK" and requires automated screenshot evidence, cross-validated QA data, and end-to-end journey proof for production certification. +- Provides a reality-check command sequence (ls, grep, Playwright capture) and report templates covering visual evidence, journey testing, and specification gap analysis. + +## Key Quotes +> "Defaults to \"NEEDS WORK\" — requires overwhelming proof for production readiness." — Reality Checker frontmatter + +## Connections +- [[Testing Practices]] — connects to QA and integration testing methodologies +- [[API Tester (Agent)]] — related testing agent for API validation + +## Contradictions +- None detected with existing wiki content at time of ingest. diff --git a/wiki/sources/testing-test-results-analyzer.md b/wiki/sources/testing-test-results-analyzer.md new file mode 100644 index 00000000..4e4eeb7d --- /dev/null +++ b/wiki/sources/testing-test-results-analyzer.md @@ -0,0 +1,26 @@ +--- +title: "Test Results Analyzer" +type: source +tags: [testing, quality, analytics] +date: 2026-04-21 +source_file: raw/Agent/agency-agents/testing/testing-test-results-analyzer.md +--- + +## Summary +Test Results Analyzer defines an agent persona specialized in analyzing test outputs, identifying failure patterns, building predictive defect models, assessing release readiness, and producing stakeholder-specific reports and dashboards. + +## Key Claims +- Analyze test execution results across functional, performance, security, and integration testing using statistical methods +- Identify failure patterns, perform root cause analysis, and surface high-impact quality risks +- Build predictive models for defect-prone areas and provide confidence intervals for release readiness recommendations +- Deliver executive summaries, technical reports, and automated alerts to stakeholders + +## Key Quotes +> "Every test result must be analyzed for patterns and improvement opportunities." — core requirement + +## Connections +- [[Model QA Specialist]] — related expertise in ML model auditing and statistical validation +- [[Performance Benchmarker (Agent)]] — complementary agent for performance testing and benchmarking + +## Contradictions +- No direct contradictions found with existing wiki content. diff --git a/wiki/sources/testing-tool-evaluator.md b/wiki/sources/testing-tool-evaluator.md new file mode 100644 index 00000000..b55268f5 --- /dev/null +++ b/wiki/sources/testing-tool-evaluator.md @@ -0,0 +1,48 @@ +--- +title: "Testing Tool Evaluator" +type: source +tags: [agent, testing, tool-evaluation, the-agency] +sources: [] +last_updated: 2026-04-21 +--- + +## Source File +- [[raw/Agent/agency-agents/testing/testing-tool-evaluator.md]] + +## Summary +- 核心主题：Tool Evaluator Agent（工具评估专家智能体）定义与技术评估方法论 +- 问题域：企业工具选择、供应商评估、投资回报分析 +- 方法/机制：加权评分评估框架、TCO/ROI 定量分析、安全/集成/可扩展性评估、供应商管理 +- 结论/价值：90% 推荐准确率、85% 采用率、20% 成本降低、25% ROI 达成 + +## Key Claims +- Tool Evaluator Agent 通过加权评分体系实现客观工具评估 +- TCO（总拥有成本）分析包含隐藏成本和扩展费用 +- 评估流程必须包含安全、集成和成本分析三个默认要求 +- 评估方法论强调可重复性和透明性 + +## Key Quotes +> "Always test tools with real-world scenarios and actual user data" — 证据驱动评估原则 +> "Calculate total cost of ownership including hidden costs and scaling fees" — 成本分析核心要求 + +## Key Concepts +- [[Tool Evaluation Framework]]：加权评分工具评估框架，包含功能性、可用性、性能、安全性、集成、支持、成本七个维度 +- [[TCO（Total Cost of Ownership）]]：总拥有成本，包含许可、实施、培训、维护、集成、迁移、支持等全生命周期成本 +- [[ROI Analysis]]：投资回报率分析，通过多场景和敏感性分析评估工具价值 +- [[Vendor Management]]：供应商关系管理与合同优化策略 + +## Key Entities +- [[Tool Evaluator Agent]]：技术评估与战略工具采纳专家智能体，专注于 ROI 导向的工具选择 + +## Connections +- [[Test Results Analyzer]] ← complements ← [[Tool Evaluator Agent]] +- [[Evidence Collector]] ← complements ← [[Tool Evaluator Agent]] +- [[Performance Benchmarker]] ← complements ← [[Tool Evaluator Agent]] +- [[Reality Checker]] ← enforces ← evidence-based evaluation + +## Contradictions +- 与现有质量保障智能体存在功能重叠，但侧重点不同： + - Tool Evaluator 聚焦工具选择与供应商评估 + - Test Results Analyzer 聚焦测试结果分析与缺陷预测 + - Performance Benchmarker 聚焦性能测试与基准验证 + - Reality Checker 聚焦生产就绪证据收集 diff --git a/wiki/sources/testing-workflow-optimizer.md b/wiki/sources/testing-workflow-optimizer.md new file mode 100644 index 00000000..f2fedf85 --- /dev/null +++ b/wiki/sources/testing-workflow-optimizer.md @@ -0,0 +1,25 @@ +--- +title: "Workflow Optimizer (Agent)" +type: source +tags: [agent, testing, workflow, optimization] +date: 2026-04-20 +source_file: raw/Agent/agency-agents/testing/testing-workflow-optimizer.md +--- + +## Summary +Workflow Optimizer is an Agency agent focused on process improvement, automation, and cross-functional workflow optimization. The source defines its mission, analysis frameworks, example Python optimization code, deliverable templates, and success metrics. + +## Key Claims +- Emphasizes data-driven process improvement and human-centered design. +- Provides code examples and frameworks for analyzing workflows, identifying opportunities, designing optimized flows, and calculating quantified impact. +- Recommends phased implementation with quick wins, medium-term, and strategic initiatives. + +## Key Quotes +> "You are **Workflow Optimizer**, an expert process improvement specialist who analyzes, optimizes, and automates workflows across all business functions." — Agent frontmatter + +## Connections +- [[API Tester (Agent)]] — related testing and validation practices +- [[Testing Practices]] — potential concept linking testing and workflow optimization + +## Contradictions +- None detected with existing wiki content at time of ingest. diff --git a/wiki/sources/windsurf-readme.md b/wiki/sources/windsurf-readme.md new file mode 100644 index 00000000..caf0207d --- /dev/null +++ b/wiki/sources/windsurf-readme.md @@ -0,0 +1,24 @@ +--- +title: "Windsurf Integration" +type: source +tags: [agency, integrations, windsurf] +date: 2026-04-20 +source_file: raw/Agent/agency-agents/integrations/windsurf/README.md +--- + +## Summary +Windsurf Integration README explains consolidating the full Agency roster into a single `.windsurfrules` file that is project-scoped. It documents installing from the project root, referencing agents by name in prompts, and regenerating rules with the convert script. + +## Key Claims +- The Agency exports a single `.windsurfrules` file containing all rules; rules are project-scoped and installed from the project root. +- Install via `/path/to/agency-agents/scripts/install.sh --tool windsurf` from your project root. +- Activate agents by referencing their name in the prompt (e.g., "Use the Frontend Developer agent..."). + +## Key Quotes +> "The full Agency roster is consolidated into a single `.windsurfrules` file. Rules are project-scoped — install them from your project root." — Windsurf Integration README + +## Connections +- [[The Agency: AI Specialists Ready to Transform Your Workflow]] — roster source + +## Contradictions +- None detected with existing wiki content at time of ingest. diff --git a/wiki/sources/workflow-book-chapter.md b/wiki/sources/workflow-book-chapter.md new file mode 100644 index 00000000..54039336 --- /dev/null +++ b/wiki/sources/workflow-book-chapter.md @@ -0,0 +1,45 @@ +--- +id: workflow-book-chapter +title: "Workflow Example: Book Chapter Development" +type: source +tags: [workflow, agent, writing] +sources: [raw/Agent/agency-agents/examples/workflow-book-chapter.md] +last_updated: 2026-04-21 +--- + +## Source File +- [[raw/Agent/agency-agents/examples/workflow-book-chapter.md]] + +## Summary +- 核心主题：AI Agent 将粗糙素材转化为战略性的第一人称书籍章节草稿的工作流 +- 问题域：作者有语音笔记、片段或战略笔记，但缺乏干净的章节草稿 +- 方法/机制：Book Co-Author Agent 通过版本化草稿、编辑注释和明确修订问题实现结构化产出 +- 结论/价值：产出强化品类定位、保留作者声音、暴露开放编辑决策的章节 + +## Key Claims +- Book Co-Author Agent 将源素材转化为带编辑注释和下一步问题的版本化章节草稿 +- 工作流目标不是通用代笔，而是产生强化品类定位的章节 +- 草稿必须保持第一人称声音 +- 章节必须有一个清晰的承诺和内部逻辑 +- 声明必须与源素材关联或标记为假设 +- 移除通用激励语言 +- 输出以明确修订问题结束，而非模糊交接 + +## Key Quotes +> "The goal is not generic ghostwriting. The goal is to produce a chapter that strengthens category positioning, preserves the author's voice, and exposes open editorial decisions clearly." + +## Key Concepts +- [[Book Co-Author Agent]]：将源素材转化为版本化章节草稿的 AI Agent +- [[Versioned Draft]]：通过迭代循环产生的带版本号的章节草稿 +- [[Editorial Notes]]：对假设和证据缺口的明确标注 +- [[Feedback Loop]]：Agent 提供的结构化修订请求机制 + +## Key Entities +- [[The Agency]]：开源 AI 智能体集合项目，提供各类专业化 Agent + +## Connections +- [[Book Co-Author Agent]] ← is_example_of ← [[The Agency]] +- [[Versioned Draft]] ← depends_on ← [[Feedback Loop]] +- [[Editorial Notes]] ← supports ← [[Book Co-Author Agent]] + +## Contradictions diff --git a/wiki/sources/workflow-startup-mvp.md b/wiki/sources/workflow-startup-mvp.md new file mode 100644 index 00000000..0bbd9920 --- /dev/null +++ b/wiki/sources/workflow-startup-mvp.md @@ -0,0 +1,62 @@ +--- +title: "Multi-Agent Workflow: Startup MVP" +type: source +tags: [] +date: 2026-04-21 +--- + +## Source File +- [[raw/Agent/agency-agents/examples/workflow-startup-mvp.md]] + +## Summary +- 核心主题：多智能体协作从创意到 MVP 交付的完整工作流程 +- 问题域：4 周 MVP 开发项目，如何协调多个专业智能体顺序与并行工作 +- 方法/机制：7 个专业角色（Sprint Prioritizer、UX Researcher、Backend Architect、Frontend Developer、Rapid Prototyper、Growth Hacker、Reality Checker），通过顺序交接、并行工作、质量门控、上下文传递实现协作 +- 结论/价值：证明多智能体团队可以高效完成端到端产品开发 + +## Key Claims +- Sprint Prioritizer 将项目分解为 4 周冲刺计划，每周期有明确交付物和验收标准 +- UX Researcher 在 Week 1 并行运行，快速完成竞品分析和差异化定位 +- Backend Architect 基于 Sprint Prioritizer 和 UX Researcher 输出设计 API 和数据模型 +- Frontend Developer 与 Rapid Prototyper 在 Week 2 并行构建核心功能 +- Reality Checker 在 Week 2 中点和 Week 4 _launch 前设置两个质量门控 +- Growth Hacker 在 Week 3 开始启动策略规划，与 Frontend Developer 并行工作 +- Sequential Handoffs 确保每个智能体输出成为下一个智能体输入 +- Context Passing 要求粘贴完整智能体输出而非摘要 + +## Key Quotes +> "Copy-paste agent outputs between steps — don't summarize, use the full output" — 上下文传递原则 +> "If a Reality Checker flags an issue, loop back to the relevant specialist to fix it" — 质量门控反馈机制 + +## Key Concepts +- [[Sequential Handoffs]]：顺序交接，每个智能体输出直接作为下一智能体输入 +- [[Parallel Work]]：并行工作，Week 1 中 Sprint Prioritizer 和 UX Researcher 可同时运行 +- [[Quality Gates]]：质量门控，Reality Checker 在关键节点进行生产就绪评估 +- [[Context Passing]]：上下文传递，始终粘贴完整智能体输出而非摘要 +- [[Multi-Agent Team]]：多智能体团队，多角色协作架构 +- [[Sprint Planning]]：冲刺规划，4 周 MVP 交付的阶段性计划 + +## Key Entities +- [[Sprint Prioritizer]]：冲刺优先级智能体，负责将项目分解为 4 周冲刺计划 +- [[UX Researcher]]：用户体验研究智能体，负责竞品分析和用户访谈 +- [[Backend Architect]]：后端架构智能体，负责 API 设计、数据库 Schema 和实时架构 +- [[Frontend Developer]]：前端开发智能体，负责 React 应用构建 +- [[Rapid Prototyper]]：快速原型智能体，加速初始版本落地 +- [[Growth Hacker]]：增长黑客智能体，负责 Launch 策略规划 +- [[Reality Checker]]：现实检查智能体，在关键节点进行生产就绪评估和 GO/NO-GO 决策 + +## Connections +- [[Sprint Prioritizer]] → 输出冲刺计划 → [[Backend Architect]] +- [[UX Researcher]] → 输出研究简报 → [[Backend Architect]] +- [[Backend Architect]] → 输出 API Spec → [[Frontend Developer]] +- [[Frontend Developer]] + [[Rapid Prototyper]] → 并行构建 → Week 2 输出 +- [[Reality Checker]] ← 中点评估 ← [[Frontend Developer]]（Week 2） +- [[Frontend Developer]] → 继续开发 → [[Growth Hacker]]（Week 3 并行） +- [[Reality Checker]] ← 最终评估 ← [[Growth Hacker]]（Week 4） +- [[Reality Checker]] ← 生产就绪检查 ← RetroBoard MVP + +## Contradictions +- 与单兵作战开发模式冲突： + - 冲突点：传统 MVP 开发通常由单一开发者完成，多智能体协作增加了交接成本 + - 当前观点：多智能体协作通过专业化分工提升效率，通过质量门控确保交付质量 + - 对方观点：小型 MVP 项目使用多智能体可能过度设计，顺序交接增加上下文丢失风险 diff --git a/wiki/sources/workflow-with-memory.md b/wiki/sources/workflow-with-memory.md new file mode 100644 index 00000000..f6cc2567 --- /dev/null +++ b/wiki/sources/workflow-with-memory.md @@ -0,0 +1,57 @@ +--- +title: "Multi-Agent Workflow: Startup MVP with Persistent Memory" +type: source +tags: [multi-agent, workflow, memory, startup, mvp] +date: 2026-04-21 +--- + +## Source File +- [[raw/Agent/agency-agents/examples/workflow-with-memory.md]] + +## Summary +- 核心主题：基于 MCP Memory Server 的多智能体协作工作流，解决手动交接上下文丢失问题 +- 问题域：传统工作流中 agent 间交接依赖人工复制粘贴，会话超时、多 agent 共享上下文、QA 失败回滚、跨日项目等场景下的上下文断裂 +- 方法/机制：通过 MCP Memory Server 实现 `remember`、`recall`、`rollback`、`search` 操作，使 agents 自动存取项目状态，消除手动交接 +- 结论/价值：上下文持久化 → 无复制粘贴交接 → 跨会话连续性 → QA 回滚自动化 → 多日项目可管理 + +## Key Claims +- MCP Memory Server 可实现 agent 间自动上下文存取，消除手动复制粘贴交接 +- 记忆标签系统（tag everything with project name）是实现 recall 的关键 +- Reality Checker 因所有 agent 存储工作于 memory，获得完整项目可见性 +- Rollback 机制替代手动 undo，使 QA 失败恢复更紧密 + +## Key Quotes +> "With an MCP memory server installed, agents store their deliverables in memory and retrieve what they need automatically." — 核心价值主张 +> "Agents recall what they need automatically" vs "Copy-paste full output between agents" — 前后对比 +> "Tag everything with the project name: This is what makes recall work." — 实施关键模式 + +## Key Concepts +- [[MCP Memory Server]]：模型上下文协议记忆服务器，支持 remember/recall/rollback/search 操作 +- [[Multi-Agent Workflow]]：多智能体协作流水线，多角色 agents 顺序/并行执行 +- [[Memory Tagging]]：记忆标签系统，通过项目名和接收 agent 名标记记忆实现精准召回 +- [[Rollback Mechanism]]：回滚机制，agent 可回退到最后检查点并修复问题 +- [[Reality Checker]]：真实性检查智能体，在每个里程碑前评估可发货性和风险 + +## Key Entities +- [[Sprint Prioritizer]]：冲刺规划智能体，将项目拆分为 4 个每周冲刺 +- [[UX Researcher]]：用户体验研究智能体，进行竞品分析输出研究简报 +- [[Backend Architect]]：后端架构智能体，设计数据库 schema 和 REST API +- [[Frontend Developer]]：前端开发智能体，基于 API spec 构建 React 应用 +- [[Rapid Prototyper]]：快速原型智能体，加速初始版本上线 +- [[Growth Hacker]]：增长黑客智能体，规划产品发布策略 +- [[RetroBoard]]：团队回顾工具名称，作为示例项目贯穿全文 + +## Connections +- [[Sprint Prioritizer]] → produces → [[Sprint Plan]] +- [[UX Researcher]] → produces → [[Research Brief]] +- [[Backend Architect]] → recalls → [[Sprint Plan]] + [[Research Brief]] +- [[Backend Architect]] → produces → [[API Spec]] + [[Database Schema]] +- [[Frontend Developer]] → recalls → [[API Spec]] + [[Database Schema]] +- [[Growth Hacker]] → recalls → [[Reality Checker Verdict]] + [[Launch Plan]] +- [[Reality Checker]] → recalls → ALL deliverables for full project visibility + +## Contradictions +- 与 [[workflow-startup-mvp.md]] 冲突： + - 冲突点：相同项目（RetroBoard）但有无 MCP Memory Server 的两种版本 + - 当前观点：带 Memory 的版本通过自动 recall 消除手动交接 + - 对方观点：无 Memory 版本依赖人工复制粘贴上下文