@atlashub/smartstack-cli 3.0.0 → 3.2.0

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

@@ -315,18 +315,23 @@ Chaque question conservee passe ce test :
 
 | Categorie | Questions | Phase | Focus |
 |-----------|-----------|-------|-------|
-| 0. Identite de l'application | 8 | step-01 (mode application) | Nom, domaines, profils |
-| 1. Contexte metier | 12 | step-01 | Probleme, situation actuelle, vision, declencheur |
-| 2. Parties prenantes | 14 | step-01 | Utilisateurs, taches, acces, changement |
-| 3. Perimetre fonctionnel | 12 | step-01 | Priorites, parcours, besoins transversaux |
-| 4. Donnees | 8 | step-03 (par module) | Entites et regles |
-| 5. Integrations | 8 | step-01 (conditionnel) | Systemes et flux |
-| 6. Securite et acces | 8 | step-01 (conditionnel) | Permissions et restrictions |
-| 7. Interface utilisateur | 8 | step-03 (par module) | Ecrans et experience |
-| 8. Performance et qualite | 4 | step-01 (conditionnel) | Temps de reponse et tests |
-| 9. Contraintes | 4 | step-01 (conditionnel) | Technologies et dependances |
-| 10. Documentation | 4 | step-01 (conditionnel) | Guides et formation |
-| 14. Risques et hypotheses | 8 | step-01 | Risques, hypotheses, lecons du passe |
-| 15. Criteres de reussite | 8 | step-01 | Indicateurs de succes, conditions d'acceptation |
-| **Total noyau** | **~86** | | |
-| 11-13 (conditionnel) | ~24 | step-03 (par module) | Cycle de vie, migration, impact inter-modules |
+| 0. Identite de l'application | 18 | step-01 (mode application) | Nom, domaines, profils |
+| 1. Contexte metier | 32 | step-01 | Probleme, situation actuelle, vision, declencheur |
+| 2. Parties prenantes | 33 | step-01 | Utilisateurs, taches, acces, changement |
+| 3. Perimetre fonctionnel | 32 | step-01 | Priorites, parcours, besoins transversaux |
+| 4. Donnees | 15 | step-03 (par module) | Entites et regles |
+| 5. Integrations | 14 | step-01 (conditionnel) | Systemes et flux |
+| 6. Securite et acces | 13 | step-01 (conditionnel) | Permissions et restrictions |
+| 7. Interface utilisateur | 19 | step-03 (par module) | Ecrans et experience |
+| 8. Performance et qualite | 8 | step-01 (conditionnel) | Temps de reponse et tests |
+| 9. Contraintes | 6 | step-01 (conditionnel) | Technologies et dependances |
+| 10. Documentation | 7 | step-01 (conditionnel) | Guides et formation |
+| 11. Cycle de vie donnees | 14 | step-03 (conditionnel) | Retention, archivage, RGPD |
+| 12. Migration et transition | 14 | step-03 (conditionnel) | Donnees existantes, cutover |
+| 13. Impact inter-modules | 14 | step-03 (conditionnel) | Dependances, evenements |
+| 14. Risques et hypotheses | 16 | step-01 | Risques, hypotheses, lecons du passe |
+| 15. Criteres de reussite | 17 | step-01 | Indicateurs de succes, conditions d'acceptation |
+| **Total noyau (01-03, 14-15)** | **130** | | **Toujours charges** |
+| **Total avec app (00)** | **148** | | **Si mode application** |
+| **Total conditionnel (04-13)** | **124** | | **Selon contexte** |
+| **Total maximum possible** | **272** | | **Noyau + app + tous conditionnels** |

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

@@ -37,7 +37,6 @@ question_mode: false
 refactor_mode: false
 micro_mode: false
 extract_mode: false
