@atlashub/smartstack-cli 2.6.2 → 2.7.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@atlashub/smartstack-cli",
-  "version": "2.6.2",
+  "version": "2.7.0",
   "description": "SmartStack Claude Code automation toolkit - GitFlow, APEX, EF Core migrations, prompts and more",
   "author": {
     "name": "SmartStack",

package/templates/agents/ba-reader.md

@@ -133,6 +133,29 @@ Permissions: business.sales.products.{read|create|update}
 FKs exposed: Product.Id, Category.Id
 ```
 
+### listAllModuleIds
+List all UC, BR, FR IDs across all specified module feature.json files. Used by ba-writer for collision detection.
+
+**Input:**
+- applicationFeatureId: FEAT-NNN (master)
+
+**Process:**
+1. Read master feature.json → get modules[].code and modules[].featureJsonPath
+2. For each module with status "specified" or "handed-off":
+   a. Read module feature.json
+   b. Extract: specification.useCases[].id, analysis.businessRules[].id, specification.functionalRequirements[].id
+3. Return map of all IDs per module
+
+**Output:**
+```json
+{
+  "UserManagement": { "ucIds": ["UC-UM-001", "UC-UM-002"], "brIds": ["BR-VAL-UM-001"], "frIds": ["FR-UM-001"] },
+  "RepairManagement": { "ucIds": ["UC-RM-001"], "brIds": ["BR-VAL-RM-001"], "frIds": ["FR-RM-001"] }
+}
+```
+
+Used by: ba-writer.enrichSection() for ID collision check before writing specification section.
+
 ### readSection
 Extract and format a specific section from a feature.json.
 

package/templates/agents/ba-writer.md

@@ -72,7 +72,35 @@ Merge a section into an existing feature.json.
 5. Update metadata.updatedBy with agent name
 6. Write back with pretty-print (2-space indent)
 7. Validate schema before writing
-8. Return confirmation with section size and status
+8. **ID Collision Check (for specification section):**
+   a. Extract all IDs from the data being written (UC-*, BR-*, FR-*)
+   b. Via ba-reader.listAllModuleIds(), list all IDs from ALREADY-SPECIFIED modules
+   c. If ANY collision detected → BLOCK write, list collisions with module names
+   d. The calling step MUST fix the IDs before retrying
+9. **Cross-Reference Validation (for specification and handoff sections):** See CROSS-REFERENCE VALIDATION section below
+10. Return confirmation with section size and status
+
+### enrichModuleHandoff
+Write the handoff section into a module feature.json. Specialized operation for step-05 module loop.
+
+**Input:**
+- moduleFeatureId: FEAT-NNN or path to module feature.json
+- handoffData: { complexity, filesToCreate, brToCodeMapping, apiEndpointSummary, prdFile, totalFiles, totalTasks, handedOffAt }
+
+**Process:**
+1. Locate the module feature.json via findFeature
+2. Validate handoffData.filesToCreate has all 7 categories (domain, application, infrastructure, api, frontend, seedData, tests)
+3. Validate each fileSpec has at minimum path + type
+4. Validate brToCodeMapping[].ruleId references exist in analysis.businessRules[].id
+5. Write the handoff section
+6. Update status → "handed-off"
+7. **POST-WRITE VERIFICATION:** Re-read the module feature.json and confirm:
+   - handoff !== {}
+   - handoff.filesToCreate contains all 7 categories
+   - handoff.brToCodeMapping.length > 0
+   - status === "handed-off"
+8. IF verification fails → return error with details
+9. Return confirmation with stats (files per category, total BRs mapped)
 
 ### updateStatus
 Transition the status through defined workflow.
@@ -173,9 +201,9 @@ Perform these structural checks before every write:
 
 **ID Patterns:**
 - id: must match `FEAT-\d{3}` (e.g., FEAT-001)
-- BR IDs: must match `BR-(VAL|CALC|WF|SEC|DATA)-\d{3}` (e.g., BR-SEC-042)
-- UC IDs: must match `UC-\d{3}` (e.g., UC-007)
-- FR IDs: must match `FR-\d{3}` (e.g., FR-012)
+- BR IDs: must match `BR-(VAL|CALC|WF|SEC|DATA)-[A-Z]{2,4}-\d{3}` (e.g., BR-SEC-RM-042) — module prefix MANDATORY in multi-module mode
+- UC IDs: must match `UC-[A-Z]{2,4}-\d{3}` (e.g., UC-RM-007) — module prefix MANDATORY in multi-module mode
+- FR IDs: must match `FR-[A-Z]{2,4}-\d{3}` (e.g., FR-RM-012) — module prefix MANDATORY in multi-module mode
 - Permission paths: must match `business\.{app}\.{module}\.{resource}\.{action}` (e.g., business.crm.contacts.read)
 
 **Metadata:**
@@ -227,6 +255,37 @@ Versions are stored as separate files in versioned directories. Always store fea
 - Update on every create operation
 - Read before write to avoid conflicts
 
+## CROSS-REFERENCE VALIDATION (MANDATORY)
+
+Before EVERY enrichSection() call for specification or handoff sections, validate referential integrity.
+
+### After enrichSection("specification")
+1. Build SET_BR from analysis.businessRules[].id
+2. For each useCases[].linkedRules[] → verify ∈ SET_BR
+3. For each functionalRequirements[].linkedRules[] → verify ∈ SET_BR
+4. Build SET_UC from useCases[].id
+5. For each functionalRequirements[].linkedUseCases[] → verify ∈ SET_UC
+6. Build SET_PERM from permissionMatrix.permissions[].path
+7. For each roleAssignments[].permissions[] → verify ∈ SET_PERM
+8. Build SET_SCREEN from uiWireframes[].screen
+9. For each sections[].wireframe → verify ∈ SET_SCREEN
+
+### After enrichSection("handoff")
+1. Build SET_FR from specification.functionalRequirements[].id
+2. Build SET_UC from specification.useCases[].id
+3. Build SET_SCREEN from specification.uiWireframes[].screen
+4. Build SET_BR from analysis.businessRules[].id
+5. For each filesToCreate.*[].linkedFRs[] → verify ∈ SET_FR
+6. For each filesToCreate.*[].linkedUCs[] → verify ∈ SET_UC
+7. For each filesToCreate.*[].linkedWireframes[] → verify ∈ SET_SCREEN
+8. For each brToCodeMapping[].ruleId → verify ∈ SET_BR
+
+### On violation
+- LIST all violations (do not stop at first)
+- AUTO-FIX: remove dangling refs, add missing items if source data exists
+- LOG in changelog[] with warning
+- NEVER write a feature.json with broken references
+
 ## Execution Rules
 
 1. **Always read before write** - merge with existing content when enriching

package/templates/skills/business-analyse/questionnaire/00-application.md

@@ -149,7 +149,7 @@ Q0.8: "Quel rôle par défaut pour les nouveaux utilisateurs ?"
 | Anti-pattern | Signal | Action |
 |--------------|--------|--------|
 | Too many modules | > 10 modules for v1 | Suggest phased approach: core modules first |
-| No clear priority | "Everything is must-have" | Apply MoSCoW: "If you could only ship 3 modules?" |
+| No clear priority | "Everything is must-have" | Challenge priorities: "If you could only ship 3 modules?" |
 | Role confusion | Mixing business roles with system roles | Clarify: "We're defining system access levels, not job titles" |
 | Monolithic thinking | "It's all one big module" | Challenge: "Could a user only need access to part of this?" |
 

package/templates/skills/business-analyse/questionnaire/03-scope.md

@@ -1,11 +1,11 @@
 # Category 3: Functional Scope
 
-> **Usage:** Scope definition with MoSCoW
+> **Usage:** Scope definition with priority levels
 > **When to load:** ALWAYS (core)
 
 ---
 
-## 3.1 Functionality (MoSCoW)
+## 3.1 Functionality (Priority Levels)
 
 | # | Question | Answer Type |
 |---|----------|-------------|

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

@@ -311,7 +311,7 @@ Each question kept passes this test:
 | 0. Application Identity | 8 | step-01 (app mode) | Application name, modules, roles |
 | 1. Business Context | 4 | step-01 | Problem + AS-IS/TO-BE |
 | 2. Stakeholders | 8 | step-01 | Roles + needs |
-| 3. Functional Scope | 8 | step-01 | MoSCoW + flows |
+| 3. Functional Scope | 8 | step-01 | Priority levels + flows |
 | 4. Data | 8 | step-03 (per module) | Entities + rules |
 | 5. Integrations | 8 | step-01 (conditional) | Systems + flows |
 | 6. Security | 8 | step-01 (conditional) | Permissions + restrictions |

package/templates/skills/business-analyse/react/application-viewer.md

@@ -62,7 +62,7 @@ Displays the application-level framing:
 | AS-IS | cadrage.asIs | Text block |
 | TO-BE | cadrage.toBe | Text block |
 | Stakeholders | cadrage.stakeholders | Table: role, description, frequency |
-| Global Scope | cadrage.globalScope | MoSCoW badges: Must/Should/Could/Out |
+| Global Scope | cadrage.globalScope | Priority badges: Essentiel/Important/Optionnel/Exclu |
 | Risks | cadrage.risks | Severity-colored cards |
 
 ### Tab: Modules

package/templates/skills/business-analyse/react/schema.md

@@ -347,6 +347,84 @@ export interface FeatureSpecification {
   lifeCycles: EntityLifeCycle[];
   seedDataCore: SeedDataCore;
   i18nKeys: I18nKey[];
+  sections: Section[];
+  dashboards: Dashboard[];
+  extensions?: Record<string, unknown>;
+}
+
+// --- Sections & Resources (Levels 4-5) ---
+
+export interface Section {
+  code: string;
+  labels: Record<'fr' | 'en' | 'it' | 'de', string>;
+  route: string;
+  icon: string;
+  permission: string;
+  wireframe: string;
+  useCases: string[];
+  businessRules: string[];
+  resources: Resource[];
+}
+
+export interface Resource {
+  code: string;
+  type: ResourceType;
+  entity: string;
+  parentEntity?: string;
+  permission: string;
+  columns?: string[];
+  fields?: FormField[];
+  actions?: string[];
+  filters?: string[];
+  kpis?: string[];
+  chartType?: ChartType;
+  dataSource?: string;
+}
+
+export type ResourceType = 'SmartTable' | 'SmartForm' | 'DetailCard' | 'KpiPanel' | 'KpiCard'
+  | 'Timeline' | 'EntitySelect' | 'Chart' | 'Map' | 'FileUpload' | 'StatusBadge'
+  | 'ActionMenu' | 'FilterBar' | 'Tabs';
+
+export type ChartType = 'bar' | 'line' | 'pie' | 'area' | 'donut' | 'stacked-bar';
+
+export interface FormField {
+  name: string;
+  component: FormComponent;
+  source?: string;
+  required?: boolean;
+  validation?: string;
+}
+
+export type FormComponent = 'Input' | 'TextArea' | 'Select' | 'MultiSelect' | 'DatePicker'
+  | 'DateRangePicker' | 'NumberInput' | 'Toggle' | 'EntitySelect' | 'FileUpload'
+  | 'RichText' | 'ColorPicker';
+
+export interface Dashboard {
+  code: string;
+  title: string;
+  description: string;
+  linkedUCs: string[];
+  refreshMode: 'static' | 'polling' | 'signalr';
+  defaultPeriod: 'day' | 'week' | 'month' | 'quarter' | 'year';
+  kpis: DashboardKpi[];
+  filters: DashboardFilter[];
+  permissionsRequired: string[];
+}
+
+export interface DashboardKpi {
+  code: string;
+  label: string;
+  metric: string;
+  format: 'number' | 'currency' | 'percent' | 'duration';
+  visualization: 'kpi-card' | 'bar' | 'line' | 'pie' | 'area' | 'donut' | 'stacked-bar';
+  dataSource: string;
+  dimensions?: string[];
+}
+
+export interface DashboardFilter {
+  field: string;
+  type: 'dateRange' | 'select' | 'multiselect' | 'search';
+  label: string;
 }
 
 export interface ValidationRule {
@@ -744,6 +822,15 @@ export type {
   BrToCodeMapping,
   ValidationDecision,
   FeatureSuggestion,
-  ChangelogEntry
+  ChangelogEntry,
+  Section,
+  Resource,
+  ResourceType,
+  FormField,
+  FormComponent,
+  Dashboard,
+  DashboardKpi,
+  DashboardFilter,
+  ChartType
 } from './business-analyse';
 ```

package/templates/skills/business-analyse/schemas/application-schema.json

@@ -162,6 +162,21 @@
         "codebaseContext": {
           "type": "string",
           "description": "Summary of existing modules/patterns found during pre-research"
+        },
+        "coverageMatrix": {
+          "type": "array",
+          "description": "Maps every requirement from the original brief/prompt to a scope category. Ensures nothing is lost silently.",
+          "items": {
+            "type": "object",
+            "required": ["item", "category", "module"],
+            "properties": {
+              "item": { "type": "string", "description": "Requirement from the original brief" },
+              "category": { "type": "string", "enum": ["mustHave", "shouldHave", "couldHave", "outOfScope", "implicit"] },
+              "module": { "type": ["string", "null"], "description": "Module code that covers this requirement (null if cross-cutting)" },
+              "ucRef": { "type": ["string", "null"], "description": "UC ID if already assigned" },
+              "notes": { "type": "string" }
+            }
+          }
         }
       }
     },
@@ -202,7 +217,7 @@
           "priority": {
             "type": "string",
             "enum": ["must", "should", "could"],
-            "description": "MoSCoW priority from global scope"
+            "description": "Priority level from global scope"
           },
           "sortOrder": {
             "type": "integer",