@atlashub/smartstack-cli 3.14.0 → 3.16.0

package/templates/skills/business-analyse/html/src/scripts/06-render-consolidation.js

@@ -2,10 +2,95 @@
    CONSOLIDATION
    ============================================ */
 function renderConsolidation() {
+    renderDataModel();
     renderConsolInteractions();
     renderConsolPermissions();
 }
 
+/* ============================================
+   DATA MODEL (cross-module entity overview)
+   ============================================ */
+function renderDataModel() {
+    const container = document.getElementById('dataModelContainer');
+    if (!container) return;
+
+    // Collect all entities from all modules
+    const allEntities = [];
+    data.modules.forEach(m => {
+        const spec = data.moduleSpecs[m.code] || {};
+        (spec.entities || []).forEach(ent => {
+            allEntities.push({ ...ent, moduleCode: m.code, moduleName: m.name || m.code });
+        });
+    });
+
+    if (allEntities.length === 0) {
+        container.innerHTML = '<p style="color:var(--text-muted);text-align:center;padding:2rem;">Aucune entite definie. Specifiez les donnees dans chaque domaine (Phase 3 > onglet Donnees).</p>';
+        return;
+    }
+
+    // Build relationship index for cross-module links
+    const entityModuleMap = {};
+    allEntities.forEach(e => { entityModuleMap[e.name] = e.moduleName; });
+
+    // Render grouped by module
+    let html = '';
+
+    // Summary bar
+    const moduleCount = data.modules.filter(m => (data.moduleSpecs[m.code]?.entities || []).length > 0).length;
+    const relCount = allEntities.reduce((sum, e) => sum + (e.relationships || []).length, 0);
+    html += `
+        <div class="dm-summary">
+            <div class="dm-summary-item"><span class="dm-summary-value">${allEntities.length}</span><span class="dm-summary-label">Entites</span></div>
+            <div class="dm-summary-item"><span class="dm-summary-value">${moduleCount}</span><span class="dm-summary-label">Domaines</span></div>
+            <div class="dm-summary-item"><span class="dm-summary-value">${relCount}</span><span class="dm-summary-label">Relations</span></div>
+        </div>`;
+
+    // Entity cards grouped by module
+    data.modules.forEach(m => {
+        const spec = data.moduleSpecs[m.code] || {};
+        const entities = spec.entities || [];
+        if (entities.length === 0) return;
+
+        html += `<div class="dm-module-group">`;
+        html += `<div class="dm-module-header">
+            <span class="dm-module-name">${m.name || m.code}</span>
+            <span class="dm-module-count">${entities.length} entite${entities.length > 1 ? 's' : ''}</span>
+        </div>`;
+
+        html += `<div class="dm-entity-grid">`;
+        entities.forEach(ent => {
+            const attrs = ent.attributes || [];
+            const rels = ent.relationships || [];
+            html += `
+                <div class="dm-entity-card">
+                    <div class="dm-entity-header">
+                        <span class="dm-entity-name">${ent.name}</span>
+                        <span class="dm-entity-attr-count">${attrs.length} champ${attrs.length > 1 ? 's' : ''}</span>
+                    </div>
+                    ${ent.description ? `<div class="dm-entity-desc">${ent.description}</div>` : ''}
+                    ${attrs.length > 0 ? `
+                    <table class="dm-attr-table">
+                        <thead><tr><th>Champ</th><th>Description</th></tr></thead>
+                        <tbody>
+                            ${attrs.map(a => `<tr><td class="dm-attr-name">${a.name}</td><td class="dm-attr-desc">${a.description || ''}</td></tr>`).join('')}
+                        </tbody>
+                    </table>` : ''}
+                    ${rels.length > 0 ? `
+                    <div class="dm-relations">
+                        <div class="dm-relations-title">Relations</div>
+                        ${rels.map(r => {
+                            const relText = typeof r === 'string' ? r : (r.target + ' (' + r.type + ') - ' + (r.description || ''));
+                            return `<div class="dm-relation-item">${relText}</div>`;
+                        }).join('')}
+                    </div>` : ''}
+                </div>`;
+        });
+        html += `</div></div>`;
+    });
+
+    container.innerHTML = html;
+}
+
 function renderConsolInteractions() {
     const container = document.getElementById('consolInteractions');
     if (!container || data.dependencies.length === 0) return;

package/templates/skills/business-analyse/html/src/styles/05-modules.css

@@ -323,3 +323,68 @@
 }
 .e2e-step-module { font-weight: 600; color: var(--primary-light); font-size: 0.65rem; }
 .e2e-step-action { color: var(--text-bright); }
