P1 Backend (8 modules, 50+ new API endpoints): - P1-1: Stakeholder management (power-interest matrix) - P1-2: WBS task decomposition (tree structure + AI split) - P1-3: Risk management (register + matrix + AI identify) - P1-4: Requirement pool (MoSCoW + coverage + conflict detect) - P1-5: Change management (submit → evaluate → approve → implement) - P1-6: Health report (6 dimensions + red/yellow/green) - P1-7: Retrospective & knowledge base - P1-8: Multi-model support (6 models + strategy selection) Frontend (9 pages with sidebar navigation): - Project wizard, Kanban, Stakeholders, WBS, Risks, Requirements, Changes, Health, Retrospective Feishu integration: - WebSocket long-connection for receiving messages - Card button callback with decision tracking - 11 chat commands for P0+P1 features Tech: TypeScript, React 18, Arco Design, Hono, @larksuiteoapi/node-sdk
1.2 KiB
1.2 KiB
P1 开发计划
Issue 拆分(按依赖顺序)
| # | Issue | 依赖 | 优先级 | 描述 |
|---|---|---|---|---|
| P1-1 | 干系人管理模块 | P0模型 | A | 权力-利益矩阵+参与策略推荐API |
| P1-2 | WBS任务拆解 | P0模型 | A | 树形结构+AI辅助拆解 |
| P1-3 | 风险管理 | P0模型 | A | 风险登记册+评估+应对策略 |
| P1-4 | 需求池管理 | P0模型 | A | MoSCoW+用户故事+冲突检测 |
| P1-5 | 变更管理 | P1-2 | B | 变更请求→评估→审批→执行 |
| P1-6 | 项目健康度报告 | P1-2,P1-3 | B | AI周报+红黄绿灯+趋势 |
| P1-7 | 复盘与知识沉淀 | P1-6 | C | 项目收尾复盘+知识归档 |
| P1-8 | 多模型支持 | 无 | B | 多模型路由+成本统计 |
执行策略
- P1-1/2/3/4 无互相依赖,可并行开发
- P1-5 依赖 WBS(P1-2),P1-6 依赖 WBS+风险,P1-7 依赖报告
- P1-8 独立,随时可做
技术规范
- 数据层:先用内存 Map/JSON(和 P0 一致),后续再迁 DB
- API:REST,Hono 路由,挂载到 main.ts
- 飞书通知:复用现有 feishu.ts 的发送能力
- 前端:暂不做,P1 先出后端 API + 飞书卡片交互