@atlashub/smartstack-cli 3.18.0 → 3.19.0

package/templates/skills/business-analyse/references/ui-resource-cards.md

@@ -73,6 +73,98 @@
 
 **MANDATORY for SmartForm:** `fields` with `component` type, `formLayout`
 
+## Detail Page section (reached from list click)
+
+> **RULE:** The detail page is NOT a sidebar navigation entry. It is reached by clicking a row in the `list` section. Its route includes `:id` parameter. Every module with a `list` section MUST have a companion detail page.
+
+```json
+{
+  "code": "detail",
+  "labels": { "fr": "Détail", "en": "Detail", "it": "Dettaglio", "de": "Detail" },
+  "route": "/business/{app}/{module}/detail/:id",
+  "icon": "file-text",
+  "permission": "business.{app}.{module}.read",
+  "wireframe": "{module}-detail",
+  "navigation": "hidden",
+  "useCases": ["UC-{PREFIX}-002"],
+  "businessRules": ["BR-VAL-{PREFIX}-001"],
+  "resources": [
+    {
+      "code": "{module}-detail-header",
+      "type": "DetailHeader",
+      "entity": "{MainEntity}",
+      "permission": "business.{app}.{module}.read",
+      "fields": ["code", "name", "status"],
+      "actions": [
+        { "action": "edit", "icon": "edit", "permission": "business.{app}.{module}.update", "showWhen": {"status": ["draft"]} },
+        { "action": "delete", "icon": "trash", "permission": "business.{app}.{module}.delete", "confirm": true }
+      ],
+      "statusBadge": { "field": "status", "colorMap": "stateMachine:{Entity}" }
+    },
+    {
+      "code": "{module}-detail-tabs",
+      "type": "TabPanel",
+      "entity": "{MainEntity}",
+      "permission": "business.{app}.{module}.read",
+      "tabs": [
+        {
+          "code": "info",
+          "label": {"fr": "Informations", "en": "Information", "it": "Informazioni", "de": "Informationen"},
+          "icon": "info",
+          "default": true,
+          "content": {
+            "type": "DetailCard",
+            "resourceRef": "{module}-info-card",
+            "fields": ["code", "name", "type", "description", "startDate", "createdAt"],
+            "editMode": {
+              "enabled": true,
+              "formRef": "{module}-form",
+              "permission": "business.{app}.{module}.update"
+            }
+          }
+        },
+        {
+          "code": "{relation}",
+          "label": {"fr": "{RelationLabel}", "en": "{RelationLabel}"},
+          "icon": "list",
+          "content": {
+            "type": "SmartTable",
+            "resourceRef": "{module}-{relation}-grid",
+            "entity": "{RelatedEntity}",
+            "parentFilter": "{MainEntity}Id"
+          }
+        },
+        {
+          "code": "history",
+          "label": {"fr": "Historique", "en": "History", "it": "Storico", "de": "Verlauf"},
+          "icon": "clock",
+          "showWhen": "auditable",
+          "content": {
+            "type": "Timeline",
+            "resourceRef": "{module}-history",
+            "source": "auditLog"
+          }
+        }
+      ]
+    }
+  ]
+}
+```
+
+**MANDATORY for detail section:**
+- `navigation: "hidden"` — detail page is NOT shown in sidebar, reached by row click from list
+- `route` MUST contain `:id` parameter
+- At least one `TabPanel` resource with `tabs[]`
+- First tab MUST be "info" with `DetailCard` + `editMode`
+- One tab per 1:N relationship (auto-inferred from entity relationships)
+- History tab if entity is auditable (has lifeCycles)
+
+**Tab auto-generation rules:**
+1. **Info tab** (always) — all entity attributes displayed as read-only fields, with edit toggle
+2. **Relation tabs** (per 1:N relationship) — SmartTable filtered by `parentFilter`
+3. **History tab** (if auditable) — Timeline from audit log
+4. **Custom tabs** (from cadrage `detailTabs[]`) — any additional tabs specified during cadrage
+
 ## specification.uiWireframes[]
 
 ```json
@@ -108,3 +200,60 @@
 **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`.
