biruk741

refine

Finalize and lock the hackathon project idea after brainstorming, mockups, and feasibility assessment. Produces the definitive IDEA-FINAL.md that all subsequent phases reference. Use when the team is ready to commit to the final idea, after feasibility has been assessed, or when someone says "let's lock this in", "finalize the idea", or "we're going with this".

biruk741 0 Updated 3mo ago
GitHub

Install

npx skillscat add biruk741/cc-plugins/refine

Install via the SkillsCat registry.

SKILL.md

Idea Refinement & Lock Skill

Read .hackathon/STATE.md, .hackathon/IDEA.md, .hackathon/FEASIBILITY.md, and .hackathon/DEMO-SCRIPT.md.

Hard gate: IDEA.md must exist. Soft gate: feasibility should be complete.

Process

Step 1: Consolidation

Synthesize everything learned from ideation, mockups, and feasibility into one clean document. Resolve any contradictions (e.g., feasibility said to cut feature X, but IDEA.md still lists it).

Step 2: Final Decisions

Walk the team through any open questions from IDEA.md and FEASIBILITY.md. Every "open question" must be resolved or explicitly deferred (with a note on when to decide).

Step 3: Write IDEA-FINAL.md

This is the definitive document. It includes:

---
owner: [team lead / pm]
status: locked
created-at: [timestamp]
last-modified: [timestamp]
locked-by: "phase-4-refine"
unlock-requires: "team consensus via /hackathon-pilot:unlock"
phase: refine
---

# [Project Name] — Final Specification

## Problem Statement
[Clear, concise problem definition]

## Target User
[Specific user persona]

## Solution
[Definitive description of what we're building]

## MVP Features (Locked)
1. [Feature] — [one-line description]
2. [Feature] — [one-line description]
3. [Feature] — [one-line description]

## Stretch Goals (Ordered by Priority)
1. [Feature] — [one-line description]
2. [Feature] — [one-line description]

## AI Integration
- Model: [which AI model/API]
- Purpose: [what it does]
- Integration point: [where in the product]

## Demo Flow (Locked v1)
[The demo beats — this becomes the north star]

## Connected Metric
[Hackathon requirement: which metric and how]

## Technical Constraints
[Anything non-negotiable: must be JS, must run on X, etc.]

## Out of Scope
[Explicitly listed so nobody wastes time on these]

Step 4: Lock IDEA.md

Set IDEA.md status to locked in its frontmatter. It's now a historical document.

Step 5: Update Demo Script

Update DEMO-SCRIPT.md to reflect the final, locked feature set. This is now v1.0 of the demo script.

Output

  • .hackathon/IDEA-FINAL.md (status: locked)
  • Updated .hackathon/IDEA.md (status: locked, historical)
  • Updated .hackathon/DEMO-SCRIPT.md (v1.0)
  • Update STATE.md: refine complete, advance phase
  • Log to changelog and decisions