@atlashub/smartstack-cli 4.40.0 → 4.42.0

package/templates/skills/apex/steps/step-00-init.md

@@ -7,6 +7,8 @@ next_step: steps/step-01-analyze.md
 
 # Step 0: Initialize
 
+**ULTRA THINK about whether this is a NEW module (create from scratch) or an UPDATE to an existing module (add sections/resources/entities to existing code). This distinction drives every downstream decision — especially seed data, permissions, and roles.**
+
 **Before anything else**, display the version banner:
 
 ```
@@ -59,6 +61,43 @@ When `-d {prd_path}` is used, extract all context from PRD file and skip section
 
 ---
 
+## 1c. Prompt Precision Guard
+
+> **APEX executes, it does not explore.** If the prompt is too vague, redirect to `/business-analyse`.
+
+**Score the prompt — count how many of these are present or inferable:**
+
+| Element | Example | Weight |
+|---------|---------|--------|
+| Module name/code | "employees", "absence management" | 1 |
+| At least 1 entity name | "Employee", "Absence" | 1 |
+| At least 1 property/field | "FirstName, StartDate, Status" | 1 |
+| Target application | "HR module", "HumanResources" | 0.5 |
+| Section hint | "list", "dashboard", "approval" | 0.5 |
+
+```
+precision_score = sum of weights for elements found in task description
+
+IF precision_score < 2:
+  DISPLAY:
+  ╔══════════════════════════════════════════════════════════════╗
+  ║  ⚠ Prompt too vague for /apex                              ║
+  ║                                                             ║
+  ║  /apex needs precise features to execute in one shot.       ║
+  ║  Your request looks more like a discovery/design task.      ║
+  ║                                                             ║
+  ║  Suggestions:                                               ║
+  ║  1. Use /sketch to quickly design your module (~2 min)      ║
+  ║  2. Use /business-analyse for full analysis (40+ questions) ║
+  ║  3. Rewrite your prompt with entities and fields, e.g.:     ║
+  ║     /apex add employees section with Employee entity        ║
+  ║     (FirstName, LastName, Email) to HumanResources module   ║
+  ╚══════════════════════════════════════════════════════════════╝
+  → STOP — do NOT proceed to section 2
+```
+
+---
+
 ## 2. Detect SmartStack Application
 
 Scan project: Glob("*.sln"), Glob("docs/business/**/*"), Glob(".ralph/prd-*.json"), Glob("src/pages/**/*.tsx")
@@ -110,11 +149,12 @@ Call `mcp__smartstack__validate_conventions` after computing derivations. Fix an
 
 ---
 
-## 5. Challenge the Need
+## 5. Collect Technical Parameters
 
-Rapid scope validation — load and execute questions from `references/challenge-questions.md`:
+Rapid technical parameter collection — load and execute questions from `references/challenge-questions.md`:
 - **5a:** Entity scope & relationships
-- **5b:** Dependencies & key properties
+- **5b:** Dependency auto-detection (NO question — agent scans codebase and infers from {entities})
+- **5b-bis:** Key properties (question kept — user may have specific field requirements)
 - **5c:** Code generation strategy
 
 **Skip 5c if:**
@@ -134,7 +174,7 @@ Propagated to: step-01 (code focus), step-02 (layer mapping), step-03 (scaffoldi
 
 ## 5e. Scope Complexity Guard
 
-**Design:** `/apex` handles 1 module at a time. Use `/ralph-loop` for multi-module projects.
+**Design:** `/apex` handles 1 module at a time. Use `/business-analyse-develop` for multi-module projects.
 
 **Calculate:**
 ```
