@atlashub/smartstack-cli 4.17.1 → 4.19.0

package/templates/skills/business-analyse/references/robustness-checks.md

@@ -1,5 +1,6 @@
 # Robustness Checks for Business Analysis
 
+> **Authoritative minimums:** See `_shared.md` § "Minimum Counts" for the single source of truth on all minimum thresholds.
 > **Objective:** Prevent incomplete specifications and broken references from reaching development.
 
 ## Overview
@@ -8,10 +9,10 @@ This document consolidates all robustness checks implemented across the business
 
 ---
 
-## Phase 1: Module Specification Checklist (Step-03d)
+## Phase 1: Module Specification Checklist (Step-03)
 
-> **When:** Before marking module status = "specified"
-> **Blocking:** YES - Module CANNOT proceed to handoff with failing checks
+> **When:** At end of step-03, before marking module status = "specified"
+> **Blocking:** YES - Module CANNOT proceed to consolidation with failing checks
 
 ### Purpose
 
@@ -42,7 +43,7 @@ Ensures each module has ALL required components before being marked as "specifie
 | 3.1 | Use cases count | ≥6 | YES | CRUD (5) + 1 business-specific minimum |
 | 3.2 | UC module prefixes | All UCs use module prefix | YES | Prevents ID collisions |
 | 3.3 | Functional requirements count | ≥4 | YES | FRs must cover key functionality |
-| 3.4 | UC-FR linkage | Every UC has ≥1 linked FR | YES | Orphan UCs indicate incomplete requirements |
+| 3.4 | UC-FR linkage | Every UC has ≥1 linked FR | NO (WARNING) | Orphan UCs indicate incomplete requirements |
 | 3.5 | FR-BR linkage | Every FR has ≥1 linked BR | NO (WARNING) | FRs without BRs may lack validation logic |
 
 #### SECTION 4: Permissions (3 checks)
@@ -74,17 +75,19 @@ Ensures each module has ALL required components before being marked as "specifie
 
 | # | Check | Minimum | Blocking | Rationale |
 |---|-------|---------|----------|-----------|
-| 7.1 | CORE seed data sections | All 7 sections present | YES | Missing CORE data breaks deployment |
+| 7.1 | CORE seed data arrays | All 9 arrays present (per `_shared.md` § "Minimum Counts") | YES | Missing CORE data breaks deployment |
 | 7.2 | Business seed data | Template defined | NO (WARNING) | Helps with testing |
 
-**CORE sections required:**
-1. `navigationModules`
-2. `navigationSections`
-3. `navigationResources`
-4. `navigationTranslations`
-5. `permissions`
-6. `rolePermissions`
-7. `permissionConstants`
+**CORE arrays required (9 total — see `_shared.md` § "seedDataCore arrays"):**
+1. `navigationApplications` — required once per application
+2. `applicationRoles` — required once per application
+3. `navigationModules` — one per module
+4. `navigationSections` — one per section (list, detail, create, etc.)
+5. `navigationResources` — optional per resource
+6. `navigationTranslations` — 4 languages per nav module
+7. `permissions` — CRUD + business actions per module
+8. `rolePermissions` — role to permission mappings
+9. `permissionConstants` — PascalCase constants for code
 
 #### SECTION 8: API Endpoints (2 checks)
 
@@ -113,7 +116,7 @@ Ensures each module has ALL required components before being marked as "specifie
 2. **DISPLAY** table of failures with details
 3. **ACTIONS:**
    - Fix ALL blocking failures
-   - Re-run step-03d validation
+   - Re-run step-03 module specification
    - Proceed only when ALL blocking checks pass
 
 **Example output:**
@@ -133,7 +136,7 @@ ACTIONS REQUIRED:
 1. Add business rules in ≥1 other category (CALC, WF, SEC, or DATA)
 2. Add 2 more use cases (business-specific)
 3. Create wireframe for "Settings" section
-4. Re-run step-03d validation
+4. Re-run step-03 validation
 
 DO NOT PROCEED TO CONSOLIDATION UNTIL ALL CHECKS PASS
 ═══════════════════════════════════════════════════════════════
@@ -226,7 +229,7 @@ BLOCKING ERRORS:
 
 ACTIONS REQUIRED:
 1. Fix ALL unresolved references listed above
