@atlashub/smartstack-cli 4.74.0 → 4.75.0

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

@@ -121,138 +121,9 @@ existing_projects: array of { projectName, projectId, applications[], version }
 
 ## Step 3b: Early Multi-Application Detection from Prompt (NEW)
 
-> **Detect multi-app structure BEFORE asking for a single application name.**
-> When the user's prompt describes multiple applications or spans multiple business domains,
-> we must recognize this immediately and set `workflow.mode = "project"` to avoid doing cadrage for a single app.
+> → **Load** `references/multi-app-detection.md` for the multi-app detection algorithm (Tier 1 patterns, Tier 2 domain diversity scoring, extraction, confirmation).
 
-### Tier 1 — Explicit patterns (ANY match = multi-app detected)
-
-French patterns:
-- "une application X ... une application Y" (two occurrences of "une application")
-- "application 1: X ... application 2: Y" (numbered applications)
-- "première application ... deuxième application"
-- "app 1: ... app 2: ..."
-
-English patterns:
-- "an application (for) X ... an application (for) Y" (two occurrences)
-- "application #1: ... application #2: ..." (numbered)
-- "first app ... second app"
-
-If ANY of these patterns is found in `{feature_description}`:
-→ `isMultiApp = true`, `detectionTier = "explicit"`
-
-### Tier 2 — Domain diversity analysis (when Tier 1 does not match)
-
-ULTRATHINK: Analyze `{feature_description}` to extract distinct business domains.
-
-**Definition:** A "domain" is an autonomous business perimeter with its own entities and processes (e.g., HR, CRM, Finance, Projects, Sales, Inventory).
-
-**Algorithm:**
-1. List all business domains mentioned or implied in the description
-2. Classify each domain:
-   - **DISTINCT** — has its own entities, processes, and lifecycle (e.g., HR vs CRM)
-   - **RELATED** — is a sub-domain of another (e.g., Payroll is a sub-domain of HR)
-3. Count DISTINCT domains only
-
-**Threshold:** 2+ DISTINCT domains → `isMultiApp = true`, `detectionTier = "domain-diversity"`
-
-**False positive protection:**
-- "RH complet avec employés, congés, paie, pointage" = 1 domain (HR) with 4 modules, NOT 4 domains
-- "HR and Payroll management" = 1 domain (HR) with 2 modules — Payroll is RELATED to HR
-- "gestion commerciale avec devis, commandes et facturation" = 1 domain (Sales) with 3 modules
-- Only count as DISTINCT when domains have genuinely independent entity models and processes
-
-### Extraction algorithm (depends on detection tier)
-
-**IF Tier 1 (explicit):**
-
-1. **Identify boundaries:** Split the prompt at each "une application" / "an application" occurrence. Each block = one candidate.
-2. **Extract per candidate:** For each block, derive `name` (application name), `description` (summary of purpose), and `modules[]` (listed modules/features).
-   - Example: `[{ name: "RH", description: "gestion des employés, congés, temps", modules: ["Employés", "Congés", "Temps"] }, ...]`
-3. **Detect shared modules:** Collect all module names across all candidates. Any module appearing in more than one candidate is a shared module.
-   - Example: `sharedModules = ["Temps"]` (appears in both RH and Projet)
-
-**IF Tier 2 (domain-diversity):**
-
-1. Each DISTINCT domain = 1 candidate application:
-   - `name` = short domain label (e.g., "RH", "CRM", "Finance")
-   - `description` = user's expressed need for that domain
-   - `modules[]` = sub-functionalities mentioned (can be empty → "(à définir au cadrage)")
-2. Group RELATED sub-domains under their parent DISTINCT domain as modules
-3. **Detect shared modules:** Same logic as Tier 1 — modules appearing in multiple candidates
-
-### Confirmation dialogue
-
-Display detection result:
-
-```
-{detectionTier == "explicit"
-  ? (language == "fr"
-    ? "### Détection multi-application\n\nJ'ai détecté **{candidates.length} applications** dans votre description :"
-    : "### Multi-application detection\n\nI detected **{candidates.length} applications** in your description:")
-  : (language == "fr"
-    ? "### Détection multi-application\n\nVotre description couvre **{candidates.length} domaines métier distincts**. Chaque domaine pourrait constituer une application séparée :"
-    : "### Multi-application detection\n\nYour description covers **{candidates.length} distinct business domains**. Each domain could be a separate application:")}
-
-| # | Application | Modules identifiés |
-|---|-------------|-------------------|
-{for each candidate: index | name | modules.join(", ") || "(à définir au cadrage)"}
-
-{sharedModules.length > 0
-  ? "⚠️ **Modules partagés détectés :** {sharedModules.join(', ')} — ces modules apparaissent dans plusieurs applications. Ils pourraient constituer une application transversale dédiée."
-  : ""}
-```
-
-Ask via AskUserQuestion:
-```
-question: "{language == 'fr' ? 'Confirmez-vous cette structure multi-application ?' : 'Do you confirm this multi-application structure?'}"
-header: "Architecture"
-options:
-  - label: "{language == 'fr' ? 'Oui, {candidates.length} applications' : 'Yes, {candidates.length} applications'}"
-    description: "{language == 'fr' ? 'Créer un projet avec les applications identifiées' : 'Create a project with the identified applications'}"
-  - label: "{language == 'fr' ? 'Extraire les modules partagés' : 'Extract shared modules'}" (only if sharedModules.length > 0)
-    description: "{language == 'fr' ? 'Créer une application dédiée pour {sharedModules.join(', ')} ({candidates.length + 1} applications au total)' : 'Create a dedicated app for {sharedModules.join(', ')} ({candidates.length + 1} total)'}"
-  - label: "{language == 'fr' ? 'Regrouper certains domaines' : 'Regroup some domains'}" (only if detectionTier == "domain-diversity")
-    description: "{language == 'fr' ? 'Fusionner des domaines en moins d\\'applications' : 'Merge domains into fewer applications'}"
-  - label: "{language == 'fr' ? 'Application unique' : 'Single application'}"
-    description: "{language == 'fr' ? 'Tout regrouper en une seule application avec plusieurs modules' : 'Group everything into one application with multiple modules'}"
-```
-
-**IF "Oui, N applications" or "Extraire les modules partagés":**
-
-```yaml
-workflow_mode: "project"
-project_name: derived from feature_description
-candidate_applications: [{ name, description, modules, context }]
-shared_modules_extracted: boolean  # true if user chose extraction
-```
-
-→ Skip step 4 (application name) — applications will be confirmed in step-01-cadrage
-→ Continue to step 5 (language selection)
-
-**IF "Regrouper certains domaines" (Tier 2 only):**
-
-Ask via AskUserQuestion:
-```
-question: "{language == 'fr' ? 'Comment souhaitez-vous regrouper ces domaines ? (ex: \"RH + Paie ensemble, CRM seul\")' : 'How would you like to regroup these domains? (e.g., \"HR + Payroll together, CRM alone\")'}"
-header: "Regroupement"
-```
-
-Process user response:
-1. Parse the grouping instructions (natural language)
-2. Rebuild `candidate_applications` based on the specified groups
-3. Re-display the confirmation dialogue with the updated candidates
-
-**IF "Application unique":**
-
-```yaml
-workflow_mode: "application"
-```
-
-→ Continue to step 4 normally
-
-**IF no multi-app detected (neither Tier 1 nor Tier 2):**
-→ Continue to step 4 normally
+Execute the multi-app detection. IF multi-app detected → set `workflow_mode = "project"` and skip step 4 (application name). ELSE continue to step 4 normally.
 
 ## Step 4: Determine Project Name & Application Name
 
