@atlashub/smartstack-cli 3.8.0 → 3.9.0

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

@@ -122,72 +122,9 @@ For EACH section confirmed in 3a, build the `specification.sections[]` structure
 
 4. Build the section object:
 
-> **STRUCTURE CARD: specification.sections[]** — Resources MUST include full depth definitions.
-> ```json
-> {
->   "code": "list",
->   "labels": { "fr": "Liste", "en": "List", "it": "Elenco", "de": "Liste" },
->   "route": "/business/{app}/{module}/list",
->   "icon": "list",
->   "permission": "business.{app}.{module}.read",
->   "wireframe": "{module}-list",
->   "useCases": ["UC-{PREFIX}-001", "UC-{PREFIX}-002"],
->   "businessRules": ["BR-VAL-{PREFIX}-001"],
->   "resources": [
->     {
->       "code": "{module}-grid",
->       "type": "SmartTable",
->       "entity": "{MainEntity}",
->       "permission": "business.{app}.{module}.read",
->       "columns": ["name", "status", "createdAt"],
->       "columnDefs": [
->         { "field": "code", "label": {"fr": "Code", "en": "Code"}, "format": "text", "sortable": true, "filterable": true, "clickAction": "navigate:detail" },
->         { "field": "name", "label": {"fr": "Nom", "en": "Name"}, "format": "text", "sortable": true, "filterable": true },
->         { "field": "status", "label": {"fr": "Statut", "en": "Status"}, "format": "badge", "sortable": true, "filterable": true, "colorMap": "stateMachine:{Entity}" },
->         { "field": "createdAt", "label": {"fr": "Créé le", "en": "Created"}, "format": "date-relative", "sortable": true }
->       ],
->       "actions": ["view", "edit", "delete"],
->       "rowActions": [
->         { "action": "view", "icon": "eye", "permission": "business.{app}.{module}.read" },
->         { "action": "edit", "icon": "edit", "permission": "business.{app}.{module}.update", "showWhen": {"status": ["draft"]} },
->         { "action": "delete", "icon": "trash", "permission": "business.{app}.{module}.delete", "confirm": true }
->       ],
->       "filters": ["status", "dateRange"],
->       "defaultSort": { "field": "createdAt", "direction": "desc" },
->       "defaultPageSize": 20,
->       "emptyState": { "icon": "inbox", "message": {"fr": "Aucun enregistrement", "en": "No records"}, "createAction": true }
->     }
->   ]
-> }
-> ```
->
-> **SmartForm resource example (for create/edit sections):**
-> ```json
-> {
->   "code": "{module}-form",
->   "type": "SmartForm",
->   "entity": "{MainEntity}",
->   "permission": "business.{app}.{module}.create",
->   "fields": [
->     { "name": "code", "component": "Input", "required": true, "validation": "Unique, auto-generated" },
->     { "name": "name", "component": "Input", "required": true },
->     { "name": "type", "component": "Select", "required": true, "source": "EntityTypeEnum" },
->     { "name": "description", "component": "TextArea", "required": false },
->     { "name": "parentId", "component": "EntitySelect", "source": "ParentEntity", "required": true },
->     { "name": "startDate", "component": "DatePicker", "required": true },
->     { "name": "isActive", "component": "Toggle", "default": true }
->   ],
->   "formLayout": {
->     "type": "tabs",
->     "tabs": [
->       { "code": "general", "label": {"fr": "Général", "en": "General"}, "fields": ["code", "name", "type", "description"] },
->       { "code": "details", "label": {"fr": "Détails", "en": "Details"}, "fields": ["parentId", "startDate", "isActive"] }
->     ]
->   }
-> }
-> ```
-> **MANDATORY for SmartTable:** `columnDefs`, `rowActions`, `defaultSort`, `emptyState`
-> **MANDATORY for SmartForm:** `fields` with `component` type, `formLayout`
+See [references/ui-resource-cards.md](../references/ui-resource-cards.md) for exact JSON formats of `specification.sections[]` (SmartTable + SmartForm resources).
+**MANDATORY for SmartTable:** `columnDefs`, `rowActions`, `defaultSort`, `emptyState`
+**MANDATORY for SmartForm:** `fields` with `component` type, `formLayout`
 
 5. Write `specification.sections[]` via ba-writer.enrichSection()
 
@@ -218,39 +155,9 @@ Example for a list section:
 
 Store in specification.uiWireframes[] (**MANDATORY** for every section):
 
