Use this skill when the user runs `/sf:concept` to produce the full Game Design Document (GDD) for a slot — theme, narrative, grid, symbols, features, target parameters, and player flow. The second step of the slot-forge pipeline, after `/sf:principles`. Activates on `/sf:concept` or when the user asks to design a new slot's concept/GDD.
Produce concept.md — the full GDD that downstream skills (/sf:math-model, /sf:reels, /sf:features) read to derive paytable, weights, and feature parameters.
Adopt the senior slot game expert persona from ../references/persona.md.
Per ../references/prerequisites.md:
principles.md. If absent, warn but continue — the skill will use industry defaults instead of project-specific conventions.slot-forge.json (locate via env-detection from ../references/environment.md).If principles.md exists, load it and apply: artifact language, ID style, target jurisdictions, max-win cap, RTP precision.
/sf:concept invocation (Rule 5)principles.md if present (sets defaults)../../knowledge/market/themes.md../../knowledge/mechanics/* (paylines, ways, cluster, megaways, cascading, hold-and-spin, etc.)../../knowledge/math/volatility-profiles.md../../knowledge/market/provider-benchmarks.md"Tell me about the slot you want to create — a sentence or two is enough. Theme, target player, what kind of experience should it deliver?"
Extract: theme, grid hint, volatility, signature mechanic, jurisdiction. Acknowledge with one expert observation (e.g. "Egyptian + ways + free spins is a proven combination — Book of Dead, Egyptian Sun, etc. — so the design risk is concentrated in the multiplier curve.").
Strict adherence to ../references/interview-protocol.md. Cover:
../../knowledge/market/themes.md.../../knowledge/mechanics/.principles.md jurisdiction range; otherwise default 94–97% bracket.FeatureType enum so /sf:features can translate directly. Pull from ../../knowledge/mechanics/.Do not exceed 13 questions. Skip any topic the lead-in already covered or that principles.md already fixed.
Generate the symbol table inline (Section 4 of the template) using the roster size and tiering convention from principles.md. Default tiering for a 10-symbol roster:
| Tier | Type | Count | Pay multiplier (5oak) |
|---|---|---|---|
| Premium | regular | 4 | 50–500× |
| Low (royals/letters) | regular | 4 | 5–50× |
| Wild | wild | 1 | matches highest premium |
| Scatter | scatter | 1 | feature trigger |
Adjust counts for grid size and feature mix. Do not invent numeric pays here — /sf:math-model owns paytable values.
Render concept.md from ../references/templates/concept-template.md. Fill all sections; for sections with no user input (art direction, audio, UX), produce reasonable expert defaults but flag them with a one-line note: > Filled with industry defaults — confirm or revise with /sf:revise concept art-direction.
Write to <project-dir>/concept.md. Honour the overwrite-prompt pattern from /sf:principles.
currentPhase: "concept""Drafted concept.md"Use ../references/closing-message.md for /sf:concept → /sf:math-model.
Per ../references/error-handling.md. Specifically:
principles.md conflicts with chosen volatility (e.g. 500× cap with very-high volatility), surface the trade-off and ask which constraint relaxes.A complete concept.md where:
{placeholder} strings remain)roster size rows with id, name, type, tierprinciples.md (no jurisdiction violations)