@atlashub/smartstack-cli 4.81.0 → 5.0.0

package/templates/skills/business-analyse-handoff/references/entity-canonicalization.md

@@ -1,158 +0,0 @@
-# Entity Name Canonicalization
-
-> **Used by:** step-01-transform (section 2: file mapping) and step-02-export (POST-CHECK)
-> **Purpose:** Convert BA entity names (potentially French, with spaces/apostrophes/accents) into valid C# identifiers for file paths.
-
----
-
-## Why This Exists
-
-Business analysts write entity names in the user's language (e.g., French: "Type d'absence", "Employé", "Congé maladie"). These names are used as-is in `entities.json`. However, C# file paths and class names **MUST** be valid identifiers:
-- No spaces
-- No apostrophes
-- No accents (diacritics)
-- PascalCase convention
-
-Without canonicalization, the handoff generates paths like `src/Domain/Entities/Type d'absence.cs` → build failure (CS1001).
-
----
-
-## Canonicalization Rules
-
-### Step 1: Map to English PascalCase (PREFERRED)
-
-If the BA provides an explicit `codeIdentifier` or `englishName` field on the entity, use it directly.
-
-### Step 2: Strip Diacritics
-
-Remove accents from characters:
-
-| Input | Output |
-|-------|--------|
-| é, è, ê, ë | e |
-| à, â, ä | a |
-| ù, û, ü | u |
-| ô, ö | o |
-| î, ï | i |
-| ç | c |
-
-Example: `Employé` → `Employe`, `Congé` → `Conge`
-
-### Step 3: Remove Apostrophes and Split on Spaces
-
-Split the name on spaces, apostrophes, hyphens, and underscores:
-
-| Input | Tokens |
-|-------|--------|
-| `Type d'absence` | `["Type", "d", "absence"]` |
-| `Congé maladie` | `["Conge", "maladie"]` |
-| `Mise à jour` | `["Mise", "a", "jour"]` |
-
-### Step 4: Remove Articles and Prepositions (1-2 letter tokens)
-
-Remove French articles and prepositions that don't contribute to the identifier:
-
-**Remove:** `d`, `de`, `du`, `l`, `la`, `le`, `les`, `un`, `une`, `des`, `a`, `au`, `aux`, `en`
-
-| Input Tokens | Filtered |
-|-------------|----------|
-| `["Type", "d", "absence"]` | `["Type", "absence"]` |
-| `["Mise", "a", "jour"]` | `["Mise", "jour"]` |
-
-### Step 5: PascalCase Assembly
-
-Capitalize first letter of each remaining token, join without separator:
-
-| Filtered Tokens | Result |
-|----------------|--------|
-| `["Type", "absence"]` | `TypeAbsence` |
-| `["Conge", "maladie"]` | `CongeMaladie` |
-| `["Mise", "jour"]` | `MiseJour` |
-| `["Employe"]` | `Employe` |
-
----
-
-## Canonicalization Function (Pseudocode)
-
-```javascript
-function canonicalizeEntityName(baName) {
-  // Step 1: Use explicit code identifier if available
-  // (handled by caller — check entity.codeIdentifier || entity.englishName first)
-
-  // Step 2: Strip diacritics
-  let name = baName.normalize('NFD').replace(/[\u0300-\u036f]/g, '');
-
-  // Step 3: Split on non-alphanumeric
-  let tokens = name.split(/[\s'\-_]+/).filter(t => t.length > 0);
-
-  // Step 4: Remove French articles/prepositions
-  const stopWords = new Set(['d', 'de', 'du', 'l', 'la', 'le', 'les', 'un', 'une', 'des', 'a', 'au', 'aux', 'en']);
-  tokens = tokens.filter(t => !stopWords.has(t.toLowerCase()));
-
-  // Step 5: PascalCase
-  return tokens.map(t => t.charAt(0).toUpperCase() + t.slice(1).toLowerCase()).join('');
-}
-```
-
----
-
-## Validation: Is Valid C# Identifier?
-
-After canonicalization, verify the result is a valid C# identifier:
-
-```javascript
-function isValidCSharpIdentifier(name) {
-  // Must start with letter or underscore
-  // Must contain only letters, digits, underscores
-  // Must not be a C# keyword
-  return /^[A-Za-z_][A-Za-z0-9_]*$/.test(name)
-    && !CSHARP_KEYWORDS.has(name);
-}
-
-const CSHARP_KEYWORDS = new Set([
-  'abstract', 'as', 'base', 'bool', 'break', 'byte', 'case', 'catch',
-  'char', 'checked', 'class', 'const', 'continue', 'decimal', 'default',
-  'delegate', 'do', 'double', 'else', 'enum', 'event', 'explicit',
-  'extern', 'false', 'finally', 'fixed', 'float', 'for', 'foreach',
-  'goto', 'if', 'implicit', 'in', 'int', 'interface', 'internal',
-  'is', 'lock', 'long', 'namespace', 'new', 'null', 'object',
-  'operator', 'out', 'override', 'params', 'private', 'protected',
-  'public', 'readonly', 'ref', 'return', 'sbyte', 'sealed', 'short',
-  'sizeof', 'stackalloc', 'static', 'string', 'struct', 'switch',
-  'this', 'throw', 'true', 'try', 'typeof', 'uint', 'ulong',
-  'unchecked', 'unsafe', 'ushort', 'using', 'virtual', 'void',
-  'volatile', 'while'
-]);
-```
-
----
-
-## Examples
-
-| BA Entity Name (French) | Canonicalized | File Path |
-|-------------------------|---------------|-----------|
-| `Type d'absence` | `TypeAbsence` | `src/Domain/Entities/App/Module/TypeAbsence.cs` |
-| `Employé` | `Employe` | `src/Domain/Entities/App/Module/Employe.cs` |
-| `Congé maladie` | `CongeMaladie` | `src/Domain/Entities/App/Module/CongeMaladie.cs` |
-| `Mise à jour` | `MiseJour` | `src/Domain/Entities/App/Module/MiseJour.cs` |
-| `Département` | `Departement` | `src/Domain/Entities/App/Module/Departement.cs` |
-| `Employee` | `Employee` | `src/Domain/Entities/App/Module/Employee.cs` (no change) |
-| `AbsenceType` | `AbsenceType` | `src/Domain/Entities/App/Module/AbsenceType.cs` (no change) |
-
----
-
-## Integration Points
-
-1. **step-01-transform.md**: Apply `canonicalizeEntityName()` to ALL entity names BEFORE generating `filesToCreate` paths
-2. **step-02-export.md**: POST-CHECK validates all paths in `filesToCreate` are valid C# identifiers
-3. **entity-domain-mapping.md**: `{EntityName}` in path templates refers to the CANONICALIZED name
-4. **handoff-file-templates.md**: All `{EntityName}` placeholders use canonicalized names
-
-## Anti-Patterns
-
-| Anti-Pattern | Risk | Correct Approach |
-|-------------|------|-----------------|
-| Translate to English semantically | `MiseJour` → `Update`? No — loses domain meaning | Only strip illegal chars, keep semantics |
-| Remove all short words | `TypeAbsence` missing `Type`? | Only remove articles/prepositions, not nouns |
-| Lowercase everything | `typeabsence` is not PascalCase | PascalCase each token |
-| Skip validation | `Task` is a valid name but also a C# type | Warn on namespace conflicts, don't block |