-> **STRUCTURE CARD: specification.uiWireframes[]** — ALL fields below are MANDATORY.
-> ```json
-> {
->   "screen": "{module}-{section}",
->   "section": "{section}",
->   "description": "Description of the screen",
->   "mockupFormat": "ascii",
->   "mockup": "╔═══...",
->   "elements": ["DataGrid", "FilterBar", "Pagination", "CreateButton"],
->   "actions": ["filter", "sort", "create", "view-detail"],
->   "permissionsRequired": ["business.{app}.{module}.read"],
->   "componentMapping": [
->     { "wireframeElement": "DataGrid", "reactComponent": "SmartTable" },
->     { "wireframeElement": "FilterBar", "reactComponent": "SmartFilter" },
->     { "wireframeElement": "CreateButton", "reactComponent": "Button" }
->   ],
->   "layout": {
->     "type": "page",
->     "regions": [
->       { "id": "toolbar", "position": "top", "components": [
->         { "type": "FilterBar", "resourceRef": "{module}-filters" },
->         { "type": "ActionMenu", "resourceRef": "{module}-actions", "permission": "business.{app}.{module}.create" }
->       ]},
->       { "id": "content", "position": "main", "span": 12, "components": [
->         { "type": "SmartTable", "resourceRef": "{module}-grid" }
->       ]}
->     ]
->   }
-> }
-> ```
-> **REQUIRED fields:** `screen`, `mockup`, `elements`, `section`, `componentMapping`, `layout` are ALL mandatory.
-> A wireframe without `componentMapping` or `layout` will FAIL validation in step 9.
-> **layout.regions[].components[].resourceRef** MUST match a `sections[].resources[].code`.
+See [references/ui-resource-cards.md](../references/ui-resource-cards.md) for exact JSON format of `specification.uiWireframes[]`.
+**REQUIRED fields:** `screen`, `mockup`, `elements`, `section`, `componentMapping`, `layout` are ALL mandatory.
+A wireframe without `componentMapping` or `layout` will FAIL validation in step 9.
 
 Ask client to validate each mockup via AskUserQuestion (batch 2-3 mockups at once if possible).
 
@@ -313,85 +220,12 @@ For each section, identify what resources/components are needed:
 
 ### 3d. Dashboard Specification (if section = dashboard)
 
-When a "dashboard" section is selected, capture structured KPI and chart data **in addition** to the standard ASCII mockup.
-
-1. **Ask client for KPIs** via AskUserQuestion (batch):
-   - KPI name and metric description
-   - Visualization type: `kpi-card`, `bar`, `line`, `pie`, `area`, `donut`, `stacked-bar`
-   - Data source entity
-   - Format: `number`, `currency`, `percent`, `duration`
-   - Thresholds (warning/critical) if applicable
-
-2. **Ask client for filters:**
-   - Date range filter? Default period? (day/week/month/quarter/year)
-   - Entity-based filters? (status, category, etc.)
-
-3. **Ask client for refresh mode:**
-   - Static (load on page open)
-   - Polling (periodic refresh)
-   - SignalR (real-time push)
-
-4. **Store in specification.dashboards[]:**
-
-```json
-{
-  "code": "{module}-dashboard",
-  "title": "{Module} Dashboard",
-  "description": "Vue d'ensemble des métriques {module}",
-  "linkedUCs": ["UC-XXX"],
-  "refreshMode": "static",
-  "defaultPeriod": "month",
-  "kpis": [
-    {
-      "code": "total-items",
-      "label": "Total Items",
-      "metric": "COUNT(entity)",
-      "format": "number",
-      "visualization": "kpi-card",
-      "dataSource": "Entity",
-      "thresholds": { "warning": 100, "critical": 50 }
-    },
-    {
-      "code": "items-by-status",
-      "label": "Items by Status",
-      "metric": "COUNT(entity) GROUP BY status",
-      "format": "number",
-      "visualization": "pie",
-      "dataSource": "Entity",
-      "dimensions": ["status"]
-    }
-  ],
-  "filters": [
-    { "field": "dateRange", "type": "dateRange", "label": "Période" },
-    { "field": "status", "type": "multiselect", "label": "Statut" }
-  ],
-  "permissionsRequired": ["business.{app}.{module}.read"]
-}
-```
-
-5. **ALSO generate the standard ASCII mockup** for the dashboard with KPI cards + chart placeholders:
-
-```
-╔═══════════════════════════════════════════════════════════════╗
-║  {Module} > Dashboard              Période: [Ce mois ▾]     ║
-╠═══════════════════════════════════════════════════════════════╣
-║  ┌──────────┐  ┌──────────┐  ┌──────────┐  ┌──────────┐    ║
-║  │ KPI #1   │  │ KPI #2   │  │ KPI #3   │  │ KPI #4   │    ║
-║  │  1,234   │  │  567     │  │  89.2%   │  │  12,400  │    ║
-║  │  ↑ +12%  │  │  ↓ -3%  │  │  → 0%   │  │  ↑ +5%   │    ║
-║  └──────────┘  └──────────┘  └──────────┘  └──────────┘    ║
-╠═══════════════════════════════════════════════════════════════╣
-║  ┌─────────────────────────┐  ┌─────────────────────────┐    ║
-║  │  [Bar Chart]            │  │  [Pie Chart]            │    ║
-║  │  Items by Month         │  │  Items by Status        │    ║
-║  │  ████                   │  │      ████████           │    ║
-║  │  ████ ████              │  │   ███      ███          │    ║
-║  │  ████ ████ ████         │  │  ██   42%    ██         │    ║
-║  └─────────────────────────┘  └─────────────────────────┘    ║
-╚═══════════════════════════════════════════════════════════════╝
-```
-
-Store the mockup in specification.wireframes[] AS WELL (for visual reference).
+See [references/ui-dashboard-spec.md](../references/ui-dashboard-spec.md) for the complete dashboard capture process:
+- Ask client for KPIs (name, visualization type, format, thresholds)
+- Ask client for filters (date range, entity-based)
+- Ask client for refresh mode (static/polling/SignalR)
+- Store in `specification.dashboards[]` with full JSON template
+- Generate standard ASCII mockup with KPI cards + chart placeholders
 
 ---
 

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