-2. Return to step-03a for affected modules
+2. Return to step-03 for affected modules
 3. Re-run step-04 consolidation
 
 DO NOT PROCEED TO HANDOFF UNTIL ALL REFERENCES RESOLVED
@@ -261,9 +264,9 @@ DEVELOPMENT CANNOT PROCEED WITH CIRCULAR DEPENDENCIES
 
 ---
 
-## Phase 3: Ralph Readiness Validation (Step-05c)
+## Phase 3: Ralph Readiness Validation (Step-05)
 
-> **When:** After artifacts deployed (step-05b), before launching /ralph-loop
+> **When:** After artifacts deployed (step-05), before launching /ralph-loop
 > **Blocking:** YES - Development blocked if critical checks fail
 
 ### Purpose
@@ -275,10 +278,10 @@ Final gate to ensure business analysis is 100% ready for implementation. Catches
 | # | Category | Checks | Blocking | Purpose |
 |---|----------|--------|----------|---------|
 | 1 | Module Status | All modules status = "handed-off" | YES | Incomplete modules break ralph-loop |
-| 2 | PRD Files | All PRD files exist, valid structure, file counts match | YES | Ralph-loop reads PRDs for tasks |
+| 2 | PRD Files | All .ralph/prd-{module}.json files exist, valid structure, file counts match index.json | YES | Ralph-loop reads PRDs for tasks |
 | 3 | Dependency Graph | Valid, no cycles, topological order correct | YES | Determines module implementation order |
 | 4 | Cross-Module References | All references resolvable | YES | Prevents FK constraint errors |
-| 5 | Handoff Completeness | All 7 file categories, brToCodeMapping, apiEndpointSummary | YES | Missing data breaks code generation |
+| 5 | Handoff Completeness | All 8 file categories, brToCodeMapping, apiEndpointSummary | YES | Missing data breaks code generation |
 | 6 | i18n Keys | All keys have 4 languages | NO (WARNING) | Missing translations won't block dev |
 | 7 | Master Feature | Status = "handed-off", handoff complete | YES | Ralph-loop needs master handoff |
 | 8 | Progress Tracker | File exists, structure valid, task count matches | NO (WARNING) | Used for progress tracking |
@@ -337,7 +340,7 @@ Status: NOT READY FOR DEVELOPMENT ✗
 Critical Issues Found:
   ✗ Module status validation: FAIL (1/5 modules incomplete)
     - Reporting module status is "specified", must be "handed-off"
-    - Fix: Return to step-05a-handoff.md for Reporting module
+    - Fix: Return to step-05-deploy.md for Reporting module
 
   ✗ PRD files validation: FAIL (1/5 files invalid)
     - prd-Reporting.json has wrong structure (filesToCreate at root level)
@@ -345,7 +348,7 @@ Critical Issues Found:
 
 Required Actions:
   1. Fix all critical issues listed above
-  2. Re-run validation: load step-05c-ralph-readiness.md
+  2. Re-run validation: load step-05-deploy.md
   3. Only proceed to /ralph-loop when all critical checks pass
 
 DO NOT PROCEED TO /RALPH-LOOP UNTIL ALL CRITICAL CHECKS PASS
@@ -411,7 +414,7 @@ WHY: This will cause FK constraint violation in database
 HOW TO FIX:
   Option 1: Create "Task" entity in Projects module
   Option 2: Remove reference from TimeEntry (change taskId to projectId)