+
+/* ============================================
+   DATA MODEL (Consolidation)
+   ============================================ */
+.dm-summary {
+    display: flex; gap: 1.5rem; margin-bottom: 1.5rem;
+    padding: 1rem 1.5rem; background: var(--bg-card);
+    border: 1px solid var(--border); border-radius: 10px;
+}
+.dm-summary-item { display: flex; align-items: baseline; gap: 0.4rem; }
+.dm-summary-value { font-size: 1.4rem; font-weight: 700; color: var(--text-bright); }
+.dm-summary-label { font-size: 0.8rem; color: var(--text-muted); }
+.dm-module-group { margin-bottom: 1.5rem; }
+.dm-module-header {
+    display: flex; align-items: center; justify-content: space-between;
+    padding: 0.5rem 0; margin-bottom: 0.75rem;
+    border-bottom: 2px solid var(--primary);
+}
+.dm-module-name { font-weight: 700; color: var(--primary-light); font-size: 1rem; }
+.dm-module-count { font-size: 0.75rem; color: var(--text-muted); }
+.dm-entity-grid {
+    display: grid; grid-template-columns: repeat(auto-fill, minmax(340px, 1fr)); gap: 1rem;
+}
+.dm-entity-card {
+    background: var(--bg-card); border: 1px solid var(--border);
+    border-radius: 10px; overflow: hidden;
+    transition: border-color var(--transition-fast);
+}
+.dm-entity-card:hover { border-color: var(--border-light); }
+.dm-entity-header {
+    display: flex; align-items: center; justify-content: space-between;
+    padding: 0.6rem 0.75rem; background: var(--bg-hover);
+    border-bottom: 1px solid var(--border);
+}
+.dm-entity-name { font-weight: 600; color: var(--text-bright); font-size: 0.95rem; }
+.dm-entity-attr-count {
+    font-size: 0.65rem; color: var(--text-muted);
+    background: rgba(99,102,241,0.1); padding: 0.1rem 0.4rem; border-radius: 4px;
+}
+.dm-entity-desc {
+    padding: 0.5rem 0.75rem; font-size: 0.8rem; color: var(--text-muted);
+    border-bottom: 1px solid var(--border);
+}
+.dm-attr-table { width: 100%; border-collapse: collapse; }
+.dm-attr-table th {
+    text-align: left; font-size: 0.65rem; text-transform: uppercase;
+    letter-spacing: 0.05em; color: var(--text-muted); padding: 0.4rem 0.75rem;
+    border-bottom: 1px solid var(--border); font-weight: 600;
+}
+.dm-attr-table td { padding: 0.35rem 0.75rem; font-size: 0.8rem; border-bottom: 1px solid rgba(51,65,85,0.2); }
+.dm-attr-name { font-weight: 500; color: var(--text-bright); white-space: nowrap; }
+.dm-attr-desc { color: var(--text-muted); }
+.dm-relations {
+    padding: 0.5rem 0.75rem; border-top: 1px solid var(--border);
+    background: rgba(6,182,212,0.03);
+}
+.dm-relations-title {
+    font-size: 0.65rem; text-transform: uppercase; letter-spacing: 0.05em;
+    color: var(--accent); font-weight: 600; margin-bottom: 0.3rem;
+}
+.dm-relation-item {
+    font-size: 0.8rem; color: var(--text); padding: 0.15rem 0;
+    padding-left: 0.75rem; border-left: 2px solid var(--accent);
+    margin-bottom: 0.2rem;
+}

package/templates/skills/business-analyse/html/src/template.html