-interactive_mode: false
 application_mode: false    # Multi-module application analysis
 ```
 
@@ -52,7 +51,6 @@ application_mode: false    # Multi-module application analysis
 | `-q` | `--question` | Question mode | next arg = FEAT-ID, remaining = question text |
 | `-r` | `--refactor` | Refactoring mode | next arg = FEAT-ID, remaining = change description |
 | `-m` | `--micro` | Micro feature mode | none |
-| `-i` | `--interactive` | Interactive mode | none |
 | `-x` | `--extract` | Extract mode: import from interactive HTML export | next arg = JSON file path |
 | `-app` | `--application` | Application mode: multi-module analysis | none |
 
@@ -232,25 +230,7 @@ mcp__smartstack__validate_conventions({ checks: ["tables"] })
 **DO NOT** continue to Step 4 or any subsequent step.
 **STOP the skill immediately.**
 
-## Step 4: Interactive Mode
-
-If `-i` or `--interactive` flag is set, prompt for confirmation.
-
-**Prompt:**
-```
-Confirm initialization with:
-- Use Case: {use_case}
-- Application: {application_name}
-- Module: {module_name}
-- Auto Mode: {auto_mode}
-- Economy Mode: {economy_mode}
-
-Continue? (y/n)
-```
-
-If 'n', EXIT.
-
-## Step 5: Validate Business Context
+## Step 4: Validate Business Context
 
 Verify that the business context is properly configured.
 
@@ -275,23 +255,27 @@ Verify that the business context is properly configured.
 }
 ```
 
-## Step 6: Determine Application and Module
+## Step 5: Determine Application and Module
 
 Scan for existing applications and modules.
 
-**Scan order:**
-1. Primary: `docs/business/` (modern structure)
-   - List subdirectories = applications
-   - Inside each app, list subdirectories = modules
-2. Fallback: `.business-analyse/business/` (legacy)
-   - Same structure as above
+**Scan location:** `docs/business/` (modern structure only)
+
+```
+1. List subdirectories in `docs/business/` = applications
+2. For each app, list subdirectories = modules
+3. IF no applications found:
+     Will create new under docs/business/
+```
+
+**Legacy structure (`.business-analyse/business/`) is NO LONGER SUPPORTED.**
 
 **Logic:**
 ```
 IF auto_mode = true:
   application_name = first found app OR "default"
   module_name = first found module OR "default"
-ELSE (interactive):
+ELSE:
   Prompt: "Select application: [list]"
   Prompt: "Select module: [list]"
   OR: "Create new application: {name}"
@@ -304,7 +288,7 @@ application_name: string
 module_name: string
 ```
 
-## Step 7: Select Language
+## Step 6: Select Language
 
 Determine the language for analysis and code generation.
 
@@ -312,13 +296,15 @@ Determine the language for analysis and code generation.
 - Retrieve `businessContext.language` from config
 - Default: "en" (English)
 
-**If interactive:**
+**If not in config OR auto_mode = false:**
 ```
-Select language:
-[ ] English (en)
-[ ] French (fr)
-[ ] Spanish (es)
-[ ] Custom: {input}
+Ask via AskUserQuestion:
+  question: "Select language for analysis"
+  header: "Language"
+  options:
+    - label: "English (en)"
+    - label: "French (fr)"
+    - label: "Spanish (es)"
 ```
 
 **Store:**
@@ -326,7 +312,7 @@ Select language:
 language: string (code, e.g., "en", "fr")
 ```
 
-## Step 8: Generate Feature ID
+## Step 7: Generate Feature ID
 
 Create a unique feature identifier.
 
@@ -345,7 +331,7 @@ ELSE:
 feature_id: string
 ```
 
-## Step 9: Create Output Directory Structure
+## Step 8: Create Output Directory Structure
 
 Create the directory hierarchy for feature documentation.
 
@@ -370,20 +356,35 @@ docs_dir: "docs/business/{app}/{module}/business-analyse/v{version}"
 output_dir: same as docs_dir
 ```
 
-## Step 9-bis: Deploy JSON Schemas to Project (MANDATORY)
+## Step 8-bis: Deploy JSON Schemas to Project (MANDATORY)
 
 > **The JSON Schemas MUST be present in the project alongside the generated feature.json files.**
 > Without schemas, feature.json files cannot be validated and have no structural reference.
 
-**Check if schemas already deployed:**
+**Performance optimization:** Use cache file to avoid redundant deployments.
+
+### Cache-based deployment logic:
+
+**Step 1: Check deployment cache**
+
+Cache file location: `docs/business/{app}/business-analyse/.schema-cache.json`
+
 ```
