Indie Game Dev OS – Scope Control & Shipping System

Project Diagnosis

Current State: Prototype (leaning toward Stalled)
Time alive: 7 months
Team: Solo

Core Fantasy: Feeling like a damaged mind piecing itself back together through skillful short-term memory manipulation in hostile data spaces.

Honest Assessment
The unique hook (memory replay) is still not delivering fun. The rest of the game is currently a fairly standard top-down roguelike. At 7 months with only one enemy type and no strong sense of identity or progression, this project is in the danger zone. Scope has been expanding sideways instead of deepening the core fantasy.

Highest-leverage next move
Stop adding systems. Force a clear decision on the memory mechanic within the next 10–14 days.

---

Scope Intervention

Apply the Three Questions to the memory replay system:

1. Does it serve the core fantasy? → Yes
2. Can we ship a good version with current resources? → Currently no
3. What happens if we cut it completely? → Game becomes generic

Verdict: Do not cut it yet — but put it on probation.

Immediate cuts / deferrals:

• Meta-progression systems
• Multiple biomes
• Complex enemy roster
• Narrative fragments / lore
• Advanced procedural features

---

Vertical Slice Definition (Next 2–3 weeks)

Build one short, honest vertical slice (target 6–8 minutes) that answers:

“Does the memory replay mechanic create interesting decisions and a feeling of cleverness?”

Must include

• 1 complete short run segment
• Memory mechanic in its best current form
• 2–3 enemy behaviors that specifically interact with memory
• Basic juice (screen shake + one sound)
• Clear success/failure state

Everything else is out of scope for this slice.

---

Decision Deadline

Set a hard date 14 days from now. On that day, play the slice and answer only one question:

Is the memory mechanic fun enough to build the entire game around?

• Yes → Lock it and build outward carefully
• No → Simplify it radically or replace it. Do not keep polishing a weak hook.

---

Next steps I recommend right now:

1. Write the explicit “Won’t-have (this version)” list
2. Define the exact success criteria for the vertical slice
3. Block 10 focused days with zero new feature work

Would you like me to generate the full cut list and vertical slice brief next?