## 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>
2.9 KiB
2.9 KiB
Phase 1: Strategy Playbook
策略阶段 - 定义解决方案架构和实施计划
阶段目标
基于 Discovery 阶段的发现,制定技术策略、架构设计和实施计划。
输入文档
从 Phase 0 接收:
- User Research Report
- Market Analysis Report
- Information Architecture Spec
- Brand Guidelines
- Success Metrics Definition
激活 Agents
| Agent | 角色 | 优先级 |
|---|---|---|
| Backend Architect | 系统架构设计 | 立即 |
| Sprint Prioritizer | 任务分解和优先级 | 立即 |
| UX Architect | 设计系统完善 | Day 2 |
| Security Engineer | 安全架构审查 | Day 2 |
关键活动
1. 系统架构设计 (Day 1-3)
Backend Architect 执行:
- 技术栈选型
- 数据库 schema 设计
- API 端点规划
- 微服务/单体架构决策
- 扩展性考虑
交付物:
## System Architecture Document
### Technology Stack
- Frontend: [技术]
- Backend: [技术]
- Database: [技术]
- Infrastructure: [技术]
### Database Schema
[ER 图或 schema 定义]
### API Endpoints
| 端点 | 方法 | 描述 | 认证 |
|------|------|------|------|
### Architecture Diagram
[系统架构图]
### Scalability Considerations
- 水平扩展: [策略]
- 缓存策略: [描述]
- CDN 配置: [描述]
2. 任务分解 (Day 2-4)
Sprint Prioritizer 执行:
- 将功能分解为用户故事
- RICE 评分和优先级排序
- Sprint 规划
- 依赖关系映射
交付物:
## Sprint Plan
### Backlog (RICE Scored)
| # | 任务 | R | I | C | E | Score | Sprint |
|---|------|---|---|---|---|-------|--------|
### Sprint Allocation
- Sprint 1: [任务列表]
- Sprint 2: [任务列表]
- Sprint 3: [任务列表]
### Dependencies
[依赖关系图]
### Risk Register
| 风险 | 概率 | 影响 | 缓解措施 |
3. 设计系统 (Day 2-4)
UX Architect + Brand Guardian 协作:
- CSS 变量和 tokens
- 组件库规划
- 响应式断点
- 主题系统(亮/暗)
4. 安全审查 (Day 3-4)
Security Engineer 执行:
- 威胁建模
- 认证/授权方案
- 数据保护策略
- 合规要求检查
阶段门禁
进入 Phase 2 前必须满足:
| # | 标准 | 阈值 | 验证方法 |
|---|---|---|---|
| 1 | 架构文档完成 | 100% | 技术审查 |
| 2 | Sprint 计划完成 | ≥ 2 Sprints | PM 审查 |
| 3 | 设计系统定义 | 核心组件 100% | 设计审查 |
| 4 | 安全审查通过 | 无 Critical 问题 | 安全审查 |
| 5 | 依赖关系明确 | 100% 映射 | 依赖图验证 |
交接文档
阶段结束时交接给 Phase 2:
- System Architecture Document
- Sprint Plan
- Design System Spec
- Security Review Report
- Risk Register
质量标准
- 架构决策有文档化的 ADR (Architecture Decision Records)
- 所有 API 端点有 OpenAPI 规格定义
- 设计系统有可工作的 Storybook
- 安全审查无 P0/P1 问题
预计时间: 3-5 天 下一阶段: Phase 2 - Foundation