package/templates/skills/business-analyse-handoff/references/entity-domain-mapping.md

@@ -1,115 +0,0 @@
-# Entity-to-Domain File Mapping
-
-> **Used by:** step-01-transform (section 6: Map Entity to Domain File)
-> **Purpose:** Define the 1:1 mapping between BA entities and Domain layer files.
-
----
-
-## Mapping Rules
-
-Each entity identified during business analysis maps to exactly one file in the Domain layer. The mapping is deterministic based on entity type and module.
-
-### Entity -> Domain Entity File
-
-```
-BA: entities.json > entities[].name = "{EntityName}"
-    entities.json > entities[].module = "{ModuleCode}"
-    metadata.application = "{AppName}"
-
-Domain: src/SmartStack.{AppName}.Domain/{ModuleCode}/Entities/{EntityName}.cs
-```
-
-**Example:**
-```
-BA: entities.json > entities[].name = "Employee"
-    module = "Employees"
-    application = "HumanResources"
-
-Domain: src/SmartStack.HumanResources.Domain/Employees/Entities/Employee.cs
-```
-
-### ValueObject -> Domain ValueObject File
-
-```
-BA: entities.json > entities[].valueObjects[].name = "{VOName}"
-
-Domain: src/SmartStack.{AppName}.Domain/{ModuleCode}/ValueObjects/{VOName}.cs
-```
-
-**Example:**
-```
-BA: valueObject.name = "Address"
-    module = "Employees"
-
-Domain: src/SmartStack.HumanResources.Domain/Employees/ValueObjects/Address.cs
-```
-
-### Enum -> Domain Enum File
-
-```
-BA: entities.json > entities[].enums[].name = "{EnumName}"
-    OR attributes with type "enum" and enumValues[]
-
-Domain: src/SmartStack.{AppName}.Domain/{ModuleCode}/Enums/{EnumName}.cs
-```
-
-**Example:**
-```
-BA: enum.name = "EmployeeStatus"
-    module = "Employees"
-
-Domain: src/SmartStack.HumanResources.Domain/Employees/Enums/EmployeeStatus.cs
-```
-
----
-
-## Path Pattern Summary
-
-| BA Element | Domain File Path |
-|------------|-----------------|
-| Entity | `src/SmartStack.{App}.Domain/{Module}/Entities/{EntityName}.cs` |
-| ValueObject | `src/SmartStack.{App}.Domain/{Module}/ValueObjects/{VOName}.cs` |
-| Enum | `src/SmartStack.{App}.Domain/{Module}/Enums/{EnumName}.cs` |
-| Domain Exception | `src/SmartStack.{App}.Domain/{Module}/Exceptions/{ExceptionName}.cs` |
-| Domain Service | `src/SmartStack.{App}.Domain/{Module}/Services/{ServiceName}.cs` |
-
----
-
-## Cross-Module Entity References
-
-When an entity in module A references an entity in module B:
-- The reference is by ID only (no direct entity dependency across modules)
-- Navigation properties use the same `{App}.Domain/{Module}/Entities/` path
-- Cross-module FK: `{OtherModuleEntity}Id` property + configuration in Infrastructure layer
-
----
-
-## Integration with filesToCreate.domain
-
-Each mapped entity becomes an entry in `handoff.filesToCreate.domain[]`:
-
-```json
-{
-  "path": "src/SmartStack.HumanResources.Domain/Employees/Entities/Employee.cs",
-  "type": "Entity",
-  "module": "Employees",
-  "dependencies": []
-}
-```
-
-ValueObjects and Enums are also included:
-
-```json
-{
-  "path": "src/SmartStack.HumanResources.Domain/Employees/ValueObjects/Address.cs",
-  "type": "ValueObject",
-  "module": "Employees",
-  "dependencies": []
-},
-{
-  "path": "src/SmartStack.HumanResources.Domain/Employees/Enums/EmployeeStatus.cs",
-  "type": "Enum",
-  "module": "Employees",
-  "dependencies": []
-}
-```

