Release v0.3.0: /design-system, /map-systems, status line, UPGRADING guide (#2)

* Add UPGRADING.md migration guide and link from README

Covers v0.1→v0.2 upgrade with three strategies (git merge, cherry-pick,
manual copy), file safety categories, and post-upgrade verification steps.
Structured to support future version sections.

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

* Rename /design-systems to /map-systems + /design-system and fix all references

Split the monolithic /design-systems skill into two focused skills:
- /map-systems: systems decomposition and index creation
- /design-system: guided section-by-section GDD authoring

Updated all cross-references across 14 files: README, UPGRADING,
WORKFLOW-GUIDE, quick-start, skills-reference, game-concept template,
systems-index template, brainstorm, design-review, gate-check,
project-stage-detect, setup-engine, and start skills. Fixed skill
counts from 36 to 37 everywhere. Added /map-systems and /design-system
to quick-start Paths A and B workflows.

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

* Fix cross-reference gaps, broken hooks, and stale workflow chains

- Fix log-agent.sh parsing agent_type instead of agent_name (always logged "unknown")
- Fix GDD status lifecycle: design-system now writes Approved/Designed/In Review
- Clean up settings.local.json vestigial Bash grants from development
- Delete orphaned docs marked for removal in UPGRADING.md
- Add /design-system to next-steps in /start, /brainstorm, /setup-engine
- Fix WORKFLOW-GUIDE: add /map-systems + /design-system to Appendix C Workflow 1
- Fix invalid /map-systems map argument in WORKFLOW-GUIDE Step 2.1
- Update map-systems frontmatter to document [system-name] argument
- Update commit hook to validate all 8 required GDD sections (was 5)
- Update README template count 28 → 29, add 5 missing templates to quick-start

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

* Add custom status line with 7-stage production pipeline

Introduces a status line showing context %, model name, and production
stage at a glance. Aligns gate-check and project-stage-detect to a
unified 7-stage model (Concept → Systems Design → Technical Setup →
Pre-Production → Production → Polish → Release). Stage is determined
by explicit override (production/stage.txt) or auto-detected from
project artifacts. Epic/Feature/Task breadcrumb appears conditionally
in Production+ stages via a structured STATUS block in active.md.

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

* Add v0.2→v0.3 upgrade guide and PR validation test suite

- UPGRADING.md: add v0.2.0→v0.3.0 section documenting breaking rename
  of /design-systems→/map-systems, new /design-system skill, statusline.sh,
  gate-check stage advancement, and safe-to-overwrite file list

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

---------

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

.claude/docs/context-management.md

@@ -20,6 +20,24 @@ after each significant milestone:
 The state file should contain: current task, progress checklist, key decisions
 made, files being worked on, and open questions.
 
+### Status Line Block (Production+ only)
+
+When the project is in Production, Polish, or Release stage, include a structured
+status block in `active.md` that the status line script can parse:
+
+```markdown
+<!-- STATUS -->
+Epic: Combat System
+Feature: Melee Combat
+Task: Implement hitbox detection
+<!-- /STATUS -->
+```
+
+- All three fields (Epic, Feature, Task) are optional — include only what applies
+- Update this block when switching focus areas
+- The status line displays it as a breadcrumb: `Combat System > Melee Combat > Hitboxes`
+- Remove or empty the block when no active work focus exists
+
 After any disruption (compaction, crash, `/clear`), read the state file first.
 
 ### Incremental File Writing

.claude/docs/quick-start.md

@@ -99,7 +99,8 @@ Ask yourself: "What department would handle this in a real studio?"
 | `/project-stage-detect` | Analyze project state, detect stage, identify gaps |
 | `/reverse-document` | Generate design/architecture docs from existing code |
 | `/setup-engine` | Configure engine + version, populate reference docs |
-| `/design-systems` | Decompose concept into systems, map dependencies, guide per-system GDDs |
+| `/map-systems` | Decompose concept into systems, map dependencies, guide per-system GDDs |
+| `/design-system` | Guided, section-by-section GDD authoring for a single game system |
 | `/team-combat` | Orchestrate full combat team pipeline |
 | `/team-narrative` | Orchestrate full narrative team pipeline |
 | `/team-ui` | Orchestrate full UI team pipeline |
@@ -136,6 +137,11 @@ Templates are in `.claude/docs/templates/`:
 - `pitch-document.md` -- for pitching the game to stakeholders
 - `economy-model.md` -- for virtual economy design (sink/faucet model)
 - `faction-design.md` -- for faction identity, lore, and gameplay role
+- `systems-index.md` -- for systems decomposition and dependency mapping
+- `project-stage-report.md` -- for project stage detection output
+- `design-doc-from-implementation.md` -- for reverse-documenting existing code into GDDs
+- `architecture-doc-from-code.md` -- for reverse-documenting code into architecture docs
+- `concept-doc-from-prototype.md` -- for reverse-documenting prototypes into concept docs
 
 ### 5. Follow the Coordination Rules
 
@@ -165,10 +171,13 @@ If you already know what you need, jump directly to the relevant path:
    - If the engine version is newer than the LLM's training data, it fetches
      current docs from the web so agents suggest correct APIs
 3. **Validate the concept** — Run `/design-review design/gdd/game-concept.md`
-4. **Test the core loop** — Run `/prototype [core-mechanic]`
-5. **Playtest it** — Run `/playtest-report` to validate the hypothesis
-6. **Plan the first sprint** — Run `/sprint-plan new`
-7. Start building
+4. **Decompose into systems** — Run `/map-systems` to map all systems and dependencies
+5. **Design each system** — Run `/design-system [system-name]` (or `/map-systems next`)
+   to write GDDs in dependency order
+6. **Test the core loop** — Run `/prototype [core-mechanic]`
+7. **Playtest it** — Run `/playtest-report` to validate the hypothesis
+8. **Plan the first sprint** — Run `/sprint-plan new`
+9. Start building
 
 ### Path B: "I know what I want to build"
 
@@ -177,10 +186,12 @@ If you already have a game concept and engine choice:
 1. **Set up the engine** — Run `/setup-engine [engine] [version]`
    (e.g., `/setup-engine godot 4.6`) — also creates technical preferences
 2. **Write the Game Pillars** — delegate to `creative-director`
-3. **Create the initial ADR** — Run `/architecture-decision`
-4. **Create the first milestone** in `production/milestones/`
-5. **Plan the first sprint** — Run `/sprint-plan new`
-6. Start building
+3. **Decompose into systems** — Run `/map-systems` to enumerate systems and dependencies
+4. **Design each system** — Run `/design-system [system-name]` for GDDs in dependency order
+5. **Create the initial ADR** — Run `/architecture-decision`
+6. **Create the first milestone** in `production/milestones/`
+7. **Plan the first sprint** — Run `/sprint-plan new`
+8. Start building
 
 ### Path C: "I know the game but not the engine"
 
@@ -208,7 +219,7 @@ CLAUDE.md                          -- Master config (read this first, ~60 lines)
 .claude/
   settings.json                    -- Claude Code hooks and project settings
   agents/                          -- 48 agent definitions (YAML frontmatter)
-  skills/                          -- 36 slash command definitions (YAML frontmatter)
+  skills/                          -- 37 slash command definitions (YAML frontmatter)
   hooks/                           -- 8 hook scripts (.sh) wired by settings.json
   rules/                           -- 11 path-specific rule files
   docs/

.claude/docs/skills-reference.md

@@ -36,5 +36,6 @@
 | `/patch-notes` | Generate player-facing patch notes from git history and internal data |
 | `/brainstorm` | Guided ideation using professional studio methods (MDA, SDT, Bartle, verb-first) |
 | `/gate-check` | Validate readiness to advance between development phases (PASS/CONCERNS/FAIL) |
-| `/design-systems` | Decompose game concept into systems, map dependencies, prioritize design order, guide per-system GDDs |
+| `/map-systems` | Decompose game concept into systems, map dependencies, prioritize design order, guide per-system GDDs |
+| `/design-system` | Guided, section-by-section GDD authoring for a single game system with cross-referencing and incremental writing |
 | `/setup-engine` | Configure engine + version, detect knowledge gaps, populate version-aware reference docs |

.claude/docs/templates/game-concept.md

@@ -309,7 +309,7 @@ the combat-crafting loop engaging for 30+ minute sessions"]
 - [ ] Get concept approval from creative-director
 - [ ] Fill in CLAUDE.md technology stack based on engine choice (`/setup-engine`)
 - [ ] Create game pillars document (`/design-review` to validate)
-- [ ] Decompose concept into systems (`/design-systems` — maps dependencies, assigns priorities, guides per-system GDD writing)
+- [ ] Decompose concept into systems (`/map-systems` — maps dependencies, assigns priorities, guides per-system GDD writing)
 - [ ] Create first architecture decision record (`/architecture-decision`)
 - [ ] Prototype core loop (`/prototype [core-mechanic]`)
 - [ ] Validate core loop with playtest (`/playtest-report`)

.claude/docs/templates/project-stage-report.md

@@ -1,7 +1,7 @@
 # Project Stage Analysis Report
 
 **Generated**: [DATE]
-**Stage**: [Concept | Pre-production | Production | Post-Launch]
+**Stage**: [Concept | Systems Design | Technical Setup | Pre-Production | Production | Polish | Release]
 **Analysis Scope**: [Full project | Specific role: programmer/designer/producer]
 
 ---

.claude/docs/templates/systems-index.md

@@ -140,7 +140,7 @@ These should be prototyped early regardless of priority tier.]
 ## Next Steps
 
 - [ ] Review and approve this systems enumeration
-- [ ] Design MVP-tier systems first (use `/design-systems [system-name]`)
+- [ ] Design MVP-tier systems first (use `/design-system [system-name]`)
 - [ ] Run `/design-review` on each completed GDD
 - [ ] Run `/gate-check pre-production` when MVP systems are designed
 - [ ] Prototype the highest-risk system early (`/prototype [system]`)