Release v1.0.0 — concept-prototype/vertical-slice split, workflow restructure, polish (#50)

* Add /vertical-slice skill, prototype overhaul, and workflow integration

- Add /vertical-slice skill for pre-production validation (Phase 4 gate)
- Overhaul /prototype skill with two-mode design: concept prototype (Phase 1)
  vs vertical slice (Phase 4), with clearer differentiation and higher standards for VS
- Update prototyper agent to own both prototype and vertical-slice workflows
- Add prototype-report.md and vertical-slice-report.md output templates
- Update WORKFLOW-GUIDE, quick-start, skills-reference, agent-coordination-map,
  and skill-flow-diagrams to fully integrate both skills into the 7-phase pipeline
- Remove orphaned empty quick-prototype/ directory

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* sync v1 counts + polish

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* Add entity inventory flow, relax vertical-slice gate, improve UX authoring prompts

- /asset-spec: new Phase 0b entity & screen inventory when no argument and no
  existing inventory — reads GDDs/art-bible, proposes categorized list, writes
  design/assets/entity-inventory.md collaboratively
- /asset-spec: entity/character target falls back to inline user description
  when no source doc exists, rather than failing
- /gate-check: vertical slice changed from blocking to CONCERNS-only when
  absent; built-but-broken slice still fails; adds entity inventory as gate artifact
- /ux-design: convert inline approval prompts to AskUserQuestion for structured
  option capture at key authoring decision points
- workflow-catalog.yaml: entity-inventory step added to pre-production; UX spec
  min_count raised to 3; vertical-slice and prototype marked required: false with
  updated descriptions
- .gitignore: exclude marrow/ eval tooling directory

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* Add missing AskUserQuestion widgets to 7 skills

Audit found 11 decision points across 7 skills where structured option
prompts were missing — using plain text, auto-selection, or no gate at all.

Skills patched:
- create-epics: per-epic approval + producer CONCERNS verdict
- sprint-plan: producer CONCERNS verdict with scope/timeline options
- milestone-review: AT RISK / OFF TRACK producer verdicts require acknowledgement
- retrospective: existing-retro handling converted from plain text [A]/[B]
- quick-design: classification confirmation + draft approve/revise/redirect
- tech-debt add mode: category (6 options) + effort (S/M/L/XL) structured capture
- regression-suite: no-arg mode selection instead of silent auto-detect
- hotfix: severity confirmation gate before workflow begins

Also added AskUserQuestion to allowed-tools headers for retrospective,
quick-design, tech-debt, regression-suite, and hotfix.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* Prep v1 stable: fix WORKFLOW-GUIDE counts, stale agent names, and skill model fields

- WORKFLOW-GUIDE.md: correct agent count (48→49), skill count (66/68→73),
  add 6 missing skills to Appendix B, fix Creative category count (2→4),
  replace 3 non-existent agent names with correct ue-*/unity-* specialists,
  add missing godot-csharp/gdextension specialists to hierarchy,
  fix production/stories/ paths → production/epics/
- coordination-rules.md: replace "not yet used" with opt-in env var note
- quick-start.md: rename duplicate "Validate the concept" label → "Prototype the mechanic"
- skill-flow-diagrams.md: remove duplicate legacy UX pipeline section
- All 62 skills missing model: field now have explicit model: sonnet

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* fix: comprehensive skill audit — consistency, UX, and flow gaps

Two-pass audit fixing ~35 bugs across 41 files.

Pre-production flow:
- Brainstorm next-steps split into Path A (design-first) and Path B
  (prototype-first) — eliminates "prototype after architecture" confusion
- /architecture-review added to pre-production flow in brainstorm and
  create-architecture handoffs
- gate-check traceability check corrected to requirements-traceability.md
- dev-story TR registry error now points to /architecture-review (not /create-epics)
- start now writes production/stage.txt on first onboarding

AskUserQuestion gaps filled:
- balance-check, code-review, hotfix, day-one-patch, consistency-check
  all gain closing widgets and/or missing allowed-tools declarations
- hotfix git branch creation now requires user confirmation
- sprint-plan review-mode setup moved to Phase 0 (before gates run)
- team-combat gains architecture→implementation approval gate
- design-review APPROVED path consolidated from 3 widgets to 1 multiSelect

All 9 team-* skills:
- Phase 0 review-mode resolution added (solo/lean/full now respected)
- team-audio output path fixed (design/gdd/ → design/audio/)
- team-level final doc compilation delegated to level-designer subagent
- team-narrative localization-lead added to composition list
- team-qa sprint path fixed (flat files, not directories)
- team-release NO-GO override captures written justification
- team-live-ops Cancel verdict now explicitly BLOCKED

Other fixes:
- Art bible path standardized to design/art/art-bible.md (3 wrong refs)
- AD-PHASE-GATE added to lean-mode skip list in director-gates.md
- design-system duplicate 5d heading fixed; skeleton decline path added;
  mandatory agent spawns now respect review mode
- story-readiness acceptance criteria thresholds now type-aware
- create-stories gains multi-ADR and no-ADR handling guidance
- consistency-check creates docs/consistency-failures.md on first run
- retrospective frontmatter bash injection replaced with explicit Bash call
- smoke-check ls -t gains PowerShell fallback
- Conventional Commits format documented in coding-standards.md
- gate-check: ADR acceptance gate, QA plan check, chain-of-verification
  tool-action requirement all added

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* fix: expose --review flag in argument-hints for all team-* skills

All 9 team-* skills already implement Phase 0 review-mode resolution
internally (full/lean/solo), but none advertised [--review full|lean|solo]
in their argument-hint. Users had no way to discover the per-run override.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* docs: add SECURITY.md with coordinated disclosure policy

Defines scope, reporting process (GitHub private vulnerability reporting),
contributor security guidelines for hooks/skills/agents, and 90-day
coordinated disclosure timeline.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* docs: add CONTRIBUTING.md with framework contribution guidelines

Covers what PRs are welcome, skill/hook/agent technical requirements,
the collaborative principle, testing expectations, commit format,
and platform compatibility requirements.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* docs: add v1.0.0-beta → v1.0 upgrade section to UPGRADING.md

Documents the 17 commits since the beta tag: new /vertical-slice gate,
entity inventory flow in /map-systems, AskUserQuestion widgets across
7 skills, --review flag exposure on team-* skills, bug fixes
(#21, #36, #42, #43, #45), and the new CONTRIBUTING.md and SECURITY.md.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

.claude/skills/smoke-check/SKILL.md

@@ -4,6 +4,7 @@ description: "Run the critical path smoke test gate before QA hand-off. Executes
 argument-hint: "[sprint | quick | --platform pc|console|mobile|all]"
 user-invocable: true
 allowed-tools: Read, Glob, Grep, Bash, Write, AskUserQuestion
+model: sonnet
 ---
 
 # Smoke Check
@@ -92,7 +93,9 @@ path for your test framework."
 Unity tests require the editor and cannot be run headlessly via shell in most
 environments. Check for recent test result artifacts:
 ```bash
-ls -t test-results/ 2>/dev/null | head -5
+# List most recent test results (bash) — on Windows PowerShell use the fallback below
+ls -t test-results/ 2>/dev/null | head -5 \
+  || powershell -Command "Get-ChildItem test-results/ -ErrorAction SilentlyContinue | Sort-Object LastWriteTime -Descending | Select-Object -First 5 -ExpandProperty Name"
 ```
 If test result files exist (XML or JSON), read the most recent one and parse
 PASS/FAIL counts. If no artifacts exist: "Unity tests must be run from the
@@ -100,7 +103,9 @@ editor or CI pipeline. Please confirm test status manually before proceeding."
 
 **Unreal Engine:**
 ```bash
-ls -t Saved/Logs/ 2>/dev/null | grep -i "test\|automation" | head -5
+# List most recent Unreal automation logs (bash) — on Windows PowerShell use the fallback below
+ls -t Saved/Logs/ 2>/dev/null | grep -i "test\|automation" | head -5 \
+  || powershell -Command "Get-ChildItem Saved/Logs/ -ErrorAction SilentlyContinue | Where-Object { $_.Name -match 'test|automation' } | Sort-Object LastWriteTime -Descending | Select-Object -First 5 -ExpandProperty Name"
 ```
 If no matching log found: "UE automation tests must be run via the Session
 Frontend or CI pipeline. Please confirm test status manually."
@@ -181,86 +186,86 @@ Use `AskUserQuestion` to batch-verify. Keep to at most 3 calls.
 
 **Batch 1 — Core stability (always run):**
 ```
-question: "Smoke check — Batch 1: Core stability. Please verify each:"
+question: "Core stability — select any items that FAILED (leave all unselected if everything passed):"
+multiSelect: true
 options:
-  - "Game launches to main menu without crash — PASS"
-  - "Game launches to main menu without crash — FAIL"
-  - "New game / session starts successfully — PASS"
-  - "New game / session starts successfully — FAIL"
-  - "Main menu responds to all inputs — PASS"
-  - "Main menu responds to all inputs — FAIL"
+  - "Game does not launch or crashes before reaching the main menu"
+  - "New game / session fails to start"
+  - "Main menu does not respond to inputs"
+  - "Crash or hang observed during basic navigation"
 ```
 
-**Batch 2 — Sprint mechanic and regression (always run):**
+For any selected item, ask the user to briefly describe what failed before generating the report.
+
+**Batch 2 — Sprint changes and regression (always run):**
 ```
-question: "Smoke check — Batch 2: This sprint's changes and regression check:"
+question: "Sprint changes and regression — select any items that FAILED (leave all unselected if everything passed):"
+multiSelect: true
 options:
-  - "[Primary mechanic this sprint] — PASS"
-  - "[Primary mechanic this sprint] — FAIL: [describe what broke]"
-  - "[Second notable change this sprint, if any] — PASS"
-  - "[Second notable change this sprint] — FAIL"
-  - "Previous sprint's features still work (no regressions) — PASS"
-  - "Previous sprint's features — regression found: [brief description]"
+  - "[Primary mechanic this sprint] — FAILED"
+  - "[Second notable change this sprint, if any] — FAILED"
+  - "Regression in a previous sprint's feature — FAILED"
+  - "Other unexpected breakage observed — FAILED"
 ```
 
+For any selected item, ask the user to briefly describe what broke before generating the report.
+
 **Batch 3 — Data integrity and performance (run unless `quick` argument):**
 ```
-question: "Smoke check — Batch 3: Data integrity and performance:"
+question: "Data integrity and performance — select any items that FAILED or were skipped (leave all unselected if everything passed):"
+multiSelect: true
 options:
-  - "Save / load completes without data loss — PASS"
-  - "Save / load — FAIL: [describe what broke]"
+  - "Save / load — FAILED (data loss or corruption observed)"
   - "Save / load — N/A (save system not yet implemented)"
-  - "No new frame rate drops or hitches observed — PASS"
-  - "Frame rate drops or hitches found — FAIL: [where]"
-  - "Performance — not checked in this session"
+  - "Frame rate drops or hitches observed — FAILED"
+  - "Performance not checked this session"
 ```
 
+For any FAILED item selected, ask the user to describe what broke before generating the report.
+
 Record each response verbatim for the Phase 5 report.
 
 **Platform Batches** *(run only if `--platform` argument was provided)*:
 
 **PC platform** (`--platform pc` or `--platform all`):
 ```
-question: "Smoke check — PC Platform: Verify platform-specific behaviour:"
+question: "PC Platform — select any items that FAILED (leave all unselected if everything passed):"
+multiSelect: true
 options:
-  - "Keyboard controls work correctly across all menus and gameplay — PASS"
-  - "Keyboard controls — FAIL: [describe issue]"
-  - "Mouse input and cursor visibility correct in all states — PASS"
-  - "Mouse input — FAIL: [describe issue]"
-  - "Windowed and fullscreen modes function without graphical issues — PASS"
-  - "Windowed/fullscreen — FAIL: [describe issue]"
-  - "Resolution changes apply correctly — PASS"
-  - "Resolution changes — FAIL: [describe issue]"
+  - "Keyboard controls — FAILED (describe issue after)"
+  - "Mouse input or cursor visibility — FAILED (describe issue after)"
+  - "Windowed / fullscreen mode — FAILED (describe issue after)"
+  - "Resolution change — FAILED (describe issue after)"
 ```
 
+For any selected item, ask the user to briefly describe what failed before generating the report.
+
 **Console platform** (`--platform console` or `--platform all`):
 ```
-question: "Smoke check — Console Platform: Verify platform-specific behaviour:"
+question: "Console Platform — select any items that FAILED (leave all unselected if everything passed):"
+multiSelect: true
 options:
-  - "Gamepad input works correctly for all actions — PASS"
-  - "Gamepad input — FAIL: [describe issue]"
-  - "UI fits within TV safe zone margins (no text clipped) — PASS"
-  - "TV safe zone — FAIL: [describe what is clipped]"
-  - "No keyboard/mouse-only fallbacks shown to gamepad user — PASS"
-  - "Input prompt inconsistency — FAIL: [describe]"
-  - "Game boots correctly from cold start (no prior save) — PASS"
-  - "Cold start — FAIL: [describe issue]"
+  - "Gamepad input — FAILED (describe issue after)"
+  - "UI outside TV safe zone / text clipped — FAILED (describe what is clipped after)"
+  - "Keyboard/mouse fallback shown to gamepad user — FAILED (describe after)"
+  - "Cold start (no prior save) — FAILED (describe issue after)"
 ```
 
+For any selected item, ask the user to briefly describe what failed before generating the report.
+
 **Mobile platform** (`--platform mobile` or `--platform all`):
 ```
-question: "Smoke check — Mobile Platform: Verify platform-specific behaviour:"
+question: "Mobile Platform — select any items that FAILED (leave all unselected if everything passed):"
+multiSelect: true
 options:
-  - "Touch controls work correctly for all primary actions — PASS"
-  - "Touch controls — FAIL: [describe issue]"
-  - "Game handles orientation change (portrait ↔ landscape) correctly — PASS"
-  - "Orientation change — FAIL: [describe what breaks]"
-  - "Background / foreground transitions (home button) handled gracefully — PASS"
-  - "Background/foreground — FAIL: [describe issue]"
-  - "No visible performance issues on target device (no thermal throttling signs) — PASS"
-  - "Mobile performance — FAIL: [describe issue]"
+  - "Touch controls — FAILED (describe issue after)"
+  - "Orientation change (portrait ↔ landscape) — FAILED (describe what breaks after)"
+  - "Background / foreground transition (home button) — FAILED (describe issue after)"
+  - "Performance / thermal throttling on target device — FAILED (describe after)"
 ```
 
+For any selected item, ask the user to briefly describe what failed before generating the report.
+
 ---
 
 ## Phase 5: Generate Report