feat(skills): complete multi-agent collaboration framework
## Skills Ecosystem (60+ Skills) - Engineering: 7 skills (ai-engineer, backend-architect, etc.) - Testing: 8 skills (reality-checker, evidence-collector, etc.) - Support: 6 skills (support-responder, analytics-reporter, etc.) - Design: 7 skills (ux-architect, brand-guardian, etc.) - Product: 3 skills (sprint-prioritizer, trend-researcher, etc.) - Marketing: 4+ skills (growth-hacker, content-creator, etc.) - PM: 5 skills (studio-producer, project-shepherd, etc.) - Spatial: 6 skills (visionos-spatial-engineer, etc.) - Specialized: 6 skills (agents-orchestrator, etc.) ## Collaboration Framework - Coordination protocols (handoff-templates, agent-activation) - 7-phase playbooks (Discovery → Operate) - Standardized skill template for consistency ## Quality Improvements - Each skill now includes: Identity, Mission, Workflow, Deliverable Format - Collaboration triggers define when to invoke other agents - Success metrics provide measurable quality standards Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
123
skills/.playbooks/phase-0-discovery.md
Normal file
123
skills/.playbooks/phase-0-discovery.md
Normal file
@@ -0,0 +1,123 @@
|
||||
# Phase 0: Discovery Playbook
|
||||
|
||||
> 项目发现阶段 - 理解需求、定义范围、建立基础
|
||||
|
||||
---
|
||||
|
||||
## 阶段目标
|
||||
|
||||
深入理解用户需求,定义项目范围,建立技术和业务基础。
|
||||
|
||||
## 激活 Agents
|
||||
|
||||
| Agent | 角色 | 优先级 |
|
||||
|-------|------|--------|
|
||||
| **UX Researcher** | 用户研究、需求收集 | 立即 |
|
||||
| **Trend Researcher** | 市场趋势、竞争分析 | 立即 |
|
||||
| **UX Architect** | 信息架构、技术基础 | Day 2 |
|
||||
| **Brand Guardian** | 品牌识别定义 | Day 2 |
|
||||
|
||||
## 关键活动
|
||||
|
||||
### 1. 需求收集 (Day 1-2)
|
||||
|
||||
**UX Researcher 执行**:
|
||||
- 用户访谈和调研
|
||||
- 痛点识别
|
||||
- 用户旅程映射
|
||||
- 成功指标定义
|
||||
|
||||
**交付物**:
|
||||
```markdown
|
||||
## User Research Report
|
||||
|
||||
### Target Users
|
||||
- [用户画像 1]
|
||||
- [用户画像 2]
|
||||
|
||||
### Pain Points
|
||||
1. [痛点 1] - 严重程度: [High/Med/Low]
|
||||
2. [痛点 2] - 严重程度: [High/Med/Low]
|
||||
|
||||
### User Journey
|
||||
[用户旅程图]
|
||||
|
||||
### Success Metrics
|
||||
- [指标 1]: [目标值]
|
||||
- [指标 2]: [目标值]
|
||||
```
|
||||
|
||||
### 2. 市场分析 (Day 1-2)
|
||||
|
||||
**Trend Researcher 执行**:
|
||||
- 竞品分析
|
||||
- 市场趋势研究
|
||||
- 差异化机会识别
|
||||
- 技术可行性评估
|
||||
|
||||
**交付物**:
|
||||
```markdown
|
||||
## Market Analysis Report
|
||||
|
||||
### Competitive Landscape
|
||||
| 竞品 | 优势 | 劣势 | 我们的差异化 |
|
||||
|------|------|------|-------------|
|
||||
|
||||
### Market Trends
|
||||
- [趋势 1]: [影响分析]
|
||||
- [趋势 2]: [影响分析]
|
||||
|
||||
### Opportunity Assessment
|
||||
- 高价值机会: [描述]
|
||||
- 技术可行性: [评估]
|
||||
```
|
||||
|
||||
### 3. 信息架构 (Day 2-3)
|
||||
|
||||
**UX Architect 执行**:
|
||||
- 内容层级定义
|
||||
- 导航结构设计
|
||||
- 响应式策略规划
|
||||
- 无障碍基础建立
|
||||
|
||||
### 4. 品牌定义 (Day 2-3)
|
||||
|
||||
**Brand Guardian 执行**:
|
||||
- 品牌基础(愿景、使命、价值观)
|
||||
- 视觉识别系统
|
||||
- 品牌声音指南
|
||||
- 颜色和排版系统
|
||||
|
||||
## 阶段门禁
|
||||
|
||||
进入 Phase 1 前必须满足:
|
||||
|
||||
| # | 标准 | 阈值 | 验证方法 |
|
||||
|---|------|------|----------|
|
||||
| 1 | 用户研究完成 | 100% | 交付物审查 |
|
||||
| 2 | 市场分析完成 | 100% | 交付物审查 |
|
||||
| 3 | 信息架构定义 | 100% | 交付物审查 |
|
||||
| 4 | 品牌基础定义 | 100% | 交付物审查 |
|
||||
| 5 | 成功指标量化 | ≥ 3 个指标 | 数值验证 |
|
||||
|
||||
## 交接文档
|
||||
|
||||
阶段结束时交接给 Phase 1:
|
||||
1. User Research Report
|
||||
2. Market Analysis Report
|
||||
3. Information Architecture Spec
|
||||
4. Brand Guidelines
|
||||
5. Success Metrics Definition
|
||||
|
||||
## 常见风险
|
||||
|
||||
| 风险 | 缓解措施 |
|
||||
|------|----------|
|
||||
| 需求不清晰 | 多轮用户验证 |
|
||||
| 范围蔓延 | 严格的 MoSCoW 优先级 |
|
||||
| 品牌不一致 | 早期建立设计系统 |
|
||||
|
||||
---
|
||||
|
||||
**预计时间**: 2-3 天
|
||||
**下一阶段**: Phase 1 - Strategy
|
||||
Reference in New Issue
Block a user