!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys review_mode,automation,workflow

Resolved above, use as-is; --review overrides review_mode for this run. No block → defaults in .claude/docs/config-resolution.md.

Prototype

Purpose

This is the concept prototype, a fast, throwaway build that answers one question: "Is this core idea actually fun to interact with?"

Default use, run right after /brainstorm and /setup-engine, before writing GDDs or architecture docs. Its verdict determines whether the concept is worth the investment of full design documentation.

Mid-production? You can also run this at any stage to test a specific mechanic, design change, or technical question. Pass --spike to activate spike mode: a lightweight ~4-hour build with no GDD prerequisites and no phase gate implications.

Already have GDDs and architecture complete? To validate the full game loop before committing to Production, run /vertical-slice instead.

---

Phase 1: Define the Question

Read references/1-question.md now and follow it, this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.

Phase 2: Load Concept Context

Read references/2-load-context.md now and follow it, this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.

Phase 3: Choose the Prototype Path

Read references/3-choose-path.md now and follow it, this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.

Phase 4: Plan the Prototype

Read references/4-plan.md now and follow it, this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.

Phase 5: Implement