hackathon-scope-cutter

hackathon-scope-cutter

目标

将项目的功能集精简至最小可行产品（MVP），确保能在黑客松时间限制内交付，同时保留演示效果。

---

触发条件

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

• 已通过 hackathon-idea-scoring 选定并确认首选创意
• 已有功能愿望清单，需要缩减为可交付的功能集
• 已知黑客松时长和团队规模
• 团队有过度开发、最终一无所成的风险
• 每个项目调用一次，紧接创意选择之后；输出是规划、实现和演示技能的上游依赖

---

输入

输入	类型	必填	描述
project_title	string	是	所选项目的名称
feature_wishlist	string[]	是	完整的期望功能列表
core_mechanism	string	是	项目必须展示的单一机制
hackathon_duration_hours	integer	是	可用总时长
team_size	integer	是	团队成员人数
team_skills	string[]	是	团队能够熟练使用的技术
wow_factor	string	是	必须实现的、能令评委印象深刻的内容

---

输出

输出	描述
mvp_features	纳入 MVP 的功能
deferred_features	从 MVP 中删减的功能（黑客松后的待办事项）
cut_rationale	每个延期功能被删减的原因
mvp_demo_flow	展示核心价值的最简用户流程
time_budget	每项 MVP 功能的大致工时估算
scope_risk	缩减范围后仍存在的风险
recommended_skills	建议接下来调用的技能

---

规则

1. 仅当某项功能是展示 core_mechanism 或 wow_factor 所必需时，才将其纳入 MVP。
2. 默认删减任何实施时间达到总时长 20% 或以上的功能。
3. 在 mvp_demo_flow 中至少保留一个视觉上引人注目的 UI 时刻。
4. time_budget 总计不得超过 hackathon_duration_hours 的 70%（预留 30% 用于润色和演示）。
5. 如果功能可以通过模拟或硬编码用于演示，将其标记为 [FAKE-OK]。
6. 不要删减带来 wow_factor 的功能。

---

输出格式

mvp_features:
  - feature: "<name>"
    purpose: "<why it's essential>"
    fake_ok: <true|false>

deferred_features:
  - feature: "<name>"
    cut_rationale: "<reason>"

mvp_demo_flow:
  - step: <number>
    action: "<user action>"
    outcome: "<visible result>"

time_budget:
  - feature: "<name>"
    estimated_hours: <number>

scope_risk:
  - "<risk>"

recommended_skills:
  - "<skill-name>"

---

示例

输入：

project_title: "AnchorAI"
feature_wishlist:
  - "User authentication and profiles"
  - "GPT-4 emotional check-in conversation"
  - "Session memory (recall past conversations)"
  - "Mood trend dashboard"
  - "Push notifications for daily check-ins"
  - "Crisis escalation to hotline resources"
  - "Onboarding quiz to personalize tone"
core_mechanism: "GPT-4 conversation with persistent emotional context memory"
hackathon_duration_hours: 24
team_size: 3
team_skills: ["Python", "React", "OpenAI API"]
wow_factor: "AI recalls emotional context from past sessions and adapts tone in real time"

输出：

mvp_features:
  - feature: "GPT-4 emotional check-in conversation"
    purpose: "Core mechanism — must ship"
    fake_ok: false
  - feature: "Session memory (recall past conversations)"
    purpose: "Delivers the wow factor"
    fake_ok: false
  - feature: "Crisis escalation to hotline resources"
    purpose: "Safety requirement visible to judges"
    fake_ok: true

deferred_features:
  - feature: "User authentication and profiles"
    cut_rationale: "3–4h cost; demo uses single hardcoded session"
  - feature: "Mood trend dashboard"
    cut_rationale: "Not in demo flow; 4h cost"
  - feature: "Push notifications"
    cut_rationale: "Backend complexity; irrelevant to live demo"
  - feature: "Onboarding quiz"
    cut_rationale: "Can be mocked with pre-set tone for demo"

mvp_demo_flow:
  - step: 1
    action: "User opens app and types: 'I'm feeling really overwhelmed today'"
    outcome: "AI responds empathetically with personalized opening"
  - step: 2
    action: "User describes a recurring work stress"
    outcome: "AI references last week's similar conversation from memory"
  - step: 3
    action: "User expresses hopelessness"
    outcome: "AI surfaces crisis resource card gracefully"

time_budget:
  - feature: "GPT-4 check-in conversation"
    estimated_hours: 4
  - feature: "Session memory"
    estimated_hours: 5
  - feature: "Crisis escalation (mocked)"
    estimated_hours: 1

scope_risk:
  - "Memory retrieval latency may degrade demo experience on slow networks"

recommended_skills:
  - "hackathon-task-planner"
  - "hackathon-wow-detector"

---

上下文文件

知识库

• ../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/knowledge/hackathon-demo-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