@atlashub/smartstack-cli 3.5.0 → 3.6.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@atlashub/smartstack-cli",
-  "version": "3.5.0",
+  "version": "3.6.0",
   "description": "SmartStack Claude Code automation toolkit - GitFlow, EF Core migrations, prompts and more",
   "author": {
     "name": "SmartStack",

package/templates/skills/business-analyse/SKILL.md

@@ -15,7 +15,8 @@ The skill auto-detects which use case applies by scanning existing features in `
 
 **Architecture highlights:**
 - Conditional context loading: each step loads only the shared files it needs (~54% context reduction)
-- Split long steps for reliability: 03→03a+03b, 05→05a+05b with self-verification at transitions
+- 12 granular steps (1-2 responsibilities each, 200-500 lines) for maximum LLM attention quality
+- Self-verification at every step transition, POST-CHECKs on critical outputs
 - Templates and references extracted to separate files, loaded on demand
 </objective>
 
@@ -94,12 +95,16 @@ When step-00 detects that the description matches an existing application:
 - **Step 00:** Detection, scan existing, create master feature.json (draft)
 - **Step 01:** Cadrage: context, stakeholders, scope, application roles (framed)
 - **Step 02:** Decomposition: modules, dependencies, client checkpoint (decomposed)
-- **Step 03a:** Interactive specification per module: sections, wireframes, entities, BR, use cases
-- **Step 03b:** Compilation: write spec to feature.json, validate, deploy HTML, loop decision
-  - Loop: 03a → 03b → 03a (next module) until all specified (specified)
+- **Step 03a:** Per-module data: sections, entities, business rules, questionnaires
+- **Step 03b:** Per-module UI: state machines, wireframes, layouts, dashboards
+- **Step 03c:** Per-module compile: actors, UCs, FRs, permissions, navigation, seed data, i18n
+- **Step 03d:** Per-module validate: completeness checks, write feature.json, incremental HTML, loop
+  - Loop: 03a → 03b → 03c → 03d → 03a (next module) until all specified (specified)
 - **Step 04:** Cross-module consolidation (consolidated)
-- **Step 05a:** Build handoff data: file mapping, BR-to-code, API summary, write to feature.json
-- **Step 05b:** Deploy artifacts: prd.json, progress.txt, HTML, manifest (handed-off)
+- **Step 05a:** Handoff strategy: file mapping (7 categories)
+- **Step 05b:** Handoff mapping: BR-to-code, API summary, write to feature.json
+- **Step 05c:** Deploy artifacts: prd.json, progress.txt, manifest
+- **Step 05d:** Deploy interactive HTML: ba-interactive.html pre-populated (handed-off)
   - Display completion summary with `/ralph-loop -r` command
   - User reviews deliverables with stakeholders before launching development
 
@@ -122,6 +127,7 @@ When step-00 detects that the description matches an existing application:
 | `{module_name}`         | string  | Target module name                                     |
 | `{context}`             | string  | Always "business" for BA                               |
 | `{workflow_mode}`       | string  | "application" or "module"                              |
+| `{vibe_coding}`         | boolean | `true` if developer builds with AI assistance (accelerated questionnaire) |
 | `{docs_dir}`            | string  | `docs/business/{app}/{module}/business-analyse/v{X.Y}/` |
 
 </state_variables>
@@ -137,14 +143,18 @@ When step-00 detects that the description matches an existing application:
 
 | Step | File                              | Model  | Purpose                                              |
 | ---- | --------------------------------- | ------ | ---------------------------------------------------- |
-| 00   | `steps/step-00-init.md`           | Haiku  | Auto-detect new/update, scan existing, create master feature.json |
+| 00   | `steps/step-00-init.md`           | Sonnet | Auto-detect new/update, scan existing, create master feature.json |
 | 01   | `steps/step-01-cadrage.md`        | Opus   | Framing: context, stakeholders, scope, application roles |
-| 02   | `steps/step-02-decomposition.md`  | Sonnet | Module decomposition, dependency graph, client checkpoint |
-| 03a  | `steps/step-03a-specify.md`       | Opus   | Per-module specification: interactive phase (sections, entities, BR, wireframes, use cases) |
-| 03b  | `steps/step-03b-compile.md`       | Opus   | Per-module compilation: write spec, validate, HTML deploy, loop decision |
-| 04   | `steps/step-04-consolidation.md`  | Sonnet | Cross-module validation, E2E flows, permissions coherence |
-| 05a  | `steps/step-05a-handoff.md`       | Sonnet | Build handoff data, write to module + master feature.json |
-| 05b  | `steps/step-05b-deploy.md`        | Sonnet | Generate prd.json, progress.txt, deploy HTML, manifest, user choice |
+| 02   | `steps/step-02-decomposition.md`  | Opus   | Module decomposition, dependency graph, client checkpoint |
+| 03a  | `steps/step-03a-data.md`          | Opus   | Per-module: sections, entities, BRs, questionnaires |
+| 03b  | `steps/step-03b-ui.md`            | Opus   | Per-module: state machines, wireframes, layouts, dashboards |
+| 03c  | `steps/step-03c-compile.md`       | Opus   | Per-module: actors, UCs, FRs, permissions, nav, seed data, i18n |
+| 03d  | `steps/step-03d-validate.md`      | Sonnet | Per-module: validation, write, incremental HTML, loop decision |
+| 04   | `steps/step-04-consolidation.md`  | Opus   | Cross-module validation, E2E flows, permissions coherence |
+| 05a  | `steps/step-05a-handoff.md`       | Sonnet | Handoff strategy, file mapping (7 categories) |
+| 05b  | `steps/step-05b-mapping.md`       | Sonnet | BR-to-code mapping, API summary, write handoff |
+| 05c  | `steps/step-05c-deploy.md`        | Sonnet | Generate prd.json, progress.txt, manifest, summary |
+| 05d  | `steps/step-05d-html.md`          | Sonnet | Deploy ba-interactive.html pre-populated with all data |
 
 </step_files>
 
@@ -188,7 +198,8 @@ Load ONLY relevant categories based on feature type:
 | spec     | `templates/tpl-frd.md`              | 02           |
 | handoff  | `templates/tpl-handoff.md`          | 04           |
 | suggestions | `patterns/suggestion-catalog.md` | 01           |
-| interactive | `html/ba-interactive.html`        | 03b (incremental), 05b (final deploy)  |
+| interactive | `html/ba-interactive.html`        | 03d (incremental), 05d (final deploy)  |
+| mapping    | `references/html-data-mapping.md`  | 03d, 05d (FEATURE_DATA + EMBEDDED_ARTIFACTS mapping) |
 
 </template_files>
 
@@ -197,7 +208,7 @@ Load ONLY relevant categories based on feature type:
 - **Load one step at a time** - Only load the current step file
 - **Load shared files conditionally** - Each step loads only the _shared files it needs (see step headers)
 - **Reference files on demand** - Templates and mappings in references/ and templates/ are loaded only when needed
-- **ULTRATHINK** for steps 01, 02, 04 (critical thinking)
+- **ULTRATHINK** for steps 01, 02, 03a-03c, 04 (critical thinking)
 - **State persisted in feature.json** (NOT markdown files)
 - **Use ba-writer agent** for all JSON writes
 - **Use ba-reader agent** for all JSON reads

package/templates/skills/business-analyse/_architecture.md

@@ -1,6 +1,6 @@
 # Business Analysis - SmartStack Architecture Reference (_architecture.md)
 
-> **Loaded by:** step-01-cadrage, step-03a-specify, step-05a-handoff
+> **Loaded by:** step-01-cadrage, step-03a-data, step-05a-handoff, step-05b-mapping
 > **Purpose:** Provide architectural context for relevant questions and aligned recommendations
 
 ---

package/templates/skills/business-analyse/_elicitation.md

@@ -1,6 +1,6 @@
 # Business Analysis - Elicitation & Interaction (_elicitation.md)
 
-> **Loaded by:** step-01-cadrage, step-03a-specify
+> **Loaded by:** step-01-cadrage, step-03a-data
 > **Purpose:** Interactive questioning techniques, AskUserQuestion formatting, ULTRATHINK mode
 
 ---

package/templates/skills/business-analyse/_module-loop.md

@@ -1,6 +1,6 @@
 # Business Analysis - Module Loop Protocol (_module-loop.md)
 
-> **Loaded by:** step-03a-specify, step-03b-compile
+> **Loaded by:** step-03a-data, step-03b-ui, step-03c-compile, step-03d-validate
 > **Purpose:** State management and iteration logic for multi-module specification loop
 
 ---
@@ -31,7 +31,7 @@
      currentModule = moduleOrder[currentModuleIndex]
      Write master feature.json
      Display: "Module {name} complete. Next: {next_name} ({N}/{total})"
-     RE-LOAD: steps/step-03a-specify.md
+     RE-LOAD: steps/step-03a-data.md
 4. ELSE:
      master.status = "specified"
      Load: steps/step-04-consolidation.md
@@ -50,7 +50,7 @@ To prevent context explosion as modules accumulate:
 1. ba-reader.findApplicationFeature() -> locate master feature.json
 2. Read metadata.workflow.currentModuleIndex
 3. IF currentModule has a feature.json with status != "validated":
-     Resume step-03a-specify for that module
+     Resume step-03a-data for that module
 4. ELSE:
-     Start step-03a-specify for next module
+     Start step-03a-data for next module
 ```

package/templates/skills/business-analyse/html/ba-interactive.html

@@ -996,10 +996,10 @@
                     <a class="nav-item active" onclick="showSection('cadrage-problem')" data-section="cadrage-problem">
                         <span class="nav-icon">&#9679;</span> Probleme a resoudre
                     </a>
-                    <a class="nav-item" onclick="showSection('cadrage-current')" data-section="cadrage-current">
+                    <a class="nav-item" onclick="showSection('cadrage-current')" data-section="cadrage-current" data-vibe-hide>
                         <span class="nav-icon">&#9679;</span> Situation actuelle
                     </a>
-                    <a class="nav-item" onclick="showSection('cadrage-vision')" data-section="cadrage-vision">
+                    <a class="nav-item" onclick="showSection('cadrage-vision')" data-section="cadrage-vision" data-vibe-hide>
                         <span class="nav-icon">&#9679;</span> Situation souhaitee
                     </a>
                     <a class="nav-item" onclick="showSection('cadrage-stakeholders')" data-section="cadrage-stakeholders">
@@ -1073,12 +1073,12 @@
                         <div class="editable" contenteditable="true" data-field="problem.description" data-placeholder="Decrivez le probleme que vous rencontrez aujourd'hui. Qu'est-ce qui ne fonctionne pas, ou pas assez bien ?"></div>
                     </div>
 
-                    <div class="card">
+                    <div class="card" data-vibe-hide>
                         <div class="card-label">Qui est le plus impacte ?</div>
                         <div class="editable" contenteditable="true" data-field="problem.impactedPeople" data-placeholder="Quelles personnes souffrent le plus de ce probleme au quotidien ? Quel impact sur leur travail ?"></div>
                     </div>
 
-                    <div class="card">
+                    <div class="card" data-vibe-hide>
                         <div class="card-label">Depuis quand ce probleme existe-t-il ?</div>
                         <div class="editable" contenteditable="true" data-field="problem.history" data-placeholder="Depuis combien de temps ce probleme existe-t-il ? A-t-il empire recemment ?"></div>
                     </div>
@@ -1088,14 +1088,14 @@
                         <div class="editable" contenteditable="true" data-field="problem.trigger" data-placeholder="Qu'est-ce qui a declenche cette demande maintenant ? Pourquoi pas il y a 6 mois ?"></div>
                     </div>
 
-                    <div class="card">
+                    <div class="card" data-vibe-hide>
                         <div class="card-label">Consequences si le projet n'est pas realise</div>
                         <div class="editable" contenteditable="true" data-field="problem.consequences" data-placeholder="Que se passerait-il si ce projet n'etait PAS realise ? Quelles consequences a court et moyen terme ?"></div>
                     </div>
                 </div>
 
                 <!-- SECTION: Situation actuelle -->
-                <div class="section" id="cadrage-current" style="display:none;">
+                <div class="section" id="cadrage-current" style="display:none;" data-vibe-hide>
                     <h2 class="section-title">Situation actuelle</h2>
                     <p class="section-subtitle">Comment les choses se passent aujourd'hui, concretement.</p>
 
@@ -1124,7 +1124,7 @@
                 </div>
 
                 <!-- SECTION: Situation souhaitee -->
-                <div class="section" id="cadrage-vision" style="display:none;">
+                <div class="section" id="cadrage-vision" style="display:none;" data-vibe-hide>
                     <h2 class="section-title">Situation souhaitee</h2>
                     <p class="section-subtitle">Ce que le client veut obtenir, pas ce qu'il veut construire.</p>
 
@@ -1309,17 +1309,17 @@
                         <div class="editable" contenteditable="true" data-field="success.definition" data-placeholder="Comment saurez-vous que le projet est un succes ? Quel changement concret observerez-vous ?"></div>
                     </div>
 
-                    <div class="card">
+                    <div class="card" data-vibe-hide>
                         <div class="card-label">Objectifs mesurables</div>
                         <div class="editable" contenteditable="true" data-field="success.metrics" data-placeholder="Quels chiffres presenteriez-vous a votre direction pour prouver le succes ? (temps, erreurs, satisfaction...)"></div>
                     </div>
 
-                    <div class="card">
+                    <div class="card" data-vibe-hide>
                         <div class="card-label">Delai d'evaluation</div>
                         <div class="editable" contenteditable="true" data-field="success.timeline" data-placeholder="Au bout de combien de temps pourrez-vous juger si ca fonctionne ? 1 semaine ? 1 mois ? 3 mois ?"></div>
                     </div>
 
-                    <div class="card">
+                    <div class="card" data-vibe-hide>
                         <div class="card-label">Conditions minimales de mise en service</div>
                         <div class="editable" contenteditable="true" data-field="success.minimumConditions" data-placeholder="Quelles conditions minimales pour mettre le systeme en service ? (fonctionnalites presentes, donnees migrees, formation faite...)"></div>
                     </div>
@@ -1540,6 +1540,31 @@
     data.customRoles = data.customRoles || [];
     data.customActions = data.customActions || [];
     data.cadrage.criteria = data.cadrage.criteria || [];
+    data.cadrage.risks = data.cadrage.risks || [];
+    data.consolidation = data.consolidation || {};
+    data.consolidation.e2eFlows = data.consolidation.e2eFlows || [];
+
+    // Defensive mapping: globalScope (feature.json format) → scope (HTML format)
+    // Handles cases where FEATURE_DATA contains raw globalScope instead of pre-mapped scope
+    if (!data.cadrage.scope || (!data.cadrage.scope.vital?.length && data.cadrage.globalScope)) {
+        const gs = data.cadrage.globalScope || {};
+        data.cadrage.scope = {
+            vital: (gs.mustHave || []).map(s => typeof s === 'string' ? { name: s, description: '' } : s),
+            important: (gs.shouldHave || []).map(s => typeof s === 'string' ? { name: s, description: '' } : s),
+            optional: (gs.couldHave || []).map(s => typeof s === 'string' ? { name: s, description: '' } : s),
+            excluded: (gs.outOfScope || []).map(s => typeof s === 'string' ? { name: s, description: '' } : s)
+        };
+    }
+    data.cadrage.scope = data.cadrage.scope || { vital: [], important: [], optional: [], excluded: [] };
+
+    // Defensive init: moduleSpecs (may be missing if LLM didn't follow mapping)
+    data.moduleSpecs = data.moduleSpecs || {};
+
+    // Vibe coding mode: hide non-relevant sections
+    const isVibeCoding = data.metadata?.vibeCoding === true;
+    if (isVibeCoding) {
+        document.querySelectorAll('[data-vibe-hide]').forEach(el => el.style.display = 'none');
+    }
 
     /* ============================================
        INITIALIZATION
@@ -1547,6 +1572,10 @@
     document.addEventListener('DOMContentLoaded', function() {
         loadFromLocalStorage();
         initEditableFields();
+        // Re-apply vibe hiding after DOM init (in case loadFromLocalStorage changed data)
+        if (isVibeCoding) {
+            document.querySelectorAll('[data-vibe-hide]').forEach(el => el.style.display = 'none');
+        }
         renderStakeholders();
         renderScope();
         renderRisks();

package/templates/skills/business-analyse/questionnaire/06-security.md

@@ -44,7 +44,7 @@
 > - Les rôles identifiés en Q6.1-Q6.4 sont des **ensembles de permissions**, pas des données métier
 > - L'accès est contrôlé par des permissions attribuées aux rôles, pas par des propriétés d'entité
 > - Ne jamais proposer de créer une entité `Role`, `UserRole`, ou un attribut `User.Role`
-> - Le mapping rôle → permissions se fait dans la **Permission Matrix** (step-03a-specify)
+> - Le mapping rôle → permissions se fait dans la **Permission Matrix** (step-03c-compile)
 
 ## Elicitation Guide
 

package/templates/skills/business-analyse/questionnaire.md

@@ -1,6 +1,6 @@
 # Elicitation Questionnaire - Business Analysis
 
-> **Usage:** Structured questions for step-01-cadrage and step-03a-specify
+> **Usage:** Structured questions for step-01-cadrage and step-03a-data
 > **Standard:** BABOK v3 - Elicitation Techniques (VibeCoding-focused)
 > **Model:** OPUS with ULTRATHINK
 > **Total:** ~68 targeted questions (dev-relevant only)
@@ -284,7 +284,7 @@
 | Phase | Categories utilisees |
 |-------|---------------------|
 | step-01-cadrage | 00 (si mode application), 01, 02, 03, 14, 15 + conditionnelles (05, 06, 08, 09, 10) |
-| step-03a-specify (par module) | 04, 07, 11, 12, 13 (chargees par module) |
+| step-03a-data (par module) | 04, 07, 11, 12, 13 (chargees par module) |
 
 ### Phase de cadrage
 

package/templates/skills/business-analyse/react/components.md

@@ -1,7 +1,7 @@
 # React Components - Business Analyse Viewer
 
 > **Usage:** React component that renders feature.json directly
-> **Loaded in:** step-05b-deploy.md
+> **Loaded in:** step-05d-html.md
 > **Data source (module):** `docs/business/{app}/{module}/business-analyse/v{X.Y}/feature.json`
 > **Data source (application):** `docs/business/{app}/business-analyse/v{X.Y}/feature.json`
 > **Related:** `react/application-viewer.md` for application-level view

package/templates/skills/business-analyse/react/schema.md

@@ -1,7 +1,7 @@
 # TypeScript Schema - Feature JSON Types
 
 > **Usage:** TypeScript interfaces aligned with feature-schema.json and application-schema.json
-> **Loaded in:** step-05b-deploy.md (for web app rendering)
+> **Loaded in:** step-05d-html.md (for web app rendering)
 > **Source (module):** `docs/business/{app}/{module}/business-analyse/v{X.Y}/feature.json`
 > **Source (application):** `docs/business/{app}/business-analyse/v{X.Y}/feature.json`
 

package/templates/skills/business-analyse/references/html-data-mapping.md

@@ -1,6 +1,6 @@
 # HTML Data Mapping Reference (references/html-data-mapping.md)
 
-> **Used by:** step-05b-deploy (section 3: Deploy Interactive HTML Document)
+> **Used by:** step-05d-html (Deploy Interactive HTML), step-03d-validate (incremental HTML)
 > **Purpose:** Exact mapping from feature.json to HTML FEATURE_DATA and EMBEDDED_ARTIFACTS objects
 
 ---
@@ -16,7 +16,8 @@ Build a JSON object following this **exact mapping** from feature.json to the HT
     applicationId: master.id,                           // e.g. "FEAT-001"
     version: master.version,                            // e.g. "1.0"
     createdAt: master.metadata.createdAt,
-    lastModified: master.metadata.updatedAt
+    lastModified: master.metadata.updatedAt,
+    vibeCoding: master.metadata.vibeCoding || false      // true if vibe coding mode
   },
   cadrage: {
     problem: {
@@ -282,7 +283,7 @@ EMBEDDED_ARTIFACTS.dependencyGraph = {
 
 ---
 
-## Usage in step-05b-deploy
+## Usage in step-05d-html
 
 1. Serialize the FEATURE_DATA object as JSON (with 2-space indentation for readability)
 2. Serialize the EMBEDDED_ARTIFACTS object as JSON (with 2-space indentation)

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

@@ -43,7 +43,7 @@
     }
   },
 
-  "$comment": "Sub-schema loading guide per BA step: step-00-init → metadata-schema.json | step-01-cadrage → discovery-schema.json (module) OR application-schema.json (master) | step-02-decomposition → application-schema.json (modules[], dependencyGraph) | step-03a-specify → analysis-schema.json | step-03b-compile → specification-schema.json | step-04-consolidation → validation-schema.json + application-schema.json (consolidation) | step-05a-handoff → handoff-schema.json | step-05b-deploy → (artifacts only)",
+  "$comment": "Sub-schema loading guide per BA step: step-00-init → metadata-schema.json | step-01-cadrage → discovery-schema.json (module) OR application-schema.json (master) | step-02-decomposition → application-schema.json (modules[], dependencyGraph) | step-03a-data → analysis-schema.json | step-03b-ui → specification-schema.json (wireframes, layouts) | step-03c-compile → specification-schema.json | step-03d-validate → validation-schema.json | step-04-consolidation → validation-schema.json + application-schema.json (consolidation) | step-05a-handoff → handoff-schema.json | step-05b-mapping → handoff-schema.json (brToCodeMapping, apiEndpointSummary) | step-05c-deploy → (prd, progress, manifest) | step-05d-html → (ba-interactive.html)",
 
   "$defs": {
     "stepStatus": { "$ref": "shared/common-defs.json#/$defs/stepStatus" },

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

@@ -2,7 +2,7 @@
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "$id": "analysis-schema.json",
   "title": "SmartStack BA - Analysis",
-  "description": "Module-level analysis: objectives, business rules, entities, process flows, integrations, data lifecycle. Enriched by step-03a-specify.",
+  "description": "Module-level analysis: objectives, business rules, entities, process flows, integrations, data lifecycle. Enriched by step-03a-data.",
   "type": "object",
   "properties": {
     "objectives": {

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

@@ -24,6 +24,7 @@
         "permissionBase": { "type": "string", "description": "e.g., business.sales.orders" },
         "previousVersion": { "type": ["string", "null"] },
         "changeReason": { "type": ["string", "null"] },
+        "vibeCoding": { "type": "boolean", "default": false, "description": "True if project is built in vibe coding mode (developer + AI)" },
         "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/schemas/sections/specification-schema.json

@@ -2,7 +2,7 @@
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "$id": "specification-schema.json",
   "title": "SmartStack BA - Specification",
-  "description": "Module-level specification: actors, use cases, FRs, permissions, navigation, wireframes, dashboards, sections, resources. Enriched by step-03b-compile.",
+  "description": "Module-level specification: actors, use cases, FRs, permissions, navigation, wireframes, dashboards, sections, resources. Enriched by step-03c-compile.",
   "type": "object",
   "properties": {
     "actors": {

package/templates/skills/business-analyse/steps/step-00-init.md

@@ -1,6 +1,7 @@
 ---
 name: step-00-init
 description: Initialize Business Analysis - Auto-detect new/update, create feature.json
+model: sonnet
 next_step: steps/step-01-cadrage.md
 ---
 
@@ -180,6 +181,31 @@ Ask via AskUserQuestion:
 language: string (code, e.g., "en", "fr")
 ```
 
+## Step 5b: Detect Development Mode
+
+Determine if the project will be built in **vibe coding** mode (developer + AI) or by a human development team.
+
+```
+Ask via AskUserQuestion:
+  question: "Comment allez-vous developper ce projet ?"
+  header: "Mode dev"
+  options:
+    - label: "Vibe coding (avec IA)"
+      description: "Je developpe moi-meme avec l'aide de l'IA — questionnaire allege"
+    - label: "Equipe de developpement"
+      description: "Une equipe humaine va developper — analyse complete"
+
+IF user selects "Vibe coding (avec IA)":
+  vibe_coding = true
+ELSE:
+  vibe_coding = false
+```
+
+**Store:**
+```yaml
+vibe_coding: boolean
+```
+
 ## Step 6: Generate Feature ID
 
 Create a unique feature identifier.
@@ -300,6 +326,7 @@ ba-writer.createApplicationFeature({
     language: {language},
     featureDescription: {feature_description},
     workflowType: {workflow_type},
+    vibeCoding: {vibe_coding},
     mcpAvailable: true,
     workflow: {
       mode: "application",
@@ -350,6 +377,7 @@ Update `.business-analyse/config.json` with new feature information.
 | Language           | {language}                                   |
 | Version            | {version}                                    |
 | MCP Available      | true                                         |
+| Dev Mode           | {vibe_coding ? "Vibe coding" : "Standard"}   |
 
 NEXT STEP: step-01-cadrage
 ═══════════════════════════════════════════════════════════════
@@ -369,6 +397,7 @@ language: string
 docs_dir: string
 mcp_available: boolean
 workflow_mode: "application"
+vibe_coding: boolean
 version: string
 ```