@@ -96,6 +96,10 @@
                 <!-- Phase 4 : Consolidation -->
                 <div class="nav-group">
                     <div class="nav-group-title">4. Consolidation</div>
+                    <a class="nav-item" onclick="showSection('consol-datamodel')" data-section="consol-datamodel">
+                        <span class="nav-icon">&#9679;</span> Modele de donnees
+                        <span class="nav-badge" id="entityCount">0</span>
+                    </a>
                     <a class="nav-item" onclick="showSection('consol-interactions')" data-section="consol-interactions">
                         <span class="nav-icon">&#9679;</span> Interactions
                     </a>
@@ -500,6 +504,15 @@
                      PHASE 4 : CONSOLIDATION
                      ================================================================ -->
 
+                <!-- SECTION: Modele de donnees -->
+                <div class="section" id="consol-datamodel" style="display:none;">
+                    <h2 class="section-title">Modele de donnees</h2>
+                    <p class="section-subtitle">Vue d'ensemble de toutes les entites metier, leurs attributs et leurs relations entre domaines.</p>
+                    <div id="dataModelContainer">
+                        <p style="color:var(--text-muted);text-align:center;padding:2rem;">Le modele de donnees sera genere a partir des specifications de chaque domaine.</p>
+                    </div>
+                </div>
+
                 <!-- SECTION: Interactions cross-module -->
                 <div class="section" id="consol-interactions" style="display:none;">
                     <h2 class="section-title">Interactions entre domaines</h2>

package/templates/skills/business-analyse/schemas/application-schema.json

@@ -48,6 +48,11 @@
           "const": "interactive",
           "description": "Analysis mode — always interactive (AI listens, reformulates, challenges, validates)"
         },