package/templates/skills/business-analyse-handoff/references/handoff-file-inventory.md

@@ -1,49 +0,0 @@
-# Handoff File Inventory
-
-## FICHIERS A CREER — LISTE FERMEE (ba-009 fix)
-
-Exhaustive inventory. ONLY these files must be created. ABSOLUTE PROHIBITION on creating README, SUMMARY, MANIFEST, INDEX, CHECKLIST, ARTIFACTS, EXECUTION-SUMMARY, etc.
-
-## Per-Module Files (Created 7 times, once per module {M})
-
-| # | Filename | Location |
-|---|----------|----------|
-| 1 | `handoff.json` | `{moduleDir}/handoff.json` (in docs/) |
-| 2 | `prd-{M}.json` | `.ralph/prd-{M}.json` (PRD master v3.0.0) |
-| 3 | `prd-{M}.entities.json` | `.ralph/` (VERBATIM copy) |
-| 4 | `prd-{M}.rules.json` | `.ralph/` (VERBATIM copy) |
-| 5 | `prd-{M}.usecases.json` | `.ralph/` (VERBATIM copy) |
-| 6 | `prd-{M}.screens.json` | `.ralph/` (VERBATIM copy) |
-| 7 | `prd-{M}.permissions.json` | `.ralph/` (VERBATIM copy) |
-
-**Subtotal per module:** 7 files
-
-## Global Files (Created once)
-
-| # | Filename | Location |
-|---|----------|----------|
-| 8 | `modules-queue.json` | `.ralph/modules-queue.json` |
-| 9 | `progress.txt` | `.ralph/progress.txt` |
-
-**Subtotal:** 2 files
-
-## Total
-
-**TOTAL: (7 × N modules) + 2 global files**
-
-For a 3-module project: 7×3 + 2 = 23 files exactly.
-
-## Companion File Naming — REGEX CANONIQUE
-
-Each companion MUST match: `prd-{ModuleCode}.{suffix}.json`
-
-where `suffix ∈ { entities | rules | usecases | screens | permissions }`
-
-### FORBIDDEN VARIANTS (ABSOLUTE PROHIBITION)
-
-- ✗ `prd-Module.useCases.json` (wrong casing — must be `usecases`)
-- ✗ `prd-Module.businessRules.json` (wrong name — must be `rules`)
-- ✗ `prd-Module.api-spec.json` (not planned)
-- ✗ `prd-Module.summary.json` (not planned)
-
-All companion filenames must use **lowercase** suffixes and EXACTLY the 5 defined names.

