hackathon-milestone-monitor

hackathon-milestone-monitor

目标

根据计划的里程碑时间表评估当前项目进度，识别进度延误或风险，并推荐具体的后续行动，确保演示在评审开始前准备就绪。

---

触发条件

在以下情况下使用此技能：

• 到了里程碑检查时间（已完成黑客马拉松时间的 25%、50%、75% 或 90%）
• 团队不确定项目是否按计划推进
• 某项任务的实际耗时显著超出预算
• 发生范围变更，需要重新评估计划
• 在第 5 阶段（构建）期间的每个里程碑节点调用；只要关键路径受到威胁，随时再次调用

---

输入

输入	类型	必填	描述
project_title	string	是	项目名称
hackathon_duration_hours	integer	是	黑客马拉松的总时长（小时）
elapsed_hours	number	是	黑客马拉松开始后已过去的小时数
milestones	object[]	是	来自 hackathon-task-planner 的里程碑计划
tasks	object[]	是	来自 hackathon-task-planner 的完整任务列表
completed_tasks	string[]	是	标记为已完成的任务 ID（例如 ["T-01", "T-02"]）
blocked_tasks	object[]	否	当前受阻的任务及原因
scope_changes	string[]	否	规划后添加或移除的任何功能

---

输出

输出	描述
progress_report	已完成工作、剩余工作和整体状态的摘要
current_phase	项目当前所处的工作流阶段
milestone_status	每个里程碑的计划完成状态与实际完成状态
critical_path_health	关键路径是否按计划推进、存在风险或已中断
recommended_actions	立即采取的优先行动
scope_recommendations	如果进度落后，应删减或推迟的功能
recommended_skills	建议接下来调用的技能

---

规则

1. 将 percent_complete 计算为 completed_tasks / total_tasks × 100。
2. 将 percent_time_used 计算为 elapsed_hours / hackathon_duration_hours × 100。
3. 如果 percent_complete < percent_time_used - 15，将状态标记为 behind。
4. 如果 percent_complete > percent_time_used，将状态标记为 ahead。
5. 否则，将状态标记为 on_track。
6. 关键路径上的任何受阻任务都必须生成一条 critical 级别的建议行动。
7. 如果 percent_time_used > 75 且演示流程尚未端到端连通，应立即建议删减范围。
8. scope_recommendations 只能删减标记为 [FAKE-OK] 的不可实现功能以外的功能，且不得删减吸睛功能。

---

输出格式

progress_report:
  completed_tasks: <number>
  total_tasks: <number>
  percent_complete: <number>
  percent_time_used: <number>
  status: "<on_track|behind|ahead|critical>"
  summary: "<one-sentence assessment>"

current_phase: "<Phase name and number>"

milestone_status:
  - name: "<milestone name>"
    target_hour: <number>
    actual_hour: "<number or 'not yet reached'>"
    status: "<completed|on_track|at_risk|missed>"
    notes: "<context>"

critical_path_health:
  status: "<healthy|at_risk|broken>"
  bottleneck_task: "<T-XX or null>"
  description: "<what is slowing the critical path>"

recommended_actions:
  - priority: <number>
    urgency: "<immediate|this_hour|today>"
    action: "<what to do>"
    rationale: "<why this matters now>"

scope_recommendations:
  - feature: "<feature name>"
    recommendation: "<cut|defer|simplify>"
    time_saved_hours: <number>
    rationale: "<why this can be safely cut>"

recommended_skills:
  - "<skill-name>"

---

示例

输入：

project_title: "AnchorAI"
hackathon_duration_hours: 24
elapsed_hours: 14
milestones:
  - name: "Backend skeleton live"
    target_hour: 7
  - name: "Frontend connected"
    target_hour: 11
  - name: "Memory working"
    target_hour: 16
  - name: "Demo-ready"
    target_hour: 19
tasks:
  - id: "T-01"
    title: "Set up FastAPI and Supabase"
  - id: "T-02"
    title: "Implement OpenAI chat endpoint"
  - id: "T-03"
    title: "Implement session memory"
  - id: "T-04"
    title: "Build chat UI component"
  - id: "T-05"
    title: "Wire frontend to API"
  - id: "T-06"
    title: "Add crisis card (mocked)"
completed_tasks: ["T-01", "T-02", "T-04"]
blocked_tasks:
  - id: "T-03"
    reason: "Supabase cold-start issue unresolved; falling back to Redis"

输出：

progress_report:
  completed_tasks: 3
  total_tasks: 6
  percent_complete: 50
  percent_time_used: 58
  status: "behind"
  summary: "3 of 6 tasks done at 58% time used; session memory is blocked and the demo flow is not yet connected."

current_phase: "Phase 5 — Implementation"

milestone_status:
  - name: "Backend skeleton live"
    target_hour: 7
    actual_hour: 8
    status: "completed"
    notes: "Completed 1 hour late due to Supabase setup delay"
  - name: "Frontend connected"
    target_hour: 11
    actual_hour: "not yet reached"
    status: "at_risk"
    notes: "T-05 (wire frontend) is blocked on T-03 (session memory); UI is built but not connected"
  - name: "Memory working"
    target_hour: 16
    actual_hour: "not yet reached"
    status: "at_risk"
    notes: "T-03 is blocked; 2 hours remain before this milestone"
  - name: "Demo-ready"
    target_hour: 19
    actual_hour: "not yet reached"
    status: "at_risk"
    notes: "Only 5 hours to complete T-03, T-05, T-06 and run full demo flow"

critical_path_health:
  status: "at_risk"
  bottleneck_task: "T-03"
  description: "Session memory (T-03) is blocked; it gates T-05 (frontend wiring) which gates demo-readiness"

recommended_actions:
  - priority: 1
    urgency: "immediate"
    action: "Abandon Supabase for session memory; switch to Redis in-memory fallback — saves 1–2 hours"
    rationale: "T-03 has been blocked for >1 hour; Redis fallback was planned in risk analysis"
  - priority: 2
    urgency: "this_hour"
    action: "Start T-05 (frontend wiring) using a hardcoded stub memory response while T-03 is resolved"
    rationale: "Decouples frontend progress from memory implementation; demo flow can proceed in parallel"
  - priority: 3
    urgency: "today"
    action: "Run full demo flow end-to-end by H+16 even if memory is mocked — freeze demo path first"
    rationale: "Demo-readiness milestone at H+19 requires 3 clean end-to-end runs"

scope_recommendations:
  - feature: "Mood trend dashboard"
    recommendation: "cut"
    time_saved_hours: 3
    rationale: "Not in MVP demo flow; team is behind schedule; dashboard was already deferred"

recommended_skills:
  - "hackathon-code-implementer"
  - "hackathon-deployment-prep"

---

上下文文件

知识库

• ../hackathon-shared-resources/knowledge/hackathon-mvp-strategy.md
• ../hackathon-shared-resources/knowledge/hackathon-common-failures.md
• ../hackathon-shared-resources/knowledge/hackathon-winning-patterns.md

操作手册

• ../hackathon-shared-resources/playbooks/hackathon-workflow.md
• ../hackathon-shared-resources/playbooks/24h-hackathon-playbook.md
• ../hackathon-shared-resources/playbooks/36h-hackathon-playbook.md
• ../hackathon-shared-resources/playbooks/48h-hackathon-playbook.md