@atlashub/smartstack-cli 3.5.0 → 3.6.0

package/templates/skills/business-analyse/steps/{step-03b-compile.md → step-03d-validate.md}

@@ -1,21 +1,20 @@
 ---
-name: step-03b-compile
-description: Module specification compilation, validation, HTML deployment, and loop decision
-model: opus
-next_step: steps/step-03a-specify.md OR steps/step-04-consolidation.md (conditional)
+name: step-03d-validate
+description: Per-module validation, write feature.json, incremental HTML deploy, loop decision
+model: sonnet
+next_step: steps/step-03a-data.md OR steps/step-04-consolidation.md (conditional)
 ---
 
 > **Context files:** `_shared.md` | `_module-loop.md`
 
-# Step 3b: Specification Compilation
+# Step 3d: Validation & Loop
 
 ## MANDATORY EXECUTION RULES
 
 - ALWAYS use ULTRATHINK mode
-- This step COMPILES the specification from the interactive phase (step-03a) into feature.json
-- ALWAYS validate specification completeness before writing
+- This step VALIDATES the specification from step-03c, writes it to feature.json, and decides loop continuation
+- ALWAYS verify specification completeness before writing
 - ALL communication in `{language}`
-- NEVER skip per-module validation
 - **ID NAMING RULE (MANDATORY, NO EXCEPTION):**
   All IDs MUST include a module prefix to guarantee application-wide uniqueness.
   The prefix is derived from the module code initials (2-4 chars):