-IF EXISTS docs/business/{app}/business-analyse/schemas/feature-schema.json:
-  Skip deployment (schemas already present)
+IF EXISTS docs/business/{app}/business-analyse/.schema-cache.json:
+  Read cache file
+  IF cache.version == "6.0" (CURRENT SKILL VERSION):
+    Display: "✓ Schemas already deployed (v6.0) - skipping"
+    SKIP deployment (trust cache)
+    → Go to Step 10
+  ELSE:
+    Display: "⚠ Schema version mismatch (cache: {cache.version}, current: 6.0)"
+    Proceed to deployment
 ELSE:
-  Deploy schemas
+  Display: "Deploying schemas (first time)..."
+  Proceed to deployment
 ```
 
-**Deploy all schema files from skill directory to project:**
+**Step 2: Deploy schemas (if needed)**
 
 Source: `schemas/` (relative to skill root = `~/.claude/skills/business-analyse/schemas/`)
 Destination: `docs/business/{app}/business-analyse/schemas/`
@@ -411,13 +412,43 @@ docs/business/{app}/business-analyse/schemas/
 1. Use Glob to find all `.json` files in `schemas/` directory (skill-relative)
 2. For each file, Read from skill directory and Write to project directory
 3. Preserve the subdirectory structure (sections/, shared/)
+4. Display progress: "Deploying schema {i}/{total}: {filename}"
+
+**Step 3: Write cache file (after successful deployment)**
+
+```json
+{
+  "version": "6.0",
+  "deployedAt": "{ISO timestamp}",
+  "schemas": [
+    "feature-schema.json",
+    "application-schema.json",
+    "sections/metadata-schema.json",
+    "sections/discovery-schema.json",
+    "sections/analysis-schema.json",
+    "sections/specification-schema.json",
+    "sections/validation-schema.json",
+    "sections/handoff-schema.json",
+    "shared/common-defs.json"
+  ]
+}
+```
+
+Write to: `docs/business/{app}/business-analyse/.schema-cache.json`
+
+Display: "✓ Schemas deployed successfully (9 files)"
 
 **Store:**
 ```yaml
 schemas_dir: "docs/business/{app}/business-analyse/schemas"
 ```
 
-## Step 10: Create Master feature.json
+**Performance gain:**
+- First deployment: ~12 seconds (unchanged)
+- Subsequent deployments: **~0 seconds (skipped via cache)** ✨
+- Cache invalidation: automatic on skill version upgrade
+
+## Step 9: Create Master feature.json
 
 Create the master feature document using ba-writer agent.
 
@@ -526,7 +557,7 @@ ba-writer.createApplicationFeature({
 {docs_dir}/feature.json
 ```
 
-## Step 11: Update Config
+## Step 10: Update Config
 
 Update `.business-analyse/config.json` with new feature information.
 
@@ -543,12 +574,11 @@ Update `.business-analyse/config.json` with new feature information.
   },
   "lastInitialized": "{ISO timestamp}",
   "autoMode": {auto_mode},
-  "economyMode": {economy_mode},
-  "interactiveMode": {interactive_mode}
+  "economyMode": {economy_mode}
 }
 ```
 
-## Step 12: Display Summary
+## Step 11: Display Summary
 
 Show initialization results in a clear table format.
 
@@ -576,7 +606,7 @@ NEXT STEP: step-01-analyse ({use_case} mode)
 ═══════════════════════════════════════════════════════════════
 ```
 
-## Step 13: Load Next Step
+## Step 12: Load Next Step
 
 **All modes except question (-q), micro (-m), and extract (-x):**
 After showing initialization summary, proceed to `./step-01-cadrage.md`
@@ -596,7 +626,6 @@ language: string
 docs_dir: string
 auto_mode: boolean
 economy_mode: boolean