-WHERE: Return to step-03a1-setup.md for TimeTracking module
+WHERE: Return to step-03-specify.md for TimeTracking module
 ```
 
 ---
@@ -430,7 +433,7 @@ WHERE: Return to step-03a1-setup.md for TimeTracking module
 
 **Fix:**
 1. Add missing components until minimums met
-2. Re-run step-03d validation
+2. Re-run step-03 validation
 3. Proceed only when ALL blocking checks pass
 
 ---
@@ -477,9 +480,9 @@ WHERE: Return to step-03a1-setup.md for TimeTracking module
 3. **Option 3: Remove unnecessary dependency**
    - Review if dependency is truly needed
    - Remove if redundant
-4. Return to step-02, fix dependency graph
-5. Re-run step-03 for affected modules
-6. Re-run step-04 consolidation
+4. Return to step-02-structure, fix dependency graph
+5. Re-run step-03-specify for affected modules
+6. Re-run step-04-consolidate
 
 ---
 
@@ -494,11 +497,11 @@ WHERE: Return to step-03a1-setup.md for TimeTracking module
 2. Identify missing/invalid artifacts
 
 **Fix:**
-- **Module status incomplete:** Return to step-05a for affected module
+- **Module status incomplete:** Return to step-05-deploy for affected module
 - **PRD files invalid:** Re-run `ss derive-prd` for affected module
-- **Handoff incomplete:** Return to step-05a, complete handoff section
-- **Cross-module refs broken:** Return to step-04, fix references
-- Re-run step-05c after fixes
+- **Handoff incomplete:** Return to step-05-deploy, complete handoff section
+- **Cross-module refs broken:** Return to step-04-consolidate, fix references
+- Re-run step-05-deploy after fixes
 
 ---
 
@@ -524,7 +527,7 @@ WHERE: Return to step-03a1-setup.md for TimeTracking module
 - Application marked as "consolidated"
 - Ready for handoff
 
-### Ralph Readiness
+### Ralph Readiness (Step-05)
 
 **Target:**
 - 100% critical checks passed
@@ -532,7 +535,7 @@ WHERE: Return to step-03a1-setup.md for TimeTracking module
 
 **Success:**
 - Application ready for /ralph-loop
-- 0% chance of ralph-loop failure due to incomplete BA
+- Development can proceed with full confidence
 
 ---
 

package/templates/skills/business-analyse/references/spec-auto-inference.md

@@ -1,6 +1,6 @@
 # Specification: Auto-Inference Rules
 
-> Reference for step-03a1-setup.md — convention/override depth auto-generation from entity definitions.
+> Reference for step-03-specify.md — convention/override depth auto-generation from entity definitions.
 
 ## Entity Attribute → SmartTable Column
 
@@ -76,7 +76,7 @@ IF coverageMatrix[module].detailTabs EXISTS:
   FOR EACH tabName IN detailTabs:
     IF tabName matches a 1:N relationship entity → SmartTable tab
     ELIF tabName == "Historique"/"History" → Timeline tab
-    ELSE → custom DetailCard tab (contents TBD in step-03b)
+    ELSE → custom DetailCard tab (contents TBD in step-03)
 
 # 3. If no cadrage tabs, auto-infer from relationships
 ELSE:

package/templates/skills/business-analyse/references/ui-dashboard-spec.md

@@ -1,6 +1,6 @@
 # UI: Dashboard Specification
 
-> Reference for step-03b-ui.md — section 3d dashboard KPI and chart capture.
+> Reference for step-03-specify.md — section 3d dashboard KPI and chart capture.
 
 ## 3d. Dashboard Specification (if section = dashboard)
 

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

@@ -1,6 +1,6 @@
 # UI: Resource Structure Cards
 
-> Reference for step-03b-ui.md — exact JSON formats for section resources (SmartTable, SmartForm) and wireframes.
+> Reference for step-03-specify.md — exact JSON formats for section resources (SmartTable, SmartForm) and wireframes.
 
 ## specification.sections[] (with resources)
 

package/templates/skills/business-analyse/references/validation-checklist.md

@@ -1,5 +1,6 @@
 # Module Specification Checklist
 
+> **Authoritative minimums:** See `_shared.md` for the single source of truth on all minimum thresholds.
 > **CRITICAL:** This checklist MUST be FULLY COMPLETED before marking module status = "specified".
 > **Rationale:** Prevents incomplete modules from reaching handoff, reduces ralph-loop failures.
 
@@ -12,7 +13,7 @@ const checklist = {
   // SECTION 1: DATA MODEL (BLOCKING)
   entities: {
     minimum: 2,
-    actual: specification.entities.length,
+    actual: analysis.entities.length,
     status: actual >= minimum ? "PASS" : "FAIL",
     blocking: true,
     details: "At least 2 entities required for a meaningful module"
@@ -34,7 +35,7 @@ const checklist = {
 
   entitySchemaCompliance: {
     check: "All entities use canonical format: attributes[] (not fields[]), relationships[] array present",
-    status: specification.entities.every(e =>
+    status: analysis.entities.every(e =>
       Array.isArray(e.attributes) && e.attributes.length > 0 &&
       !e.fields && !e.tableName && !e.primaryKey
     ) ? "PASS" : "FAIL",
@@ -189,7 +190,7 @@ const checklist = {
   // SECTION 6: I18N & MESSAGES (BLOCKING)
   i18nKeys: {
     minimum: 42,  // Realistic minimum for a module
-    actual: specification.i18nKeys.length,
+    actual: Object.keys(specification.i18nKeys || {}).length,
     status: actual >= minimum ? "PASS" : "FAIL",
     blocking: true,
     details: "Keys needed: entities (×2), fields, messages, validation, navigation"
@@ -212,8 +213,10 @@ const checklist = {
 
   // SECTION 7: SEED DATA (BLOCKING)
   seedDataCore: {
-    check: "All 7 CORE seed data sections present",
+    check: "All 9 CORE seed data sections present",
     requiredSections: [
+      "navigationApplications",
+      "applicationRoles",
       "navigationModules",
       "navigationSections",
       "navigationResources",
@@ -266,7 +269,7 @@ const checklist = {
     status: Array.isArray(specification.gherkinScenarios) ? "PASS" : "FAIL",
     blocking: true,
     details: "gherkinScenarios MUST be an array [{feature, scenarios}], not a single object. " +
-             "Auto-fix: wrap in array [gherkinScenarios]. See step-03c ABSOLUTE FORMAT CHECKS."
+             "Auto-fix: wrap in array [gherkinScenarios]. See step-03 ABSOLUTE FORMAT CHECKS."
   },
 
   gherkinContent: {
@@ -308,7 +311,7 @@ IF blockingFailures.length > 0:
 
   ACTIONS REQUIRED:
   1. Fix ALL blocking failures listed above
-  2. Re-run step-03d validation
+  2. Re-run step-03 validation
   3. DO NOT mark module as "specified" until ALL blocking checks pass
 
   STOP - DO NOT PROCEED TO UPDATE STATUS

package/templates/skills/business-analyse/references/wireframe-svg-style-guide.md

@@ -2,7 +2,7 @@
 
 > **Purpose:** Self-contained specification for generating professional SVG wireframes from ASCII art.
 > This document is sent as the FULL prompt to a Sonnet Task agent alongside the ASCII wireframe.
-> Referenced by: `validate-incremental-html.md` (Step 3-bis), `step-05b-deploy.md` (Section 7-bis)
+> Referenced by: `step-05-deploy.md` (Section 8: Generate SVG Wireframes)
 
 ## Agent Prompt Template
 
@@ -280,7 +280,7 @@ This signals the system to use the ASCII wireframe instead.
 
 ## Orchestration Instructions
 
-> **FOR the agent executing step-03d 11-bis or step-05b**: Follow this process to generate SVGs.
+> **FOR the agent executing step-03 or step-05**: Follow this process to generate SVGs.
 
 ### Step-by-step process:
 

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

@@ -2,7 +2,7 @@
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "$id": "application-schema.json",
   "title": "SmartStack Business Analysis - Application Level",
-  "description": "Master feature.json for multi-module application analysis. Published to docs/{app}/business-analyse/v{X.Y}/feature.json",
+  "description": "Master index.json for multi-module application analysis. Published to docs/{app}/business-analyse/v{X.Y}/index.json",
   "type": "object",
   "required": ["id", "version", "status", "scope", "metadata"],
   "properties": {
@@ -24,7 +24,7 @@
     "scope": {
       "type": "string",
       "const": "application",
-      "description": "Marks this as an application-level feature.json"
+      "description": "Marks this as an application-level index.json"
     },
 
     "metadata": {
@@ -55,16 +55,16 @@
         },
         "applicationCode": {
           "type": "string",
-          "description": "PascalCase application code for navigation hierarchy (e.g., HumanResources). Confirmed in step-01b."
+          "description": "PascalCase application code for navigation hierarchy (e.g., HumanResources). Confirmed in step-02."
         },
         "applicationRoute": {
           "type": "string",
           "pattern": "^/[a-z-/]+$",
-          "description": "Kebab-case route path for navigation (e.g., /human-resources). Confirmed in step-01b."
+          "description": "Kebab-case route path for navigation (e.g., /human-resources). Confirmed in step-02."
         },
         "applicationIcon": {
           "type": "string",
-          "description": "Lucide icon name for application navigation entry (e.g., users, shopping-cart). Confirmed in step-01b."
+          "description": "Lucide icon name for application navigation entry (e.g., users, shopping-cart). Confirmed in step-02."
         },
         "workflow": {
           "type": "object",
@@ -215,7 +215,7 @@
 
     "modules": {
       "type": "array",
-      "description": "Enriched by step-02-decomposition: module registry with dependencies",
+      "description": "Enriched by step-02-structure: module registry with dependencies",
       "items": {
         "type": "object",
         "required": ["code", "description"],
@@ -244,7 +244,7 @@
           },
           "featureJsonPath": {
             "type": ["string", "null"],
-            "description": "Path to the module-level feature.json once created"
+            "description": "Path to the module-level index.json once created"
           },
           "priority": {
             "type": "string",
@@ -287,7 +287,7 @@
 
     "dependencyGraph": {
       "type": "object",
-      "description": "Enriched by step-02-decomposition: module dependency graph",
+      "description": "Enriched by step-02-structure: module dependency graph",
       "properties": {
         "edges": {
           "type": "array",

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

@@ -1,8 +1,8 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "feature.json",
+  "$id": "feature-schema.json",
   "title": "SmartStack Business Analysis Feature v5.0",
-  "description": "Root schema for module-level feature.json. References sub-schemas in sections/ and shared/. Each BA step loads only the sub-schema(s) it needs.",
+  "description": "Root schema for module-level index.json. References sub-schemas in sections/ and shared/. Each BA step loads only the sub-schema(s) it needs.",
   "type": "object",
   "required": ["id", "version", "status", "metadata"],
   "properties": {
@@ -43,7 +43,7 @@
     }
   },
 
-  "$comment": "Sub-schema loading guide per BA step: step-00-init → metadata-schema.json | step-01-cadrage → discovery-schema.json (module) OR application-schema.json (master) | step-02-decomposition → application-schema.json (modules[], dependencyGraph) | step-03a-data → analysis-schema.json | step-03b-ui → specification-schema.json (wireframes, layouts) | step-03c-compile → specification-schema.json | step-03d-validate → validation-schema.json | step-04-consolidation → validation-schema.json + application-schema.json (consolidation) | step-05a-handoff → handoff-schema.json (filesToCreate, brToCodeMapping, apiEndpointSummary) | step-05b-deploy → (prd, progress, manifest, ba-interactive.html)",
+  "$comment": "Sub-schema loading guide per BA step: step-00-init → metadata-schema.json | step-01-cadrage → discovery-schema.json (module) OR application-schema.json (master) | step-02-structure → application-schema.json (modules[], dependencyGraph) | step-03-specify → analysis-schema.json + specification-schema.json | step-04-consolidate → validation-schema.json + application-schema.json (consolidation) | step-05-deploy → handoff-schema.json (filesToCreate, brToCodeMapping, apiEndpointSummary) + (prd, progress, manifest, ba-interactive.html) | step-06-review → applies ba-review.json corrections, creates new version",
 
   "$defs": {
     "stepStatus": { "$ref": "shared/common-defs.json#/$defs/stepStatus" },

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

@@ -0,0 +1,47 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "index-schema.json",
+  "title": "Business Analysis Index",
+  "description": "Index file for granular business analysis JSON files. References individual thematic files (entities, rules, usecases, etc.) with metadata and hashes.",
+  "type": "object",
+  "required": ["metadata", "files"],
+  "properties": {
+    "metadata": {
+      "type": "object",
+      "required": ["featureId", "moduleCode", "version", "status"],
+      "properties": {
+        "featureId": { "type": "string", "description": "Unique feature identifier (e.g. FEAT-001)" },
+        "moduleCode": { "type": "string", "description": "PascalCase module code (e.g. Employees)" },
+        "applicationCode": { "type": "string", "description": "PascalCase application code (e.g. HumanResources)" },
+        "version": { "type": "string", "description": "Semantic version (e.g. 1.0)" },
+        "status": { "type": "string", "enum": ["draft", "identified", "specified", "validated", "reviewed"] },
+        "createdAt": { "type": "string", "format": "date-time" },
+        "lastModified": { "type": "string", "format": "date-time" }
+      }
+    },
+    "files": {
+      "type": "object",
+      "description": "References to individual JSON files",
+      "additionalProperties": {
+        "type": "object",
+        "required": ["path"],
+        "properties": {
+          "path": { "type": "string", "description": "Relative path to the JSON file" },
+          "hash": { "type": "string", "description": "Content hash for change detection" },
+          "lastModified": { "type": "string", "description": "Last modification date" }
+        }
+      }
+    },
+    "summary": {
+      "type": "object",
+      "properties": {
+        "entityCount": { "type": "integer" },
+        "ruleCount": { "type": "integer" },
+        "useCaseCount": { "type": "integer" },
+        "permissionCount": { "type": "integer" },
+        "screenCount": { "type": "integer" },
+        "dependencies": { "type": "array", "items": { "type": "string" } }
+      }
+    }
+  }
+}

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

@@ -2,7 +2,7 @@
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "$id": "project-schema.json",
   "title": "SmartStack Business Analysis - Project Level",
-  "description": "Master feature.json for multi-application project analysis. Published to docs/business-analyse/v{X.Y}/feature.json. Only created when 2+ applications are identified.",
+  "description": "Master index.json for multi-application project analysis. Published to docs/business-analyse/v{X.Y}/index.json. Only created when 2+ applications are identified.",
   "type": "object",
   "required": ["id", "version", "status", "scope", "metadata"],
   "properties": {
@@ -24,7 +24,7 @@
     "scope": {
       "type": "string",
       "const": "project",
-      "description": "Marks this as a project-level feature.json (multi-application)"
+      "description": "Marks this as a project-level index.json (multi-application)"
     },
 
     "metadata": {
@@ -79,7 +79,7 @@
           "properties": {
             "init": { "$ref": "#/$defs/stepStatus" },
             "cadrage": { "$ref": "#/$defs/stepStatus" },
-            "applicationDecomposition": { "$ref": "#/$defs/stepStatus" },
+            "structure": { "$ref": "#/$defs/stepStatus" },
             "specify": { "$ref": "#/$defs/stepStatus" },
             "consolidation": { "$ref": "#/$defs/stepStatus" },
             "handoff": { "$ref": "#/$defs/stepStatus" }
@@ -219,7 +219,7 @@
 
     "applications": {
       "type": "array",
-      "description": "Enriched by step-01b-applications: application registry",
+      "description": "Enriched by step-02-structure: application registry",
       "items": {
         "type": "object",
         "required": ["code", "name"],
@@ -273,7 +273,7 @@
           },
           "featureJsonPath": {
             "type": ["string", "null"],
-            "description": "Path to the application-level feature.json once created"
+            "description": "Path to the application-level index.json once created"
           },
           "estimatedComplexity": {
             "type": "string",
@@ -285,7 +285,7 @@
 
     "applicationDependencyGraph": {
       "type": "object",
-      "description": "Enriched by step-01b-applications: inter-application dependency graph",
+      "description": "Enriched by step-02-structure: inter-application dependency graph",
       "properties": {
         "edges": {
           "type": "array",

package/templates/skills/business-analyse/schemas/sections/analysis-schema.json

@@ -2,7 +2,7 @@
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "$id": "analysis-schema.json",
   "title": "SmartStack BA - Analysis",
-  "description": "Module-level analysis: objectives, business rules, entities, process flows, integrations, data lifecycle. Enriched by step-03a-data.",
+  "description": "Module-level analysis: objectives, business rules, entities, process flows, integrations, data lifecycle. Enriched by step-03-specify.",
   "type": "object",
   "properties": {
     "objectives": {

package/templates/skills/business-analyse/schemas/sections/handoff-schema.json

@@ -2,7 +2,7 @@
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "$id": "handoff-schema.json",
   "title": "SmartStack BA - Handoff",
-  "description": "Module-level handoff: file mapping (7 categories), BR-to-code mapping, API endpoint summary. Used by step-05a-handoff.",
+  "description": "Module-level handoff: file mapping (8 categories), BR-to-code mapping, API endpoint summary. Used by /derive-prd skill.",
   "type": "object",
   "properties": {
     "complexity": { "type": "string", "enum": ["simple", "medium", "complex"] },
@@ -15,8 +15,10 @@
         "api": { "type": "array", "items": { "$ref": "../shared/common-defs.json#/$defs/fileSpec" } },
         "frontend": { "type": "array", "items": { "$ref": "../shared/common-defs.json#/$defs/fileSpec" } },
         "seedData": { "type": "array", "items": { "$ref": "../shared/common-defs.json#/$defs/fileSpec" } },
-        "tests": { "type": "array", "items": { "$ref": "../shared/common-defs.json#/$defs/fileSpec" } }
-      }
+        "tests": { "type": "array", "items": { "$ref": "../shared/common-defs.json#/$defs/fileSpec" } },
+        "documentation": { "type": "array", "items": { "$ref": "../shared/common-defs.json#/$defs/fileSpec" } }
+      },
+      "required": ["domain", "application", "infrastructure", "api", "frontend", "seedData", "tests", "documentation"]
     },
     "brToCodeMapping": {
       "type": "array",

package/templates/skills/business-analyse/schemas/sections/metadata-schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "metadata-schema.json",
+  "$id": "metadata-schema",
   "title": "SmartStack BA - Metadata & Application Context",
   "description": "Module metadata and inherited application context. Used by step-00-init.",
 
@@ -13,7 +13,7 @@
         "updatedAt": { "type": "string", "format": "date-time" },
         "application": { "type": "string", "description": "Application name (PascalCase)" },
         "module": { "type": "string", "description": "Module name (PascalCase)" },
-        "projectRef": { "type": ["string", "null"], "description": "Parent project ID (PROJ-XXX) when part of a multi-application project" },
+        "projectRef": { "type": ["string", "null"], "description": "Parent project ID (PROJ-XXX) when part of a multi-application project, null for standalone" },
         "language": { "type": "string", "enum": ["fr", "en", "it", "de"] },
         "featureDescription": { "type": "string" },
         "featureType": {
@@ -29,7 +29,7 @@
         "mcpAvailable": { "type": "boolean" },
         "scope": { "type": "string", "enum": ["application", "module"], "default": "module" },
         "applicationRef": { "type": ["string", "null"], "description": "Parent application feature ID (FEAT-XXX)" },
-        "applicationPath": { "type": ["string", "null"], "description": "Path to parent application-level feature.json" },
+        "applicationPath": { "type": ["string", "null"], "description": "Path to parent application-level index.json" },
         "moduleIndex": { "type": ["integer", "null"], "description": "Position in topological order (0-based)" },
         "totalModules": { "type": ["integer", "null"] },
         "inheritsRoles": { "type": "boolean", "default": false },
@@ -48,7 +48,7 @@
 
     "applicationContext": {
       "type": "object",
-      "description": "Inherited from parent application feature.json when part of multi-module analysis",
+      "description": "Inherited from parent application index.json when part of multi-module analysis",
       "properties": {
         "applicationRoles": {
           "type": "array",

package/templates/skills/business-analyse/schemas/sections/specification-schema.json

@@ -2,7 +2,7 @@
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "$id": "specification-schema.json",
   "title": "SmartStack BA - Specification",
-  "description": "Module-level specification: actors, use cases, FRs, permissions, navigation, wireframes, dashboards, sections, resources. Enriched by step-03c-compile.",
+  "description": "Module-level specification: actors, use cases, FRs, permissions, navigation, wireframes, dashboards, sections, resources. Enriched by step-03-specify.",
   "type": "object",
   "properties": {
     "actors": {

package/templates/skills/business-analyse/schemas/shared/common-defs.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "common-defs.json",
+  "$id": "common-defs",
   "title": "SmartStack BA - Shared Definitions",
   "description": "Reusable $defs shared across all BA sub-schemas",
 
@@ -16,7 +16,8 @@
 
     "moduleStatus": {
       "type": "string",
-      "enum": ["draft", "framed", "analysed", "specified", "approved", "consolidated", "handed-off"]
+      "description": "Status of a module or application through the BA workflow. Module flow: draft → identified → specified → validated → reviewed → handed-off. Application flow: draft → framed → decomposed → specified → consolidated → handed-off.",
+      "enum": ["draft", "framed", "decomposed", "identified", "specified", "validated", "consolidated", "reviewed", "handed-off"]
     },
 
     "priority": {
@@ -47,7 +48,7 @@
           "description": "Acceptance criteria describing how the implementation must match the wireframe layout. MANDATORY for Page and DashboardPage types."
         },
         "category": { "type": "string", "enum": ["core", "business"], "description": "SeedData category: core (navigation/permissions) or business (lookup tables)" },
-        "source": { "type": "string", "description": "Source path in feature.json for derivation" },
+        "source": { "type": "string", "description": "Source path in index.json for derivation" },
         "description": { "type": "string" },
         "pattern": { "type": "string", "description": "Reference pattern from existing codebase" },
         "instructions": { "type": "string" },