@@ -142,10 +182,10 @@ scope_score = entity_count + (section_count * 0.5) + (app_count * 3)
 ```
 
 **Rules:**
-- `delegate_mode (-d)` → SKIP guard (ralph-loop handles scope per module)
-- `app_count > 1` → Warning: use `/ralph-loop` or split requests
-- `entity_count > 6` → BLOCKING: max 6 entities. Solutions: `/ralph-loop`, `/apex -d`, or split manually
-- `scope_score > 8` → WARNING: ask user to split or use `/ralph-loop`
+- `delegate_mode (-d)` → SKIP guard (business-analyse-develop handles scope per module)
+- `app_count > 1` → Warning: use `/business-analyse-develop` or split requests
+- `entity_count > 6` → BLOCKING: max 6 entities. Solutions: `/business-analyse-develop`, `/apex -d`, or split manually
+- `scope_score > 8` → WARNING: ask user to split or use `/business-analyse-develop`
 
 **Recommended Scope:**
 | Metric | Safe | Warning | Blocking |

package/templates/skills/apex/steps/step-01-analyze.md

@@ -8,6 +8,8 @@ next_step: steps/step-02-plan.md
 
 # Step 1: Analyze
 
+**ULTRA THINK about existing code structure. Pay special attention to seed data files — they may exist but be INCOMPLETE (missing sections, permissions, or roles for the new scope). An existing file does NOT mean it's complete.**
+
 **Goal:** Understand what EXISTS in the codebase. Pure exploration, NO planning.
 
 ## LOAD CONDITIONALLY
@@ -37,7 +39,7 @@ This saves ~2 minutes of Glob searches on an empty project.
 
 ## 0b. Delegate Mode Fast Path (if delegate_mode)
 
-> **When called via `/ralph-loop -d`, PRD tasks provide pre-computed scope. Reduce exploration to verification only.**
+> **When called via `/business-analyse-develop -d`, PRD tasks provide pre-computed scope. Reduce exploration to verification only.**
 
 ```
 IF delegate_mode:
