hackathon-scope-cutter

Reduce a hackathon project feature set to a shippable MVP within the time limit while preserving demo impact.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "hackathon-scope-cutter" with this command: npx skills add bernieweb3/hackathon-ai-devkit/bernieweb3-hackathon-ai-devkit-hackathon-scope-cutter

hackathon-scope-cutter

Goal

Reduce a project's feature set to the minimum viable product (MVP) that can be shipped within the hackathon time limit while preserving demo impact.


Trigger Conditions

Use this skill when:

  • A top idea has been selected and confirmed by hackathon-idea-scoring
  • A feature wishlist exists and must be reduced to a shippable set
  • The hackathon duration and team size are known
  • The team is at risk of building too much and shipping nothing
  • Invoked once per project, immediately after idea selection; output is an upstream dependency for planning, implementation, and presentation skills

Inputs

InputTypeRequiredDescription
project_titlestringYesName of the selected project
feature_wishliststring[]YesFull desired feature list
core_mechanismstringYesThe single mechanism the project must demonstrate
hackathon_duration_hoursintegerYesTotal hours available
team_sizeintegerYesNumber of team members
team_skillsstring[]YesTechnologies the team can use effectively
wow_factorstringYesWhat must land for judges to be impressed

Outputs

OutputDescription
mvp_featuresFeatures included in the MVP
deferred_featuresFeatures cut from MVP (post-hackathon backlog)
cut_rationaleWhy each deferred feature was cut
mvp_demo_flowMinimal user journey that demonstrates core value
time_budgetRough hour estimate per MVP feature
scope_riskRemaining risks even after scoping
recommended_skillsSuggested next skills to invoke

Rules

  1. Include a feature in MVP only if it is required to demonstrate core_mechanism or wow_factor.
  2. Default to cutting any feature that cannot be implemented in less than 20% of total time.
  3. Preserve at least one visually compelling UI moment in mvp_demo_flow.
  4. Total time_budget must not exceed 70% of hackathon_duration_hours (reserve 30% for polish and presentation).
  5. Mark features as [FAKE-OK] if they can be simulated or hardcoded for demo purposes.
  6. Do not cut the feature that delivers wow_factor.

Output Format

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>"

Example

Input:

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"

Output:

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"

Context Files

Knowledge Base

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

Playbooks

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

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Web3

hackathon-code-implementer

No summary provided by upstream source.

Repository SourceNeeds Review
Web3

hackathon-wow-detector

No summary provided by upstream source.

Repository SourceNeeds Review
Web3

hackathon-judge-simulator

No summary provided by upstream source.

Repository SourceNeeds Review
Web3

hackathon-doc-writer

No summary provided by upstream source.

Repository SourceNeeds Review