@atlashub/smartstack-cli 3.1.0 → 3.3.0

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-03-specify.",
+  "description": "Module-level analysis: objectives, business rules, entities, process flows, integrations, data lifecycle. Enriched by step-03a-specify.",
   "type": "object",
   "properties": {
     "objectives": {

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

@@ -2,7 +2,7 @@
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "$id": "handoff-schema.json",
   "title": "SmartStack BA - Handoff",
-  "description": "Module-level handoff: file mapping (7 categories), BR-to-code mapping, API endpoint summary. Used by step-05-handoff.",
+  "description": "Module-level handoff: file mapping (7 categories), BR-to-code mapping, API endpoint summary. Used by step-05a-handoff.",
   "type": "object",
   "properties": {
     "complexity": { "type": "string", "enum": ["simple", "medium", "complex"] },

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-03-specify.",
+  "description": "Module-level specification: actors, use cases, FRs, permissions, navigation, wireframes, dashboards, sections, resources. Enriched by step-03b-compile.",
   "type": "object",
   "properties": {
     "actors": {

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

@@ -4,6 +4,8 @@ description: Initialize Business Analysis - Parse flags, route use case, create
 next_step: steps/step-01-cadrage.md
 ---
 
+> **Context files:** `_shared.md`
+
 # Step 00: Initialize Business Analysis
 
 Initialize the business analysis workflow by parsing input flags, routing to the appropriate use case handler, and creating the initial feature.json structure.
@@ -37,7 +39,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 +53,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 +232,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 +257,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,21 +290,24 @@ application_name: string
 module_name: string
 ```
 
-## Step 7: Select Language
+## Step 6: Select Language
 
 Determine the language for analysis and code generation.
 
 **Check config:**
 - Retrieve `businessContext.language` from config
-- Default: "en" (English)
+- Default: "fr" (Francais)
 
-**If interactive:**
+**If not in config OR auto_mode = false:**
 ```
-Select language:
-[ ] English (en)
-[ ] French (fr)
-[ ] Spanish (es)
-[ ] Custom: {input}
+Ask via AskUserQuestion:
+  question: "Quelle langue pour l'analyse ?"
+  header: "Langue"
+  options:
+    - label: "Francais (fr)"
+    - label: "English (en)"
+    - label: "Italiano (it)"
+    - label: "Deutsch (de)"
 ```
 
 **Store:**
@@ -326,7 +315,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 +334,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 +359,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 == "{CLI_VERSION}" (from package.json):
+    Display: "✓ Schemas already deployed ({CLI_VERSION}) - skipping"
+    SKIP deployment (trust cache)
+    → Go to Step 10
+  ELSE:
+    Display: "⚠ Schema version mismatch (cache: {cache.version}, current: {CLI_VERSION})"
+    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 +415,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": "{CLI_VERSION}",
+  "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 +560,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 +577,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,13 +609,13 @@ 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`
 
 **Question mode (-q):** EXIT after ba-reader answers the question.
-**Micro mode (-m):** Load `./step-05-handoff.md` directly.
+**Micro mode (-m):** Load `./step-05a-handoff.md` directly.
 **Extract mode (-x):** Load `./step-06-extract.md` with `{json_data}` from parsed JSON file.
 
 **Pass context variables:**
@@ -596,7 +629,6 @@ language: string
 docs_dir: string
 auto_mode: boolean
 economy_mode: boolean
-interactive_mode: boolean
 mcp_available: boolean
 workflow_mode: string
 ```
@@ -625,9 +657,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-01-cadrage.md

@@ -5,6 +5,8 @@ model: opus
 next_step: steps/step-02-decomposition.md
 ---
 
+> **Context files:** `_shared.md` | `_elicitation.md` | `_architecture.md` | `_suggestions.md`
+
 # Step 1: Cadrage (Framing)
 
 ## MANDATORY EXECUTION RULES

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

@@ -2,9 +2,11 @@
 name: step-02-decomposition
 description: Module decomposition - identify modules, dependency graph, topological sort, client checkpoint
 model: sonnet
-next_step: steps/step-03-specify.md
+next_step: steps/step-03a-specify.md
 ---
 
+> **Context files:** `_shared.md`
+
 # Step 2: Decomposition
 
 ## MANDATORY EXECUTION RULES
@@ -36,7 +38,7 @@ ba-reader.findFeature({feature_id})
 
 IF status already "decomposed":
   Display: "Decomposition already completed. Loading next step."
-  Load: steps/step-03-specify.md
+  Load: steps/step-03a-specify.md
   STOP
 
 ### 2. Module Identification
@@ -290,4 +292,4 @@ When `workflow.mode = "module"` or only 1 scope item identified:
 
 ## NEXT STEP
 
-Load: `./step-03-specify.md`
+Load: `./step-03a-specify.md`