diff --git a/.claude/skills/asset-audit/SKILL.md b/.claude/skills/asset-audit/SKILL.md index 019fc4e..476ca2b 100644 --- a/.claude/skills/asset-audit/SKILL.md +++ b/.claude/skills/asset-audit/SKILL.md @@ -5,7 +5,7 @@ argument-hint: "[category|all]" user-invocable: true allowed-tools: Read, Glob, Grep context: fork -agent: Explore +# Read-only diagnostic skill — no specialist agent delegation needed --- ## Phase 1: Read Standards diff --git a/.claude/skills/design-review/SKILL.md b/.claude/skills/design-review/SKILL.md index a0ec264..a505d74 100644 --- a/.claude/skills/design-review/SKILL.md +++ b/.claude/skills/design-review/SKILL.md @@ -5,7 +5,7 @@ argument-hint: "[path-to-design-doc]" user-invocable: true allowed-tools: Read, Glob, Grep context: fork -agent: Explore +# Read-only diagnostic skill — no specialist agent delegation needed --- ## Phase 1: Load Documents diff --git a/.claude/skills/design-system/SKILL.md b/.claude/skills/design-system/SKILL.md index b721fc8..daa791c 100644 --- a/.claude/skills/design-system/SKILL.md +++ b/.claude/skills/design-system/SKILL.md @@ -268,7 +268,7 @@ Use the template structure from `.claude/docs/templates/game-design-document.md` Ask: "May I create the skeleton file at `design/gdd/[system-name].md`?" -After writing, update `production/session-state/active.md` with: +After writing, create `production/session-state/active.md` if it does not exist, then update it with: - Task: Designing [system-name] GDD - Current section: Starting (skeleton created) - File: design/gdd/[system-name].md @@ -602,7 +602,7 @@ Use `AskUserQuestion`: If yes, invoke the design-review skill on the completed file. -### 5c: Update Systems Index +### 5d: Update Systems Index After the GDD is complete (and optionally reviewed): diff --git a/.claude/skills/gate-check/SKILL.md b/.claude/skills/gate-check/SKILL.md index 6422bd5..7aa7a11 100644 --- a/.claude/skills/gate-check/SKILL.md +++ b/.claude/skills/gate-check/SKILL.md @@ -144,8 +144,8 @@ The project progresses through these stages: - [ ] Architecture document has no unresolved open questions in Foundation or Core layers - [ ] All ADRs have Engine Compatibility sections stamped with the engine version - [ ] All ADRs have ADR Dependencies sections (even if all fields are "None") -- [ ] `/bmad-bmm-check-implementation-readiness` has been run or equivalent manual - validation confirms GDDs + architecture + epics are coherent +- [ ] Manual validation confirms GDDs + architecture + epics are coherent + (run `/review-all-gdds` and `/architecture-review` if not done recently) - [ ] **Core fantasy is delivered** — at least one playtester independently described an experience that matches the Player Fantasy section of the core system GDDs (without being prompted). **Vertical Slice Validation** (FAIL if any item is NO): diff --git a/.claude/skills/map-systems/SKILL.md b/.claude/skills/map-systems/SKILL.md index 3077ce3..ece6e9d 100644 --- a/.claude/skills/map-systems/SKILL.md +++ b/.claude/skills/map-systems/SKILL.md @@ -202,7 +202,7 @@ Wait for approval. Write the file only after "yes." ### Step 5c: Update Session State -After writing, update `production/session-state/active.md` with: +After writing, create `production/session-state/active.md` if it does not exist, then update it with: - Task: Systems decomposition - Status: Systems index created - File: design/gdd/systems-index.md diff --git a/.claude/skills/project-stage-detect/SKILL.md b/.claude/skills/project-stage-detect/SKILL.md index 1040763..3a1ad00 100644 --- a/.claude/skills/project-stage-detect/SKILL.md +++ b/.claude/skills/project-stage-detect/SKILL.md @@ -6,7 +6,7 @@ user-invocable: true allowed-tools: Read, Glob, Grep, Bash, Write context: fork model: haiku -agent: Explore +# Read-only diagnostic skill — no specialist agent delegation needed --- # Project Stage Detection diff --git a/.claude/skills/reverse-document/SKILL.md b/.claude/skills/reverse-document/SKILL.md index 3a1d4d6..c2c8024 100644 --- a/.claude/skills/reverse-document/SKILL.md +++ b/.claude/skills/reverse-document/SKILL.md @@ -5,7 +5,7 @@ argument-hint: " (e.g., 'design src/gameplay/combat' or 'architectu user-invocable: true allowed-tools: Read, Glob, Grep, Write, Edit, Bash context: fork -agent: Explore +# Read-only diagnostic skill — no specialist agent delegation needed --- # Reverse Documentation diff --git a/.claude/skills/sprint-plan/SKILL.md b/.claude/skills/sprint-plan/SKILL.md index 030c4c4..9f83259 100644 --- a/.claude/skills/sprint-plan/SKILL.md +++ b/.claude/skills/sprint-plan/SKILL.md @@ -8,7 +8,7 @@ context: | !ls production/sprints/ 2>/dev/null --- -When this skill is invoked: +## Phase 1: Gather Context 1. **Read the current milestone** from `production/milestones/`. @@ -20,9 +20,13 @@ When this skill is invoked: 4. **Check the risk register** at `production/risk-register/`. +--- + +## Phase 2: Generate Output + For `new`: -5. **Generate a sprint plan** following this format and present it to the user. Ask: "May I write this sprint plan to `production/sprints/sprint-[N].md`?" If yes, write the file, creating the directory if needed. Verdict: **COMPLETE** — sprint plan created. If no: Verdict: **BLOCKED** — user declined write. +**Generate a sprint plan** following this format and present it to the user. Ask: "May I write this sprint plan to `production/sprints/sprint-[N].md`?" If yes, write the file, creating the directory if needed. Verdict: **COMPLETE** — sprint plan created. If no: Verdict: **BLOCKED** — user declined write. ```markdown # Sprint [N] -- [Start Date] to [End Date] @@ -70,7 +74,7 @@ For `new`: For `status`: -5. **Generate a status report**: +**Generate a status report**: ```markdown # Sprint [N] Status -- [Date] @@ -101,7 +105,9 @@ For `status`: - [Any new risks identified this sprint] ``` -### Sprint Status File +--- + +## Phase 3: Write Sprint Status File After generating a new sprint plan, also write `production/sprint-status.yaml`. This is the machine-readable source of truth for story status — read by @@ -142,16 +148,27 @@ Initialize each story from the sprint plan's task tables: For `update`: read the existing `sprint-status.yaml`, carry over statuses for stories that haven't changed, add new stories, remove dropped ones. -### Scope Reminder +--- + +## Phase 4: Scope and Risk Check After presenting the sprint plan, add: > **Scope check:** If this sprint includes stories added beyond the original epic scope, run `/scope-check [epic]` to detect scope creep before implementation begins. -When reviewing stories during selection (step 3 above), note any stories that appear outside the original epic goals. If any are uncertain, flag them inline: "Are these stories within the original epic scope? If unsure, `/scope-check` can verify." - -### Agent Consultation +When reviewing stories during selection, note any stories that appear outside the original epic goals. If any are uncertain, flag them inline: "Are these stories within the original epic scope? If unsure, `/scope-check` can verify." For comprehensive sprint planning, consider consulting: - `producer` agent for capacity planning, risk assessment, and cross-department coordination - `game-designer` agent for feature prioritization and design readiness assessment + +--- + +## Phase 5: Next Steps + +After the sprint plan is written, recommend: + +- `/sprint-status` — check progress mid-sprint +- `/scope-check [epic]` — verify no scope creep before implementation begins +- `/dev-story [story-file]` — begin implementing the first story +- `/story-readiness [story-file]` — validate a story is ready before starting it diff --git a/.claude/skills/start/SKILL.md b/.claude/skills/start/SKILL.md index e0adb59..bc71f30 100644 --- a/.claude/skills/start/SKILL.md +++ b/.claude/skills/start/SKILL.md @@ -61,10 +61,20 @@ The user needs creative exploration before anything else. 2. Briefly explain what `/brainstorm` does (guided ideation using professional frameworks — MDA, player psychology, verb-first design) 3. Recommend running `/brainstorm open` as the next step 4. Show the recommended path: + **Concept phase:** - `/brainstorm` — discover your game concept - `/setup-engine` — configure the engine (brainstorm will recommend one) - - `/map-systems` — decompose the concept into systems and plan GDD writing order - - `/prototype` — test the core mechanic + - `/map-systems` — decompose the concept into systems + - `/design-system` — author a GDD for each MVP system + - `/review-all-gdds` — cross-system consistency check + - `/gate-check` — validate readiness before architecture work + **Architecture phase:** + - `/architecture-decision` — record key technical decisions (one per system) + - `/create-control-manifest` — compile decisions into an actionable rules sheet + - `/architecture-review` — validate architecture coverage + **Production phase:** + - `/create-epics` — map systems to epics + - `/create-stories` — break epics into implementable stories - `/sprint-plan` — plan the first sprint #### If B: Vague idea @@ -73,10 +83,20 @@ The user needs creative exploration before anything else. 2. Validate the idea as a starting point (don't judge or redirect) 3. Recommend running `/brainstorm [their hint]` to develop it 4. Show the recommended path: + **Concept phase:** - `/brainstorm [hint]` — develop the idea into a full concept - `/setup-engine` — configure the engine - `/map-systems` — decompose the concept into systems - - `/prototype` — test the core mechanic + - `/design-system` — author a GDD for each MVP system + - `/review-all-gdds` — cross-system consistency check + - `/gate-check` — validate readiness before architecture work + **Architecture phase:** + - `/architecture-decision` — record key technical decisions (one per system) + - `/create-control-manifest` — compile decisions into an actionable rules sheet + - `/architecture-review` — validate architecture coverage + **Production phase:** + - `/create-epics` — map systems to epics + - `/create-stories` — break epics into implementable stories - `/sprint-plan` — plan the first sprint #### If C: Clear concept @@ -89,11 +109,20 @@ The user needs creative exploration before anything else. - **Formalize first**: Run `/brainstorm` to structure the concept into a proper game concept document - **Jump to engine setup**: Go straight to `/setup-engine` and write the GDD manually afterward 3. Show the recommended path: + **Concept phase:** - `/brainstorm` or `/setup-engine` (their pick) - `/design-review` — validate the concept doc - `/map-systems` — decompose the concept into individual systems - - `/design-system` — author per-system GDDs - - `/architecture-decision` — make first technical decisions + - `/design-system` — author a GDD for each MVP system + - `/review-all-gdds` — cross-system consistency check + - `/gate-check` — validate readiness before architecture work + **Architecture phase:** + - `/architecture-decision` — record key technical decisions (one per system) + - `/create-control-manifest` — compile decisions into an actionable rules sheet + - `/architecture-review` — validate architecture coverage + **Production phase:** + - `/create-epics` — map systems to epics + - `/create-stories` — break epics into implementable stories - `/sprint-plan` — plan the first sprint #### If D: Existing work