+
+## Detail Page Wireframe
+
+> **RULE:** For every `list` section, a companion detail wireframe MUST exist with `section: "detail"`.
+
+```json
+{
+  "screen": "{module}-detail",
+  "section": "detail",
+  "description": "Page de détail avec onglets — accessible depuis la liste par clic sur une ligne",
+  "mockupFormat": "ascii",
+  "mockup": "╔═══════════════════════════════════════════════════════════╗\n║  ← Retour à la liste                                    ║\n╠═══════════════════════════════════════════════════════════╣\n║  {Entity} : {code} — {name}        ● Statut  [✏️] [🗑️]  ║\n╠═══════════════════════════════════════════════════════════╣\n║  [ Informations ]  [ {Relation} ]  [ Historique ]        ║\n╠═══════════════════════════════════════════════════════════╣\n║  ┌─────────────────────────────────────────────────────┐  ║\n║  │  Code:        {code}                                │  ║\n║  │  Nom:         {name}                                │  ║\n║  │  Type:        {type}                 [Modifier]     │  ║\n║  │  Description: {description}                         │  ║\n║  │  Créé le:     {createdAt}                           │  ║\n║  └─────────────────────────────────────────────────────┘  ║\n╚═══════════════════════════════════════════════════════════╝",
+  "elements": [
+    { "id": "elem-back", "type": "BackButton", "label": "Retour à la liste" },
+    { "id": "elem-header", "type": "DetailHeader", "label": "En-tête entité" },
+    { "id": "elem-status", "type": "StatusBadge", "label": "Badge statut" },
+    { "id": "elem-tabs", "type": "TabPanel", "label": "Onglets de détail" },
+    { "id": "elem-info", "type": "DetailCard", "label": "Carte informations" },
+    { "id": "elem-edit", "type": "SmartForm", "label": "Formulaire d'édition" }
+  ],
+  "actions": [
+    { "trigger": "Click back", "action": "Navigate to list" },
+    { "trigger": "Click edit", "action": "Toggle edit mode on info tab" },
+    { "trigger": "Click tab", "action": "Switch tab content" },
+    { "trigger": "Click status action", "action": "Trigger state transition (if lifeCycles)" }
+  ],
+  "componentMapping": [
+    { "wireframeElement": "BackButton", "reactComponent": "BackButton" },
+    { "wireframeElement": "DetailHeader", "reactComponent": "EntityDetailHeader" },
+    { "wireframeElement": "StatusBadge", "reactComponent": "StatusBadge" },
+    { "wireframeElement": "TabPanel", "reactComponent": "Tabs" },
+    { "wireframeElement": "DetailCard", "reactComponent": "EntityDetailCard" },
+    { "wireframeElement": "SmartForm", "reactComponent": "SmartForm" }
+  ],
+  "layout": {
+    "type": "page",
+    "regions": [
+      { "id": "header", "position": "top", "components": [
+        { "type": "BackButton", "target": "/business/{app}/{module}/list" },
+        { "type": "DetailHeader", "resourceRef": "{module}-detail-header" },
+        { "type": "StatusBadge", "resourceRef": "{module}-status" }
+      ]},
+      { "id": "tabs", "position": "main", "span": 12, "components": [
+        { "type": "TabPanel", "resourceRef": "{module}-detail-tabs" }
+      ]}
+    ]
+  },
+  "permissionsRequired": ["business.{app}.{module}.read"]
+}
+```
+
+**Detail wireframe adaptation rules:**
+- **Tabs** must match `sections[code=detail].resources[type=TabPanel].tabs[]`
+- **Relation tabs** show a SmartTable of child entities filtered by parent ID
+- **History tab** only included if entity has `lifeCycles` defined
+- **Edit button** only shown if user has `update` permission
+- **Status actions** only shown if entity has state machine transitions from current state

package/templates/skills/business-analyse/steps/step-01-cadrage.md

@@ -6,6 +6,7 @@ next_step: steps/step-02-decomposition.md
 ---
 
 > **Context files:** `_shared.md` | `_elicitation.md` | `_architecture.md` | `_suggestions.md`
+> **Reference (4d-bis):** `references/entity-architecture-decision.md` — Entity scoring, domain coherence, section patterns
 
 # Step 1: Cadrage (Framing)
 
@@ -135,11 +136,12 @@ pre_analysis:
 
 **Modules identifiés :**
 - **{Module 1}** : {functional description}
-  - Sections pressenties : {list, detail, create, edit...}
-  - Resources clés : {grid, form, card, chart...}
+  - Section **list** : {entity}-grid, {entity}-filters, {entity}-form (création en modale)
+  - Page détail (onglets) : {Infos, {relation_tabs}...}
+  - {IF dashboard needed:} Section **dashboard** : {kpi-cards, charts...}
 - **{Module 2}** : {functional description}
-  - Sections pressenties : {list, create...}
-  - Resources clés : {grid, form...}
+  - Section **list** : {entity}-grid, {entity}-filters, {entity}-form
+  - Page détail (onglets) : {Infos, ...}
 
 **Points que j'ai notés :**
 - {specific point 1 from the brief, quoted verbatim when possible}