package/templates/skills/business-analyse-handoff/references/handoff-file-templates.md

@@ -1,197 +0,0 @@
-# Handoff File Templates (8 Categories)
-
-> **PATH HIERARCHY CONVENTION:** All backend file paths MUST include the application hierarchy.
-> - `{ApplicationName}` = `metadata.application` (e.g., `"HumanResources"`)
-> - `{ModuleName}` = `metadata.module` (e.g., `"Projects"`)
-
-## 4.1 Domain Files
-
-From `entities.json > entities[]`:
-
-```json
-"domain": [
-  { "path": "src/Domain/Entities/{ApplicationName}/{ModuleName}/{EntityName}.cs", "type": "Entity", "linkedFRs": [], "linkedUCs": [], "module": "{moduleCode}" }
-]
-```
-
-Include: Value objects, Enums (`src/Domain/Enums/...`), Domain exceptions (`src/Domain/Exceptions/...`)
-
-## 4.2 Application Files
-
-From `usecases.json > useCases[]`:
-
-```json
-"application": [
-  { "path": "src/Application/Services/{ApplicationName}/{ModuleName}/{ServiceName}Service.cs", "type": "Service", "linkedFRs": [], "linkedUCs": [], "module": "{moduleCode}" },
-  { "path": "src/Application/DTOs/{ApplicationName}/{ModuleName}/{DtoName}Dto.cs", "type": "Dto", "linkedUCs": [], "module": "{moduleCode}" },
-  { "path": "src/Application/Validators/{ApplicationName}/{ModuleName}/{ValidatorName}Validator.cs", "type": "Validator", "linkedFRs": [], "module": "{moduleCode}" }
-]
-```
-
-Include: Service per UC cluster, DTOs for API contracts, Validators (FluentValidation), Query handlers
-
-**Validator generation rules:**
-- Every entity with Create and/or Update use cases MUST have a corresponding Validator
-- Validators MUST be registered in DI (`services.AddScoped<IValidator<CreateXxxDto>, CreateXxxValidator>()`)
-- Validators MUST be injected into controllers/services that handle POST/PUT operations
-- NO TODO/placeholder comments allowed in Validators — all validation rules from business rules (BR-VAL-*) must be implemented
-
-## 4.3 Infrastructure Files
-
-From `entities.json > entities[]`:
-
-```json
-"infrastructure": [
-  { "path": "src/Infrastructure/Persistence/Configurations/{ApplicationName}/{ModuleName}/{EntityName}Configuration.cs", "type": "EFConfiguration", "linkedFRs": [], "module": "{moduleCode}" }
-]
-```
-
-Include: EF Core config per entity, DbSet in IExtensionsDbContext, DI registration, Specifications
-
-## 4.4 API Files
-
-Generated from `usecases.json` + `entities.json`:
-
-```json
-"api": [
-  { "path": "src/API/Controllers/{ApplicationName}/{EntityName}Controller.cs", "type": "ApiController", "navRoute": "{app-kebab}.{module-kebab}", "isSection": false, "linkedUCs": [], "linkedFRs": [], "module": "{moduleCode}" },
-  { "path": "src/API/Controllers/{ApplicationName}/{ModuleName}/{SectionEntityName}Controller.cs", "type": "ApiController", "navRoute": "{app-kebab}.{module-kebab}.{section-kebab}", "isSection": true, "linkedUCs": [], "linkedFRs": [], "module": "{moduleCode}" }
-]
-```
-
-Include: One controller per aggregate root, all HTTP methods, error handling
-
-## 4.5 Frontend Files
-
-From `screens.json > screens[]` and `usecases.json > useCases[]`:
-
-> **WIREFRAME TRACEABILITY:** Every frontend file MUST include `linkedWireframes[]` referencing wireframe `screen` identifiers.
-
-```json
-"frontend": [
-  { "path": "src/pages/{ApplicationName}/{ModuleName}/{PageName}Page.tsx", "type": "Page", "linkedUCs": [], "linkedWireframes": ["{module}-list"], "module": "{moduleCode}", "wireframeAcceptanceCriteria": "Layout MUST match wireframe...", "skill": "/ui-components" },
-  { "path": "src/pages/{ApplicationName}/{ModuleName}/{PageName}DetailPage.tsx", "type": "Page", "linkedUCs": [], "linkedWireframes": ["{module}-detail"], "module": "{moduleCode}", "skill": "/ui-components" },
-  { "path": "src/pages/{ApplicationName}/{ModuleName}/{DashboardName}DashboardPage.tsx", "type": "DashboardPage", "linkedUCs": [], "linkedWireframes": ["{module}-dashboard"], "module": "{moduleCode}", "dashboardRef": "{module}-dashboard", "instructions": "Use Recharts library...", "skill": "/ui-components" },
-  { "path": "src/components/{ModuleName}/{ComponentName}.tsx", "type": "Component", "linkedUCs": [], "linkedWireframes": [], "module": "{moduleCode}", "skill": "/ui-components" },
-  { "path": "src/hooks/use{ModuleName}{Hook}.ts", "type": "Hook", "linkedUCs": [], "module": "{moduleCode}" },
-  { "path": "src/i18n/locales/fr/{moduleLower}.json", "type": "I18n", "language": "fr", "module": "{moduleCode}" },
-  { "path": "src/i18n/locales/en/{moduleLower}.json", "type": "I18n", "language": "en", "module": "{moduleCode}" },
-  { "path": "src/i18n/locales/it/{moduleLower}.json", "type": "I18n", "language": "it", "module": "{moduleCode}" },
-  { "path": "src/i18n/locales/de/{moduleLower}.json", "type": "I18n", "language": "de", "module": "{moduleCode}" }
-]
-```
-
-**Page generation:** ALL pages and components MUST be generated via `/ui-components` skill (entity lists, grids, tables, dashboards, charts). The `"skill"` field indicates which skill to invoke.
-
-**I18n generation:** 4 JSON files per module (fr, en, it, de) with identical key structures. `{moduleLower}` = lowercase module code. See `smartstack-frontend.md` for JSON template (keys: actions, labels, columns, form, errors, validation, messages, empty).
-
-**Dashboard acceptance criteria:** Chart library (Recharts), chart types matching spec, KPI cards, filters, CSS variables, responsive layout, wireframe-matching positions.
-
-## 4.5b Notification Files (CONDITIONAL)
-
-> Generated only when `lifeCycles[].transitions[].effects[]` contains entries with `type: "notification"`.
-
-```json
-"notifications": [
-  { "path": "src/Application/Notifications/{ApplicationName}/{ModuleName}/{NotificationName}Notification.cs", "type": "Notification", "linkedUCs": [], "module": "{moduleCode}", "description": "Notification triggered by lifecycle transition" },
-  { "path": "src/Application/Notifications/{ApplicationName}/{ModuleName}/{NotificationName}NotificationHandler.cs", "type": "NotificationHandler", "linkedUCs": [], "module": "{moduleCode}", "description": "Handler that sends in-app/email notification" }
-]
-```
-
-**Generation rules:**
-- One Notification + Handler pair per unique `notification` effect in lifecycle transitions
-- NotificationName derived from transition: `{Entity}{TransitionName}` (e.g., `OrderApproved`)
-- Handler must use `INotificationService` for in-app and `IEmailService` for email type
-- Notification must include: recipient resolution, template reference, and payload mapping
-
-## 4.6 SeedData Files
-
-**OBLIGATORY: 2 app-level CORE + per module CORE (NavigationModule + NavigationSections + Permissions + Roles) + business per module:**
-
-```json
-"seedData": [
-  { "path": "src/Infrastructure/Persistence/Seeding/Data/NavigationApplicationSeedData.cs", "type": "SeedData", "category": "core", "source": "generated from permissions.json + screens.json", "module": "shared", "description": "Application-level navigation seed data. Created ONCE per application (FIRST). Provides ApplicationId for modules and roles." },
-  { "path": "src/Infrastructure/Persistence/Seeding/Data/ApplicationRolesSeedData.cs", "type": "SeedData", "category": "core", "source": "generated from permissions.json + screens.json", "module": "shared", "description": "Application-scoped role definitions (admin, manager, contributor, viewer). Created ONCE per application. Provides role entries for SeedRolesAsync()." },
-  { "path": "src/Infrastructure/Persistence/Seeding/Data/{ModuleName}/NavigationModuleSeedData.cs", "type": "SeedData", "category": "core", "source": "generated from permissions.json + screens.json", "module": "{moduleCode}" },
-  { "path": "src/Infrastructure/Persistence/Seeding/Data/{ModuleName}/NavigationSectionSeedData.cs", "type": "SeedData", "category": "core", "source": "generated from permissions.json + screens.json", "module": "{moduleCode}", "description": "MANDATORY when sections defined. Seeds section-level navigation entries (list, dashboard, etc.) with full absolute routes." },
-  { "path": "src/Infrastructure/Persistence/Seeding/Data/{ModuleName}/PermissionsSeedData.cs", "type": "SeedData", "category": "core", "source": "generated from permissions.json + screens.json", "module": "{moduleCode}" },
-  { "path": "src/Infrastructure/Persistence/Seeding/Data/{ModuleName}/RolesSeedData.cs", "type": "SeedData", "category": "core", "source": "generated from permissions.json + screens.json", "module": "{moduleCode}" },
-  { "path": "src/Infrastructure/Persistence/Seeding/Data/{ModuleName}/{Entity}SeedData.cs", "type": "SeedData", "category": "business", "source": "generated from entities.json", "module": "{moduleCode}" }
-]
-```
-
-**For client projects (ExtensionsDbContext), add MANDATORY infrastructure files:**
-
-```json
-[
-  { "path": "src/Infrastructure/Persistence/Seeding/{AppPascalName}SeedDataProvider.cs", "type": "IClientSeedDataProvider", "category": "infrastructure", "description": "Runtime provider that injects core seed data into Core schema" },
-  { "path": "src/Infrastructure/Persistence/Seeding/DevDataSeeder.cs", "type": "DevDataSeeder", "category": "infrastructure" },
-  { "path": "src/Infrastructure/Persistence/Seeding/Data/SeedConstants.cs", "type": "SeedConstants", "category": "infrastructure" }
-]
-```
-
-**Path convention:** All seed data under `Persistence/Seeding/Data/`. NEVER use `Data/SeedData/`.
-
-## 4.7 Test Files
-
-```json
-"tests": [
-  { "path": "src/Tests/Unit/Domain/{ApplicationName}/{ModuleName}/{Entity}Tests.cs", "type": "UnitTests", "linkedFRs": [], "module": "{moduleCode}" },
-  { "path": "src/Tests/Unit/Application/{ApplicationName}/{ModuleName}/{ServiceName}ServiceTests.cs", "type": "UnitTests", "linkedFRs": [], "linkedUCs": [], "module": "{moduleCode}" },
-  { "path": "src/Tests/Integration/{ApplicationName}/{ModuleName}/{ApiControllerName}ControllerTests.cs", "type": "IntegrationTests", "linkedUCs": [], "module": "{moduleCode}" },
-  { "path": "src/Tests/Security/{ApplicationName}/{ModuleName}/{ModuleName}SecurityTests.cs", "type": "SecurityTests", "linkedFRs": [], "module": "{moduleCode}" }
-]
-```
-
-## 4.8 Documentation Files
-
-```json
-"documentation": [
-  { "path": "src/docs/{ModuleName}/doc-data.ts", "type": "DocData", "module": "{moduleCode}", "description": "Documentation data export for /documentation skill" }
-]
-```
-
-Include: Technical documentation data, API specification files, user guides.
-This category can be an empty array `[]` if no documentation is planned at this stage. It will be populated by the `/documentation` skill after `/business-analyse-develop` completes.
-
-## 4.9 Specification Files (Companion Files)
-
-> **Purpose:** Enable `/apex` and `/business-analyse-develop` to load full BA specifications per layer, avoiding monolithic context loading.
-
-Each PRD MUST include a `specificationFiles` object referencing 5 companion files:
-
-```json
-"specificationFiles": {
-  "entities": "prd-{moduleCode}.entities.json",
-  "rules": "prd-{moduleCode}.rules.json",
-  "usecases": "prd-{moduleCode}.usecases.json",
-  "screens": "prd-{moduleCode}.screens.json",
-  "permissions": "prd-{moduleCode}.permissions.json"
-}
-```
-
-### Naming Convention
-
-`prd-{moduleCode}.{section}.json` — all files colocated in `.ralph/` alongside the PRD.
-
-| File | Source | Content |
-|------|--------|---------|
-| `prd-{moduleCode}.entities.json` | `{moduleDir}/entities.json` | VERBATIM copy |
-| `prd-{moduleCode}.rules.json` | `{moduleDir}/rules.json` | VERBATIM copy |
-| `prd-{moduleCode}.usecases.json` | `{moduleDir}/usecases.json` | VERBATIM copy |
-| `prd-{moduleCode}.screens.json` | `{moduleDir}/screens.json` | VERBATIM copy |
-| `prd-{moduleCode}.permissions.json` | `{moduleDir}/permissions.json` | VERBATIM copy |
-
-### Rules
-
-- **VERBATIM copy:** Each companion file is a 1:1 copy of the BA source file. Zero transformation, zero filtering.
-- **Colocated:** All companion files live in `.ralph/` alongside the PRD file.
-- **Mandatory:** All 5 companion files MUST be generated for every module PRD.
-- **Layer loading:** `/apex` loads only the companion files needed per layer (see loading plan below).
-
-| Layer | Files loaded | Estimated context |
-|-------|-------------|-------------------|
-| Layer 0 (domain) | `entities.json` | ~200-400 lines |
-| Layer 1 (seed) | `entities.json` + `permissions.json` | ~300-500 lines |
-| Layer 2 (backend) | `rules.json` + `usecases.json` | ~300-600 lines |
-| Layer 3 (frontend) | `screens.json` + `usecases.json` | ~300-500 lines |