@@ -228,56 +228,11 @@ 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.
+> The client can review completed modules while the next module is being specified.
 
-**Source:** `html/ba-interactive.html` (relative to skill root = `~/.claude/skills/business-analyse/html/`)
+See [references/validate-incremental-html.md](../references/validate-incremental-html.md) for the complete deployment process (read sources, build FEATURE_DATA, replace placeholders, write 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-05b-deploy.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"`).
-
-   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.
+Uses the **same mapping** as step-05b-deploy.md — only difference is `moduleSpecs` only includes completed modules.
 
 ---
 

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

@@ -212,112 +212,17 @@ Store results in consolidation.semanticChecks[]:
 
 ### 4-bis. Structural Schema Conformity Check (MANDATORY)
 
-> **Post-generation validation.** After semantic checks, verify that ALL module feature.json files conform to the JSON schema structure. This catches field name mismatches, missing sections, and wrong nesting.
-
-For EACH module feature.json, run these structural checks:
-
-**A. Required Sections Presence**
-
-| Section | Required | Check |
-|---------|----------|-------|
-| `metadata` | YES | Must have: app, module, language, featureDescription, featureType |
-| `discovery` | YES | Must exist (even if minimal) |
-| `analysis.entities[]` | YES | Must have ≥1 entity |
-| `analysis.businessRules[]` | YES | Must have ≥1 BR |
-| `analysis.objectives[]` | YES | Must have ≥1 objective |
-| `analysis.processFlow` | YES | Must have entryPoints, mainFlow, decisionPoints |
-| `analysis.dataLifecycle` | YES | Must have retention, archival, deletion, gdprRelevant |
-| `specification.useCases[]` | YES | Must have ≥1 UC |
-| `specification.functionalRequirements[]` | YES | Must have ≥1 FR |
-| `specification.permissionMatrix` | YES | Must be `{permissions[], roleAssignments[]}` (NOT flat array) |
-| `specification.sections[]` | YES | Must have ≥1 section with resources |
-| `specification.uiWireframes[]` | YES | Must have ≥1 wireframe with `layout` object |
-| `specification.lifeCycles[]` | IF entities have status | States must be objects (NOT strings) |
-| `specification.seedDataCore` | YES | Must have 5 arrays: navigationModules, navigationTranslations, permissions, rolePermissions, permissionConstants |
-| `specification.gherkinScenarios` | YES | Must be `{feature, scenarios[]}` (NOT flat array) |
-| `specification.navigation` | YES | Must have entries[] |
-| `specification.i18nKeys[]` | YES | Must have ≥1 key with fr, en, nl, de |
-| `validation` | YES | Must have completenessChecks, consistencyChecks, semanticChecks, decision |
-| `handoff` | Written by step-05 | Checked post-handoff |
-
-**B. Field Name Conformity**
-
-For each section, verify NO FORBIDDEN field names are used:
-
-| Section | FORBIDDEN fields | Correct fields |
-|---------|-----------------|----------------|
-| `entities[].attributes[]` | `type`, `values`, `rules` | `description`, `unique`, `validation` |
-| `businessRules[]` | `rule`, `condition` (singular), `action` | `name`, `statement`, `conditions[]` |
-| `useCases[]` | `actor`, `linkedBRs`, `linkedFRs` | `primaryActor`, `linkedRules` |
-| `functionalRequirements[]` | `name`, `description`, `linkedUCs`, `linkedBRs` | `statement`, `linkedUseCases`, `linkedRules` |
-| `permissionMatrix` | flat array with `resource`/`roles` | `{permissions[], roleAssignments[]}` |
-| `lifeCycles[].states[]` | string values like `"Active"` | objects with `{id, displayName, color, isTerminal}` |
-| `seedDataCore` | flat object, string values | 5 typed arrays |
-| `gherkinScenarios` | flat scenario array | `{feature, scenarios[]}` nested |
-
-**C. ID Pattern Conformity**
-
-| ID Type | Pattern | Example |
-|---------|---------|---------|
-| BR | `BR-(VAL\|CALC\|WF\|SEC\|DATA)-{PREFIX}-\d{3}` | BR-VAL-RM-001 |
-| UC | `UC-{PREFIX}-\d{3}` | UC-RM-001 |
-| FR | `FR-{PREFIX}-\d{3}` | FR-RM-001 |
-| Permissions | `business.{app}.{module}.{resource}.{action}` | business.freebike.repairs.create |
-
-Verify all IDs use the correct module prefix (2-4 uppercase letters).
-
-**D. Cross-Module ID Uniqueness**
-
-Verify no ID collision across modules:
-```
-SET all_ids = {}
-FOR each module:
-  FOR each BR, UC, FR id:
-    IF id IN all_ids → ERROR: "Duplicate {id} in {module1} and {module2}"
-    ADD id to all_ids
-```
+> **Post-generation validation.** After semantic checks, verify ALL module feature.json files conform to JSON schema.
 
-**E. Wireframe Layout Completeness**
+See [references/consolidation-structural-checks.md](../references/consolidation-structural-checks.md) for the full 6-category structural check:
+- **A.** Required Sections Presence (18 sections)
+- **B.** Field Name Conformity (forbidden vs correct fields)
+- **C.** ID Pattern Conformity (BR, UC, FR, Permissions)
+- **D.** Cross-Module ID Uniqueness
+- **E.** Wireframe Layout Completeness
+- **F.** SeedDataCore Translation Coverage
 
-For each `uiWireframes[]`:
-```
-IF missing componentMapping[] → ERROR
-IF missing layout object → ERROR
-IF missing layout.regions[] → ERROR
-FOR each region in layout.regions[]:
-  IF missing position → ERROR
-  IF missing components[] → ERROR
-```
-
-**F. SeedDataCore Translation Coverage**
-
-```
-FOR each navigationModules[].code:
-  FOR each language in [fr, en, nl, de]:
-    IF NOT EXISTS navigationTranslations[] with moduleCode AND language → ERROR
-```
-
-**Result aggregation:**
-```json
-{
-  "structuralChecks": [
-    { "check": "required-sections", "module": "...", "status": "PASS|ERROR", "details": "Missing: analysis.objectives" },
-    { "check": "field-names", "module": "...", "status": "PASS|ERROR", "details": "businessRules[0] uses 'rule' instead of 'name'+'statement'" },
-    { "check": "id-patterns", "module": "...", "status": "PASS|ERROR", "details": "BR-001 missing category segment" },
-    { "check": "id-uniqueness", "module": "...", "status": "PASS|ERROR", "details": "UC-RM-003 duplicated in Vehicles and Repairs" },
-    { "check": "wireframe-layout", "module": "...", "status": "PASS|ERROR", "details": "Wireframe repairs-list missing layout object" },
-    { "check": "seeddata-translations", "module": "...", "status": "PASS|ERROR", "details": "Missing nl translation for NavigationModuleRepairs" }
-  ]
-}
-```
-
-**Blocking rule:**
-- 0 ERROR → PASS (merge structuralChecks into consolidation.semanticChecks[])
-- ≥1 ERROR → BLOCK. For each ERROR:
-  1. Attempt AUTO-FIX (rename fields, restructure)
-  2. Re-write the module feature.json with fixes
-  3. Re-check
-  4. If still ERROR → ask user
+**Blocking rule:** 0 ERROR → PASS. ≥1 ERROR → BLOCK (attempt auto-fix, re-write, re-check).
 
 ### 5. End-to-End Flows