Auto-sync: 2026-04-26 00:02
This commit is contained in:
24
wiki/entities/Backend-Architect.md
Normal file
24
wiki/entities/Backend-Architect.md
Normal file
@@ -0,0 +1,24 @@
|
||||
---
|
||||
title: "Backend Architect"
|
||||
type: entity
|
||||
sources: [workflow-startup-mvp]
|
||||
last_updated: 2026-04-25
|
||||
---
|
||||
|
||||
## Definition
|
||||
Backend Architect 是 [[workflow-startup-mvp]] 中负责设计完整 API 和数据模型的 Agent 角色,是前后端交接的关键桥梁。
|
||||
|
||||
## Details
|
||||
- **输入**:Sprint Prioritizer 输出的冲刺计划 + UX Researcher 输出的调研简报
|
||||
- **输出**:
|
||||
1. 数据库 Schema(SQL)
|
||||
2. REST API 端点列表
|
||||
3. WebSocket 实时事件规范
|
||||
4. 认证策略建议
|
||||
- **执行时机**:Week 1 第三步,接收前两个 Agent 的输出
|
||||
|
||||
## Aliases
|
||||
- Backend Architect
|
||||
|
||||
## Sources
|
||||
- [[workflow-startup-mvp]]
|
||||
34
wiki/entities/Content-Creator.md
Normal file
34
wiki/entities/Content-Creator.md
Normal file
@@ -0,0 +1,34 @@
|
||||
---
|
||||
title: "Content Creator"
|
||||
type: entity
|
||||
entity_type: Agent Role
|
||||
tags: [content, copywriting, landing-page, the-agency]
|
||||
last_updated: 2026-04-25
|
||||
---
|
||||
|
||||
## Role
|
||||
|
||||
The Agency Design/Marketing 部门的文案撰写专家 Agent,负责为 landing page、产品介绍、营销材料等场景创作高质量文案。
|
||||
|
||||
## In [[workflow-landing-page]]
|
||||
|
||||
Content Creator 在上午 9:00 与 UI Designer 并行启动([[Parallel-Kickoff]]),负责为 FlowSync(API 集成平台)撰写完整 landing page 文案:
|
||||
|
||||
- **目标受众**:开发者和技术 PM,中型公司
|
||||
- **语调**:自信、简洁、略带趣味
|
||||
- **交付物结构**:
|
||||
1. Hero(标题 + 副标题 + CTA)
|
||||
2. Problem Statement(3个痛点)
|
||||
3. How It Works(3步流程)
|
||||
4. Social Proof(推荐语占位格式)
|
||||
5. Pricing(3档:Free/Pro/Enterprise)
|
||||
6. Final CTA
|
||||
|
||||
## Aliases
|
||||
- Copywriter
|
||||
- Landing Page Copywriter
|
||||
|
||||
## Related Agents
|
||||
- [[UI-Designer]]:并行搭档([[workflow-landing-page]])
|
||||
- [[Frontend-Developer]]:下游合并点([[workflow-landing-page]])
|
||||
- [[Growth-Hacker]]:内容审查([[workflow-landing-page]])
|
||||
@@ -33,6 +33,20 @@ last_updated: 2026-04-25
|
||||
- 医疗广告须经过行业资质审核
|
||||
- 创意内容须经平台人工审核
|
||||
|
||||
## Marketing & Short-Video Strategy
|
||||
- **推荐算法优先级**:完播率 > 点赞率 > 评论率 > 分享率
|
||||
- **黄金3秒原则**:前三秒决定视频生死,必须用冲突/悬念/价值钩子开场
|
||||
- **内容矩阵类型**:教育类、剧情类、产品测评类、Vlog类
|
||||
- **热门BGM**:每周追踪平台趋势热点
|
||||
- **限流红线**:视频内禁止引流外部平台
|
||||
|
||||
## Key Agents
|
||||
- [[MarketingDouyinStrategist]]:The Agency 抖音短视频营销与直播带货策略专家
|
||||
|
||||
## Connections
|
||||
- [[MarketingDouyinStrategist]] ← 核心 Agent ← [[MarketingShortVideoEditingCoach]](内容剪辑支撑)
|
||||
- [[OceanEngine]] ← 广告投放平台 ← Douyin
|
||||
|
||||
## Aliases
|
||||
- 抖音
|
||||
- Douyin
|
||||
|
||||
22
wiki/entities/Frontend-Developer.md
Normal file
22
wiki/entities/Frontend-Developer.md
Normal file
@@ -0,0 +1,22 @@
|
||||
---
|
||||
title: "Frontend Developer"
|
||||
type: entity
|
||||
sources: [workflow-startup-mvp]
|
||||
last_updated: 2026-04-25
|
||||
---
|
||||
|
||||
## Definition
|
||||
Frontend Developer 是 [[workflow-startup-mvp]] 中负责基于 API 规范构建 React 应用前端的 Agent 角色,是产品核心体验的实现者。
|
||||
|
||||
## Details
|
||||
- **输入**:Backend Architect 输出的完整 API 规范
|
||||
- **技术栈**:React + TypeScript + Tailwind + Socket.io-client
|
||||
- **交付页面**:Login、Dashboard、Board View
|
||||
- **交付组件**:RetroCard、VoteButton、ActionItem、BoardColumn
|
||||
- **执行时机**:Week 2,与 Rapid Prototyper 并行工作
|
||||
|
||||
## Aliases
|
||||
- Frontend Developer
|
||||
|
||||
## Sources
|
||||
- [[workflow-startup-mvp]]
|
||||
24
wiki/entities/Growth-Hacker.md
Normal file
24
wiki/entities/Growth-Hacker.md
Normal file
@@ -0,0 +1,24 @@
|
||||
---
|
||||
title: "Growth Hacker"
|
||||
type: entity
|
||||
sources: [workflow-startup-mvp]
|
||||
last_updated: 2026-04-25
|
||||
---
|
||||
|
||||
## Definition
|
||||
Growth Hacker 是 [[workflow-startup-mvp]] 中负责制定发布策略和增长计划的 Agent 角色,在 Week 3 与前端开发并行启动。
|
||||
|
||||
## Details
|
||||
- **输入**:产品介绍、目标用户、零预算限制
|
||||
- **输出**:
|
||||
1. 着陆页文案(Hero、Features、CTA)
|
||||
2. 发布渠道(Product Hunt、Reddit、Hacker News、Twitter)
|
||||
3. Day-by-day 发布序列
|
||||
4. Week 1 关键指标定义
|
||||
- **执行时机**:Week 3,与 Frontend Developer 继续开发并行
|
||||
|
||||
## Aliases
|
||||
- Growth Hacker
|
||||
|
||||
## Sources
|
||||
- [[workflow-startup-mvp]]
|
||||
34
wiki/entities/OceanEngine.md
Normal file
34
wiki/entities/OceanEngine.md
Normal file
@@ -0,0 +1,34 @@
|
||||
---
|
||||
title: "Ocean Engine(巨量引擎)"
|
||||
type: entity
|
||||
tags: [platform, advertising, china, douyin]
|
||||
sources: [marketing-douyin-strategist]
|
||||
last_updated: 2026-04-25
|
||||
---
|
||||
|
||||
## Overview
|
||||
巨量引擎(Ocean Engine)是字节跳动旗下的一站式数字化营销服务平台,为抖音、今日头条、西瓜视频等字节系产品提供广告投放服务,是抖音电商和品牌营销的核心商业化基础设施。
|
||||
|
||||
## Core Products
|
||||
- **千川(Qianchuan)**:抖音电商广告投放平台,专注于直播带货和短视频带货广告
|
||||
- **品牌广告**:开屏广告、信息流广告、搜索广告等品牌曝光产品
|
||||
- **DOU+**:抖音原生内容加热工具,支持精准人群定向
|
||||
|
||||
## Key Metrics
|
||||
- **GPM**(GMV per thousand views):直播每千次观看产生的销售额,核心效率指标
|
||||
- **CVR**(Conversion Rate):转化率,从观看→下单的比例
|
||||
- **ROI**:广告投入产出比,DOU+ ROI 基准 > 1:3
|
||||
|
||||
## Douyin Marketing Integration
|
||||
- 付费广告(千川)与自然流量运营协同
|
||||
- DOU+ 用于测试内容方向和人群包
|
||||
- 矩阵账号运营配合付费投放放大效果
|
||||
|
||||
## Key Agents
|
||||
- [[MarketingDouyinStrategist]]:依赖 Ocean Engine 工具进行付费流量策略规划
|
||||
|
||||
## Aliases
|
||||
- 巨量引擎
|
||||
- Ocean Engine
|
||||
- 字节跳动商业化
|
||||
- 千川
|
||||
21
wiki/entities/OrchestratorAgent.md
Normal file
21
wiki/entities/OrchestratorAgent.md
Normal file
@@ -0,0 +1,21 @@
|
||||
---
|
||||
title: "Orchestrator Agent"
|
||||
type: entity
|
||||
sources: [workflow-startup-mvp]
|
||||
last_updated: 2026-04-25
|
||||
---
|
||||
|
||||
## Definition
|
||||
Orchestrator Agent 是未来用于自动化多 Agent 工作流的编排 Agent,可替代手动 copy-paste 实现自动化流水线协作。
|
||||
|
||||
## Details
|
||||
- **用途**:自动化 [[workflow-startup-mvp]] 中描述的手动 7 步多 Agent 流程
|
||||
- **核心能力**:自动触发专业 Agent、自动传递上下文、自动评估质量门控
|
||||
- **相关模式**:[[Sequential Handoff]]、[[Quality Gate]]、[[Context Passing]]
|
||||
|
||||
## Aliases
|
||||
- Orchestrator Agent
|
||||
- Orchestrator
|
||||
|
||||
## Sources
|
||||
- [[workflow-startup-mvp]]
|
||||
20
wiki/entities/Rapid-Prototyper.md
Normal file
20
wiki/entities/Rapid-Prototyper.md
Normal file
@@ -0,0 +1,20 @@
|
||||
---
|
||||
title: "Rapid Prototyper"
|
||||
type: entity
|
||||
sources: [workflow-startup-mvp]
|
||||
last_updated: 2026-04-25
|
||||
---
|
||||
|
||||
## Definition
|
||||
Rapid Prototyper 是 [[workflow-startup-mvp]] 中负责快速产出第一个可运行版本的 Agent 角色,目标是尽快验证核心功能。
|
||||
|
||||
## Details
|
||||
- **目标**:让第一个版本快速跑起来
|
||||
- **执行时机**:Week 2,与 Frontend Developer 并行工作
|
||||
- **质量门控**:产出需经 [[Reality Checker]] 评估后方可继续
|
||||
|
||||
## Aliases
|
||||
- Rapid Prototyper
|
||||
|
||||
## Sources
|
||||
- [[workflow-startup-mvp]]
|
||||
24
wiki/entities/Reality-Checker.md
Normal file
24
wiki/entities/Reality-Checker.md
Normal file
@@ -0,0 +1,24 @@
|
||||
---
|
||||
title: "Reality Checker"
|
||||
type: entity
|
||||
sources: [workflow-startup-mvp]
|
||||
last_updated: 2026-04-25
|
||||
---
|
||||
|
||||
## Definition
|
||||
Reality Checker 是 [[workflow-startup-mvp]] 中负责在关键里程碑评估生产就绪状态的质量门控 Agent,给出 GO/NO-GO 决策。
|
||||
|
||||
## Details
|
||||
- **评估维度**:
|
||||
1. 是否能在剩余时间内完成
|
||||
2. 需要削减什么功能以满足截止日期
|
||||
3. 哪些技术债务会在发布时反噬
|
||||
- **执行时机**:Week 2 中点和 Week 4 发布前
|
||||
- **决策输出**:GO(可继续)或 NO-GO(需回滚修复)
|
||||
- **触发回滚**:发现问题后回滚到对应专业 Agent 修复
|
||||
|
||||
## Aliases
|
||||
- Reality Checker
|
||||
|
||||
## Sources
|
||||
- [[workflow-startup-mvp]]
|
||||
22
wiki/entities/RetroBoard.md
Normal file
22
wiki/entities/RetroBoard.md
Normal file
@@ -0,0 +1,22 @@
|
||||
---
|
||||
title: "RetroBoard"
|
||||
type: entity
|
||||
sources: [workflow-startup-mvp]
|
||||
last_updated: 2026-04-25
|
||||
---
|
||||
|
||||
## Definition
|
||||
RetroBoard 是本文档中的示例 SaaS 产品——一个面向远程团队的实时团队回顾工具,4 周内从创意到 MVP 交付。
|
||||
|
||||
## Details
|
||||
- **目标用户**:远程团队(5-20 人),包括工程经理和 Scrum Master
|
||||
- **核心功能**:用户注册、创建回顾板、添加卡片、投票、行动项
|
||||
- **技术栈**:React + TypeScript + Tailwind(前端),Node.js + Express + PostgreSQL + Socket.io(后端)
|
||||
- **部署**:Vercel(前端)+ Railway(后端)
|
||||
- **竞争对手**:EasyRetro、Retrium、Parabol
|
||||
|
||||
## Aliases
|
||||
- RetroBoard
|
||||
|
||||
## Sources
|
||||
- [[workflow-startup-mvp]]
|
||||
20
wiki/entities/Sprint-Prioritizer.md
Normal file
20
wiki/entities/Sprint-Prioritizer.md
Normal file
@@ -0,0 +1,20 @@
|
||||
---
|
||||
title: "Sprint Prioritizer"
|
||||
type: entity
|
||||
sources: [workflow-startup-mvp]
|
||||
last_updated: 2026-04-25
|
||||
---
|
||||
|
||||
## Definition
|
||||
Sprint Prioritizer 是 [[workflow-startup-mvp]] 中的第一个 Agent 角色,负责将项目拆解为可执行的周级冲刺计划。
|
||||
|
||||
## Details
|
||||
- **输入**:项目名称、目标、时间线、核心功能、约束条件
|
||||
- **输出**:4 周每周一个有明确交付物和验收标准的冲刺计划
|
||||
- **执行时机**:Week 1 第一步,可与 UX Researcher 并行激活
|
||||
|
||||
## Aliases
|
||||
- Sprint Prioritizer
|
||||
|
||||
## Sources
|
||||
- [[workflow-startup-mvp]]
|
||||
37
wiki/entities/UI-Designer.md
Normal file
37
wiki/entities/UI-Designer.md
Normal file
@@ -0,0 +1,37 @@
|
||||
---
|
||||
title: "UI Designer"
|
||||
type: entity
|
||||
entity_type: Agent Role
|
||||
tags: [ui-design, visual-design, landing-page, the-agency]
|
||||
last_updated: 2026-04-25
|
||||
---
|
||||
|
||||
## Role
|
||||
|
||||
The Agency Design 部门的视觉界面设计专家 Agent,负责为 SaaS 产品 landing page 设计布局、配色、字体和组件规格。
|
||||
|
||||
## In [[workflow-landing-page]]
|
||||
|
||||
UI Designer 在上午 9:00 与 Content Creator 并行启动([[Parallel-Kickoff]]),为 FlowSync(API 集成平台)设计完整的视觉规范:
|
||||
|
||||
- **风格参考**:Linear / Vercel 美学,支持深色模式
|
||||
- **交付物结构**:
|
||||
1. Layout Wireframe(版块顺序和间距)
|
||||
2. Color Palette(主色/辅色/强调色/背景色)
|
||||
3. Typography(字体配对、标题和正文尺寸)
|
||||
4. Component Specs(Hero区/功能卡片/定价表/CTA按钮规格)
|
||||
5. Responsive Breakpoints(Mobile/Tablet/Desktop)
|
||||
|
||||
## Relationship with Other Agents
|
||||
|
||||
- **并行搭档**:[[Content-Creator]](两者在 [[workflow-landing-page]] 中并行启动,无依赖)
|
||||
- **下游合并点**:[[Frontend-Developer]] 等待 UI Designer 交付完整设计规范后开始构建([[Merge-Point]])
|
||||
|
||||
## Aliases
|
||||
- Visual Designer
|
||||
- Landing Page Designer
|
||||
- UI Design Specialist
|
||||
|
||||
## Related Agents
|
||||
- [[Content-Creator]]:并行搭档([[workflow-landing-page]])
|
||||
- [[Frontend-Developer]]:下游合并点([[workflow-landing-page]])
|
||||
20
wiki/entities/UX-Researcher.md
Normal file
20
wiki/entities/UX-Researcher.md
Normal file
@@ -0,0 +1,20 @@
|
||||
---
|
||||
title: "UX Researcher"
|
||||
type: entity
|
||||
sources: [workflow-startup-mvp]
|
||||
last_updated: 2026-04-25
|
||||
---
|
||||
|
||||
## Definition
|
||||
UX Researcher 是 [[workflow-startup-mvp]] 中负责快速用户调研和竞品分析的 Agent 角色,帮助识别产品的差异化方向。
|
||||
|
||||
## Details
|
||||
- **输入**:目标用户画像、竞品列表
|
||||
- **输出**:1 页调研简报,包含:竞品标配功能、竞品短板、可差异化方向
|
||||
- **执行时机**:Week 1 第二步,与 Sprint Prioritizer 并行激活
|
||||
|
||||
## Aliases
|
||||
- UX Researcher
|
||||
|
||||
## Sources
|
||||
- [[workflow-startup-mvp]]
|
||||
Reference in New Issue
Block a user