@@ -365,20 +236,27 @@ ELSE:
 feature_id: string
 ```
 
-## Step 7: Create Output Directory Structure
+## Step 7: Create Output Directory Structure (EXECUTABLE)
 
 ```
 projectDir = "docs/" + projectSlug + "/v" + version
+docs_dir = projectDir
+```
 
-IF workflow_type = "new":
-  mkdir -p {projectDir}
-  docs_dir = projectDir
+**MANDATORY — Execute via Bash tool (NOT just pseudocode):**
 
-ELSE:
-  // Directory already exists from previous session
-  docs_dir = projectDir
+```bash
+mkdir -p "{projectDir}"
+```
+
+**POST-CHECK (BLOCKING):**
+
+```bash
+ls -d "{projectDir}" 2>/dev/null || echo "DIRECTORY_MISSING"
 ```
 
+If output contains `DIRECTORY_MISSING` → **BLOCKING ERROR: directory creation failed. Check permissions.**
+
 > **Key change (ba-006):** All project data lives under `docs/{projectSlug}/v{X.Y}/`.
 > No more `business-analyse/` intermediate directory. Applications and modules are
 > direct subdirectories: `docs/{projectSlug}/v{X.Y}/{appKebab}/{moduleKebab}/`.
@@ -575,57 +453,11 @@ analysisMode: "interactive"
 version: string
 ```
 