@@ -23,302 +22,16 @@ next_step: steps/step-03a-specify.md OR steps/step-04-consolidation.md (conditio
     RepairManagement → RM | MaintenanceSchedule → MS | DataSync → DS
     Notifications → NT | Dashboard → DB | Orders → OR | Customers → CU
 
-  Patterns:
-    UC-{PREFIX}-{NNN}        → UC-RM-001, UC-PI-003
-    BR-{CAT}-{PREFIX}-{NNN}  → BR-VAL-RM-001, BR-CALC-PI-002
-    FR-{PREFIX}-{NNN}        → FR-RM-001
-    OBJ-{PREFIX}-{NNN}       → OBJ-RM-001
-    AC-{PREFIX}-{NNN}        → AC-RM-001
-    RISK-{PREFIX}-{NNN}      → RISK-RM-001
-
   NEVER use bare IDs (UC-001, BR-VAL-001) in multi-module mode.
-- **SCHEMA CONFORMITY RULE:**
-  ALL data MUST fit within the defined feature-schema.json structure.
-  NEVER create custom top-level fields (KPIDefinitions, ChartConfigurations, etc.)
-  Dashboard modules MUST use specification.dashboards[] (it exists in the schema).
-  If truly needed, use specification.extensions: {} (additionalProperties: true).
 
 ## YOUR TASK
 
-Compile all data collected in step-03a into the module feature.json: write specification (8a-8l), validate, update status, deploy incremental HTML, and decide loop continuation.
+Validate the module specification for completeness and consistency, write to feature.json, deploy incremental HTML, and decide whether to loop to the next module or proceed to consolidation.
 
 ---
 
-### 8. Full Specification
-
-Generate the complete specification for this module. **Each subsection below includes a STRUCTURE CARD showing the EXACT JSON format. Follow them precisely.**
-
-#### 8a. Actors
-
-Inherited from application roles → mapped to module permissions.
-
-> **STRUCTURE CARD: specification.actors[]**
-> ```json
-> {
->   "role": "Sales Manager",
->   "description": "Creates and approves orders",
->   "permissions": [
->     "business.{app}.{module}.read",
->     "business.{app}.{module}.create",
->     "business.{app}.{module}.update"
->   ]
-> }
-> ```
-> **MANDATORY fields:** `role`, `permissions` (array of permission paths)
-> **FORBIDDEN fields:** Do NOT use `systemRole`. Use `permissions` array.
-
-#### 8b. Use Cases (UC-{PREFIX}-NNN)
-
-Per section: list, create, read, update, delete, approve, etc.
-
-> **STRUCTURE CARD: specification.useCases[]**
-> ```json
-> {
->   "id": "UC-{PREFIX}-001",
->   "name": "Create Order",
->   "primaryActor": "Sales Representative",
->   "permission": "business.{app}.{module}.create",
->   "preconditions": ["Customer exists", "Products in stock"],
->   "postconditions": ["Order created with Draft status"],
->   "mainScenario": [
->     "1. User navigates to creation form",
->     "2. User fills in required fields",
->     "3. System validates data (BR-VAL-{PREFIX}-001)",
->     "4. System creates the record",
->     "5. System displays confirmation"
->   ],
->   "alternativeScenarios": [
->     { "name": "Validation failure", "steps": ["1. System detects invalid data", "2. System highlights errors"] }
->   ],
->   "errorScenarios": [
->     { "name": "Server error", "steps": ["1. System shows error message", "2. Data preserved for retry"] }
->   ],
->   "linkedRules": ["BR-VAL-{PREFIX}-001", "BR-WF-{PREFIX}-002"]
-> }
-> ```
-> **MANDATORY fields:** `id`, `name`, `primaryActor`, `permission`, `mainScenario`, `linkedRules`
-> **FORBIDDEN fields:** Do NOT use `actor` (use `primaryActor`), `linkedBRs` (use `linkedRules`), `linkedFRs` (not in UC, FRs link to UCs instead)
-
-#### 8c. Functional Requirements (FR-{PREFIX}-NNN)
-
-Linked to BRs and UCs.
-
-> **STRUCTURE CARD: specification.functionalRequirements[]**
-> ```json
-> {
->   "id": "FR-{PREFIX}-001",
->   "statement": "System MUST validate customer budget before order creation",
->   "priority": "must|should|could",
->   "linkedRules": ["BR-VAL-{PREFIX}-001"],
->   "linkedUseCases": ["UC-{PREFIX}-001"],
->   "acceptanceCriteria": [
->     "Order rejected if total > budget",
->     "Error message displayed with remaining budget"
->   ]
-> }
-> ```
-> **MANDATORY fields:** `id`, `statement`, `priority`, `linkedUseCases`
-> **FORBIDDEN fields:** Do NOT use `name`/`description` (use `statement` with System MUST/SHOULD/COULD format), `linkedUCs` (use `linkedUseCases`), `linkedBRs` (use `linkedRules`)
-
-#### 8d. Permission Matrix
-
-Roles × resources × operations with full paths.
-
-> **STRUCTURE CARD: specification.permissionMatrix**
-> ```json
-> {
->   "permissions": [
->     { "path": "business.{app}.{module}.read", "action": "read", "description": "View records" },
->     { "path": "business.{app}.{module}.create", "action": "create", "description": "Create new records" },
->     { "path": "business.{app}.{module}.update", "action": "update", "description": "Update existing records" },
->     { "path": "business.{app}.{module}.delete", "action": "delete", "description": "Delete records" },
->     { "path": "business.{app}.{module}.export", "action": "export", "description": "Export data" }
->   ],
->   "roleAssignments": [
->     { "role": "{App} Admin", "permissions": ["business.{app}.{module}.read", "business.{app}.{module}.create", "business.{app}.{module}.update", "business.{app}.{module}.delete", "business.{app}.{module}.export"] },
->     { "role": "{App} Manager", "permissions": ["business.{app}.{module}.read", "business.{app}.{module}.create", "business.{app}.{module}.update"] },
->     { "role": "{App} Viewer", "permissions": ["business.{app}.{module}.read"] }
->   ]
-> }
-> ```
-> **STRUCTURE:** Object with 2 arrays: `permissions[]` and `roleAssignments[]`
-> **FORBIDDEN:** Do NOT use a flat array with `resource`/`roles` fields. Always use the nested structure above.
-
-#### 8e. Navigation
-
-Module → Sections → Resources (levels 3-4-5 of the hierarchy).
-
-> **STRUCTURE CARD: specification.navigation**
-> ```json
-> {
->   "entries": [
->     { "level": "module", "code": "{module}", "labels": {"fr": "...", "en": "..."}, "route": "/business/{app}/{module}", "icon": "list" },
->     { "level": "section", "code": "list", "labels": {"fr": "Liste", "en": "List", "it": "Elenco", "de": "Liste"}, "route": "/business/{app}/{module}/list", "icon": "list" },
->     { "level": "section", "code": "dashboard", "labels": {"fr": "Dashboard", "en": "Dashboard"}, "route": "/business/{app}/{module}/dashboard", "icon": "chart-bar", "isNew": true }
->   ]
-> }
-> ```
-
-#### 8f. SeedData Core
-
-5 MANDATORY typed arrays — each with structured objects, NOT flat strings or objects.
-
-> **STRUCTURE CARD: specification.seedDataCore**
-> ```json
-> {
->   "navigationModules": [
->     { "code": "{module}", "label": "{Module Name}", "icon": "list", "route": "/business/{app}/{module}", "parentCode": "{app}", "sort": 1 }
->   ],
->   "navigationTranslations": [
->     { "moduleCode": "{module}", "language": "fr", "label": "..." },
->     { "moduleCode": "{module}", "language": "en", "label": "..." },
->     { "moduleCode": "{module}", "language": "it", "label": "..." },
->     { "moduleCode": "{module}", "language": "de", "label": "..." }
->   ],
->   "permissions": [
->     { "path": "business.{app}.{module}.read", "action": "read", "description": "View {module}" },
->     { "path": "business.{app}.{module}.create", "action": "create", "description": "Create {module}" }
->   ],
->   "rolePermissions": [
->     { "role": "{App} Admin", "permissionPath": "business.{app}.{module}.*" },
->     { "role": "{App} Manager", "permissionPath": "business.{app}.{module}.read" }
->   ],
->   "permissionConstants": [
->     { "constantName": "{Module}Read", "path": "business.{app}.{module}.read" },
->     { "constantName": "{Module}Create", "path": "business.{app}.{module}.create" }
->   ]
-> }
-> ```
-> **MANDATORY:** All 5 arrays must be present. Each element must be an object, NOT a string.
-> **FORBIDDEN:** Do NOT use `navigationModule` (singular string), `permissions` as flat string array, `rolePermissions` as flat object, `permissionsConstants` as comma-separated string.
-
-#### 8g. Gherkin Scenarios
-
-BDD acceptance tests per UC.
-
-> **STRUCTURE CARD: specification.gherkinScenarios[]**
-> ```json
-> {
->   "feature": "{Module} Management",
->   "scenarios": [
->     {
->       "name": "Create a new record with valid data",
->       "tags": ["@{module}", "@create", "@smoke"],
->       "given": ["An authenticated user with role Manager", "No existing record with code 'TEST-001'"],
->       "when": ["The user fills the creation form", "The user submits the form"],
->       "then": ["The record is created with Draft status", "A success message is displayed"]
->     }
->   ]
-> }
-> ```
-> **STRUCTURE:** Object with `feature` string + `scenarios[]` array. Each scenario has `given`, `when`, `then` as ARRAYS of strings.
-> **FORBIDDEN:** Do NOT use flat arrays of `{uc, scenario, given, when, then}` where given/when/then are single strings.
-
-#### 8h. Validations
-
-Field validation rules per entity.
-
-> **STRUCTURE CARD: specification.validations[]**
-> ```json
-> {
->   "entity": "Order",
->   "field": "amount",
->   "rules": ["required", "decimal", "min:0.01", "max:999999.99"],
->   "errorMessageKey": "validation.{module}.amount.invalid"
-> }
-> ```
-> **MANDATORY fields:** `entity`, `field`, `rules` (array), `errorMessageKey`
-> **FORBIDDEN fields:** Do NOT use `rule` (singular string) or `message` (use `errorMessageKey`).
-
-#### 8i. Business Messages
-
-Minimum 4: success, error CRUD, error validation, error permission.
-
-> **STRUCTURE CARD: specification.messages[]**
-> ```json
-> {
->   "code": "{MODULE}-SUCCESS-CREATE",
->   "type": "success|error|warning|info",
->   "title": "Record Created",
->   "message": "The record {code} has been created successfully.",
->   "i18nKey": "message.{module}.created"
-> }
-> ```
-> **MANDATORY fields:** `code`, `type`, `message`, `i18nKey`
-> **FORBIDDEN:** Do NOT omit `title` or `i18nKey`. Every message MUST have an i18n key.
-
-#### 8j. Entity Lifecycle
-
-State machines for entities with status/state.
-**Note:** If depth = full and 3a-state was executed, lifeCycles are already defined. Verify completeness and add any missing states/transitions.
-
-> **STRUCTURE CARD: specification.lifeCycles[]**
-> ```json
-> {
->   "entity": "Order",
->   "field": "status",
->   "initialState": "draft",
->   "states": [
->     { "id": "draft", "displayName": "Brouillon", "color": "gray", "allowedTransitions": ["submitted"], "isTerminal": false },
->     { "id": "submitted", "displayName": "Soumis", "color": "blue", "allowedTransitions": ["approved", "rejected"], "isTerminal": false },
->     { "id": "approved", "displayName": "Approuvé", "color": "green", "allowedTransitions": ["archived"], "isTerminal": false },
->     { "id": "rejected", "displayName": "Rejeté", "color": "red", "allowedTransitions": [], "isTerminal": true },
->     { "id": "archived", "displayName": "Archivé", "color": "purple", "allowedTransitions": [], "isTerminal": true }
->   ],
->   "transitions": [
->     {
->       "from": "draft", "to": "submitted", "action": "submit",
->       "label": { "fr": "Soumettre", "en": "Submit" },
->       "permission": "business.{app}.{module}.update",
->       "guards": ["BR-VAL-{PREFIX}-001"],
->       "effects": [{ "type": "notification", "target": "role:manager", "template": "{module}-submitted" }],
->       "confirm": true
->     }
->   ]
-> }
-> ```
-> **MANDATORY:** `states` MUST be an array of OBJECTS with `id`, `displayName`, `color`, `allowedTransitions`, `isTerminal`. NEVER use flat string arrays.
-> **Colors:** gray (draft/new), blue (in-progress), green (active/approved), yellow (warning/pending), orange (review), red (error/rejected), purple (archived/terminal)
-> **FORBIDDEN:** Do NOT use `states: ["Active", "Inactive"]` (flat strings), `terminalStates` (use `isTerminal: true` on each state).
-
-#### 8k. API Endpoints
-
-RESTful routes following SmartStack patterns.
-
-> **STRUCTURE CARD: specification.apiEndpoints[]**
-> ```json
-> {
->   "method": "GET|POST|PUT|PATCH|DELETE",
->   "path": "/api/business/{app}/{module}",
->   "permission": "business.{app}.{module}.read",
->   "requestDto": "Get{Module}Query",
->   "responseDto": "{Module}Dto[]",
->   "description": "List all records with pagination and filters"
-> }
-> ```
-> **MANDATORY fields:** `method`, `path`, `permission`, `description`
-> **Recommended:** Include `requestDto` and `responseDto` for implementation clarity.
-
-#### 8l. i18n Keys
-
-Translation keys for all UI text (4 languages: fr, en, it, de).
-
-> **STRUCTURE CARD: specification.i18nKeys**
-> ```json
-> {
->   "title": { "fr": "{Module}", "en": "{Module}", "it": "{Module}", "de": "{Module}" },
->   "list": { "title": { "fr": "Liste", "en": "List" }, "empty": { "fr": "Aucun enregistrement", "en": "No records" } },
->   "create": { "title": { "fr": "Nouveau", "en": "New" } },
->   "detail": { "title": { "fr": "Détail", "en": "Detail" } },
->   "buttons": { "create": { "fr": "Créer", "en": "Create" }, "edit": { "fr": "Modifier", "en": "Edit" }, "delete": { "fr": "Supprimer", "en": "Delete" } },
->   "validation": { "required": { "fr": "Ce champ est requis", "en": "This field is required" } }
-> }
-> ```
-
 ### 9. Per-Module Validation
 
-> **Fused from old step-03-validate.md, run INLINE after specification.**
-
 #### 9a. Completeness Checks
 
 | Section | Minimum | Status |
@@ -413,6 +126,8 @@ ba-writer.enrichSection({
 })
 ```
 
+---
+
 ### 10. Module Summary with Roles & Permissions
 
 Display comprehensive summary:
@@ -458,6 +173,8 @@ options:
     description: "Modifier des éléments du module"
 ```
 
+---
+
 ### 11. Write Module Feature.json
 
 ```
@@ -506,6 +223,8 @@ 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.**
@@ -525,7 +244,7 @@ ba-writer.updateModuleStatus({feature_id}, {currentModule.code}, "specified")
 
 2. **Build FEATURE_DATA object:**
 
-   > **Use the EXACT SAME mapping defined in step-05b-deploy.md section 3.**
+   > **Use the EXACT SAME mapping defined in step-05d-html.md and references/html-data-mapping.md.**
    > 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"`).
 