@@ -209,10 +211,31 @@ Ask in 1-2 batches. After each batch:
 **Mandatory minimum:** Q3.2 (must-have), Q3.4 (exclusions), Q3.5 (main journey).
 
 Ask in 1-2 batches. After each batch:
-- If everything is "must-have" → apply priority test: "If you could only keep 3 features, which ones?"
+- If everything is "must-have" → **BLOCKING**: apply MoSCoW prioritization question (see POST-CHECK below)
 - If no exclusions → probe: "What should this system explicitly NOT do?"
 - If journey is too simple → detail: "What happens when something goes wrong? When someone cancels?"
 
+> **BLOCKING RULE — MoSCoW DISTRIBUTION:**
+> If the client classifies ALL features as "must-have", you MUST challenge this BEFORE proceeding.
+> Ask via AskUserQuestion:
+> ```
+> question: "{language == 'fr'
+>   ? 'Toutes les fonctionnalités sont marquées indispensables. Si vous ne pouviez livrer que 60% du périmètre en v1, lesquelles pourraient attendre la v2 ?'
+>   : 'All features are marked must-have. If you could only deliver 60% of scope in v1, which ones could wait for v2?'}"
+> header: "Priorisation"
+> multiSelect: true
+> options:
+>   - label: "{feature_1}"
+>     description: "{language == 'fr' ? 'Pourrait passer en Important (v1.x)' : 'Could move to Important (v1.x)'}"
+>   - label: "{feature_2}"
+>     description: "{language == 'fr' ? 'Pourrait passer en Optionnel (v2)' : 'Could move to Optional (v2)'}"
+>   - label: "{feature_3}"
+>     description: "{language == 'fr' ? 'Pourrait passer en Important (v1.x)' : 'Could move to Important (v1.x)'}"
+>   - label: "{language == 'fr' ? 'Tout est vraiment indispensable' : 'Everything is truly must-have'}"
+>     description: "{language == 'fr' ? 'Je confirme que toutes les fonctionnalités sont critiques pour la v1' : 'I confirm all features are critical for v1'}"
+> ```
+> If client moves items → update categories. If client confirms ALL mustHave → accept but log in changelog.
+
 #### 4d. Challenge Implicit Assumptions (CRITICAL)
 
 > **Apply elicitation techniques to challenge what the client considers "obvious".**
@@ -243,46 +266,174 @@ Ask challenge questions via AskUserQuestion (1-2 batches of max 4).
 
 #### 4d-bis. Entity Sourcing Pattern (MANDATORY for detected dependencies)
 
-> **When the analysis detects a referenced entity/concept (e.g., "Projets" referenced by activities, "Clients" referenced by orders), ALWAYS ask how this entity is sourced.**
-> This question detects potential new modules that were not mentioned in the original brief.
+> **When the analysis detects a referenced entity/concept (e.g., "Projets" referenced by activities, "Clients" referenced by orders), ALWAYS analyze and recommend BEFORE asking the client.**
+> This pattern detects potential new modules not mentioned in the original brief.
+> **Reference:** Load [references/entity-architecture-decision.md](../references/entity-architecture-decision.md) for scoring grid, decision tree, and section patterns.
 
 For EACH referenced entity/concept detected during phases 2-4 that is NOT already covered by an identified module:
 
-Ask via AskUserQuestion:
+##### PHASE 1 — ULTRATHINK: Silent Architecture Analysis (NO output to client)
+
+> **The AI reasons about the entity BEFORE presenting options. This is internal thinking only.**
+
+```
+ULTRATHINK — Entity Architecture Analysis for {entity_name}:
+
+1. DOMAIN COHERENCE (from decision tree in reference)
+   - Application domain: {app_description}
+   - Entity fit: CORE | SUPPORT | PERIPHERAL
+   - Justification: {1 sentence — why this entity is/isn't core to the app}
+   - Example: "Projets" in a time management app = CORE (without projects, time entries have no target)
+   - Example: "Codes d'imputation" in a time management app = SUPPORT (useful for accounting, but not central)
+
+2. ENTITY SCORING (5 criteria, 0-3 each — from scoring grid in reference)
+   - Lifecycle:  {score}/3 — {brief justification}
+   - Actors:     {score}/3 — {brief justification}
+   - Relations:  {score}/3 — {brief justification}
+   - Volume:     {score}/3 — {brief justification}
+   - Autonomy:   {score}/3 — {brief justification}
+   - TOTAL:      {total}/15 → {classification: config_list | in_app | light_module | full_module}
+
+3. PRE-CLASSIFICATION CHECK (from entity patterns in reference)
+   - Does {entity_name} match a known pattern? → {yes: which one | no: use scoring}
+   - Override needed? → {yes: why | no}
+
+4. RECOMMENDATION
+   - Option: {config_list | in_app_section | new_module | external_system}
+   - Confidence: HIGH | MEDIUM | LOW
+   - Reasoning: {1-2 sentences}
+   - Risk if wrong choice: {what goes wrong if user picks a different option}
+
+5. IF recommendation = new_module → PRE-BUILD ARCHITECTURE
+   - Module code: {PascalCase}
+   - Section `list`: {main entity grid + create action + navigation to detail}
+   - Detail page tabs: [{tab_name: content}] (accessible by clicking a row in list)
+   - Additional sections: [{code: justification}] (ONLY functional zones: dashboard, approve, import, rapport...)
+   - Dependencies: [{which modules reference/are referenced by this entity}]
+   - Topological position: layer {N} (foundation if no dependencies)
+```
+
+##### PHASE 2 — Present Analysis & Recommendation to Client
+
+**BEFORE the AskUserQuestion, display the analysis as markdown:**
+
+```
+### {language == "fr" ? "Analyse" : "Analysis"} : {entity_plural}
+
+{language == "fr"
+  ? "Les **{entity_plural}** sont référencés par {parent_module} ({relationship_description})."
+  : "**{entity_plural}** are referenced by {parent_module} ({relationship_description})."}
+
+{language == "fr" ? "**Mon analyse :**" : "**My analysis:**"}
+- {language == "fr" ? "Cohérence domaine" : "Domain coherence"} : **{CORE|SUPPORT|PERIPHERAL}** — {justification}
+- {language == "fr" ? "Score de complexité" : "Complexity score"} : **{score}/15** ({classification})
+- {language == "fr" ? "Recommandation" : "Recommendation"} : **{recommended_option}** — {reasoning}
+```
+
+**IF recommendation = new_module AND confidence >= MEDIUM, ALSO display:**
+
+```
+{language == "fr" ? "**Architecture proposée :**" : "**Proposed architecture:**"}
+
+| {language == "fr" ? "Niveau" : "Level"} | {language == "fr" ? "Valeur" : "Value"} | {language == "fr" ? "Justification" : "Rationale"} |
+|--------|--------|---------------|
+| Context | `business` | {language == "fr" ? "Contexte métier standard" : "Standard business context"} |
+| Application | `{app_code}` | {app_name} |
+| Module | `{ModuleCode}` | {language == "fr" ? "{pourquoi ce découpage}" : "{why this decomposition}"} |
+
+| Section | {language == "fr" ? "Justification" : "Rationale"} | Resources |
+|---------|---------------|-----------|
+| `list` | {language == "fr" ? "Page principale : grille, création, navigation vers détail" : "Main page: grid, create action, navigate to detail"} | {entity}-grid, {entity}-filters, {entity}-form |
+| {additional_section} | {justification} | {resources} |
+
+{language == "fr"
+  ? "**Page détail** (onglets accessibles depuis la liste) :"
+  : "**Detail page** (tabs accessible from list):"}
+
+| {language == "fr" ? "Onglet" : "Tab"} | {language == "fr" ? "Contenu" : "Content"} |
+|--------|---------|
+| {language == "fr" ? "Informations" : "Information"} | {language == "fr" ? "Fiche principale" : "Main record"} |
+| {tab_name} | {tab_content} |
+
+{language == "fr"
+  ? "**Impact :** {ModuleName} deviendra une dépendance de {parent_module} (couche {N} du graphe)."
+  : "**Impact:** {ModuleName} will become a dependency of {parent_module} (layer {N} in the graph)."}
+```
+
+##### PHASE 3 — Ask with Recommended Option First
+
+**Order the options with the recommendation FIRST, marked "(Recommandé)" / "(Recommended)":**
+
 ```
 question: "{language == 'fr'
-  ? 'Les {entity_plural} auxquel(le)s les {parent_entity_plural} sont lié(e)s : comment sont-ils gérés ?'
-  : 'The {entity_plural} that {parent_entity_plural} are linked to: how are they managed?'}"
+  ? 'Comment souhaitez-vous gérer les {entity_plural} ?'
+  : 'How do you want to manage {entity_plural}?'}"
 header: "{entity_name}"
 options:
-  - label: "{language == 'fr' ? 'Gérés dans l\'app' : 'Managed in app'}"
+  (ORDER: recommended option FIRST, then the 3 remaining options in logical order)
+
+  IF recommendation = new_module:
+  - label: "{language == 'fr' ? 'Nouveau module dédié (Recommandé)' : 'New dedicated module (Recommended)'}"
+    description: "{language == 'fr'
+      ? 'Module {ModuleCode} avec page liste, détail par onglets, permissions dédiées'
+      : '{ModuleCode} module with list page, tabbed detail, dedicated permissions'}"
+  - label: "{language == 'fr' ? 'Géré dans l\'app' : 'Managed in app'}"
+    description: "..."
+  - label: "{language == 'fr' ? 'Système externe' : 'External system'}"
+    description: "..."
+  - label: "{language == 'fr' ? 'Liste simple en config' : 'Simple config list'}"
+    description: "..."
+
+  IF recommendation = config_list:
+  - label: "{language == 'fr' ? 'Liste simple en config (Recommandé)' : 'Simple config list (Recommended)'}"
     description: "{language == 'fr'
-      ? 'Les {entity_plural} sont créés et gérés dans cette application (liste simple)'
-      : '{entity_plural} are created and managed in this application (simple list)'}"
+      ? 'Table de référence administrable, pas de module dédié'
+      : 'Admin-managed reference table, no dedicated module'}"
+  - label: "{language == 'fr' ? 'Géré dans l\'app' : 'Managed in app'}"
+    description: "..."
   - label: "{language == 'fr' ? 'Nouveau module dédié' : 'New dedicated module'}"
+    description: "..."
+  - label: "{language == 'fr' ? 'Système externe' : 'External system'}"
+    description: "..."
+
+  IF recommendation = in_app_section:
+  - label: "{language == 'fr' ? 'Géré dans l\'app (Recommandé)' : 'Managed in app (Recommended)'}"
     description: "{language == 'fr'
-      ? 'Les {entity_plural} méritent leur propre module avec CRUD complet, permissions et navigation'
-      : '{entity_plural} deserve their own module with full CRUD, permissions and navigation'}"
+      ? 'Accessible via un onglet dans la page détail de {parent_module}'
+      : 'Accessible via a tab in {parent_module} detail page'}"
+  - label: "{language == 'fr' ? 'Nouveau module dédié' : 'New dedicated module'}"
+    description: "..."
+  - label: "{language == 'fr' ? 'Liste simple en config' : 'Simple config list'}"
+    description: "..."
   - label: "{language == 'fr' ? 'Système externe' : 'External system'}"
+    description: "..."
+
+  IF recommendation = external_system:
+  - label: "{language == 'fr' ? 'Système externe (Recommandé)' : 'External system (Recommended)'}"
     description: "{language == 'fr'
       ? 'Les {entity_plural} viennent d\'un autre système (import ou API)'
       : '{entity_plural} come from another system (import or API)'}"
+  - label: "{language == 'fr' ? 'Nouveau module dédié' : 'New dedicated module'}"
+    description: "..."
+  - label: "{language == 'fr' ? 'Géré dans l\'app' : 'Managed in app'}"
+    description: "..."
   - label: "{language == 'fr' ? 'Liste simple en config' : 'Simple config list'}"
-    description: "{language == 'fr'
-      ? 'Juste une liste configurable par l\'admin, pas un module complet'
-      : 'Just a configurable list managed by admin, not a full module'}"
+    description: "..."
+
+  IF confidence = LOW (no clear recommendation):
+  (all 4 options in neutral order, NO "(Recommandé)" tag)
 ```
 
