@atlashub/smartstack-cli 1.33.0 → 1.35.0

package/templates/skills/gitflow/steps/step-init.md

@@ -16,7 +16,8 @@ Set up GitFlow configuration with bare repository, worktrees, and branches.
 
 ## MANDATORY QUESTIONS
 
-**⛔ ALWAYS ask these 3 questions, even if values can be auto-detected:**
+**⛔ ALWAYS ask these 3 questions, even if values can be auto-detected.**
+**⛔ ALWAYS detect workspace context (step 2) to show sibling projects.**
 
 | Question | Variable | Auto-detect from |
 |----------|----------|------------------|
@@ -24,6 +25,10 @@ Set up GitFlow configuration with bare repository, worktrees, and branches.
 | Root folder | `{ROOT_FOLDER}` | Parent of current directory |
 | Project name | `{PROJECT_NAME}` | Repo name from URL or folder |
 
+**Multi-project principle:** Each repository has its OWN independent GitFlow config. Step 2 scans for sibling projects to provide context, not to share configuration.
+
+**⛔ FOLLOW-UP RULE:** When a user selects a "Custom..." option (custom name, custom path, custom URL), that selection is just a CHOICE, not the actual value. You MUST immediately ask a follow-up question to capture the actual value. Never proceed with a blank or default value.
+
 ---
 
 ## EXECUTION SEQUENCE:
