@atlashub/smartstack-cli 4.20.0 → 4.21.0

package/templates/skills/{business-analyse/steps/step-06-review.md → ba-review/steps/step-01-apply.md}

@@ -1,12 +1,12 @@
 ---
-name: step-06-review
+name: step-01-apply
 description: Apply review corrections from ba-review.json, create new version, regenerate all artifacts
 model: opus
 ---
 
-> **Context files:** `_shared.md`, `references/review-data-mapping.md`, `references/html-data-mapping.md`
+> **Context files:** `references/review-data-mapping.md`
 
-# Step 06: Apply Review Corrections
+# Step 01: Apply Review Corrections
 
 Apply corrections exported from the interactive HTML review (`ba-review.json`) to create a new version of the business analysis with all downstream artifacts regenerated.
 
@@ -182,23 +182,12 @@ Create review.json with review_section and update hash in index.json
 
 ## Step 8: Regenerate Interactive HTML
 
-> **Reference:** `references/html-data-mapping.md` for FEATURE_DATA and EMBEDDED_ARTIFACTS mapping
+Delegate HTML generation to `/ba-generate-html` skill:
 
 ```
-1. Read ba-interactive.html template from skill templates
-2. Build FEATURE_DATA from NEW version:
-   - Read index.json for metadata
-   - Read cadrage.json for cadrage section
-   - Read entities.json, rules.json, usecases.json, etc.
-   (follow exact mapping from html-data-mapping.md)
-3. Build EMBEDDED_ARTIFACTS from thematic files
-   (wireframes, e2eFlows, dependencyGraph)
-4. Replace placeholders:
-   - {{FEATURE_DATA}} → serialized FEATURE_DATA JSON
-   - {{EMBEDDED_ARTIFACTS}} → serialized EMBEDDED_ARTIFACTS JSON
-   - {{APPLICATION_NAME}} → application_name
-   - {{APPLICATION_ID}} → feature_id
-5. Write to new version directory: {new_version_dir}/ba-interactive.html
+1. Load skill: /ba-generate-html with feature_id
+2. The skill handles: collect → build → render → verify
+3. Output: {new_version_dir}/ba-interactive.html
 ```
 
 ## Step 9: Update Manifest

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

@@ -9,7 +9,7 @@ user_invocable: true
 
 ## Architecture
 
-**2 phases, 7 steps** — "Macro vers Specification"
+**2 phases, 5 steps** — "Macro vers Specification"
 
 ### Phase 1 — Macro (Identification + Challenge)
 
@@ -19,29 +19,28 @@ user_invocable: true
 | 01 | `step-01-cadrage.md` | Opus | Context, stakeholders, scope, risks. ~40 core questions |
 | 02 | `step-02-structure.md` | Opus | Identify App > Module > Section > Resource hierarchy, CHALLENGE each element |
 
-### Phase 2 — Specification (Deep dive + Client enrichment)
+### Phase 2 — Specification (Deep dive + Consolidation)
 
 | Step | File | Model | Role |
 |------|------|-------|------|
 | 03 | `step-03-specify.md` | Opus | Deep dive per module: entities, BRs, UCs, permissions, screens. Sequential internal loop |
 | 04 | `step-04-consolidate.md` | Opus | Cross-module validation: data model, permission coherence, E2E flows |
-| 05 | `step-05-deploy.md` | Sonnet | Deploy interactive HTML document |
-| 06 | `step-06-review.md` | Opus | Apply client corrections from ba-review.json exported from HTML |
 
-### IA + Client Loop
+### Post-BA Workflow
 ```
-Phase 1 (steps 00-02) → Phase 2 (steps 03-05) → Client reviews HTML
-                                                       ↓
-                                          Client comments/enriches
-                                                       ↓
-                                          Export ba-review.json
-                                                       ↓
-                                          Step 06 → re-deploy HTML
-                                                       ↓
-                                          /derive-prd → /ralph-loop
+Phase 1 (steps 00-02) → Phase 2 (steps 03-04) → /ba-generate-html → Client reviews HTML
+                                                                            ↓
+                                                               Client comments/enriches
+                                                                            ↓
+                                                               Export ba-review.json
+                                                                            ↓
+                                                               /ba-review → /ba-generate-html
+                                                                            ↓
+                                                               /derive-prd → /ralph-loop
 ```
 
-> **PRD generation:** Handoff data and PRD files are generated by the `/derive-prd` skill, not by step-05.
+> After step-04, invoke `/ba-generate-html` to generate the HTML, then `/ba-review` for the client correction cycle.
+> **PRD generation:** Handoff data and PRD files are generated by the `/derive-prd` skill.
 
 ## JSON Architecture — Granular files + Index
 
@@ -83,7 +82,6 @@ docs/
 Each step loads only the files it needs via `index.json`:
 - Step 03 (specify): loads `index.json` + `entities.json` for current module only
 - Step 04 (consolidate): loads all `index.json` files for summary counts
-- Step 05 (deploy): assembles all files into unified FEATURE_DATA for HTML
 
 ## Workflow Modes
 
@@ -91,7 +89,6 @@ Each step loads only the files it needs via `index.json`:
 |------|-----------|----------|
 | `new` | No existing index.json | Full analysis from step 00 |
 | `update` | Existing index.json found | Delta analysis, skip completed sections |
-| `review` | ba-review.json provided | Apply corrections (step 06 only) |
 
 ## Context Loading Rules
 
@@ -104,8 +101,6 @@ Each step loads ONLY what it needs:
 | 02 | `_shared.md`, `step-02-structure.md` | cadrage.json from step 01 |
 | 03 | `_shared.md`, `step-03-specify.md` | current module's index.json + relevant files |
 | 04 | `_shared.md`, `step-04-consolidate.md` | all module index.json files |
-| 05 | `_shared.md`, `step-05-deploy.md` | all JSON files for HTML assembly |
-| 06 | `_shared.md`, `step-06-review.md` | ba-review.json + current feature files |
 
 ## Agents
 
@@ -116,27 +111,7 @@ Each step loads ONLY what it needs:
 
 ## HTML Output
 
-**Single unified HTML** document (`ba-interactive.html`) with:
-- Multi-app navigation (4 levels: App > Module > Section > Resource)
-- Inline editing (UC, BR, entities, sections/resources)
-- HTML mockups from `screens[]` specs (SmartTable, SmartForm, SmartCard, SmartKanban, SmartDashboard)
-- Wireframe fallback from EMBEDDED_ARTIFACTS
-- Comment system with review panel
-- Export: ba-review.json for step 06 loop
-
-### FEATURE_DATA structure
-
-```javascript
-{
-  metadata: { projectName, version, ... },
-  applications: [{ code, name, icon, route, modules: [...] }],
-  cadrage: { context, scope, stakeholders, risks, criteria },
-  modules: [{ code, applicationCode, name, ... }],
-  moduleSpecs: { [code]: { useCases, businessRules, entities, permissions, screens, sections, resources } },
-  consolidation: { interactions, e2eFlows },
-  comments: []
-}
-```
+HTML generation is handled by the `/ba-generate-html` skill. After step-04, invoke `/ba-generate-html` to produce the interactive HTML document. For client review corrections, use `/ba-review`.
 
 ## Step Execution
 
@@ -164,31 +139,21 @@ STEP 03 (specify) — SEQUENTIAL MODULE LOOP
     → Output: entities.json, rules.json, usecases.json, permissions.json, screens.json
   → No team mode — sequential ensures 100% context per module
 
-STEP 04 (consolidate)
+STEP 04 (consolidate) — FINAL BA STEP
   → Load: _shared.md, step-04-consolidate.md, all index.json
   → Execute: Data model validation, permission coherence, E2E flows
   → Output: validation.json, consolidated data
-
-STEP 05 (deploy)
-  → Load: _shared.md, step-05-deploy.md, all JSON files
-  → Execute: Assemble FEATURE_DATA, generate HTML
-  → Output: ba-interactive.html (single file)
-
-STEP 06 (review) — CLIENT LOOP ENTRY
-  → Load: _shared.md, step-06-review.md, ba-review.json
-  → Execute: Apply corrections, create new version
-  → Output: Updated JSON files, regenerated HTML
+  → Next: invoke /ba-generate-html, then /ba-review for client cycle
 ```
 
 ## References
 
 | File | Content |
 |------|---------|
-| `references/html-data-mapping.md` | FEATURE_DATA mapping for HTML generation |
+| `/ba-generate-html` skill | HTML generation (FEATURE_DATA mapping, build, render, verify) |
+| `/ba-review` skill | Apply client corrections from ba-review.json |
 | `references/naming-conventions.md` | SmartStack naming rules |
-| `references/wireframe-svg-style-guide.md` | SVG wireframe rendering guide |
 | `references/validation-checklist.md` | Validation criteria checklist |
-| `references/deploy-modes.md` | Deployment configuration |
 | `references/acceptance-criteria.md` | Acceptance criteria patterns |
 
 > **Cross-reference:** Handoff data, PRD generation, file templates, and BR-to-code mappings are in the `/derive-prd` skill.

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

@@ -68,16 +68,16 @@ Steps load only the files they need:
 |------|---------|-------------|
 | `new` | No existing index.json | Full analysis from scratch |
 | `update` | Existing index.json found | Delta analysis (add modules, update specs) |
-| `review` | ba-review.json provided | Apply client corrections from HTML export |
 
 ### Workflow detection
 
 ```
-1. Check for ba-review.json in project root → mode = "review"
-2. Check for existing docs/**/index.json → mode = "update"
-3. Otherwise → mode = "new"
+1. Check for existing docs/**/index.json → mode = "update"
+2. Otherwise → mode = "new"
 ```
 
+> **Note:** Review mode (`ba-review.json`) is handled by the `/ba-review` skill.
+
 ## Navigation Hierarchy
 
 Maps to SmartStack DB tables:
@@ -138,24 +138,19 @@ draft → identified → specified → validated → reviewed
 | identified | Step 02 | Hierarchy identified (App > Module > Section > Resource) |
 | specified | Step 03 | Module fully specified (entities, UCs, BRs, permissions, screens) |
 | validated | Step 04 | Cross-module validation passed |
-| reviewed | Step 06 | Client review applied |
+| reviewed | `/ba-review` | Client review applied |
 
 ## Handoff & PRD Generation
 
-Handoff data and PRD files are generated by the `/derive-prd` skill, not by step-05. Step-05 only deploys the interactive HTML document. The workflow is:
+Handoff data and PRD files are generated by the `/derive-prd` skill. The workflow is:
 
 ```
-/business-analyse (steps 00-05) → /derive-prd → /ralph-loop
+/business-analyse (steps 00-04) → /ba-generate-html → /ba-review (if needed) → /derive-prd → /ralph-loop
 ```
 
-## HTML Integration
-
-Single unified HTML (`ba-interactive.html`) generated in step 05:
-
-- **Single-app**: `docs/{app}/business-analyse/v{X.Y}/ba-interactive.html`
-- **Multi-app**: `docs/business-analyse/v{X.Y}/ba-interactive.html`
+## HTML Generation
 
-The HTML embeds all data as `FEATURE_DATA` JavaScript object. See `references/html-data-mapping.md` for the complete mapping.
+For HTML generation, use the `/ba-generate-html` skill after step-04 consolidation. For client review corrections, use `/ba-review`.
 
 ## Resume Protocol
 

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

@@ -1,7 +1,7 @@
 # React Components - Business Analyse Viewer
 
 > **Usage:** React component that renders index.json directly
-> **Loaded in:** step-05-deploy.md
+> **Loaded in:** /ba-generate-html
 > **Data source (module):** `docs/{app}/{module}/business-analyse/v{X.Y}/index.json`
 > **Data source (application):** `docs/{app}/business-analyse/v{X.Y}/index.json`
 > **Related:** `react/application-viewer.md` for application-level view

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

@@ -1,7 +1,7 @@
 # TypeScript Schema - Feature JSON Types
 
 > **Usage:** TypeScript interfaces aligned with index.json and application-schema.json
-> **Loaded in:** step-05-deploy.md (for web app rendering)
+> **Loaded in:** /ba-generate-html (for web app rendering)
 > **Source (module):** `docs/{app}/{module}/business-analyse/v{X.Y}/index.json`
 > **Source (application):** `docs/{app}/business-analyse/v{X.Y}/index.json`
 

package/templates/skills/business-analyse/references/acceptance-criteria.md

@@ -1,6 +1,6 @@
 # Module Acceptance Criteria (Shared Reference)
 
-> **Loaded by:** step-03-specify (post-check), step-05-deploy (pre-handoff gate), ralph-loop step-01-task (input validation)
+> **Loaded by:** step-03-specify (post-check), ralph-loop step-01-task (input validation)
 > **Purpose:** Define measurable, bash-verifiable acceptance criteria that a module MUST pass before being marked "specified".
 > **Key principle:** These checks read the REAL JSON files on disk — NOT in-memory data the model "thinks" it wrote.
 
@@ -137,12 +137,7 @@ console.log('PASS: All acceptance criteria met (AC-01 to AC-17)');
 After writing module JSON files, run the bash script above.
 IF FAIL → re-execute section 11 write with corrected data → re-run until PASS.
 
-### 2. step-05-deploy.md (pre-handoff gate)
-
-Before writing handoff for each module, run the bash script on the module index.json.
-IF FAIL → STOP handoff for this module, report which criteria failed.
-
-### 3. ralph-loop step-01-task.md (input validation)
+### 2. ralph-loop step-01-task.md (input validation)
 
 At PRD load time, run the bash script on each module index.json.
 IF FAIL → BLOCKING: "Module {name} does not meet acceptance criteria — run /business-analyse to fix".

package/templates/skills/business-analyse/references/detection-strategies.md

@@ -63,7 +63,7 @@ function detectReviewMode(feature_description) {
     reviewJsonPath: reviewFilePath,
     applicationName: latestApp.metadata.application,
     docsDir: versionDir,
-    nextStep: 'step-06-review.md'
+    nextStep: 'redirect-to-ba-review'
   };
 }
 ```
@@ -73,7 +73,7 @@ function detectReviewMode(feature_description) {
 | Condition | Action |
 |-----------|--------|
 | `{feature_description}` starts with `-review` | Activate review mode detection |
-| ba-review.json found | Skip to step-06-review.md |
+| ba-review.json found | Redirect user to `/ba-review` skill |
 | ba-review.json NOT found | Display error with fix instructions, STOP |
 | No applications exist | Display error, STOP |
 
@@ -416,7 +416,7 @@ interface DetectionResult {
 **Test Case 4: Review Mode**
 - Input: `"-review"`
 - Existing: `HumanResources` with ba-review.json present
-- Expected: Load ba-review.json, skip to step-06-review.md
+- Expected: Redirect user to `/ba-review` skill
 
 **Test Case 5: Review Mode - File Missing**
 - Input: `"-review"`

package/templates/skills/business-analyse/references/naming-conventions.md

@@ -75,7 +75,7 @@ Route = ToKebabCase($"/{appCode}/{moduleCode}")
 
 ### JavaScript (BA Handoff Generation)
 
-**Location:** Used in step-05-deploy.md when building seedDataCore
+**Location:** Used in /ba-generate-html when building seedDataCore
 
 **Usage:**
 ```javascript
@@ -240,4 +240,4 @@ src/API/Controllers/HumanResources/TimeManagementController.cs
 - **Template:** `templates/skills/ralph-loop/references/core-seed-data.md`
 - **Validation:** `src/mcp/tools/validate-frontend-routes.ts`
 - **POST-CHECK:** `templates/skills/ralph-loop/steps/step-02-execute.md` (section 5)
-- **Handoff:** `templates/skills/business-analyse/steps/step-05-deploy.md` (handoff section)
+- **Handoff:** `/derive-prd` skill (handoff section)

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

@@ -264,96 +264,7 @@ DEVELOPMENT CANNOT PROCEED WITH CIRCULAR DEPENDENCIES
 
 ---
 
-## Phase 3: Ralph Readiness Validation (Step-05)
-
-> **When:** After artifacts deployed (step-05), before launching /ralph-loop
-> **Blocking:** YES - Development blocked if critical checks fail
-
-### Purpose
-
-Final gate to ensure business analysis is 100% ready for implementation. Catches issues before ralph-loop starts, preventing failed development attempts.
-
-### Checks (9 categories)
-
-| # | Category | Checks | Blocking | Purpose |
-|---|----------|--------|----------|---------|
-| 1 | Module Status | All modules status = "handed-off" | YES | Incomplete modules break ralph-loop |
-| 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 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 |
-| 9 | Final Readiness | Aggregate all checks, calculate score | YES if <100% | All critical checks must pass |
-
-### Readiness Score
-
-```
-Readiness Score = (passed critical checks / total critical checks) × 100%
-```
-
-**Thresholds:**
-- **100%** → READY FOR DEVELOPMENT ✓
-- **<100%** → NOT READY - FIX REQUIRED ✗
-
-### Example Output
-
-**Ready:**
-
-```
-═══════════════════════════════════════════════════════════════
-  RALPH READINESS CHECK - COMPLETE
-═══════════════════════════════════════════════════════════════
-
-Validation Summary:
-  ✓ Module status validation: PASS (5/5 modules)
-  ✓ PRD files validation: PASS (5/5 files)
-  ✓ Dependency graph validation: PASS (4 edges)
-  ✓ Cross-module references validation: PASS (4 references)
-  ✓ Handoff completeness check: PASS (5/5 modules)
-  ⚠ i18n keys validation: WARNING (1 missing translation)
-  ✓ Master feature validation: PASS
-  ✓ Progress tracker validation: PASS
-
-Readiness Score: 100% (7/7 critical checks passed, 1 warning)
-
-Status: READY FOR DEVELOPMENT ✓
-
-Next Steps:
-  1. Address warnings (optional, recommended)
-  2. Review progress tracker: .ralph/progress.txt
-  3. Launch development: /ralph-loop
-     (Use /ralph-loop -r ONLY to resume an interrupted loop)
-═══════════════════════════════════════════════════════════════
-```
-
-**Not Ready:**
-
-```
-═══════════════════════════════════════════════════════════════
-  RALPH READINESS CHECK - FAILED
-═══════════════════════════════════════════════════════════════
-
-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-05-deploy.md for Reporting module
-
-  ✗ PRD files validation: FAIL (1/5 files invalid)
-    - prd-Reporting.json has wrong structure (filesToCreate at root level)
-    - Fix: Re-run ss derive-prd --feature {path} --output .ralph/prd-Reporting.json
-
-Required Actions:
-  1. Fix all critical issues listed above
-  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
-═══════════════════════════════════════════════════════════════
-```
+> **Note:** Ralph Readiness Validation (PRD files, handoff completeness, etc.) is handled by the `/derive-prd` skill.
 
 ---
 
@@ -374,7 +285,6 @@ DO NOT PROCEED TO /RALPH-LOOP UNTIL ALL CRITICAL CHECKS PASS
 **Checkpoints:**
 - Step-03d: Module completeness (before marking "specified")
 - Step-04: Cross-module coherence (before marking "consolidated")
-- Step-05c: Development readiness (before /ralph-loop)
 
 ### 3. Auto-Fix vs. Manual Fix
 
@@ -486,25 +396,6 @@ WHERE: Return to step-03-specify.md for TimeTracking module
 
 ---
 
-### Issue: Ralph Readiness Check Fails
-
-**Symptoms:**
-- Step-05c reports readiness score < 100%
-- Critical checks failed
-
-**Diagnosis:**
-1. Review failed checks in summary
-2. Identify missing/invalid artifacts
-
-**Fix:**
-- **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-05-deploy, complete handoff section
-- **Cross-module refs broken:** Return to step-04-consolidate, fix references
-- Re-run step-05-deploy after fixes
-
----
-
 ## Metrics & Success Criteria
 
 ### Module Specification Checklist
@@ -525,17 +416,7 @@ WHERE: Return to step-03-specify.md for TimeTracking module
 
 **Success:**
 - Application marked as "consolidated"
-- Ready for handoff
-
-### Ralph Readiness (Step-05)
-
-**Target:**
-- 100% critical checks passed
-- Warnings addressed or documented
-
-**Success:**
-- Application ready for /ralph-loop
-- Development can proceed with full confidence
+- Ready for `/ba-generate-html` and `/derive-prd`
 
 ---
 

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

@@ -147,18 +147,17 @@ const checklist = {
   },
 
   wireframeSchemaCompliance: {
-    check: "All wireframes have required fields: screen, section, mockupFormat, elements[], componentMapping[], layout (object), permissionsRequired[]",
+    check: "All wireframes have required fields: screen, section, mockupFormat, elements[], layout (object), permissionsRequired[]",
     status: (specification.uiWireframes || specification.wireframes || []).every(wf =>
       (wf.screen || wf.title) && wf.section && (wf.mockupFormat || wf.mockup || wf.ascii) &&
       Array.isArray(wf.elements) && wf.elements.length > 0 &&
-      Array.isArray(wf.componentMapping) && wf.componentMapping.length > 0 &&
       typeof wf.layout === 'object' && wf.layout !== null &&
       Array.isArray(wf.permissionsRequired)
     ) ? "PASS" : "FAIL",
     blocking: true,
-    details: "Wireframes missing metadata render as empty frames in HTML documentation. " +
+    details: "Wireframes missing metadata render as empty frames. " +
              "Check: screen (not name/id/title), section, mockupFormat, elements[] non-empty, " +
-             "componentMapping[] as array of {wireframeElement, reactComponent}, layout as object (not string). " +
+             "layout as object (not string). " +
              "Also see references/acceptance-criteria.md for bash-verifiable checks."
   },
 

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

@@ -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-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",
+  "$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). HTML generation → /ba-generate-html skill. Review corrections → /ba-review skill. Handoff → /derive-prd skill",
 
   "$defs": {
     "stepStatus": { "$ref": "shared/common-defs.json#/$defs/stepStatus" },

package/templates/skills/business-analyse/steps/step-00-init.md

@@ -101,7 +101,7 @@ Execute workflow detection algorithm:
    - Continue to application name determination.
 
 **Key decision points:**
-1. IF review mode → load ba-review.json, skip to step-06-review.md
+1. IF review mode → inform user to use `/ba-review` skill instead
 2. IF no existing apps → workflow_type = "new"
 3. IF existing apps → analyze similarity → prompt user
 
@@ -496,13 +496,9 @@ If initialization was interrupted:
 
    **Status-based resume routing (check in this order):**
 
-   - If status = `"handed-off"`:
-     → Resume at `step-06-review.md`
-     → Display: "Handoff complete — proceeding to review..."
-
-   - If status = `"consolidated"`:
-     → Resume directly at `step-05-deploy.md`
-     → Display: "Resuming from consolidation — proceeding to deployment..."
+   - If status = `"handed-off"` or `"consolidated"`:
+     → Display: "BA workflow complete. Use /ba-generate-html to generate HTML, /ba-review for corrections."
+     → STOP
 
    - If status = `"specified"` AND `metadata.workflow.allModulesSpecified === true`:
      → Resume at `step-04-consolidate.md`
@@ -531,4 +527,5 @@ If a project-level index.json is found (scope = "project"):
      → All applications specified → Resume at `step-04-consolidate.md`
 
    - If status = `"consolidated"`:
-     → Resume at `step-05-deploy.md`
+     → Display: "BA workflow complete. Use /ba-generate-html to generate HTML."
+     → STOP

package/templates/skills/business-analyse/steps/step-04-consolidate.md

@@ -2,7 +2,7 @@
 name: step-04-consolidate
 description: Cross-module validation - data model, permissions, E2E flows, approval
 model: opus
-next_step: steps/step-05-deploy.md
+next_step: none
 ---
 
 > **Context files:** `_shared.md`
@@ -34,8 +34,8 @@ ba-reader.readApplicationContext({feature_id})
 → cadrage.applicationRoles, modules[], dependencyGraph
 
 IF status already "consolidated":
-  Display: "Consolidation already completed. Loading step-05-deploy."
-  Load: steps/step-05-deploy.md
+  Display: "Consolidation already completed. BA workflow finished."
+  Display: "Next: invoke /ba-generate-html then /ba-review for client cycle."
   STOP
 ```
 
@@ -443,7 +443,11 @@ Display final summary:
 ✓ All validations passed
 ✓ Client approval obtained
 ✓ Status: consolidated
-→ Proceeding to step-05-deploy.md
+
+BA workflow complete. Next steps:
+→ Invoke /ba-generate-html to generate the interactive HTML
+→ Invoke /ba-review to apply client corrections
+→ Invoke /derive-prd → /ralph-loop for implementation
 ```
 
 ---
@@ -473,6 +477,9 @@ Display final summary:
 
 ---
 
-## NEXT STEP
+## NEXT STEPS
 
-Load: `./step-05-deploy.md`
+BA workflow ends here. After consolidation:
+1. Invoke `/ba-generate-html` to generate the interactive HTML document
+2. Invoke `/ba-review` to apply client corrections (if needed)
+3. Invoke `/derive-prd` then `/ralph-loop` for implementation

package/templates/skills/business-analyse/templates/tpl-handoff.md

@@ -1,6 +1,6 @@
 # Template Development Handoff
 
-> **Usage:** Template for step-05-deploy.md
+> **Usage:** Template for /derive-prd
 > **Data source:** index.json (sections: metadata, analysis, specification, handoff)
 
 ---

package/templates/skills/business-analyse/templates/tpl-launch-displays.md

@@ -1,6 +1,6 @@
 # Skill Launch Display Templates (templates/tpl-launch-displays.md)
 
-> **Used by:** step-05-deploy (Completion Summary)
+> **Used by:** /ba-generate-html (Completion Summary)
 > **Purpose:** User-facing display templates for BA completion
 > **Note:** No emojis - uses text markers per Claude Code conventions