package/templates/skills/business-analyse-handoff/references/handoff-global-validation.md

@@ -1,142 +0,0 @@
-# Handoff Global Validation
-
-## Overview
-
-POST-CHECK GLOBAL validation (BLOCKING — ba-009 fix). Verifies overall handoff integrity across all modules, not just individual PRDs.
-
-Blocks completion if expected files are missing.
-
-## Module-Level Integrity Checks
-
-For each module:
-
-### handoff.json Presence (CRITICAL)
-
-Check that handoff.json exists in module's docs directory.
-
-This file was missing for 3/12 modules in ba-009 and is critical for handoff integrity.
-
-```javascript
-if (!EXISTS(moduleDir + '/handoff.json'))
-  errors.push('MISSING: ' + moduleDir + '/handoff.json');
-```
-
-### PRD Master File
-
-Check that main PRD file exists in .ralph/ directory.
-
-```javascript
-if (!EXISTS('.ralph/prd-' + mod.code + '.json'))
-  errors.push('MISSING: .ralph/prd-' + mod.code + '.json');
-```
-
-### Companion Files
-
-Check that all 5 companion specification files exist in .ralph/:
-- entities
-- rules
-- usecases
-- screens
-- permissions
-
-```javascript
-['entities', 'rules', 'usecases', 'screens', 'permissions'].forEach(suffix => {
-  const path = '.ralph/prd-' + mod.code + '.' + suffix + '.json';
-  if (!EXISTS(path)) errors.push('MISSING: ' + path);
-});
-```
-
-## Global File Checks
-
-### Multi-Module Queue
-
-If processing 2+ modules, check that modules-queue.json exists.
-
-```javascript
-if (modules.length >= 2 && !EXISTS('.ralph/modules-queue.json'))
-  errors.push('MISSING: .ralph/modules-queue.json');
-```
-
-### Progress Tracker
-
-Check that progress.txt exists.
-
-```javascript
-if (!EXISTS('.ralph/progress.txt'))
-  errors.push('MISSING: .ralph/progress.txt');
-```
-
-## Surplus File Detection
-
-Check for unexpected files in .ralph/ that aren't part of the template.
-
-### Expected Files Set
-
-Build set of all expected files:
-- PRD masters: `prd-{moduleCode}.json` for each module
-- Companion files: `prd-{moduleCode}.{suffix}.json` for each module and suffix
-- Global files: `modules-queue.json`, `progress.txt`
-
-```javascript
-const expectedFiles = new Set();
-modules.forEach(m => {
-  expectedFiles.add('prd-' + m.code + '.json');
-  ['entities','rules','usecases','screens','permissions'].forEach(s =>
-    expectedFiles.add('prd-' + m.code + '.' + s + '.json'));
-});
-expectedFiles.add('modules-queue.json');
-expectedFiles.add('progress.txt');
-```
-
-### Actual Files in .ralph/
-
-Scan .ralph/ directory for all files (excluding logs/).
-
-Flag any file not in expected set as surplus with warning message.
-
-```javascript
-const actualFiles = GLOB('.ralph/*').filter(f => !f.includes('/logs/'));
-actualFiles.forEach(f => {
-  const basename = f.split('/').pop();
-  if (!expectedFiles.has(basename))
-    warnings.push('SURPLUS: ' + f + ' — fichier non prevu par le template');
-});
-```
-
-## Result Handling
-
-### Blocking Errors
-
-If errors exist, display all errors and block completion.
-
-```javascript
-if (errors.length > 0) {
-  Display('POST-CHECK GLOBAL FAILED (' + errors.length + ' errors):');
-  errors.forEach(e => Display('  X ' + e));
-  BLOCKING_ERROR('Fix all missing files before completing. See FICHIERS A CREER in step-01.');
-}
-```
-
-### Warnings
-
-Display any surplus files found (non-blocking).
-
-```javascript
-if (warnings.length > 0) {
-  Display('POST-CHECK warnings (' + warnings.length + ' surplus files):');
-  warnings.forEach(w => Display('  ! ' + w));
-}
-```
-
-### Success Message
-
-Display final validation pass message with module count and expected file count.
-
-```javascript
-Display('POST-CHECK GLOBAL PASS: ' + modules.length + ' modules, ' +
-  (modules.length * 7 + 2) + ' fichiers attendus');
-```
-
-Formula: `modules.length * 7 + 2`
-- Each module: 1 PRD master + 5 companions + 1 handoff.json = 7 files
-- Global: modules-queue.json (if multi-module) + progress.txt = 2 files