@atlashub/smartstack-cli 3.4.0 → 3.4.1

package/package.json

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

package/templates/project/appsettings.json.template

@@ -5,9 +5,18 @@
   "SmartStack": {
     "AutoMigrate": true,
     "FailOnMigrationError": true,
-    "EnableDevSeeding": false
+    "EnableDevSeeding": false,
+    "UseAzureStorage": false,
+    "UseEntraId": false,
+    "EnableSwagger": true,
+    "CorsOrigins": [
+      "http://localhost:5173",
+      "http://localhost:5174",
+      "http://localhost:5175"
+    ]
   },
   "Jwt": {
+    "Secret": "{{JwtSecret}}",
     "Issuer": "{{ProjectName}}",
     "Audience": "{{ProjectName}}",
     "AccessTokenExpirationMinutes": 60,
@@ -33,7 +42,8 @@
     "EnableValidation": true,
     "RefreshTokenExpirationDays": 7,
     "CleanupBatchSize": 100,
-    "MaxConcurrentSessions": 1
+    "MaxConcurrentSessions": 1,
+    "CleanupIntervalMinutes": 5
   },
   "Serilog": {
     "MinimumLevel": {

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

@@ -1,11 +1,17 @@
 ---
 name: business-analyse
 description: Iterative multi-module business analysis with progressive context loading, JSON-first architecture, and interactive HTML deliverables.
-argument-hint: "[-a] [-e] [-q <FEAT-ID> \"question\"] [-r <FEAT-ID> \"change\"] [-m] [-x <json-path>] <feature description>"
+argument-hint: "<feature description>"
 ---
 
 <objective>
-Execute VibeCoding-focused business analysis workflows. This skill produces a single feature.json progressively enriched at each step, published to docs/business/ for web app rendering. Supports 5 use cases: new feature analysis, questions about existing features, feature refactoring, one-shot micro-features, and extraction from interactive HTML documentation.
+Execute business analysis workflows. This skill produces a single feature.json progressively enriched at each step, published to docs/business/ for web app rendering.
+
+**Two use cases:**
+1. **New application** — full analysis workflow for a new business need
+2. **Update** — delta changes on an existing application or module
+
+The skill auto-detects which use case applies by scanning existing features in `docs/business/`.
 
 **Architecture highlights:**
 - Conditional context loading: each step loads only the shared files it needs (~54% context reduction)
@@ -14,92 +20,26 @@ Execute VibeCoding-focused business analysis workflows. This skill produces a si
 </objective>
 
 <quick_start>
-**Five use cases:**
 
 ```bash
-# A. New feature (full workflow)
-/business-analyse Order management module
-
-# B. Question about existing feature
-/business-analyse -q FEAT-001 "What permissions does the manager have?"
-
-# C. Refactoring (delta on existing)
-/business-analyse -r FEAT-001 "Add export PDF functionality"
-
-# D. Micro-feature (one-shot, minimal questions)
-/business-analyse -m Add a status field to orders
-
-# E. Extract from interactive HTML export
-/business-analyse -x ./docs/business/MyApp/ba-export.json
-```
+# New application analysis
+/business-analyse Complete sales management system
 
-**Recommended autonomous workflow:**
-
-```bash
-/business-analyse -a New payment gateway integration
+# The skill auto-detects if an existing application matches
+# and proposes "new" or "update" accordingly
+/business-analyse Add export PDF to orders module
 ```
 
-See `<parameters>` for complete flag list.
 </quick_start>
 
 <parameters>
 
-<flags>
-**Enable flags (turn ON):**
-| Short | Long | Description |
-|-------|------|-------------|
-| `-a` | `--auto` | Autonomous mode: skip confirmations |
-| `-e` | `--economy` | Economy mode: no subagents |
-| `-q` | `--question` | Question mode: query an existing feature (requires FEAT-ID + question) |
-| `-r` | `--refactor` | Refactoring mode: delta changes on existing feature (requires FEAT-ID + change description) |
-| `-m` | `--micro` | Micro-feature mode: minimal questions, direct handoff |
-| `-x` | `--extract` | Extract mode: import from interactive HTML export JSON (requires json-path) |
-| `-app` | `--application` | Application mode: multi-module analysis with module decomposition |
-
-**Disable flags (turn OFF):**
-| Short | Long | Description |
-|-------|------|-------------|
-| `-A` | `--no-auto` | Disable auto mode |
-| `-E` | `--no-economy` | Disable economy mode |
-</flags>
-
-<examples>
-```bash
-# A. New feature analysis (single module - goes through full workflow)
-/business-analyse Order management module
-
-# B. Application analysis (multi-module)
-/business-analyse -app Complete sales management system
-
-# C. Question about existing feature
-/business-analyse -q FEAT-001 "What permissions does the manager have?"
-
-# D. Refactoring (create v1.1)
-/business-analyse -r FEAT-001 "Add export PDF functionality"
-
-# E. Micro-feature (minimal questions)
-/business-analyse -m Add a status field to orders
+No flags. The entire input is the `{feature_description}`.
 
-# F. Extract from interactive HTML export
-/business-analyse -x ./docs/business/MyApp/ba-export.json
-
-# Autonomous application mode
-/business-analyse -app -a New HR management system
-
-# Economy mode (no subagents)
-/business-analyse -e Order management
-```
-</examples>
-
-<parsing_rules>
-**Flag parsing:**
-
-1. Defaults loaded from `steps/step-00-init.md` `<defaults>` section
-2. Command-line flags override defaults
-3. Flags removed from input, remainder becomes `{feature_description}`
-4. Use case determined by flags: question > refactor > extract > micro > new (default)
-5. Feature ID generated as `FEAT-NNN` for new features
-</parsing_rules>
+Step-00 handles all detection automatically:
+- **New vs Update**: scans `docs/business/` for existing applications
+- **Single vs Multi-module**: determined during step-02 decomposition
+- **Language**: detected from config or asked once
 
 </parameters>
 
@@ -131,46 +71,27 @@ docs/business/
 </output_structure>
 
 <resume_workflow>
-**Question mode (`-q {FEAT-ID} "question"`):**
-
-When provided, step-00 will:
-
-1. Locate the feature.json in `docs/business/{app}/{module}/business-analyse/v{X.Y}/`
-2. Load ba-reader agent to answer question from existing feature.json
-3. Return answer and EXIT (no further steps)
+**Update mode (auto-detected):**
 
-**Refactoring mode (`-r {FEAT-ID} "change description"`):**
+When step-00 detects that the description matches an existing application:
 
-When provided, step-00 will:
-
-1. Locate existing feature.json
-2. Create new version folder (v1.1 from v1.0, etc.)
+1. Propose to user: "New application" or "Update {appName}"
+2. If update: locate existing feature.json, create new version (v1.1, etc.)
 3. Load existing feature context
-4. Continue through steps 01-04 with delta focus
-
-**Extract mode (`-x <json-path>`):**
-
-When provided, step-00 will:
-
-1. Validate the JSON file at `<json-path>` exists and is valid JSON
-2. Pass parsed content to step-06-extract.md
-3. Step-06 maps ALL client data to feature.json format (zero information loss)
-4. Post-extraction: choice to enrich, handoff, or terminate
+4. Continue through steps 01-05 with delta focus
 </resume_workflow>
 
 <workflow>
-**Use case routing (step-00):**
-
-1. Parse flags and feature description
-2. If `-q`: Load ba-reader, answer question → EXIT
-3. If `-r`: Load existing feature.json, create new version
-4. If `-x`: Load JSON export, extract to feature.json → step-06
-5. If `-m`: Create minimal feature.json → simplified handoff
-6. If `-app` or auto-detected multi-module: Full application workflow
-7. Default: Single module workflow (same phases, decomposition is trivial)
-
-**Application workflow (multi-module):**
-- **Step 00:** Parse flags, create master feature.json (draft)
+**Step-00 routing (auto-detection):**
+
+1. Read `{feature_description}`
+2. Scan `docs/business/` for existing applications
+3. If match found → ask user: "New application" or "Update {app}" ?
+4. If no match → new application
+5. Create master feature.json and proceed to step-01
+
+**New application workflow:**
+- **Step 00:** Detection, scan existing, create master feature.json (draft)
 - **Step 01:** Cadrage: context, stakeholders, scope, application roles (framed)
 - **Step 02:** Decomposition: modules, dependencies, client checkpoint (decomposed)
 - **Step 03a:** Interactive specification per module: sections, wireframes, entities, BR, use cases
@@ -178,28 +99,14 @@ When provided, step-00 will:
   - Loop: 03a → 03b → 03a (next module) until all specified (specified)
 - **Step 04:** Cross-module consolidation (consolidated)
 - **Step 05a:** Build handoff data: file mapping, BR-to-code, API summary, write to feature.json
-- **Step 05b:** Deploy artifacts: prd.json, progress.txt, HTML, manifest, user choice (handed-off)
-  - User chooses development approach (AskUserQuestion)
-  - **If "Ralph Loop":** Automatic launch → `/ralph-loop` (seamless transition)
-  - **If "Feature Full":** Automatic launch → `/feature-full` (parallel generation)
-  - **If "Terminer":** BA ends, manual development
-
-**Single module workflow (same phases, simplified):**
-- **Step 00:** Parse flags, create master feature.json (draft)
-- **Step 01:** Cadrage: context, stakeholders, scope, roles (framed)
-- **Step 02:** Decomposition: trivial (1 module), quick checkpoint (decomposed)
-- **Step 03a → 03b:** Specification: single iteration (specified)
-- **Step 04:** Consolidation: auto-pass (consolidated)
-- **Step 05a → 05b:** Handoff + deploy (handed-off)
-
-**Micro workflow:**
-- **Step 00:** Create minimal feature.json
-- **Step 05a → 05b:** Direct handoff + deploy (skip 01-04)
-
-**Extract workflow (from interactive HTML):**
-- **Step 00:** Parse `-x` flag, validate JSON file
-- **Step 06:** Map HTML export to feature.json (cadrage, modules, specs, consolidation)
-- Post-extraction choice: enrich with questionnaire (step-01), go to handoff (step-05), or terminate
+- **Step 05b:** Deploy artifacts: prd.json, progress.txt, HTML, manifest (handed-off)
+  - Display completion summary with `/ralph-loop -r` command
+  - User reviews deliverables with stakeholders before launching development
+
+**Update workflow (same phases, delta focus):**
+- **Step 00:** Detection, locate existing feature, create version N+1
+- **Step 01:** Cadrage delta: what changes, impact on existing
+- **Step 02-05:** Same flow as new, with existing context loaded
 </workflow>
 
 <state_variables>
@@ -208,14 +115,12 @@ When provided, step-00 will:
 | Variable                | Type    | Description                                            |
 | ----------------------- | ------- | ------------------------------------------------------ |
 | `{feature_id}`          | string  | Unique identifier (e.g., `FEAT-001`)                   |
-| `{feature_description}` | string  | What to analyze (flags removed)                        |
-| `{use_case}`            | string  | One of: new, question, refactoring, micro, extract     |
+| `{feature_description}` | string  | What to analyze                                        |
+| `{workflow_type}`       | string  | `"new"` or `"update"`                                  |
 | `{version}`             | string  | SemVer (1.0, 1.1, 2.0, etc.)                           |
 | `{application_name}`    | string  | Target application name                                |
 | `{module_name}`         | string  | Target module name                                     |
 | `{context}`             | string  | Always "business" for BA                               |
-| `{auto_mode}`           | boolean | Skip confirmations                                     |
-| `{economy_mode}`        | boolean | No subagents, direct tool usage only                   |
 | `{workflow_mode}`       | string  | "application" or "module"                              |
 | `{docs_dir}`            | string  | `docs/business/{app}/{module}/business-analyse/v{X.Y}/` |
 
@@ -232,7 +137,7 @@ When provided, step-00 will:
 
 | Step | File                              | Model  | Purpose                                              |
 | ---- | --------------------------------- | ------ | ---------------------------------------------------- |
-| 00   | `steps/step-00-init.md`           | Haiku  | Parse flags, route use case, create master feature.json |
+| 00   | `steps/step-00-init.md`           | Haiku  | Auto-detect new/update, scan existing, create master feature.json |
 | 01   | `steps/step-01-cadrage.md`        | Opus   | Framing: context, stakeholders, scope, application roles |
 | 02   | `steps/step-02-decomposition.md`  | Sonnet | Module decomposition, dependency graph, client checkpoint |
 | 03a  | `steps/step-03a-specify.md`       | Opus   | Per-module specification: interactive phase (sections, entities, BR, wireframes, use cases) |
@@ -240,7 +145,6 @@ When provided, step-00 will:
 | 04   | `steps/step-04-consolidation.md`  | Sonnet | Cross-module validation, E2E flows, permissions coherence |
 | 05a  | `steps/step-05a-handoff.md`       | Sonnet | Build handoff data, write to module + master feature.json |
 | 05b  | `steps/step-05b-deploy.md`        | Sonnet | Generate prd.json, progress.txt, deploy HTML, manifest, user choice |
-| 06   | `steps/step-06-extract.md`        | Sonnet | Extract interactive HTML export → feature.json |
 
 </step_files>
 
@@ -251,7 +155,7 @@ Load ONLY relevant categories based on feature type:
 
 | Categorie | Fichier                               | Questions | Quand charger |
 | --------- | ------------------------------------- | --------- | ------------- |
-| 00        | `questionnaire/00-application.md`     | 18        | Si mode application |
+| 00        | `questionnaire/00-application.md`     | 18        | Si workflow_mode = "application" |
 | 01        | `questionnaire/01-context.md`         | 32        | Toujours      |
 | 02        | `questionnaire/02-stakeholders.md`    | 33        | Toujours      |
 | 03        | `questionnaire/03-scope.md`           | 32        | Toujours      |
@@ -299,7 +203,7 @@ Load ONLY relevant categories based on feature type:
 - **Use ba-reader agent** for all JSON reads
 - **Follow next_step directive** at end of each step
 - **Context: business only** - Reject platform/personal/system contexts
-- **Use parallel agents** for exploration (unless economy_mode)
+- **Use parallel agents** for codebase exploration
 </execution_rules>
 
 <success_criteria>
@@ -309,7 +213,7 @@ Load ONLY relevant categories based on feature type:
 - Each module specified iteratively with client validation
 - ASCII/SVG mockups proposed for each module's sections
 - Cross-module consolidation passed (step-04)
-- Development handoff ready for `/ralph-loop -r` or `/feature-full`
+- Development handoff ready for `/ralph-loop -r`
 - Ralph Loop prd.json generated (per module or consolidated)
 - All outputs renderable by SmartStack app viewer at `/docs/business/{app}/`
 </success_criteria>

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

@@ -232,7 +232,7 @@ resume_workflow(feat_id):
   1. ba-reader.findFeature(feat_id) -> latest feature.json
   2. Read feature.json.metadata.steps -> find last completed step
   3. Load next step file
-  4. If not found in docs/: fallback to .business-analyse/ (legacy)
+  4. If not found: offer to create fresh feature.json
 ```
 
 ---