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:
159
skills/.playbooks/phase-3-build.md
Normal file
159
skills/.playbooks/phase-3-build.md
Normal file
@@ -0,0 +1,159 @@
|
||||
# Phase 3: Build Playbook
|
||||
|
||||
> 构建阶段 - 功能开发、代码实现、迭代开发
|
||||
|
||||
---
|
||||
|
||||
## 阶段目标
|
||||
|
||||
实现所有计划功能,通过 Dev↔QA 循环确保质量,完成代码集成。
|
||||
|
||||
## 输入文档
|
||||
|
||||
从 Phase 2 接收:
|
||||
1. System Architecture Document
|
||||
2. Sprint Plan
|
||||
3. Design System Spec
|
||||
4. Security Review Report
|
||||
5. Risk Register
|
||||
|
||||
## 激活 Agents
|
||||
|
||||
| Agent | 角色 | 优先级 |
|
||||
|-------|------|--------|
|
||||
| **Senior Developer** | 核心功能实现 | 立即 |
|
||||
| **Frontend Developer** | UI 组件开发 | 立即 |
|
||||
| **Backend Architect** | API 实现 | 立即 |
|
||||
| **AI Engineer** | AI 功能集成 | 按需 |
|
||||
| **Reality Checker** | QA 验证 | 每任务完成时 |
|
||||
| **Evidence Collector** | 测试证据收集 | QA 时 |
|
||||
|
||||
## Dev↔QA 循环协议
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────────────────────┐
|
||||
│ Dev↔QA 循环 │
|
||||
├─────────────────────────────────────────────────────────────┤
|
||||
│ │
|
||||
│ ┌─────────────┐ │
|
||||
│ │ Task Start │ │
|
||||
│ └──────┬──────┘ │
|
||||
│ │ │
|
||||
│ ▼ │
|
||||
│ ┌─────────────┐ │
|
||||
│ │ Developer │ ──── 实现功能 ────┐ │
|
||||
│ │ Implements │ │ │
|
||||
│ └─────────────┘ │ │
|
||||
│ ▲ ▼ │
|
||||
│ │ ┌─────────────┐ │
|
||||
│ │ │ Reality │ │
|
||||
│ │ │ Checker │ │
|
||||
│ │ │ QA Review │ │
|
||||
│ │ └──────┬──────┘ │
|
||||
│ │ │ │
|
||||
│ │ ┌──────────┴──────────┐ │
|
||||
│ │ │ │ │
|
||||
│ │ PASS │ │ FAIL │
|
||||
│ │ ▼ ▼ │
|
||||
│ │ ┌─────────────┐ ┌─────────────┐ │
|
||||
│ │ │ Task Done │ │ Retry < 3? │ │
|
||||
│ │ │ Next Task │ └──────┬──────┘ │
|
||||
│ │ └─────────────┘ │ │
|
||||
│ │ YES ─────┘ │
|
||||
│ │ │ │
|
||||
│ └──────────────────────────┘ │
|
||||
│ │ │
|
||||
│ ▼ NO │
|
||||
│ ┌─────────────┐ │
|
||||
│ │ ESCALATE │ → 重新分配/拆分/推迟 │
|
||||
│ └─────────────┘ │
|
||||
│ │
|
||||
└─────────────────────────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
## 关键活动
|
||||
|
||||
### 1. Sprint 执行 (每个 Sprint)
|
||||
|
||||
**每日流程**:
|
||||
1. **Morning**: 检查 overnight 测试结果
|
||||
2. **Development**: 实现 Sprint backlog 中的任务
|
||||
3. **QA**: 完成的任务提交 Reality Checker
|
||||
4. **Evening**: 更新进度,处理阻塞
|
||||
|
||||
**任务状态追踪**:
|
||||
```markdown
|
||||
## Sprint N Progress
|
||||
|
||||
### In Progress
|
||||
| Task | Developer | Started | Status |
|
||||
|------|-----------|---------|--------|
|
||||
| [ID] | [Agent] | [Date] | [状态] |
|
||||
|
||||
### QA Pending
|
||||
| Task | Developer | QA Agent | Attempt |
|
||||
|------|-----------|----------|---------|
|
||||
| [ID] | [Agent] | [Agent] | [N]/3 |
|
||||
|
||||
### Completed This Sprint
|
||||
| Task | Developer | QA Agent | Attempts | Date |
|
||||
|------|-----------|----------|----------|------|
|
||||
|
||||
### Blocked
|
||||
| Task | Blocker | Impact | Resolution |
|
||||
|------|---------|--------|------------|
|
||||
```
|
||||
|
||||
### 2. 代码审查标准
|
||||
|
||||
**Reality Checker 检查清单**:
|
||||
- [ ] 功能与验收标准完全匹配
|
||||
- [ ] 代码遵循项目风格指南
|
||||
- [ ] 测试覆盖率 ≥ 80%
|
||||
- [ ] 无安全漏洞
|
||||
- [ ] 性能符合标准
|
||||
- [ ] 无障碍要求满足
|
||||
- [ ] 文档完整
|
||||
|
||||
### 3. 集成协议
|
||||
|
||||
**每次代码合并**:
|
||||
1. 运行完整测试套件
|
||||
2. 通过 Reality Checker 验证
|
||||
3. 更新 CHANGELOG
|
||||
4. 通知相关 Agents
|
||||
|
||||
## 质量门禁
|
||||
|
||||
每个 Sprint 结束时检查:
|
||||
|
||||
| # | 标准 | 阈值 | 验证方法 |
|
||||
|---|------|------|----------|
|
||||
| 1 | Sprint 目标完成 | 100% | 任务追踪 |
|
||||
| 2 | 首次通过率 | ≥ 70% | QA 统计 |
|
||||
| 3 | 测试覆盖率 | ≥ 80% | 覆盖率报告 |
|
||||
| 4 | 无 P0/P1 问题 | 0 | Issue 追踪 |
|
||||
| 5 | 文档更新 | 100% | 文档审查 |
|
||||
|
||||
## 交接文档
|
||||
|
||||
阶段结束时交接给 Phase 4:
|
||||
1. 完整的代码库
|
||||
2. 测试报告和覆盖率
|
||||
3. 已知问题列表
|
||||
4. 技术债务记录
|
||||
5. 部署检查清单
|
||||
|
||||
## 常见问题处理
|
||||
|
||||
| 问题 | 处理方式 |
|
||||
|------|----------|
|
||||
| 任务超时 | 评估复杂度,考虑拆分 |
|
||||
| QA 连续失败 | 升级,考虑重新分配 |
|
||||
| 依赖阻塞 | 标记阻塞,通知依赖方 |
|
||||
| 技术债务 | 记录,安排后续 Sprint |
|
||||
|
||||
---
|
||||
|
||||
**预计时间**: 2-4 周 (根据项目规模)
|
||||
**下一阶段**: Phase 4 - Hardening
|
||||
Reference in New Issue
Block a user