-**Processing each answer:**
+##### PHASE 4 — Process Answer
 
 | Choice | Action |
 |--------|--------|
-| **Gérés dans l'app** | Entity stays as a child/section of the current module. Note in coverageMatrix. |
-| **Nouveau module dédié** | **Add new module to `{pre_analysis}.detected_modules[]`**. Flag for inclusion in decomposition (step-02). Add to `coverageMatrix` as mustHave with anticipated sections (list, detail, create, edit). This module becomes a dependency of the referencing module. |
+| **Géré dans l'app** | Entity becomes a sub-entity of the parent module. Add as a **tab in the detail page** of the referencing module. Note in coverageMatrix with `parentModule` field. |
+| **Nouveau module dédié** | **Add new module to `{pre_analysis}.detected_modules[]`** with the proposed architecture (sections, detail tabs, dependencies). Add to `coverageMatrix` as mustHave. The `list` section is ALWAYS the main section. Additional sections ONLY for distinct functional zones (dashboard, approve, import...). `create` and `edit` are ACTIONS within `list` and detail pages, NEVER standalone sections. |
 | **Système externe** | Flag for integration specification. Add to `coverageMatrix` as integration. Load `questionnaire/05-integrations.md` if not already loaded. |
-| **Liste simple en config** | Entity becomes a lookup/reference table (no dedicated module). Note in coverageMatrix as config data. |
+| **Liste simple en config** | Entity becomes a lookup/reference table (no dedicated module, no section). Note in coverageMatrix as config data. |
 