+        "tablePrefix": {
+          "type": "string",
+          "pattern": "^[a-z]{2,5}_$",
+          "description": "Application table prefix for database tables (e.g., rh_, fi_, crm_). Defined during cadrage, used by all entities in this application."
+        },
         "workflow": {
           "type": "object",
           "description": "Iterative module loop state",

package/templates/skills/business-analyse/schemas/sections/metadata-schema.json

@@ -25,6 +25,7 @@
         "previousVersion": { "type": ["string", "null"] },
         "changeReason": { "type": ["string", "null"] },
         "analysisMode": { "type": "string", "const": "interactive", "description": "Analysis mode — always interactive (AI listens, reformulates, challenges, validates)" },
+        "tablePrefix": { "type": "string", "pattern": "^[a-z]{2,5}_$", "description": "Application table prefix inherited from parent (e.g., rh_, fi_, crm_)" },
         "mcpAvailable": { "type": "boolean" },
         "scope": { "type": "string", "enum": ["application", "module"], "default": "module" },
         "applicationRef": { "type": ["string", "null"], "description": "Parent application feature ID (FEAT-XXX)" },

package/templates/skills/business-analyse/steps/step-01-cadrage.md

@@ -241,6 +241,49 @@ Use these techniques:
 
 Ask challenge questions via AskUserQuestion (1-2 batches of max 4).
 
+#### 4d-bis. Entity Sourcing Pattern (MANDATORY for detected dependencies)
+
+> **When the analysis detects a referenced entity/concept (e.g., "Projets" referenced by activities, "Clients" referenced by orders), ALWAYS ask how this entity is sourced.**
+> This question detects potential new modules that were not mentioned in the original brief.
+
+For EACH referenced entity/concept detected during phases 2-4 that is NOT already covered by an identified module:
+
+Ask via AskUserQuestion:
+```
+question: "{language == 'fr'
+  ? 'Les {entity_plural} auxquel(le)s les {parent_entity_plural} sont lié(e)s : comment sont-ils gérés ?'
+  : 'The {entity_plural} that {parent_entity_plural} are linked to: how are they managed?'}"
+header: "{entity_name}"
+options:
+  - label: "{language == 'fr' ? 'Gérés dans l\'app' : 'Managed in app'}"
+    description: "{language == 'fr'
+      ? 'Les {entity_plural} sont créés et gérés dans cette application (liste simple)'
+      : '{entity_plural} are created and managed in this application (simple list)'}"
+  - label: "{language == 'fr' ? 'Nouveau module dédié' : 'New dedicated module'}"
+    description: "{language == 'fr'
+      ? 'Les {entity_plural} méritent leur propre module avec CRUD complet, permissions et navigation'
+      : '{entity_plural} deserve their own module with full CRUD, permissions and navigation'}"
+  - label: "{language == 'fr' ? 'Système externe' : 'External system'}"
+    description: "{language == 'fr'
+      ? 'Les {entity_plural} viennent d\'un autre système (import ou API)'
+      : '{entity_plural} come from another system (import or API)'}"
+  - label: "{language == 'fr' ? 'Liste simple en config' : 'Simple config list'}"
+    description: "{language == 'fr'
+      ? 'Juste une liste configurable par l\'admin, pas un module complet'
+      : 'Just a configurable list managed by admin, not a full module'}"
+```
+
+**Processing each answer:**
+
+| Choice | Action |
+|--------|--------|
+| **Gérés dans l'app** | Entity stays as a child/section of the current module. Note in coverageMatrix. |
+| **Nouveau module dédié** | **Add new module to `{pre_analysis}.detected_modules[]`**. Flag for inclusion in decomposition (step-02). Add to `coverageMatrix` as mustHave with anticipated sections (list, detail, create, edit). This module becomes a dependency of the referencing module. |
+| **Système externe** | Flag for integration specification. Add to `coverageMatrix` as integration. Load `questionnaire/05-integrations.md` if not already loaded. |
+| **Liste simple en config** | Entity becomes a lookup/reference table (no dedicated module). Note in coverageMatrix as config data. |
+
+> **CRITICAL:** The "Nouveau module dédié" option is essential for detecting modules not mentioned in the original brief. Without it, complex entities get reduced to simple config lists when they deserve full CRUD management.
+
 #### 4e. Risks & Success Criteria (ALWAYS — from `questionnaire/14-risk-assumptions.md` and `questionnaire/15-success-metrics.md`)
 
 Select the most pertinent questions:
@@ -350,6 +393,45 @@ options:
 IF single-module mode:
   Same role definition but inferred from stakeholders
 
+### 6b. Table Prefix Definition (MANDATORY)
+
+> **Every business application MUST define a table prefix.**
+> This prefix identifies which application a database table belongs to (e.g., `rh_Employees`, `fi_Invoices`).
+
+**Process:**
+
+1. Derive a suggested prefix from the application name:
+   - Use the most recognizable abbreviation (2-5 lowercase letters + `_`)
+   - Examples: HumanResources → `rh_`, SalesManagement → `sales_`, Finance → `fi_`, CRM → `crm_`
+
+2. **Display as markdown** (direct text output):
+
+```
+{language == "fr"
+  ? "### Préfixe de table\n\nToutes les tables de cette application en base de données porteront un préfixe pour identifier leur appartenance.\n\nPréfixe suggéré : **`{suggested_prefix}`**\n\nExemple : `{suggested_prefix}Employees`, `{suggested_prefix}Contracts`"
+  : "### Table Prefix\n\nAll database tables for this application will carry a prefix to identify their ownership.\n\nSuggested prefix: **`{suggested_prefix}`**\n\nExample: `{suggested_prefix}Employees`, `{suggested_prefix}Contracts`"}
+```
+
+3. Ask via AskUserQuestion:
+```
+question: "{language == 'fr' ? 'Ce préfixe de table vous convient-il ?' : 'Does this table prefix work for you?'}"
+header: "Préfixe"
+options:
+  - label: "{language == 'fr' ? 'Oui, parfait' : 'Yes, perfect'}"
+    description: "{language == 'fr' ? 'Utiliser le préfixe suggéré' : 'Use the suggested prefix'}"
+  - label: "{language == 'fr' ? 'Personnaliser' : 'Customize'}"
+    description: "{language == 'fr' ? 'Choisir un autre préfixe (2-5 lettres minuscules + _)' : 'Choose a different prefix (2-5 lowercase letters + _)'}"
+```
+
+4. IF "Customize" → ask for custom prefix via AskUserQuestion (open-ended "Other" option)
+
+5. **Validate the prefix:**
+   - Format: `^[a-z]{2,5}_$` (2-5 lowercase letters followed by underscore)
+   - Must NOT collide with platform prefixes: `auth_`, `nav_`, `usr_`, `ai_`, `cfg_`, `wkf_`, `support_`, `entra_`, `ref_`, `loc_`, `lic_`, `tenant_`
+   - If collision detected → ask the user to choose another prefix
+
+6. Store in `metadata.tablePrefix`
+
 ### 7. Coverage Matrix with Sections & Resources (MANDATORY)
 
 > **ENRICHMENT: The coverage matrix now includes anticipated sections (Level 4) and resources (Level 5).**
@@ -416,6 +498,14 @@ Use ba-writer to enrich master feature.json. **Follow the STRUCTURE CARDS exactl
 See [references/cadrage-structure-cards.md](../references/cadrage-structure-cards.md) for exact JSON formats of: `stakeholders[]`, `applicationRoles[]`, `risks[]`, `acceptanceCriteria[]`, `coverageMatrix[]`, `codebaseContext`.
 
 ```
+ba-writer.enrichSection({
+  featureId: {feature_id},
+  section: "metadata",
+  data: {
+    tablePrefix: "{from Phase 5, section 6b — validated prefix, e.g., rh_}"
+  }
+})
+
 ba-writer.enrichSection({
   featureId: {feature_id},
   section: "cadrage",

package/templates/skills/business-analyse/steps/step-02-decomposition.md

@@ -100,6 +100,10 @@ Display the identified modules as markdown:
 ```
 ## Modules identifiés pour {application_name}
 
+{language == "fr"
+  ? "**Préfixe de table :** `{metadata.tablePrefix}` — toutes les tables de cette application seront préfixées (ex: `{metadata.tablePrefix}Customers`, `{metadata.tablePrefix}Orders`)"
+  : "**Table prefix:** `{metadata.tablePrefix}` — all tables in this application will be prefixed (e.g., `{metadata.tablePrefix}Customers`, `{metadata.tablePrefix}Orders`)"}
+
 | # | Module | Type | Priorité | Complexité | Sections pressenties | Entités |
 |---|--------|------|----------|------------|---------------------|---------|
 | 1 | Customers | data-centric | must | medium | list, detail, create, edit | Customer, Address, Contact |

package/templates/skills/business-analyse/steps/step-03a1-setup.md

@@ -349,6 +349,45 @@ options:
     description: "Pas de référence à {completedModule}"
 ```
 
+#### 5-bis. Unresolved Entity Dependencies (New Module Detection)
+
+> **When an entity reference is detected that does NOT belong to any completed or planned module, apply the Entity Sourcing Pattern from step-01-cadrage (section 4d-bis).**
+
+For each entity referenced by {currentModule} that is NOT covered by any existing/planned module:
+
+```
+question: "{language == 'fr'
+  ? 'Les {entity_plural} référencés par {currentModule} ne font partie d\'aucun module. Comment les gérer ?'
+  : '{entity_plural} referenced by {currentModule} are not part of any module. How should they be managed?'}"
+header: "{entity_name}"
+options:
+  - label: "{language == 'fr' ? 'Dans ce module' : 'In this module'}"
+    description: "{language == 'fr'
+      ? 'Gérer les {entity_plural} comme une section/entité de {currentModule}'
+      : 'Manage {entity_plural} as a section/entity of {currentModule}'}"
+  - label: "{language == 'fr' ? 'Nouveau module dédié' : 'New dedicated module'}"
+    description: "{language == 'fr'
+      ? 'Créer un module complet avec CRUD, permissions et navigation'
+      : 'Create a full module with CRUD, permissions and navigation'}"
+  - label: "{language == 'fr' ? 'Système externe' : 'External system'}"
+    description: "{language == 'fr'
+      ? 'Import ou API depuis un autre système'
+      : 'Import or API from another system'}"
+  - label: "{language == 'fr' ? 'Liste de référence' : 'Reference list'}"
+    description: "{language == 'fr'
+      ? 'Table de lookup configurable par l\'admin'
+      : 'Admin-configurable lookup table'}"
+```
+
+**IF "Nouveau module dédié" is selected:**
+1. Add new module to master `modules[]` via ba-writer (status: "pending", sortOrder: after current module)
+2. Update dependency graph: current module depends on the new module
+3. **WARNING:** The new module will need specification AFTER the current one. Display:
+   ```
+   "⚠ Nouveau module '{entity_name}' ajouté. Il sera spécifié après {currentModule}."
+   ```
+4. Update `metadata.workflow.moduleOrder` to include the new module (inserted after its dependents)
+
 ---
 
 ## NEXT STEP

package/templates/skills/efcore/steps/shared/step-00-init.md

@@ -16,6 +16,61 @@ Detect EF Core project structure, identify DbContext (Core vs Extensions), and l
 
 ## EXECUTION SEQUENCE:
 
+### 0. Ensure dotnet ef Available (Platform-Aware)
+
+> **CRITICAL:** On Windows (Git Bash, MSYS2), `dotnet ef` may not be on the shell PATH
+> even though it's installed. This step fixes PATH before any EF Core command.
+
+```bash
+ensure_dotnet_ef() {
+  # Quick check: already available?
+  if dotnet ef --version &>/dev/null; then
+    DOTNET_EF_VERSION=$(dotnet ef --version 2>/dev/null)
+    echo "dotnet-ef: $DOTNET_EF_VERSION"
+    return 0
+  fi
+
+  echo "dotnet-ef not on PATH, attempting platform-aware fix..."
+
+  # Try all known .NET global tools locations
+  # - $USERPROFILE/.dotnet/tools  → Windows via Git Bash (USERPROFILE=C:\Users\xxx)
+  # - $HOME/.dotnet/tools         → Linux/macOS or Git Bash fallback
+  # - $LOCALAPPDATA/Microsoft/dotnet/tools → Windows alternate location
+  for TOOLS_DIR in \
+    "$USERPROFILE/.dotnet/tools" \
+    "$HOME/.dotnet/tools" \
+    "$LOCALAPPDATA/Microsoft/dotnet/tools"; do
+    if [ -n "$TOOLS_DIR" ] && [ -d "$TOOLS_DIR" ]; then
+      export PATH="$TOOLS_DIR:$PATH"
+      echo "  PATH += $TOOLS_DIR"
+    fi
+  done
+
+  # Verify after PATH fix
+  if dotnet ef --version &>/dev/null; then
+    DOTNET_EF_VERSION=$(dotnet ef --version 2>/dev/null)
+    echo "dotnet-ef: $DOTNET_EF_VERSION (found after PATH fix)"
+    return 0
+  fi
+
+  echo "ERROR: dotnet-ef not available"
+  echo "Install with: dotnet tool install --global dotnet-ef"
+  echo ""
+  echo "If installed but not found, check:"
+  echo "  Windows: %USERPROFILE%\\.dotnet\\tools must be in PATH"
+  echo "  Linux:   ~/.dotnet/tools must be in PATH"
+  exit 1
+}
+
+ensure_dotnet_ef
+```
+
+**IMPORTANT — WSL pitfall:**
+If the shell resolves `$HOME` to `/home/{user}` (WSL path) instead of `/c/Users/{user}` (Git Bash),
+the .NET SDK may not be found even if `dotnet-ef` is. Use `$USERPROFILE` first on Windows.
+
+---
+
 ### 1. Detect EF Core Project
 
 ```bash

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

@@ -115,6 +115,7 @@ LOAD → GENERATE → COMPILE → TEST → [FAIL?] → FIX → RE-TEST → [PASS
 | `references/category-rules.md` | Step-02 and compact loop (execution rules per category) |
 | `references/compact-loop.md` | Step-04 section 5 (inline execution after first iteration) |
 | `references/core-seed-data.md` | Infrastructure task with seed data keywords |
+| `references/error-classification.md` | Build failure in compact loop or validation (error diagnosis) |
 | `references/team-orchestration.md` | Step-00 when multi-module detected (2+ PRDs) |
 </step_files>