@@ -52,7 +57,51 @@ fi
 ALREADY_INITIALIZED=$([ -f ".claude/gitflow/config.json" ] && echo "true" || echo "false")
 ```
 
-### 2. Handle Existing Configuration
+### 2. Detect Workspace (multi-project context)
+
+**Scan the parent directory for sibling projects already using GitFlow:**
+
+```bash
+WORKSPACE_DIR=$(dirname "$(pwd)")
+SIBLING_PROJECTS=()
+
+for dir in "$WORKSPACE_DIR"/*/; do
+  [ -d "$dir/.bare" ] || [ -d "$dir/01-Main" ] || [ -d "$dir/02-Develop" ] && {
+    PROJECT_NAME_SIBLING=$(basename "$dir")
+    SIBLING_PROJECTS+=("$PROJECT_NAME_SIBLING")
+  }
+done
+```
+
+**Display workspace context:**
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│  WORKSPACE: {WORKSPACE_DIR}                                  │
+├─────────────────────────────────────────────────────────────┤
+│  Each project has its OWN independent GitFlow configuration. │
+│  This init configures only: {DETECTED_NAME}                  │
+├─────────────────────────────────────────────────────────────┤
+{if SIBLING_PROJECTS not empty}
+│  Existing GitFlow projects:                                  │
+│  {for each SIBLING} ✅ {SIBLING_NAME}/                       │
+│     ├── .bare/  01-Main/  02-Develop/                        │
+│     └── features/  releases/  hotfixes/                      │
+│  {end for}                                                   │
+│                                                              │
+│  New project to initialize:                                  │
+│  ⬜ {DETECTED_NAME}/                                         │
+│     └── (same structure will be created)                     │
+{else}
+│  No existing GitFlow projects detected.                      │
+│  This will be the first project in this workspace.           │
+{endif}
+└─────────────────────────────────────────────────────────────┘
+```
+
+**Key principle:** GitFlow is **per-repository**. Each project has its own `config.json`, its own worktree structure, and its own version history. Projects do not share configuration.
+
+### 3. Handle Existing Configuration
 
 **If `ALREADY_INITIALIZED` = true:**
 
@@ -75,12 +124,12 @@ AskUserQuestion:
 ```
 
 **Handle choices:**
-- **Reconfigure**: Continue to step 3 (will ask all questions again)
+- **Reconfigure**: Continue to step 4 (will ask all questions again)
 - **Repair**: Check directories, fix missing ones, exit
 - **View only**: Display config, exit
 - **Cancel**: Exit immediately
 
-### 3. MANDATORY: Ask Repository URL
+### 4. MANDATORY: Ask Repository URL
 
 **⛔ ALWAYS ask, even if URL was detected:**
 
@@ -100,34 +149,83 @@ AskUserQuestion:
     multiSelect: false
 ```
 
-**If user selects "Enter GitHub URL" or "Enter Azure DevOps URL":**
-- Capture URL via "Other" input
+**⛔ FOLLOW-UP: If user selects "Enter GitHub URL" or "Enter Azure DevOps URL":**
+
+The selected option is just a choice, NOT the actual URL. You MUST ask a follow-up question:
+
+```yaml
+AskUserQuestion:
+  - header: "URL"
+    question: "Enter the repository URL:"
+    options:
+      - label: "https://github.com/org/repo.git"
+        description: "Example GitHub format"
+      - label: "https://dev.azure.com/org/project/_git/repo"
+        description: "Example Azure DevOps format"
+    multiSelect: false
+```
+
+The user will type the actual URL via "Other". Then:
 - Validate format
 - Update `{REPO_URL}` and `{GIT_PROVIDER}`
 
-### 4. MANDATORY: Ask Root Folder
+### 5. MANDATORY: Ask Root Folder
+
+**⛔ ALWAYS ask where to create THIS project's structure:**
+
+**If sibling projects exist, show where it fits:**
 
-**⛔ ALWAYS ask where to create the project structure:**
+```
+{WORKSPACE_DIR}/
+├── SmartStack.app/    ✅ (gitflow)
+├── SmartStack.mcp/    ✅ (gitflow)
+├── SmartStack.cli/    ✅ (gitflow)
+└── NewProject/        ← THIS PROJECT
+    ├── .bare/
+    ├── 01-Main/
+    ├── 02-Develop/
+    ├── features/
+    ├── releases/
+    └── hotfixes/
+```
 
 ```yaml
 AskUserQuestion:
   - header: "Location"
-    question: "Root folder for project? (All worktrees will be created here)"
+    question: "Root folder for THIS project? (worktrees will be created here)"
     options:
       - label: "Use parent folder (Recommended)"
-        description: "{DETECTED_FOLDER}/"
+        description: "{DETECTED_FOLDER}/ - consistent with {#SIBLING_PROJECTS} sibling project(s)"
       - label: "Use current folder"
         description: "$(pwd)/ - Will create subfolders here"
-      - label: "Enter custom path"
+      - label: "Custom path"
         description: "Specify a different location"
     multiSelect: false
 ```
 
-**Explain the structure that will be created:**
+**⛔ FOLLOW-UP: If user selects "Custom path":**
+
+You MUST ask a follow-up question to get the actual path:
+
+```yaml
+AskUserQuestion:
+  - header: "Path"
+    question: "Enter the full path for the project root folder:"
+    options:
+      - label: "{DETECTED_FOLDER}/"
+        description: "Parent of current directory"
+      - label: "{WORKSPACE_DIR}/"
+        description: "Workspace root"
+    multiSelect: false
+```
+
+The user will type the actual path via "Other". Validate the path exists or can be created.
+
+**Explain the structure that will be created for this project:**
 
 ```
 {ROOT_FOLDER}/
-├── .bare/                 # Git bare repository
+├── .bare/                 # Git bare repository (this repo only)
 ├── 01-Main/               # Worktree: main branch
 ├── 02-Develop/            # Worktree: develop branch
 ├── features/              # Feature branch worktrees
@@ -135,7 +233,7 @@ AskUserQuestion:
 └── hotfixes/              # Hotfix branch worktrees
 ```
 
-### 5. MANDATORY: Ask Project Name
+### 6. MANDATORY: Ask Project Name
 
 **⛔ ALWAYS ask to confirm project name:**
 
@@ -146,12 +244,150 @@ AskUserQuestion:
     options:
       - label: "Use detected name (Recommended)"
         description: "Project: {DETECTED_NAME}"
-      - label: "Enter custom name"
+      - label: "Custom name"
         description: "Specify a different project name"
     multiSelect: false
 ```
 
-### 6. Ask Worktree Mode
+**⛔ FOLLOW-UP: If user selects "Custom name":**
+
+You MUST ask a follow-up question to get the actual name:
+
+```yaml
+AskUserQuestion:
+  - header: "Name"
+    question: "Enter the project name:"
+    options:
+      - label: "{DETECTED_NAME}"
+        description: "Detected from repository"
+      - label: "{DETECTED_NAME}-v2"
+        description: "Variant of detected name"
+    multiSelect: false
+```
+
+The user will type the actual name via "Other". Use this raw input for step 6b.
+
+### 6b. Normalize Project Name (INTELLIGENT)
+
+**⛔ ALWAYS normalize, even if user chose the detected name.**
+
+**Step 1: Parse input into words**
+
+Split the raw input on any separator: spaces, hyphens, underscores, dots, camelCase boundaries.
+
+| Raw input | Parsed words |
+|-----------|-------------|
+| `mon super projet` | `["mon", "super", "projet"]` |
+| `gestion-des-stocks` | `["gestion", "des", "stocks"]` |
+| `my_awesome_app` | `["my", "awesome", "app"]` |
+| `SmartStack.App` | `["Smart", "Stack", "App"]` |
+| `userManagement` | `["user", "Management"]` |
+
+**Step 2: Language detection and spell check**
+
+For EACH word, you MUST:
+1. **Detect the language** (French, English, or technical/proper noun)
+2. **Check spelling** - flag obvious typos
+3. **Suggest corrections** if misspelled
+
+| Word | Language | Spelling | Suggestion |
+|------|----------|----------|------------|
+| `gestion` | FR | ✅ | - |
+| `gestoin` | FR | ❌ typo | → `gestion` |
+| `managment` | EN | ❌ typo | → `management` |
+| `SmartStack` | Proper noun | ✅ | - |
+| `auth` | EN (abbreviation) | ✅ | - |
+
+**If typos detected**, ask the user BEFORE generating variants:
+
+```yaml
+AskUserQuestion:
+  - header: "Spelling"
+    question: "Corrections detected. Accept?"
+    options:
+      - label: "Accept corrections (Recommended)"
+        description: "'gestoin' → 'gestion', 'managment' → 'management'"
+      - label: "Keep original"
+        description: "Use the name as typed"
+    multiSelect: false
+```
+
+**Step 3: Generate all name variants**
+
+From the cleaned words, generate ALL variants:
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│  PROJECT NAME VARIANTS                                       │
+│  Input: "gestion des stocks"                                 │
+├─────────────────────────────────────────────────────────────┤
+│                                                              │
+│  A) PascalCase.Dot    →  Gestion.Des.Stocks                 │
+│     Best for: .NET namespace, C# project, folder name        │
+│                                                              │
+│  B) PascalCase        →  GestionDesStocks                    │
+│     Best for: Class name, assembly name                      │
+│                                                              │
+│  C) kebab-case        →  gestion-des-stocks                  │
+│     Best for: Git repo, npm package, URL slug                │
+│                                                              │
+│  D) snake_case        →  gestion_des_stocks                  │
+│     Best for: Database, Python, file system                  │
+│                                                              │
+└─────────────────────────────────────────────────────────────┘
+```
+
+**Step 4: Ask user to choose the PRIMARY format**
+
+```yaml
+AskUserQuestion:
+  - header: "Format"
+    question: "Which format for the project name?"
+    options:
+      - label: "PascalCase.Dot (Recommended)"
+        description: "{PascalCase.Dot variant} - .NET convention"
+      - label: "PascalCase"
+        description: "{PascalCase variant} - single word"
+      - label: "kebab-case"
+        description: "{kebab-case variant} - git/npm convention"
+      - label: "snake_case"
+        description: "{snake_case variant} - database/python convention"
+    multiSelect: false
+```
+
+**Step 5: Store all derived names**
+
+Regardless of the chosen primary format, ALL variants are generated and stored:
+
+```json
+{
+  "PROJECT_NAME": "{chosen format}",
+  "PROJECT_VARIANTS": {
+    "pascalCaseDot": "Gestion.Des.Stocks",
+    "pascalCase": "GestionDesStocks",
+    "kebabCase": "gestion-des-stocks",
+    "snakeCase": "gestion_des_stocks",
+    "displayName": "Gestion Des Stocks",
+    "words": ["gestion", "des", "stocks"],
+    "language": "fr"
+  }
+}
+```
+
+These variants are available for subsequent steps (repo name, namespace, folder, etc.).
+
+**Real-world examples:**
+
+| User types | PascalCase.Dot | kebab-case | PascalCase |
+|-----------|---------------|------------|------------|
+| `smart stack app` | `SmartStack.App` | `smart-stack-app` | `SmartStackApp` |
+| `gestion-des-stocks` | `Gestion.Des.Stocks` | `gestion-des-stocks` | `GestionDesStocks` |
+| `Mon Projet V2` | `Mon.Projet.V2` | `mon-projet-v2` | `MonProjetV2` |
+| `user auth module` | `User.Auth.Module` | `user-auth-module` | `UserAuthModule` |
+| `PROJET TEST` | `Projet.Test` | `projet-test` | `ProjetTest` |
+| `e-commerce platform` | `ECommerce.Platform` | `e-commerce-platform` | `ECommercePlatform` |
+
+### 7. Ask Worktree Mode
 
 ```yaml
 AskUserQuestion:
@@ -167,7 +403,7 @@ AskUserQuestion:
     multiSelect: false
 ```
 
-### 7. Create Directory Structure
+### 8. Create Directory Structure
 
 **⛔ Create the COMPLETE structure:**
 
@@ -207,7 +443,7 @@ DEVELOP_PATH=$([ "$WORKTREE_MODE" = "organized" ] && echo "02-Develop" || echo "
 mkdir -p "$DEVELOP_PATH/.claude/gitflow/{plans,logs,cache,backup}"
 ```
 
-### 8. Create Configuration
+### 9. Create Configuration
 
 **Write `.claude/gitflow/config.json` in develop worktree:**
 
@@ -216,6 +452,13 @@ mkdir -p "$DEVELOP_PATH/.claude/gitflow/{plans,logs,cache,backup}"
   "version": "2.0.0",
   "repository": {
     "name": "{PROJECT_NAME}",
+    "nameVariants": {
+      "pascalCaseDot": "{PascalCase.Dot}",
+      "pascalCase": "{PascalCase}",
+      "kebabCase": "{kebab-case}",
+      "snakeCase": "{snake_case}",
+      "displayName": "{Display Name}"
+    },
     "rootFolder": "{ROOT_FOLDER}",
     "remoteUrl": "{REPO_URL}"
   },
@@ -265,7 +508,7 @@ mkdir -p "$DEVELOP_PATH/.claude/gitflow/{plans,logs,cache,backup}"
 }
 ```
 
-### 9. Detect Version
+### 10. Detect Version
 
 ```bash
 # In develop worktree
@@ -280,7 +523,7 @@ VERSION=$(grep -oP '<Version>\K[^<]+' *.csproj 2>/dev/null | head -1)
 [ -z "$VERSION" ] && VERSION="0.1.0"
 ```
 
-### 10. Summary
+### 11. Summary
 
 ```
 ╔══════════════════════════════════════════════════════════════════╗
@@ -300,6 +543,11 @@ VERSION=$(grep -oP '<Version>\K[^<]+' *.csproj 2>/dev/null | head -1)
 ║  ├── releases/        (release worktrees)   ✅                    ║
 ║  └── hotfixes/        (hotfix worktrees)    ✅                    ║
 ╠══════════════════════════════════════════════════════════════════╣
+{if SIBLING_PROJECTS not empty}
+║  Workspace: {WORKSPACE_DIR}                                       ║
+║  GitFlow projects: {#SIBLING_PROJECTS + 1} (including this one)   ║
+╠══════════════════════════════════════════════════════════════════╣
+{endif}
 ║  Config: 02-Develop/.claude/gitflow/config.json                   ║
 ╠══════════════════════════════════════════════════════════════════╣
 ║  NEXT: cd 02-Develop && /gitflow -f <feature-name>                ║

package/templates/skills/gitflow/templates/config.json

@@ -2,6 +2,13 @@
   "version": "2.0.0",
   "repository": {
     "name": "",
+    "nameVariants": {
+      "pascalCaseDot": "",
+      "pascalCase": "",
+      "kebabCase": "",
+      "snakeCase": "",
+      "displayName": ""
+    },
     "defaultBranch": "main",
     "remoteUrl": ""
   },

package/templates/skills/ralph-loop/SKILL.md

@@ -194,12 +194,15 @@ Before ANY work, verify MCP servers:
   "created": "2024-01-01T00:00:00Z",
   "max_iterations": 50,
   "completion_promise": "COMPLETE",
+  "source": null,
   "tasks": [
     { "id": 1, "description": "Task 1", "passes": false },
     { "id": 2, "description": "Task 2", "passes": false }
   ]
 }
 ```
+
+> **`source` field:** Optional path to the BA handoff document that generated this task list (set by `/business-analyse` step-05). When present, Ralph Loop can reference the handoff for detailed specifications. `null` when tasks are created directly by Ralph Loop.
 </file_structure>
 
 <execution_rules>