-> **CRITICAL:** The "Nouveau module dédié" option is essential for detecting modules not mentioned in the original brief. Without it, complex entities get reduced to simple config lists when they deserve full CRUD management.
+> **CRITICAL:** The intelligence of this step is in the ULTRATHINK analysis. The AI must REASON about domain coherence, score the entity, and recommend — not just present 4 neutral options. The client can always override the recommendation, but they should benefit from expert architectural guidance.
 
 #### 4e. Risks & Success Criteria (ALWAYS — from `questionnaire/14-risk-assumptions.md` and `questionnaire/15-success-metrics.md`)
 
@@ -445,12 +596,17 @@ BEFORE transitioning to step-02:
    a. Create an entry in `cadrage.coverageMatrix[]`
    b. Assign it to mustHave, shouldHave, couldHave, or outOfScope
    c. Assign the module that will cover it (or null if cross-cutting)
-   d. **List anticipated sections** (Level 4) based on module type and feature needs
+   d. **List anticipated sections** (Level 4) — ONLY functional zones (see `references/entity-architecture-decision.md` section 4)
    e. **List anticipated resources** (Level 5) for each section
+   f. **List detail page tabs** — for entities accessible via click from `list`
+
+> **SECTION RULE:** Sections are functional zones (list, dashboard, approve, import, rapport...).
+> `create` and `edit` are ACTIONS within the `list` page (modal/drawer).
+> `detail` is a page with tabs accessible by clicking a row in `list`, NOT a standalone section.
 
 4. **OUTPUT the matrix as text** (do NOT put it inside AskUserQuestion — it won't render):
 
-Print a markdown table with columns: **Fonctionnalité | Priorité | Module | Sections pressenties | Resources clés**
+Print a markdown table with columns: **Fonctionnalité | Priorité | Module | Section | Resources clés | Onglets détail**
 
 Example:
 ```
@@ -458,13 +614,15 @@ Example:
   ? "Voici la matrice de couverture enrichie. J'ai identifié {N} fonctionnalités :"
   : "Here is the enriched coverage matrix. I identified {N} features:"}
 
-| Fonctionnalité | Priorité | Module | Sections pressenties | Resources clés |
-|---|---|---|---|---|
-| Gestion des employés | mustHave | Employees | list, detail, create, edit | employee-grid, employee-form, employee-card |
-| Saisie d'activités | mustHave | TimeTracking | list, create, edit | activity-grid, activity-form |
-| Saisie d'absences | mustHave | TimeTracking | list, create | absence-grid, absence-form, absence-calendar |
-| Rapports temps | mustHave | TimeTracking | dashboard, export | time-summary-chart, time-export-panel |
-| Soldes de congés | shouldHave | TimeTracking | detail | leave-balance-card |
+| Fonctionnalité | Priorité | Module | Section | Resources clés | Onglets détail |
+|---|---|---|---|---|---|
+| Gestion des employés | mustHave | Employees | list | employee-grid, employee-filters, employee-form | Infos, Contrats, Documents |
+| Suivi des activités | mustHave | TimeTracking | list | activity-grid, activity-filters, activity-form | Infos, Imputations |
+| Saisie d'absences | mustHave | TimeTracking | list | absence-grid, absence-form, absence-calendar | Infos, Justificatifs |
+| Rapports temps | shouldHave | TimeTracking | dashboard | time-kpi-cards, time-summary-chart | — |
+| Validation absences | shouldHave | TimeTracking | approve | approval-queue, status-timeline | — |
+| Export PDF/Excel | couldHave | TimeTracking | rapport | export-panel | — |
+| Intégration paie | outOfScope | — | — | — | — |
 ```
 
 5. **THEN** (after the table is displayed) ask via AskUserQuestion:
@@ -487,6 +645,36 @@ options:
 - If a feature is in mustHave → it MUST have at least one anticipated section.
 - Accepted suggestions from Phase 4 must appear in the matrix.
 
+**POST-CHECK — PRIORITY DISTRIBUTION (BLOCKING):**
+
+```
+coverageItems = cadrage.coverageMatrix[]
+mustHaveCount = coverageItems.filter(i => i.category === "mustHave").length
+shouldHaveCount = coverageItems.filter(i => i.category === "shouldHave").length
+couldHaveCount = coverageItems.filter(i => i.category === "couldHave").length
+outOfScopeCount = coverageItems.filter(i => i.category === "outOfScope").length
+
+IF shouldHaveCount === 0 AND couldHaveCount === 0 AND outOfScopeCount === 0:
+  → FAIL: ALL {mustHaveCount} items are mustHave — no distribution.
+  → ACTION: Return to Phase 3 section 4c and apply MoSCoW question.
+  → DO NOT write cadrage until at least shouldHave OR outOfScope has ≥ 1 item.
+  → EXCEPTION: If client explicitly confirmed "tout est indispensable" during
+    Phase 3 section 4c, accept but ADD a changelog entry:
+    "Client confirmed all {N} features as mustHave after MoSCoW challenge"
+```
+
+**POST-CHECK — CROSS-CUTTING COVERAGE (WARNING):**
+
+```
+FOR each item in coverageMatrix WHERE item.module === null:
+  IF item.category === "mustHave":
+    → WARNING: "{item.item}" is mustHave but has no assigned module.
+    → Ensure it is covered by infrastructure or a cross-cutting concern.
+    → Add a note explaining HOW it will be implemented (e.g., "handled by platform notification service").
+  IF item.anticipatedSections.length === 0 AND item.category !== "outOfScope":
+    → WARNING: "{item.item}" has no anticipated sections — will it be implemented?
+```
+
 ---
 
 ## WRITE & SUMMARY

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

@@ -61,6 +61,7 @@ For each mustHave/shouldHave scope item:
 > ```json
 > {
 >   "code": "PascalCase",
+>   "name": "Human-readable display name (e.g., 'Gestion du temps', 'Ressources Humaines')",
 >   "description": "1-2 sentence description",
 >   "featureType": "data-centric|integration|ui-centric|workflow|reporting|full-module",
 >   "dependencies": ["OtherModule"],
@@ -72,18 +73,20 @@ For each mustHave/shouldHave scope item:
 >   "entities": ["Anticipated entity names"],
 >   "estimatedComplexity": "simple|medium|complex",
 >   "anticipatedSections": [
->     { "code": "list", "description": "Main entity list with filters", "resources": ["entity-grid", "entity-filter"] },
->     { "code": "detail", "description": "Entity detail view", "resources": ["entity-card"] },
->     { "code": "create", "description": "Create new entity", "resources": ["entity-form"] }
->   ]
+>     { "code": "list", "description": "Main page: grid, create action (modal), click to detail", "resources": ["entity-grid", "entity-filters", "entity-form"] },
+>     { "code": "dashboard", "description": "Module KPIs and overview (if needed)", "resources": ["entity-kpi-cards", "entity-charts"] }
+>   ],
+>   "detailTabs": ["Informations", "RelatedEntity1", "Historique"]
 > }
 > ```
-> **MANDATORY fields:** `code`, `description`, `featureType`, `dependencies`, `dependents`, `status`, `priority`, `sortOrder`, `entities`, `estimatedComplexity`
+> **MANDATORY fields:** `code`, `name`, `description`, `featureType`, `dependencies`, `dependents`, `status`, `priority`, `sortOrder`, `entities`, `estimatedComplexity`
+> **`name` vs `code`:** `code` is PascalCase for file paths/keys (e.g., "GestionTemps"). `name` is the human-readable label shown in navigation and HTML (e.g., "Gestion du temps"). They are ALWAYS both required.
 > **OPTIONAL fields:** `anticipatedSections` (from cadrage coverageMatrix, enriched here with resources)
 > **status:** Always `"pending"` at creation (updated to `"in-progress"` → `"specified"` → `"validated"` by step-03/04)
 > **sortOrder:** Integer from topological sort (0 = foundation layer)
 > **featureJsonPath:** Set to null at creation; updated to actual path when module feature.json is created in step-03
-> **anticipatedSections:** Array of `{ code, description, resources[] }` objects. Derived from `cadrage.coverageMatrix[].anticipatedSections` aggregated per module, then refined during decomposition. These serve as starting point for step-03a1 section walkthrough.
+> **anticipatedSections:** Array of `{ code, description, resources[] }` objects. ONLY functional zones: `list` (always), `dashboard`, `approve`, `import`, `rapport`, `planning`. NEVER `create`, `edit`, or `detail` (those are actions/pages within `list`). Derived from `cadrage.coverageMatrix[].anticipatedSections` aggregated per module, then refined during decomposition.
+> **detailTabs:** Array of tab names for the detail page (reached by clicking a row in `list`). Always includes "Informations". Add relationship tabs based on entity relations.
 
 **Complexity estimation rules:**
 | Criteria | Simple | Medium | Complex |
@@ -104,16 +107,17 @@ Display the identified modules as markdown:
   ? "**Préfixe de table :** `{metadata.tablePrefix}` — toutes les tables de cette application seront préfixées (ex: `{metadata.tablePrefix}Customers`, `{metadata.tablePrefix}Orders`)"
   : "**Table prefix:** `{metadata.tablePrefix}` — all tables in this application will be prefixed (e.g., `{metadata.tablePrefix}Customers`, `{metadata.tablePrefix}Orders`)"}
 
