gsd-cc 0.1.0 → 0.2.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gsd-cc",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "Get Shit Done on Claude Code — structured AI development with your Max plan",
   "author": "Philipp Briese (https://github.com/0ui-labs)",
   "homepage": "https://github.com/0ui-labs/GSD-CC#readme",

package/skills/gsd/SKILL.md

@@ -12,6 +12,10 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 
 You are the GSD-CC router. Your job is to read the current project state and suggest **exactly one** next action. Not a menu. Not "what do you want to do?". One clear recommendation.
 
+## Language
+
+Read the `language` field from `.gsd/STATE.md`. All output — messages, suggestions, file content — must use that language. If no language is set, default to English.
+
 ## Step 1: Detect State
 
 Check what exists on disk:
@@ -143,6 +147,7 @@ When routing to a sub-skill, tell the user what you're doing and then invoke the
 - Reconciliation → `/gsd-cc-unify`
 - Auto mode → `/gsd-cc-auto`
 - Status overview → `/gsd-cc-status`
+- Update skills → `/gsd-cc-update`
 
 Power users can invoke these directly. But the default path only needs `/gsd-cc` + Enter.
 

package/skills/gsd/apply/SKILL.md

@@ -12,6 +12,10 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 
 You execute one task at a time from the current slice plan. Each task has a plan with acceptance criteria and boundaries. Follow the plan precisely.
 
+## Language
+
+Read the `language` field from `.gsd/STATE.md`. All output — messages, summaries, commit messages — must use that language. If no language is set, default to English.
+
 ## Step 1: Determine Current Task
 
 1. Read `.gsd/STATE.md` — get `current_slice` and `current_task`

package/skills/gsd/auto/SKILL.md

@@ -11,6 +11,10 @@ allowed-tools: Read, Write, Bash, Glob
 
 You start the auto-loop that executes tasks autonomously, each in a fresh context window.
 
+## Language
+
+Read the `language` field from `.gsd/STATE.md`. All output — messages, status updates — must use that language. If no language is set, default to English.
+
 ## Step 1: Check Prerequisites
 
 Before starting, verify ALL of these:

package/skills/gsd/discuss/SKILL.md

@@ -12,6 +12,10 @@ allowed-tools: Read, Write, Edit, Glob, Grep
 
 You help the user resolve ambiguities BEFORE planning begins. Your job is to identify gray areas in the current slice and turn them into concrete decisions.
 
+## Language
+
+Read the `language` field from `.gsd/STATE.md`. All output — messages, questions, decision records — must use that language. If no language is set, default to English.
+
 ## Step 1: Load Context
 
 1. Read `.gsd/STATE.md` — get `current_slice` and `milestone`

package/skills/gsd/plan/SKILL.md

@@ -11,6 +11,10 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 
 You turn a slice description into a set of executable task plans. Each task gets BDD acceptance criteria and explicit boundaries. The result is a set of files that `/gsd-cc-apply` or `auto-loop.sh` can execute without ambiguity.
 
+## Language
+
+Read the `language` field from `.gsd/STATE.md`. All output — messages, plans, acceptance criteria, boundaries — must use that language. If no language is set, default to English.
+
 ## Step 1: Load Context
 
 Read these files (all that exist):

package/skills/gsd/seed/SKILL.md

@@ -14,13 +14,26 @@ You are a project coach. You think WITH the user, not interrogate them. Your job
 
 ## Behavior
 
-### Step 1: Ask What They're Building
+### Step 0: Language Selection
 
-Start with a simple, open question:
+Before anything else, ask the user which language to use:
 
 ```
 No .gsd/ directory found. Let's start a new project.
 
+Which language should I use? (e.g. English, Deutsch, Français, ...)
+Default: English
+```
+
+If the user responds with a project description instead of a language, default to English and continue with Step 1 using their response as the project description.
+
+Store the chosen language. **All communication, generated files, plans, acceptance criteria, UNIFY reports, and status output will use this language from now on.**
+
+### Step 1: Ask What They're Building
+
+If not already answered in Step 0, ask:
+
+```
 What are you building?
 Tell me in a sentence or two — I'll figure out the rest.
 ```