-## Error Handling
-
-| Error | Action |
-|-------|--------|
-| Config missing | Create fresh with defaults, continue |
-| Directory creation fails | Check permissions, display error, EXIT |
-| index.json creation fails | Validate ba-writer, retry or fallback |
-| Feature ID not unique | Generate new ID, retry |
-
-### Resume After Interruption
-
-If initialization was interrupted:
-
-1. Check `.business-analyse/config.json` for currentFeature or currentProject
-2. If project ID exists, search for project index.json in `docs/*/v*/` (or legacy `docs/business-analyse/`)
-   - If found with scope = "project": resume project mode (see Project Resume below)
-3. If feature ID exists, search for index.json in `docs/`
-4. If found, check status and `metadata.workflow.lastCompletedStep`:
-
-   **Status-based resume routing (check in this order):**
-
-   - If status = `"handed-off"` or `"consolidated"`:
-     → Display: "BA workflow complete. Use /business-analyse-html to generate HTML, /business-analyse-review for corrections."
-     → STOP
-
-   - If status = `"specified"` AND `metadata.workflow.allModulesSpecified === true`:
-     → Resume at `step-04-consolidate.md`
-     → Display: "All modules specified — resuming at consolidation..."
-
-   - If status = `"specified"` AND `metadata.workflow.completedModules.length > 0` AND `metadata.workflow.completedModules.length < metadata.workflow.moduleOrder.length`:
-     → Resume at `step-03-specify.md` (continue specifying remaining modules)
-     → Display: "Resuming module specification ({completedCount}/{totalCount})..."
-
-   - Otherwise: offer to resume from last completed step
-
-5. If not found, create fresh index.json
-
-**Project Resume (project mode):**
-
-If a project-level index.json is found (scope = "project"):
-
-   - If status = `"draft"` or `"framed"`:
-     → Resume at `step-01-cadrage.md`
-
-   - If status = `"decomposed"`:
-     → Check `metadata.workflow.currentApplicationIndex` and `completedApplications[]`
-     → Resume module specification for current application (step-02 or step-03)
+## Error Handling & Resume Logic
 
-   - If status = `"specified"`:
-     → All applications specified → Resume at `step-04-consolidate.md`
+> → **Load** `references/init-resume-logic.md` for error handling matrix, resume detection, and status-based routing (draft → framed → decomposed → specified → consolidated → handed-off).
 
-   - If status = `"consolidated"`:
-     → Display: "BA workflow complete. Use /business-analyse-html to generate HTML."
-     → STOP
+When re-running initialization, check for interrupted workflows:
+1. Read `.business-analyse/config.json` for currentFeature or currentProject
+2. Search for existing index.json files in `docs/` hierarchy
+3. Check status and route appropriately (see reference for status-based routing matrix)