-| # | Module | Type | Priorité | Complexité | Sections pressenties | Entités |
-|---|--------|------|----------|------------|---------------------|---------|
-| 1 | Customers | data-centric | must | medium | list, detail, create, edit | Customer, Address, Contact |
-| 2 | Products | data-centric | must | simple | list, detail, create | Product, Category |
-| 3 | Orders | workflow | must | complex | list, detail, create, approve, history | Order, OrderLine |
-| 4 | Invoices | workflow | should | medium | list, detail, create, export | Invoice, InvoiceLine, Payment |
+| # | Code | Nom | Type | Priorité | Complexité | Sections | Onglets détail | Entités |
+|---|------|-----|------|----------|------------|----------|----------------|---------|
+| 1 | Customers | Clients | data-centric | must | medium | list | Infos, Adresses, Contacts | Customer, Address, Contact |
+| 2 | Products | Produits | data-centric | must | simple | list | Infos, Catégories | Product, Category |
+| 3 | Orders | Commandes | workflow | must | complex | list, approve | Infos, Lignes, Historique | Order, OrderLine |
+| 4 | Invoices | Facturation | workflow | should | medium | list, dashboard | Infos, Lignes, Paiements | Invoice, InvoiceLine, Payment |
 ```
 
-> **Sections are derived from:** cadrage.coverageMatrix[].anticipatedSections aggregated per module.
-> If cadrage did not provide sections, infer from module featureType using the standard section table.
+> **Sections = functional zones only:** `list` (always), `dashboard`, `approve`, `import`, `rapport`, `planning`.
+> **Onglets detail** = tabs in the detail page (reached by clicking a row in list).
+> NEVER list `create`, `edit`, or `detail` as sections — they are actions/pages within `list`.
 
 Ask via AskUserQuestion:
 ```