-interactive_mode: boolean
 mcp_available: boolean
 workflow_mode: string
 ```
@@ -625,9 +654,3 @@ If initialization was interrupted:
 3. If found, offer to resume from last completed step
 4. If not found, create fresh feature.json
 
-### Clean Fallbacks
-
-If modern paths unavailable:
-1. Search `.business-analyse/business/` (legacy)
-2. Create new structure under `docs/business/` regardless
-3. Log migration notice (automated, non-blocking)

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

@@ -1263,6 +1263,62 @@ ba-writer.updateStatus({module_feature_id}, "specified")
 ba-writer.updateModuleStatus({feature_id}, {currentModule.code}, "specified")
 ```
 
+### 11-bis. Deploy Incremental Interactive HTML (MANDATORY)
+
+> **After each module is specified, deploy/update the interactive HTML document with all available data.**
+> This allows the client to review completed modules while the next module is being specified.
+> The HTML is incrementally enriched: after module 1, only module 1 specs appear; after module 2, both appear; etc.
+
+**Source:** `html/ba-interactive.html` (relative to skill root = `~/.claude/skills/business-analyse/html/`)
+
+**Destination:** `docs/business/{app}/business-analyse/v{version}/ba-interactive.html`
+
+**Steps:**
+
+1. **Read sources:**
+   - Read the HTML template from skill directory
+   - Read the master feature.json (application level — now updated with current module status)
+   - Read EACH completed module's feature.json (including the one just specified)
+
+2. **Build FEATURE_DATA object:**
+
+   > **Use the EXACT SAME mapping defined in step-05-handoff.md section 9d.**
+   > The mapping is identical — the only difference is that `moduleSpecs` only includes completed modules.
+   > Modules not yet specified will NOT appear in `moduleSpecs` (their entry in `modules[]` will show `status: "pending"`).
+
+   Follow step-05 section 9d "Step 2: Build FEATURE_DATA object" for the complete mapping pseudocode:
+   - `metadata`, `cadrage`, `modules[]`, `dependencies[]` → from master feature.json
+   - `moduleSpecs[moduleCode]` → only for modules with status "specified" (completed so far)
+   - `consolidation` → empty `{ interactions: [], e2eFlows: [] }` (not yet consolidated)
+   - `handoff` → empty `{}` (not yet handed off)
+
+3. **Replace placeholders in template:**
+   - Serialize the FEATURE_DATA object as JSON (2-space indentation)
+   - Replace `{{FEATURE_DATA}}` with the serialized JSON
+   - Replace `{{APPLICATION_NAME}}` → `{application_name}`
+   - Replace `{{APPLICATION_ID}}` → `{feature_id}`
+   - Replace `{{VERSION}}` → `{version}`
+   - Replace `{{CREATED_AT}}` → `{ISO timestamp}`
+
+4. **Write and confirm:**
+
+```
+✓ Interactive HTML updated (incremental):
+  Path: docs/business/{app}/business-analyse/v{version}/ba-interactive.html
+  Modules included: {completedModules.length}/{totalModules} specified
+    - {completedModule1}: {uc_count} UCs, {br_count} BRs, {entity_count} entities
+    - {completedModule2}: ...
+  Remaining: {pendingModules.join(', ')} (will be added after specification)
+  → Client can open in browser to review completed modules now.
+```
+
+> **WHY incremental?** The client doesn't have to wait until handoff to start reviewing.
+> While module 2 is being specified, the client can already give feedback on module 1.
+> Each incremental deployment OVERWRITES the previous HTML (latest state always).
+> The FINAL deployment at step-05 (handoff) will include consolidation and handoff data.
+
+---
+
 ### 12. Loop Decision
 
 ```
@@ -1338,6 +1394,7 @@ Read metadata.workflow.currentModule
 - Client confirmed module specification
 - Module feature.json written
 - Master updated with module status
+- **Interactive HTML deployed/updated with completed module data (incremental)**
 - Loop advanced correctly
 
 ## FAILURE MODES