anbeime/skill / skills/multi-agent-meeting/multi-agent-meeting
multi-agent-meeting
Verified项目管理专家与产品经理在做项目决策、技术评审或商业策略制定时,当需要多视角碰撞以打破思维局限,请用此技能模拟多智能体真实会议辩论,一键生成包含决策结论、核心论据与风险提示的完整会议记录,让复杂决策高效落地!
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.6 KB |
| assets/meeting-templates/customer-insight-analysis.md | markdown | 6.2 KB |
| assets/meeting-templates/product-feature-review.md | markdown | 6.1 KB |
| assets/meeting-templates/product-pricing-strategy.md | markdown | 1.8 KB |
| assets/meeting-templates/project-risk-assessment.md | markdown | 2.0 KB |
| assets/meeting-templates/tech-architecture-decision.md | markdown | 1.8 KB |
| references/agent-roles.md | markdown | 5.6 KB |
| references/meeting-record-format.md | markdown | 7.0 KB |
assets/meeting-templates/tech-architecture-decision.md
View on GitHub# 技术架构决策会议模板
## 会议类型
技术架构决策会议
## 适用场景
- 评估新架构方案(微服务、Serverless、事件驱动等)
- 技术栈选型(编程语言、框架、数据库、中间件)
- 架构重构决策
- 技术方向调整
## 推荐角色组合
### 最小组合(4人)
1. **技术架构师**: 主持技术讨论,从架构角度分析
2. **DevOps工程师**: 评估运维复杂度和成本
3. **前端工程师** 或 **后端工程师**: 根据架构影响选择
4. **CTO**: 战略决策和资源平衡
### 完整组合(6人)
1. **技术架构师**: 系统架构设计
2. **DevOps工程师**: 部署运维
3. **前端工程师**: 用户体验和前端性能
4. **后端工程师**: 业务逻辑和数据设计
5. **安全专家**: 安全和合规评估
6. **CTO**: 战略决策和资源分配
## 典型讨论点
### 技术可行性
- 技术成熟度和稳定性
- 团队技能储备
- 学习曲线和培训成本
- 第三方依赖风险
### 成本效益
- 开发成本(人力、时间)
- 运维成本(基础设施、工具)
- 维护成本(技术债务、升级)
- 收益量化(性能提升、开发效率)
### 风险评估
- 技术风险(实现难度、兼容性)
- 运营风险(稳定性、可维护性)
- 商业风险(延期、超支)
- 缓解措施和备选方案
## 典型决策结果类型
- **采纳**: 完全采用新方案,制定实施计划
- **有条件采纳**: 在满足特定条件下采用
- **试点**: 先小范围验证,成功后推广
- **暂缓**: 延后决策,等待更多数据
- **拒绝**: 不采用,说明理由
## 示例会议主题
- 是否将单体架构改造为微服务架构
- 是否引入Kubernetes进行容器编排
- 是否从MySQL迁移到PostgreSQL
- 是否采用Serverless架构降低成本
- 是否引入GraphQL替代REST API
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |