@atlashub/smartstack-cli 4.80.0 → 5.0.0

package/templates/skills/business-analyse/references/entity-architecture-decision.md

@@ -1,240 +0,0 @@
-# Entity Architecture Decision Reference
-
-> **Loaded by:** step-01-cadrage (section 4d-bis)
-> **Purpose:** Provide a structured decision framework for entity placement in the C/A/M/S/R hierarchy
-> **Mode:** ULTRATHINK — all scoring is internal reasoning, only the recommendation is shown to the client
-
----
-
-## 0. Pre-check: Person Extension
-
-**BEFORE** running the entity architecture scoring, check if this entity represents a person role.
-
-### Detection criteria:
-1. **Name match**: Entity name is in the known person role list (Employee, Customer, Manager, Supplier, etc.)
-2. **Attribute match**: Entity has 3+ attributes among (firstName, lastName, email, phoneNumber, department, jobTitle, address)
-
-### If detected:
-→ Recommend **Person Extension Pattern** (link to User via UserId FK)
-→ Ask user to confirm variant: mandatory (always a User) or optional (may or may not have a User)
-→ Store `personRoleConfig` in entity structure card
-→ **Skip standard entity architecture scoring** for person-specific fields (they come from User)
-
-### Known person role names:
-| Variant | Entity names |
-|---------|-------------|
-| **Mandatory** (always a User) | Employee, Manager, Instructor, Teacher, Trainer, Technician |
-| **Optional** (may have a User) | Customer, Client, Supplier, Vendor, Patient, Student, Member, Participant, Candidate, Applicant, Contact, Lead, Prospect, Volunteer, Contractor, Freelancer, Consultant |
-
----
-
-## 1. Entity Scoring Grid (5 criteria, 0-3 each)
-
-For EACH referenced entity detected during approfondissement, score silently:
-
-| Critere | 0 (Lookup) | 1 (Composant) | 2 (Module leger) | 3 (Module complet) |
-|---------|-----------|---------------|-------------------|---------------------|
-| **Cycle de vie** | Statique (rarement modifie, admin-only) | CRUD basique (creer, modifier, supprimer) | CRUD + etats/transitions simples | Lifecycle complet (etats multiples, transitions, approbations, archivage) |
-| **Nombre d'acteurs** | Admin seul | 1 role utilisateur | 2-3 roles distincts | 4+ roles avec permissions differenciees |
-| **Relations** | Lookup (0-1 FK entrantes) | Composant (1-3 FK) | Hub (3-5 FK entrantes/sortantes) | Pivot (5+ FK, central dans le graphe de donnees) |
-| **Volume prevu** | < 50 entrees stables | 50-500 entrees | 500-5000 entrees | 5000+ ou croissance continue |
-| **Autonomie fonctionnelle** | Pas de sens seul (ex: code postal) | Sens uniquement dans le contexte parent | Pourrait etre utilise seul | Domaine metier independant (ex: Clients, Projets) |
-
-### Interpretation du score total (0-15)
-
-| Score | Classification | Action |
-|-------|---------------|--------|
-| **0-3** | **Config list** (lookup table) | Table de reference administrable. Pas de module, pas de section. Gere dans la config admin. |
-| **4-6** | **Gere dans l'app** (sous-entite) | L'entite est geree comme composant du module parent. Accessible via un onglet dans la page detail du parent. |
-| **7-10** | **Module leger** | Module avec section `list` principale. Peu de sections fonctionnelles additionnelles. |
-| **11-15** | **Module complet dedie** | Module avec section `list` + sections fonctionnelles riches (dashboard, rapports, workflows). |
-
----
-
-## 2. Domain Coherence Decision Tree
-
-> **CRITICAL:** Evaluer la coherence domaine AVANT le scoring. Une entite PERIPHERAL avec un score eleve reste un risque de scope creep.
-
-```
-L'entite {E} est-elle CORE pour cette application ?
-│
-├── CORE (sans {E}, l'application perd son sens)
-│   │   Exemples : Projets dans une app de gestion du temps,
-│   │              Clients dans un CRM,
-│   │              Employes dans une app RH
-│   │
-│   └── Score >= 7 ? → Module dedie (RECOMMANDE avec haute confiance)
-│   └── Score 4-6 ? → Section/onglet dans le module principal
-│   └── Score 0-3 ? → Config list (rare pour une entite CORE)
-│
-├── SUPPORT (utile, enrichit l'app, mais pas central)
-│   │   Exemples : Departements dans une app de gestion du temps,
-│   │              Fournisseurs dans un CRM orientee ventes,
-│   │              Categories dans un module produits
-│   │
-│   ├── Deja gere ailleurs dans l'ecosysteme ? → Systeme externe (RECOMMANDE)
-│   └── Pas encore gere ?
-│       └── Score >= 7 ? → Module leger (confiance MOYENNE, alerter sur le scope)
-│       └── Score 4-6 ? → Section/onglet du module qui en a le plus besoin
-│       └── Score 0-3 ? → Config list (RECOMMANDE)
-│
-└── PERIPHERAL (tangentiel au domaine applicatif)
-    │   Exemples : Comptabilite dans une app de gestion du temps,
-    │              Logistique dans un CRM,
-    │              Facturation dans une app RH (sauf si paie)
-    │
-    └── TOUJOURS → Config list ou Systeme externe (RECOMMANDE)
-        Avertir : "Cette entite sort du perimetre applicatif.
-                   Risque de scope creep si integree comme module."
-```
-
----
-
-## 3. Pre-classified Entity Patterns
-
-> **Raccourcis de scoring** : ces patterns accelerent l'analyse en fournissant une classification par defaut.
-> Le scoring complet reste necessaire pour confirmer ou overrider.
-
-### 3a. Toujours Module Dedie (score typique >= 11)
-
-| Entite | Domaines typiques | Pourquoi module dedie |
-|--------|-------------------|-----------------------|
-| Clients/Customers | CRM, Ventes, Facturation | Hub relationnel central, multi-acteur, lifecycle complet avec etats |
-| Employes/Employees | RH, Temps, Paie | Acteur central avec donnees sensibles, multi-workflows (conges, evaluations) |
-| Projets/Projects | Gestion, Temps, Facturation | Lifecycle complexe (ouvert → en cours → cloture), multi-ressources, reporting |
-| Commandes/Orders | Ventes, Logistique | Workflow d'approbation, etats multiples, sous-entites (lignes) |
-| Factures/Invoices | Finance, Ventes | Obligations legales, workflow complexe, etats fiscaux |
-| Contrats/Contracts | Juridique, RH, Ventes | Lifecycle avec echeances, obligations, renouvellement automatique |
-| Produits/Products | Commerce, Inventaire | Catalogue avec variantes, tarification, stock |
-
-### 3b. Souvent Sous-entite du Parent (score typique 4-6)
-
-| Entite | Module parent typique | Pourquoi sous-entite |
-|--------|----------------------|-----------------------|
-| Adresses | Clients, Employes | Composant du parent, pas de sens sans le parent |
-| Notes/Commentaires | Tout module | Sous-objet universel, pas d'autonomie fonctionnelle |
-| Pieces jointes/Documents | Tout module | Stockage lie au parent, pas de lifecycle propre |
-| Lignes de commande | Commandes | Composant structurel de la commande |
-| Tags/Labels | Tout module | Categorisation simple, admin-configurable |
-| Contacts (d'un client) | Clients | Personnes liees a l'entite parente |
-
-### 3c. Toujours Config List (score typique 0-3)
-
-| Entite | Pourquoi config list |
-|--------|---------------------|
-| Pays, Villes | Reference geographique stable, rarement modifiee |
-| Devises | Reference systeme, standard ISO |
-| Statuts (types enumeres) | Enum ou lookup, admin-only, < 20 valeurs |
-| Unites de mesure | Reference technique stable |
-| Codes postaux | Reference externe, pas de CRUD utilisateur |
-| Types/Categories simples | Flat list sans hierarchie, configurable par admin |
-
-> **Override rule:** Une entite pre-classifiee "config list" peut etre promue en "module leger" si le client exprime un besoin de hierarchie (> 2 niveaux), de workflow, ou de permissions specifiques.
-
----
-
-## 4. Section Pattern for Modules
-
-> **REGLE FONDAMENTALE : Les sections representent des sections fonctionnelles, PAS des operations CRUD.**
-
-### Le pattern de navigation SmartStack
-
-```
-Module
-├── Section: list
-│   └── Page principale avec grille/table
-│   └── Action "Creer" (navigue vers la page /create avec formulaire)
-│   └── Clic sur une ligne → navigation vers la page detail
-│   └── Resources : {entity}-grid, {entity}-filters, {entity}-form
-│
-├── (detail = page de detail avec onglets, accessible depuis list)
-│   └── Onglet Info → informations principales (lecture + edition)
-│   └── Onglet {relation} → sous-entites liees (ex: Lignes, Contacts, Documents)
-│   └── Onglet Historique → journal d'activite
-│   └── Resources : {entity}-detail, {entity}-tabs, {relation}-panel
-│
-├── Section: dashboard (SI KPIs/reporting necessaire)
-│   └── Vue d'ensemble avec cartes KPI, graphiques, activite recente
-│   └── Resources : {entity}-kpi-cards, {entity}-charts, {entity}-activity
-│
-├── Section: approve (SI workflow d'approbation)
-│   └── File d'attente d'approbation, timeline de statut
-│   └── Resources : approval-queue, status-timeline
-│
-├── Section: import (SI import en masse)
-│   └── Upload fichier, mapping colonnes, preview, execution
-│   └── Resources : import-upload, import-mapping, import-preview
-│
-└── Section: rapport (SI reporting specifique au module)
-    └── Rapports configurables, export, planification
-    └── Resources : report-builder, report-export
-```
-
-### Ce qui n'est JAMAIS une section
-
-| PAS une section | C'est quoi en realite |
-|-----------------|----------------------|
-| `create` | Action (bouton) dans la page `list`, navigue vers la page `/create` avec formulaire |
-| `edit` | Action dans la page list/detail, navigue vers la page `/:id/edit` avec formulaire pre-rempli |
-| `detail` | Page de detail accessible par navigation depuis `list` (pas une section menu) |
-| `delete` | Action avec confirmation dans la page `list` ou `detail` |
-| `search` | Composant de filtrage integre dans la section `list` |
-
-### Regles de proposition de sections
-
-| Condition detectee | Section a proposer |
-|--------------------|--------------------|
-| Module avec entites | `list` (TOUJOURS — section par defaut obligatoire) |
-| KPIs, indicateurs, ou role manager | `dashboard` |
-| Workflow de validation/approbation | `approve` |
-| Volume > 100 ou import mentionne | `import` |
-| Reporting specifique au module | `rapport` |
-| Planification temporelle | `planning` / `calendar` |
-| Visualisation geographique | `map` |
-
----
-
-## 5. Architecture Proposal Template
-
-> **Utiliser ce template quand la recommandation est "Module dedie".**
-
-```markdown
-### Architecture proposee : {ModuleName}
-
-| Niveau | Valeur | Justification |
-|--------|--------|---------------|
-| Context | `business` | Contexte metier standard |
-| Application | `{ApplicationCode}` | {Nom de l'application en cours d'analyse} |
-| Module | `{ModuleCode}` | {Pourquoi ce decoupage : autonomie fonctionnelle, domaine distinct, cycle de vie propre} |
-
-**Sections fonctionnelles :**
-
-| Section | Justification | Resources |
-|---------|---------------|-----------|
-| `list` | Page principale de gestion des {entity_plural} | {entity}-grid, {entity}-filters, {entity}-form |
-| {section_2} | {pourquoi cette section est necessaire pour CE module} | {resources} |
-| ... | ... | ... |
-
-**Onglets de la page detail :**
-
-| Onglet | Contenu | Pourquoi |
-|--------|---------|----------|
-| Informations | Fiche principale de l'{entity} | Toujours present |
-| {relation_1} | {sous-entites ou entites liees} | {pourquoi cet onglet} |
-| Historique | Journal des modifications | Toujours present si audit requis |
-
-**Impact sur le graphe de dependances :**
-- {ModuleName} sera une dependance de : {list of modules that reference this entity}
-- {ModuleName} depend de : {list of modules it references, or "aucun (module fondation)"}
-- Position dans le tri topologique : couche {N}
-```
-
----
-
-## 6. Confidence Levels
-
-| Confiance | Quand | Presentation au client |
-|-----------|-------|------------------------|
-| **HAUTE** | Pre-classification match + Score coherent + Domaine CORE | "Je recommande fortement..." + option en premier avec "(Recommande)" |
-| **MOYENNE** | Score dans la zone grise (6-8) ou domaine SUPPORT | "Mon analyse suggere..." + option en premier avec "(Suggere)" |
-| **BASSE** | Informations insuffisantes ou domaine PERIPHERAL | "Plusieurs options sont possibles..." + pas de recommandation, options neutres |

package/templates/skills/business-analyse/references/entity-sourcing-presentation.md

@@ -1,166 +0,0 @@
-# Entity Sourcing Presentation (4-Phase Flow)
-
-> **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.
-
-## 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 sections: 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"} |
-|--------|--------|---------------|
-| 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'
-  ? 'Comment souhaitez-vous gérer les {entity_plural} ?'
-  : 'How do you want to manage {entity_plural}?'}"
-header: "{entity_name}"
-options:
-  (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'
-      ? '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'
-      ? '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: "..."
-
-  IF confidence = LOW (no clear recommendation):
-  (all 4 options in neutral order, NO "(Recommandé)" tag)
-```
-
-## PHASE 4 — Process Answer
-
-| Choice | Action |
-|--------|--------|
-| **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 inScope. The `list` section is ALWAYS the main section. Additional sections ONLY for distinct functional sections (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 materials on integrations if not already covered. |
-| **Liste simple en config** | Entity becomes a lookup/reference table (no dedicated module, no section). Note in coverageMatrix as config data. |
-
-> **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.

package/templates/skills/business-analyse/references/init-resume-logic.md

@@ -1,70 +0,0 @@
-# Initialize Resume Logic & Error Handling
-
-> **Purpose:** Handle interruptions, resume previous workflows, and route based on status.
-> Executed at the end of initialization to check if a workflow can be resumed.
-
-## Error Handling Matrix
-
-| Error | Action |
-|-------|--------|
-| Config missing | Create fresh with defaults, continue |
-| Directory creation fails | Check permissions, display error, EXIT |
-| index.json creation fails | Validate ba-writer, retry or fallback |
-| Feature ID not unique | Generate new ID, retry |
-
-## Resume After Interruption
-
-If initialization was interrupted:
-
-1. Check `.business-analyse/config.json` for currentFeature or currentProject
-2. If project ID exists, search for project index.json in `docs/*/v*/` (or legacy `docs/business-analyse/`)
-   - If found with scope = "project": resume project mode (see Project Resume below)
-3. If feature ID exists, search for index.json in `docs/`
-4. If found, check status and `metadata.workflow.lastCompletedStep`
-
-## Status-Based Resume Routing (check in this order)
-
-### If status = `"handed-off"` or `"consolidated"`
-
-→ Display: "BA workflow complete. Use /business-analyse-html to generate HTML, /business-analyse-review for corrections."
-→ **STOP**
-
-### If status = `"specified"` AND `metadata.workflow.allModulesSpecified === true`
-
-→ Resume at `step-04-consolidate.md`
-→ Display: "All modules specified — resuming at consolidation..."
-
-### If status = `"specified"` AND `metadata.workflow.completedModules.length > 0` AND `metadata.workflow.completedModules.length < metadata.workflow.moduleOrder.length`
-
-→ Resume at `step-03-specify.md` (continue specifying remaining modules)
-→ Display: "Resuming module specification ({completedCount}/{totalCount})..."
-
-### Otherwise
-
-→ Offer to resume from last completed step
-
-### If not found
-
-→ Create fresh index.json
-
-## Project Resume (project mode)
-
-If a project-level index.json is found (scope = "project"):
-
-### If status = `"draft"` or `"framed"`
-
-→ Resume at `step-01-cadrage.md`
-
-### If status = `"decomposed"`
-
-→ Check `metadata.workflow.currentApplicationIndex` and `completedApplications[]`
-→ Resume module specification for current application (step-02 or step-03)
-
-### If status = `"specified"`
-
-→ All applications specified → Resume at `step-04-consolidate.md`
-
-### If status = `"consolidated"`
-
-→ Display: "BA workflow complete. Use /business-analyse-html to generate HTML."
-→ **STOP**

package/templates/skills/business-analyse/references/init-schema-deployment.md

@@ -1,65 +0,0 @@
-# Init: JSON Schema Deployment
-
-> Reference for step-00-init.md — cache-based schema deployment.
-
-## Cache-Based Deployment Logic
-
-### Step 1: Check Deployment Cache
-
-Cache file location: `docs/{app}/business-analyse/.schema-cache.json`
-
-```
-IF EXISTS .schema-cache.json:
-  Read cache file
-  IF cache.version == "{CLI_VERSION}" (from package.json):
-    Display: "Schemas already deployed ({CLI_VERSION}) - skipping"
-    SKIP deployment → Go to Step 9
-  ELSE:
-    Display: "Schema version mismatch (cache: {cache.version}, current: {CLI_VERSION})"
-    Proceed to deployment
-ELSE:
-  Display: "Deploying schemas (first time)..."
-  Proceed to deployment
-```
-
-### Step 2: Deploy Schemas (if needed)
-
-Source: `schemas/` (relative to skill root = `~/.claude/skills/business-analyse/schemas/`)
-Destination: `docs/{app}/business-analyse/schemas/`
-
-```
-docs/{app}/business-analyse/schemas/
-├── feature-schema.json
-├── application-schema.json
-├── sections/
-│   ├── metadata-schema.json
-│   ├── discovery-schema.json
-│   ├── analysis-schema.json
-│   ├── specification-schema.json
-│   ├── validation-schema.json
-│   └── handoff-schema.json
-└── shared/
-    └── common-defs.json
-```
-
-**Total: 9 files to deploy.**
-
-### Step 3: Write Cache File
-
-```json
-{
-  "version": "{CLI_VERSION}",
-  "deployedAt": "{ISO timestamp}",
-  "schemas": [
-    "feature-schema.json",
-    "application-schema.json",
-    "sections/metadata-schema.json",
-    "sections/discovery-schema.json",
-    "sections/analysis-schema.json",
-    "sections/specification-schema.json",
-    "sections/validation-schema.json",
-    "sections/handoff-schema.json",
-    "shared/common-defs.json"
-  ]
-}
-```