@@ -135,7 +137,9 @@ Agent(subagent_type='Explore', model='sonnet',
 
 ---
 
-## 3. Seed Data Inventory
+## 3. Seed Data Inventory (CONTENT-AWARE)
+
+> **CRITICAL:** Finding that a seed file EXISTS is not enough. You must READ it and compare its content against the target scope to determine if it needs MODIFICATION.
 
 ```
 Glob("**/Seeding/Data/{module_code}/*SeedData.cs")
@@ -144,6 +148,42 @@ Glob("**/Seeding/*SeedDataProvider.cs")
 
 Identify: NavigationModuleSeedData, PermissionsSeedData, RolesSeedData, SeedConstants, IClientSeedDataProvider (+ DI registration).
 
+### 3b. Seed Data Content Analysis (if files exist)
+
+For each existing seed file, READ IT and extract what's already covered:
+
+```
+NavigationModuleSeedData.cs:
+  → Extract existing section codes (from GetSectionEntries or similar methods)
+  → Extract existing resource codes (from GetResourceEntries or similar methods)
+  → Compare against {sections} from step-00
+  → Mark MISSING sections/resources → these need "modify" action
+
+Permissions.cs:
+  → Extract existing permission constants (Read, Create, Update, Delete per section)
+  → Compare against {sections} from step-00
+  → Mark sections WITHOUT permissions → these need "modify" action
+
+PermissionsSeedData.cs:
+  → Extract existing permission paths from HasData() entries
+  → Mark missing paths → "modify"
+
+RolesSeedData.cs:
+  → Extract existing role-permission mappings
+  → Mark missing mappings for new sections → "modify"
+
+{App}SeedDataProvider.cs:
+  → Check which seed methods are called (SeedNavigationAsync, SeedPermissionsAsync, etc.)
+  → Check if new module/section seed classes are referenced → "modify" if missing
+```
+
+**Result:** For each seed file, set action to:
+- `"skip"` — file exists AND covers ALL target sections/entities
+- `"modify"` — file exists BUT is MISSING entries for new sections/entities
+- `"create"` — file does not exist
+
+> **Common mistake:** Marking seed files as "skip" just because the file exists. A `NavigationModuleSeedData.cs` that covers sections A and B MUST be marked "modify" if the task adds section C.
+
 ---
 
 ## 4-7. Analysis Methods & Validation

package/templates/skills/apex/steps/step-02-plan.md

@@ -8,6 +8,8 @@ next_step: steps/step-03-execute.md
 
 # Step 2: Plan
 
+**ULTRA THINK about the execution strategy. For each file: is it CREATE (new) or MODIFY (exists but needs additions for new sections/entities)? Seed data files are frequently marked "skip" by mistake when they should be "modify" — verify this explicitly.**
+
 **Goal:** Create a precise, file-by-file plan. Each file mapped to a SKILL or MCP tool.
 
 ## LOAD CONDITIONALLY
@@ -19,7 +21,7 @@ Read `references/smartstack-layers.md` for layer execution rules, skill/MCP mapp
 
 ## 0. Delegate Mode Fast Path (if delegate_mode)
 
-> **When called via `/ralph-loop -d`, PRD tasks already define the scope. Map directly to layers.**
+> **When called via `/business-analyse-develop -d`, PRD tasks already define the scope. Map directly to layers.**
 
 ```
 IF delegate_mode:

package/templates/skills/apex/steps/step-03-execute.md

@@ -8,6 +8,8 @@ next_step: steps/step-04-examine.md
 
 # Step 3: Execute — Orchestrator
 
+**ULTRA THINK about the full execution context. Before dispatching layers, verify: are we creating a NEW module or UPDATING an existing one? This is critical for Layer 1 (seed data) — existing seed files must be MODIFIED, not recreated or skipped.**
+
 /apex ORCHESTRATES. It does not write SmartStack code directly.
 All code goes through skills (/controller, /application, /ui-components, /efcore) or MCP tools.
 
@@ -79,7 +81,7 @@ Load each sub-step sequentially:
 
 ## PRD State Update (delegate mode only)
 
-> **After completing EACH layer**, update the PRD file so `/ralph-loop` can track progress.
+> **After completing EACH layer**, update the PRD file so `/business-analyse-develop` can track progress.
 
 ```
 IF delegate_mode:

package/templates/skills/apex/steps/step-03a-layer0-domain.md

@@ -5,6 +5,8 @@ model: opus
 parent_step: steps/step-03-execute.md
 ---
 
+**ULTRA THINK about domain entities: which are NEW (create) vs which EXIST (modify/extend)?**
+
 ## Layer 0 — Domain + Infrastructure (sequential, agent principal)
 
 ### Task Progress

package/templates/skills/apex/steps/step-03b-layer1-seed.md

@@ -5,6 +5,8 @@ model: opus
 parent_step: steps/step-03-execute.md
 ---
 
+**ULTRA THINK about seed data completeness: is this a NEW module (create all seed files from scratch) or an UPDATE to an existing module (modify existing seed files to add new sections/resources/permissions)? Read existing files BEFORE deciding what to generate.**
+
 ## Layer 1 — Seed Data (DEDICATED LAYER — sequential, agent principal)
 
 ### Task Progress
@@ -15,7 +17,33 @@ TaskUpdate(taskId: progress_tracker_id,
 
 > This layer is required. Seed data makes modules visible in the UI. Without it, the module exists in code but is invisible to users. Reference: `references/core-seed-data.md` (loaded above) for complete C# templates.
 
-### Application-Level Seed Data (ONCE per application)
+---
+
+### Mode Detection: CREATE vs UPDATE
+
+> **CRITICAL — Run this BEFORE generating any seed data.**
+
+```
+Glob("**/Seeding/Data/{module_code}/*SeedData.cs") → existing_seed_files
+Glob("**/Seeding/Data/NavigationApplicationSeedData.cs") → app_seed_exists
+Glob("**/Seeding/*SeedDataProvider.cs") → provider_exists
+
+IF existing_seed_files is EMPTY:
+  SEED_MODE = "CREATE"
+  → Generate ALL seed data from scratch (full templates below)
+
+IF existing_seed_files is NOT EMPTY:
+  SEED_MODE = "UPDATE"
+  → Read EACH existing file
+  → Compare content against {sections} and {entities} from step-00
+  → ADD only what's MISSING — do NOT recreate or duplicate existing entries
+```
+
+---
+
+### CREATE Mode — Application-Level Seed Data (ONCE per application)
+
+> Skip if `app_seed_exists` (files already present from previous APEX run).
 
 ```
 1. NavigationApplicationSeedData.cs
@@ -27,7 +55,13 @@ TaskUpdate(taskId: progress_tracker_id,
    → References NavigationApplicationSeedData.ApplicationId
 ```
 
-### Per-Module Seed Data
+---
+
+### Per-Module Seed Data (CREATE or UPDATE)
+
+#### If SEED_MODE = "CREATE"
+
+Generate all files from scratch using `references/core-seed-data.md` templates:
 
 ```
 3. NavigationModuleSeedData.cs
@@ -51,7 +85,51 @@ TaskUpdate(taskId: progress_tracker_id,
    → Look up roles by Code at runtime
 ```
 
-### Infrastructure Provider (ONCE per application)
+#### If SEED_MODE = "UPDATE"
+
+> **Read each existing file FIRST, then surgically add only what's missing.**
+
+```
+3. NavigationModuleSeedData.cs — READ EXISTING FILE
+   → Extract existing section codes (look for GetSectionEntries or section GUID definitions)
+   → Extract existing resource codes
+   → For each section in {sections} NOT already present:
+     - Add new section entry in GetSectionEntries() with new Guid.NewGuid()
+     - Add section translations (4 languages) in GetSectionTranslationEntries()
+     - Add route entry: /{app-kebab}/{module-kebab}/{new-section-kebab}
+   → For each resource in {resources} NOT already present:
+     - Add resource entry in GetResourceEntries()
+     - Add resource translations
+   → PRESERVE all existing entries unchanged
+
+4. Permissions.cs — READ EXISTING FILE
+   → Extract existing permission constants
+   → For each NEW section:
+     - Add section-level constants: Wildcard, Read, Create, Update, Delete
+     - Path format: {app}.{module}.{new-section}.{action}
+   → MCP generate_permissions for validation (compare output vs file)
+   → PRESERVE all existing constants unchanged
+
+5. PermissionsSeedData.cs — READ EXISTING FILE
+   → Extract existing HasData() permission entries
+   → Add HasData() entries for each NEW permission from step 4
+   → PRESERVE all existing entries unchanged
+
+6. RolesSeedData.cs — READ EXISTING FILE
+   → Extract existing role-permission mappings
+   → For each NEW permission:
+     - Admin → wildcard or all new permissions
+     - Manager → Read + Create + Update for new section
+     - Contributor → Read + Create for new section
+     - Viewer → Read for new section
+   → PRESERVE all existing mappings unchanged
+```
+
+---
+
+### Infrastructure Provider (CREATE or UPDATE)
+
+#### If SEED_MODE = "CREATE"
 
 ```
 7. {App}SeedDataProvider.cs
@@ -63,8 +141,38 @@ TaskUpdate(taskId: progress_tracker_id,
    → DI: services.AddScoped<IClientSeedDataProvider, {App}SeedDataProvider>()
 ```
 
+#### If SEED_MODE = "UPDATE"
+
+```
+7. {App}SeedDataProvider.cs — READ EXISTING FILE
+   → Verify SeedNavigationAsync() calls the module's NavigationModuleSeedData
+   → If new sections were added: verify they are seeded (new section entries are part of existing methods)
+   → Verify SeedPermissionsAsync() covers new PermissionsSeedData entries
+   → Verify SeedRolePermissionsAsync() covers new RolesSeedData entries
+   → Add any missing calls or registrations
+   → PRESERVE all existing logic unchanged
+```
+
 <!-- TODO A4: Replace direct seed generation with MCP scaffold_seed_data when B1 is ready. This will eliminate the need for references/core-seed-data.md (1464 lines). -->
 
+---
+
+### Post-Layer 1 Verification Checklist
+
+> **Before the build gate, verify ALL new scope elements are covered:**
+
+```
+For each section in {sections} from step-00:
+  ✓ NavigationModuleSeedData has section entry + translations (4 langs)
+  ✓ NavigationModuleSeedData has route: /{app}/{module}/{section}
+  ✓ Permissions.cs has constants for this section (Read/Create/Update/Delete/Wildcard)
+  ✓ PermissionsSeedData has HasData() for each permission
+  ✓ RolesSeedData maps all 4 roles to section permissions
+  ✓ {App}SeedDataProvider references all seed data classes
+
+IF any check fails → fix BEFORE build gate
+```
+
 ### Post-Layer 1 Build Gate
 
 ```bash

package/templates/skills/apex/steps/step-03c-layer2-backend.md

@@ -5,6 +5,8 @@ model: opus
 parent_step: steps/step-03-execute.md
 ---
 
+**ULTRA THINK about backend services: which services/controllers are NEW vs which need MODIFICATION for new entities/endpoints?**
+
 ## Layer 2 — Backend (Services + Controllers)
 
 ### Task Progress

package/templates/skills/apex/steps/step-03d-layer3-frontend.md

@@ -5,6 +5,8 @@ model: opus
 parent_step: steps/step-03-execute.md
 ---
 
+**ULTRA THINK about frontend completeness: new pages, routes, i18n keys, AND permissions/navigation alignment with Layer 1 seed data.**
+
 # Layer 3 — Frontend (Pages + I18n + Documentation)
 
 ### ⛔ HARD RULE — /ui-components is NON-NEGOTIABLE (read BEFORE any Layer 3 action)

package/templates/skills/apex/steps/step-03e-layer4-devdata.md

@@ -5,6 +5,8 @@ model: opus
 parent_step: steps/step-03-execute.md
 ---
 
+**ULTRA THINK about dev data coverage: all NEW entities need realistic test data.**
+
 ## Layer 4 — DevData (optional)
 
 ### Task Progress

package/templates/skills/apex/steps/step-04-examine.md

@@ -8,6 +8,8 @@ next_step: steps/step-05-deep-review.md
 
 # Step 4: eXamine
 
+**ULTRA THINK about completeness. Did ALL new sections/entities get their navigation entries, permissions, and roles? Cross-check the scope from step-00 against what was actually generated in Layer 1.**
+
 > **This is the X in APEX.** Mandatory automated examination of all generated code.
 
 **Goal:** Verify everything works. MCP conventions, build, seed data, acceptance criteria.
@@ -92,6 +94,8 @@ If migration fails (SQLite-only syntax, type mismatches, missing FK targets), fi
 
 ## 6. Seed Data Completeness Check (if needs_seed_data)
 
+> **CRITICAL — Cross-check against {sections} from step-00.** Every section in scope MUST have navigation, permissions, and roles. This is the most common miss when UPDATING an existing module.
+
 | File | Checks |
 |------|--------|
 | NavigationApplicationSeedData | 4 lang translations |
@@ -105,6 +109,20 @@ If migration fails (SQLite-only syntax, type mismatches, missing FK targets), fi
 | IClientSeedDataProvider | 4 Seed methods, idempotent, SaveChanges per group |
 | DI Registration | `services.AddScoped<IClientSeedDataProvider, {App}SeedDataProvider>()` |
 
+### 6a. Section Coverage Matrix (MANDATORY for updates)
+
+```
+For EACH section in {sections} from step-00:
+  Read NavigationModuleSeedData.cs → has section entry?       YES / NO
+  Read NavigationModuleSeedData.cs → has translations (4)?    YES / NO
+  Read NavigationModuleSeedData.cs → has route?               YES / NO
+  Read Permissions.cs → has section permissions?              YES / NO
+  Read PermissionsSeedData.cs → has HasData() entries?        YES / NO
+  Read RolesSeedData.cs → has role-permission mappings?       YES / NO
+
+IF ANY cell = NO → BLOCKING — return to step-03b to fix
+```
+
 ---
 
 ## 6b. POST-CHECKs

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

@@ -26,25 +26,86 @@ user_invocable: true
 | 03 | `step-03-specify.md` | Opus | Deep dive per module: entities, BRs, UCs, permissions. Sequential internal loop |
 | 04 | `step-04-consolidate.md` | Opus | Cross-module validation: data model, permission coherence, E2E flows |
 
-### Post-BA Workflow
+### Development Paths — When to use what
+
+SmartStack offers **two paths** from idea to code, depending on scope:
+
 ```
-Phase 1: /business-analyse (steps 00-04)
-    |
-    v
-Phase 2: /ba-design-ui (screens, wireframes, navigation)
-    |
-    v
-Phase 3: /ba-generate-html (interactive HTML with mockups, ERD, permissions)
-    |
-    v
-Phase 4: /ba-review (client corrections → back to Phase 1 or 2)
-    |
-    v (client approves)
-Phase 5: /derive-prd → Phase 6: /ralph-loop
+Path A — FAST (small module, < 5 min)          Path B — FULL (multi-module, hours/days)
+═══════════════════════════════════════         ═══════════════════════════════════════
+
+  "I want employees + absences"                  "Build a complete HR platform"
+          │                                               │
+          ▼                                               ▼
+  ┌──────────────┐                               ┌──────────────────┐
+  │   /sketch    │  0-2 questions                 │ /business-analyse│  ~40 questions
+  │  (2 min)     │  Pure inference                │  (steps 00-04)   │  JSON output
+  └──────┬───────┘                               └────────┬─────────┘
+         │ Natural language prompt                        │ entities/rules/usecases.json
+         ▼                                               ▼
+  ┌──────────────┐                               ┌──────────────────┐
+  │    /apex     │  1 module                      │  /business-analyse-design   │  screens/wireframes
+  │  (30-60 min) │  APEXE methodology             │                  │  navigation tree
+  └──────────────┘                               └────────┬─────────┘
+                                                          │ screens.json, navigation.json
+                                                          ▼
+                                                 ┌──────────────────┐
+                                                 │/business-analyse-html│  Interactive HTML
+                                                 │                  │  for client review
+                                                 └────────┬─────────┘
+                                                          │ ba-interactive.html
+                                                          ▼
+                                                 ┌──────────────────┐
+                                                 │/business-analyse-review│◄── ba-review.json
+                                                 │  Corrections?    │    (exported from HTML)
+                                                 └───┬─────────┬───┘
+                                              YES    │         │ NO (approved)
+                                         ┌───────────┘         └──────────┐
+                                         ▼                                ▼
+                                  Back to Phase 1             ┌────────────────────────┐
+                                  or Phase 2                  │/business-analyse-     │  PRD + handoff
+                                  (depends on scope)          │      handoff           │
+                                                              └────────┬───────────────┘
+                                                                       │ .ralph/prd-*.json
+                                                                       ▼
+                                                              ┌──────────────────┐
+                                                              │   /business-analyse-develop    │  Orchestrator
+                                                              │  (iterative)     │  delegates to ▼
+                                                              └────────┬─────────┘
+                                                                       │ /apex -d per module
+                                                                       ▼
+                                                              ┌──────────────────┐
+                                                              │    /apex -d      │  Code generation
+                                                              │  (per module)    │  5 layers
+                                                              └──────────────────┘
 ```
 
-> After step-04, invoke `/ba-design-ui` to design interfaces, then `/ba-generate-html` to generate the HTML, then `/ba-review` for the client correction cycle.
-> **PRD generation:** Handoff data and PRD files are generated by the `/derive-prd` skill.
+### Data flow between skills
+
+| From | To | Data | Format |
+|------|----|------|--------|
+| `/sketch` | `/apex` | Inferred design (entities, FK, labels, code patterns) | Natural language prompt |
+| `/business-analyse` | `/business-analyse-design` | Entities, use cases, permissions | JSON (`entities.json`, `usecases.json`, `permissions.json`) |
+| `/business-analyse-design` | `/business-analyse-html` | Screen specs, wireframes, navigation | JSON (`screens.json`, `navigation.json`) |
+| `/business-analyse-html` | Client | Interactive review document | HTML (`ba-interactive.html`) |
+| Client | `/business-analyse-review` | Corrections | JSON (`ba-review.json`, exported from HTML) |
+| `/business-analyse-review` | `/business-analyse` or `/business-analyse-design` | Corrections applied, new version | JSON (updated thematic files) |
+| `/business-analyse` (approved) | `/business-analyse-handoff` | Consolidated BA data | JSON (all `index.json` + thematic files) |
+| `/business-analyse-handoff` | `/business-analyse-develop` | Handoff data + PRD | JSON (`.ralph/prd-*.json`, `handoff.json`) |
+| `/business-analyse-develop` | `/apex -d` | Module context + PRD | JSON (`.ralph/prd-{module}.json`) |
+
+### /business-analyse-review correction routing
+
+| Correction scope | Route to | Reason |
+|------------------|----------|--------|
+| Entities, rules, UCs, permissions | `/business-analyse` step-03 | Re-specify affected modules |
+| Screens, wireframes, navigation | `/business-analyse-design` | Re-design UI |
+| Both analysis + UI | `/business-analyse` step-03, then `/business-analyse-design` | Full re-spec |
+| Cadrage/scope only | `/business-analyse-html` | Just regenerate HTML |
+| No corrections (approved) | `/business-analyse-handoff` | Proceed to code generation |
+
+> **Rule:** Path A (`/sketch` → `/apex`) is for quick, single-module additions. Path B (full cycle) is for multi-module projects or when the client needs a formal review process.
+> **PRD generation:** Handoff data and PRD files are generated by the `/business-analyse-handoff` skill.
 
 ## JSON Architecture — Granular files + Index
 
@@ -58,7 +119,7 @@ docs/{app}/{module}/business-analyse/v1.0/
   rules.json              ← Business rules (BRs)
   usecases.json           ← Use cases (UCs)
   permissions.json        ← Permissions, roles, access matrix
-  screens.json            ← Interface specs (produced by /ba-design-ui)
+  screens.json            ← Interface specs (produced by /business-analyse-design)
   validation.json         ← Validation results, checks
   handoff.json            ← File mapping, APIs, handoff data
 ```
@@ -115,7 +176,7 @@ Each step loads ONLY what it needs:
 
 ## HTML Output
 
-HTML generation is handled by the `/ba-generate-html` skill. After step-04, invoke `/ba-generate-html` to produce the interactive HTML document. For client review corrections, use `/ba-review`.
+HTML generation is handled by the `/business-analyse-html` skill. After step-04, invoke `/business-analyse-html` to produce the interactive HTML document. For client review corrections, use `/business-analyse-review`.
 
 ## Step Execution
 
@@ -147,20 +208,20 @@ STEP 04 (consolidate) — FINAL BA STEP
   → Load: _shared.md, step-04-consolidate.md, all index.json
   → Execute: Data model validation, permission coherence, E2E flows
   → Output: validation.json, consolidated data
-  → Next: invoke /ba-design-ui (Phase 2), then /ba-generate-html, then /ba-review for client cycle
+  → Next: invoke /business-analyse-design (Phase 2), then /business-analyse-html, then /business-analyse-review for client cycle
 ```
 
 ## References
 
 | File | Content |
 |------|---------|
-| `/ba-generate-html` skill | HTML generation (FEATURE_DATA mapping, build, render, verify) |
-| `/ba-review` skill | Apply client corrections from ba-review.json |
+| `/business-analyse-html` skill | HTML generation (FEATURE_DATA mapping, build, render, verify) |
+| `/business-analyse-review` skill | Apply client corrections from ba-review.json |
 | `references/naming-conventions.md` | SmartStack naming rules |
 | `references/validation-checklist.md` | Validation criteria checklist |
 | `references/acceptance-criteria.md` | Acceptance criteria patterns |
 
-> **Cross-reference:** Handoff data, PRD generation, file templates, and BR-to-code mappings are in the `/derive-prd` skill.
+> **Cross-reference:** Handoff data, PRD generation, file templates, and BR-to-code mappings are in the `/business-analyse-handoff` skill.
 
 ## Questionnaires
 

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

@@ -76,7 +76,7 @@ Steps load only the files they need:
 2. Otherwise → mode = "new"
 ```
 
-> **Note:** Review mode (`ba-review.json`) is handled by the `/ba-review` skill.
+> **Note:** Review mode (`ba-review.json`) is handled by the `/business-analyse-review` skill.
 
 ## Navigation Hierarchy
 
@@ -124,33 +124,36 @@ Reads via index.json. Key operations:
 - `readSection(moduleCode, fileType)` — Read specific file via index
 - `getModuleStatus()` — Status table of all modules
 - `getCompletedModulesSummary()` — Compact summaries for context loading
-- `getSummaryForSkill(skill)` — Context for other skills (ralph-loop, etc.)
+- `getSummaryForSkill(skill)` — Context for other skills (business-analyse-develop, etc.)
 
 ## Status Progression
 
 ```
-draft → identified → specified → validated → reviewed
+draft → framed → decomposed → specified → consolidated → designed → reviewed → handed-off
 ```
 
 | Status | Set by | Meaning |
 |--------|--------|---------|
 | draft | Step 00 | Feature created, no content |
-| identified | Step 02 | Hierarchy identified (App > Module > Section > Resource) |
+| framed | Step 01 | Application-level framing complete (scope, stakeholders, roles) |
+| decomposed | Step 02 | Module hierarchy identified (App > Module > Section > Resource) |
 | specified | Step 03 | Module fully specified (entities, UCs, BRs, permissions, screens) |
-| validated | Step 04 | Cross-module validation passed |
-| reviewed | `/ba-review` | Client review applied |
+| consolidated | Step 04 | Cross-module validation and consolidation passed |
+| designed | Step 05 | UI/UX design and navigation complete |
+| reviewed | `/business-analyse-review` | Client review applied |
+| handed-off | `/business-analyse-handoff` | PRD files generated, ready for development |
 
 ## Handoff & PRD Generation
 
-Handoff data and PRD files are generated by the `/derive-prd` skill. The workflow is:
+Handoff data and PRD files are generated by the `/business-analyse-handoff` skill. The workflow is:
 
 ```
-/business-analyse (steps 00-04) → /ba-generate-html → /ba-review (if needed) → /derive-prd → /ralph-loop
+/business-analyse (steps 00-04) → /business-analyse-html → /business-analyse-review (if needed) → /business-analyse-handoff → /business-analyse-develop
 ```
 
 ## HTML Generation
 
-For HTML generation, use the `/ba-generate-html` skill after step-04 consolidation. For client review corrections, use `/ba-review`.
+For HTML generation, use the `/business-analyse-html` skill after step-04 consolidation. For client review corrections, use `/business-analyse-review`.
 
 ## Resume Protocol
 

package/templates/skills/business-analyse/questionnaire/02-stakeholders-scope.md

@@ -66,6 +66,19 @@
 
 ---
 
+## 2.6 Intégrations et systèmes externes
+
+> **But :** Identifier les échanges de données avec l'extérieur et les migrations initiales.
+
+| # | Question | Type de réponse |
+|---|----------|-----------------|
+| Q2.19 | Ce système doit-il échanger des données avec d'autres outils ? (comptabilité, email, banque, API tierces) | Liste d'intégrations |
+| Q2.20 | Y a-t-il des données existantes à importer lors du démarrage ? (Excel, ancien système) | Description import |
+
+- Mapping → `cadrage.json` : champs `externalIntegrations[]` et `dataImport`
+
+---
+
 ## Guide d'élicitation approfondi
 
 ### Techniques de relance