@@ -205,22 +209,27 @@ Products ───┘
 
 ### Ordre de traitement
 
-| Ordre | Module | Dépend de | Complexité | Sections pressenties |
-|-------|--------|-----------|------------|---------------------|
-| 1 | Customers | (aucune) | medium | list, detail, create, edit |
-| 2 | Products | (aucune) | simple | list, detail, create |
-| 3 | Orders | Customers, Products | complex | list, detail, create, approve, history |
-| 4 | Invoices | Orders, Customers | medium | list, detail, create, export |
+| Ordre | Module | Dépend de | Complexité | Sections | Onglets détail |
+|-------|--------|-----------|------------|----------|----------------|
+| 1 | Customers | (aucune) | medium | list | Infos, Adresses, Contacts |
+| 2 | Products | (aucune) | simple | list | Infos, Catégories |
+| 3 | Orders | Customers, Products | complex | list, approve | Infos, Lignes, Historique |
+| 4 | Invoices | Orders, Customers | medium | list, dashboard | Infos, Lignes, Paiements |
 
 ### Détail des sections et resources par module
 
 **Module : {module_name}**
-| Section | Description | Resources pressenties |
-|---------|-------------|----------------------|
-| list | {description} | {entity}-grid, {entity}-filter |
-| detail | {description} | {entity}-card, {entity}-tabs |
-| create | {description} | {entity}-form |
-| ... | ... | ... |
+
+| Section | Description | Resources |
+|---------|-------------|-----------|
+| list | Page principale : grille + création + navigation détail | {entity}-grid, {entity}-filters, {entity}-form |
+| {section_2} | {functional zone description} | {resources} |
+
+| Onglet détail | Contenu |
+|---------------|---------|
+| Informations | Fiche principale de l'entité |
+| {relation_tab} | {sous-entités ou entités liées} |
+| Historique | Journal des modifications |
 
 (Repeat for each module)