@@ -572,7 +291,7 @@ ba-writer.advanceModuleLoop({feature_id})
 
 IF currentModuleIndex < moduleOrder.length:
   Display: "→ Module suivant: {nextModule} ({currentModuleIndex + 1}/{total})"
-  Load: steps/step-03a-specify.md
+  Load: steps/step-03a-data.md
 
 IF currentModuleIndex >= moduleOrder.length:
   Display: "═══ Tous les modules spécifiés! Passage à la consolidation... ═══"
@@ -599,7 +318,7 @@ Before proceeding to step-03a (next module) or step-04 (consolidation), VERIFY:
 
 When only 1 module in moduleOrder:
 
-- Same full specification flow
+- Same full validation flow
 - Skip cross-module references (section 5)
 - After validation → direct to step-04-consolidation.md (auto-consolidation)
 
@@ -642,21 +361,20 @@ Read metadata.workflow.currentModule
 
 ## SUCCESS METRICS
 
-- All sections walked through with client
-- ASCII mockups generated and validated for EVERY section (1 wireframe per section minimum)
-- Entities defined with business attributes
-- Business rules extracted and categorized
-- Per-module validation PASS
+- Module specification validation PASS
+- Per-module validation results recorded in feature.json
 - Client confirmed module specification
-- Module feature.json written
+- Module feature.json written with all sections
 - Master updated with module status