@@ -137,7 +150,8 @@ Short project vision — 3-5 sentences max. This is the "elevator pitch" that ev
 ```json
 {
   "type": "{type}",
-  "rigor": "{rigor}"
+  "rigor": "{rigor}",
+  "language": "{language}"
 }
 ```
 
@@ -150,6 +164,7 @@ Initialize from the STATE.md template with:
 - `phase: seed-complete`
 - `rigor: {rigor}`
 - `project_type: {type}`
+- `language: {language}`
 - `auto_mode: false`
 - `last_updated: {now ISO}`
 

package/skills/gsd/status/SKILL.md

@@ -11,6 +11,10 @@ allowed-tools: Read, Glob, Grep, Bash
 
 You show a clear, concise overview of where the project stands. No actions — just information and one suggested next step.
 
+## Language
+
+Read the `language` field from `.gsd/STATE.md`. All output — messages, progress reports — must use that language. If no language is set, default to English.
+
 ## Step 1: Read State
 
 1. Read `.gsd/STATE.md`

package/skills/gsd/templates/STATE.md

@@ -7,6 +7,7 @@ loop_position: 0
 unify_required: false
 rigor: standard
 project_type: application
+language: English
 auto_mode: false
 last_updated: {{ISO_DATE}}
 ---

package/skills/gsd/unify/SKILL.md

@@ -13,6 +13,10 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 
 UNIFY is not optional. It runs after every slice. The `/gsd-cc` router blocks all other actions until UNIFY is complete. This is the single most important quality mechanism in GSD-CC.
 
+## Language
+
+Read the `language` field from `.gsd/STATE.md`. All output — messages, UNIFY reports, deviation analysis — must use that language. If no language is set, default to English.
+
 ## Why UNIFY Exists
 
 - Without UNIFY, the next slice builds on assumptions instead of facts.

package/skills/gsd/update/SKILL.md

@@ -0,0 +1,69 @@
+---
+name: gsd-cc-update
+description: >
+  Update GSD-CC skills to the latest version from npm. Use when user says
+  /gsd-cc-update, /gsd-cc update, or asks to update GSD-CC.
+allowed-tools: Read, Bash, Glob
+---
+
+# /gsd-cc-update — Update GSD-CC
+
+You update GSD-CC to the latest version by running the installer.
+
+## Step 1: Detect Current Installation
+
+Check where GSD-CC is installed:
+
+```
+1. Check ~/.claude/skills/gsd/SKILL.md (global)
+2. Check ./.claude/skills/gsd/SKILL.md (local)
+```
+
+Use `Glob` to find which exists. If both exist, update both.
+
+## Step 2: Get Current Version
+
+Run:
+```bash
+npm view gsd-cc version
+```
+
+This shows the latest available version on npm.
+
+Also check if a `package.json` exists in the installed skills directory's parent to find the current version. If not available, report "unknown".
+
+## Step 3: Confirm with User
+
+Show:
+```
+GSD-CC Update
+
+  Installed: {current_version or "unknown"}
+  Latest:    {latest_version}
+  Location:  {global and/or local path}
+
+Update now? (y/n)
+```
+
+If the versions match, tell the user they're already on the latest version and stop.
+
+## Step 4: Run Update
+
+Based on where it's installed, run:
+
+- **Global only:** `npx gsd-cc@latest --global`
+- **Local only:** `npx gsd-cc@latest --local`
+- **Both:** `npx gsd-cc@latest --global && npx gsd-cc@latest --local`
+
+## Step 5: Confirm
+
+```
+✓ GSD-CC updated to {version}.
+  Your .gsd/ project state is unchanged.
+```
+
+## Safety
+
+- **Never touch .gsd/ directory.** The update only replaces skill files, not project state.
+- **Existing project state (STATE.md, plans, summaries) is preserved.**
+- **Custom project types** in `seed/types/` will be overwritten if they share a name with built-in types. Warn the user if custom types are detected.