-- **Interactive HTML deployed/updated with completed module data (incremental)**
-- Loop advanced correctly
+- Interactive HTML deployed/updated with completed module data (incremental)
+- Loop advanced correctly or consolidation phase initiated
+
+---
 
 ## FAILURE MODES
 
 - Validation FAIL → offer auto-correct / manual revise / force
-- Client rejects → revise specific sections
+- Client rejects → revise specific sections via step-03a or step-03b
 - Cross-module reference error → clarify with client
 - Interruption → resumable via workflow state
 
@@ -666,5 +384,5 @@ Read metadata.workflow.currentModule
 
 Conditional:
 
-- IF modules remaining → Load `steps/step-03a-specify.md`
+- IF modules remaining → Load `steps/step-03a-data.md`
 - IF all modules done → Load `steps/step-04-consolidation.md`

package/templates/skills/business-analyse/steps/step-04-consolidation.md

@@ -1,7 +1,7 @@
 ---
 name: step-04-consolidation
 description: Cross-module consolidation - interactions, permission coherence, E2E flows, final approval
-model: sonnet
+model: opus
 next_step: steps/step-05a-handoff.md
 ---
 
@@ -412,7 +412,7 @@ options:
 ```
 
 IF "Réviser un module":
-  Ask which module → set currentModuleIndex to that module → load step-03a-specify.md
+  Ask which module → set currentModuleIndex to that module → load step-03a-data.md
 
 IF "Modifier les interactions":
   Re-enter section 2-4 of this step