@atlashub/smartstack-cli 1.34.0 → 1.36.0

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

@@ -1,13 +1,12 @@
 ---
 name: step-00-init
 description: Initialize Business Analysis - Parse flags, create structure, setup state
-model: haiku
 next_step: steps/step-01-discover.md
 ---
 
-<objective>
+## YOUR TASK:
+
 Parse command-line flags, create feature directory structure, and initialize state variables for the Business Analysis workflow.
-</objective>
 
 <defaults>
 ```yaml
@@ -18,7 +17,7 @@ context: business    # BA is RESTRICTED to business context
 ```
 </defaults>
 
-## EXECUTION SEQUENCE
+## EXECUTION SEQUENCE:
 
 ### 1. Parse Flags and Input
 
@@ -57,9 +56,10 @@ After removing flags, remaining text becomes `{feature_description}`
 
 If `{resume_task}` is set:
 1. Search for matching feature in `.business-analyse/`
-   ```bash
-   find .business-analyse -type d -name "*{resume_task}*" 2>/dev/null | head -1
-   ```
+   Use Glob tool to search for matching feature:
+   - Pattern: `.business-analyse/**/features/*{resume_task}*`
+   - If match found: read 00-context.md from that directory
+   - If no match: list available features for user selection
 2. If found: Read `00-context.md` to restore state variables
 3. Find last completed step (look for "Status: Complete" in progress table)
 4. Load next incomplete step
@@ -72,6 +72,30 @@ If NOT found:
 
 ---
 
+### 2b. Verify MCP Availability
+
+**Check SmartStack MCP (non-blocking):**
+
+Call `mcp__smartstack__validate_conventions` with minimal parameters to verify connectivity.
+
+| MCP Status | Behavior |
+|------------|----------|
+| Available | Full mode - use MCP tools in all steps |
+| Unavailable | Degraded mode - warn user, skip MCP calls, use manual exploration |
+
+Store: `{mcp_available}` = true/false
+
+**Display if unavailable:**
+```
+Warning: SmartStack MCP unavailable. Running in degraded mode.
+Run `smartstack check-mcp` to diagnose.
+BA will continue without MCP validation.
+```
+
+**Add to state variables:** `{mcp_available}` persisted in 00-context.md
+
+---
+
 ### 3. Interactive Mode (if -i flag)
 
 If `{interactive_mode}` = true:
@@ -151,6 +175,36 @@ Store in:
 
 ---
 
+### 5b. Select Communication Language
+
+```json
+{
+  "questions": [
+    {
+      "question": "Dans quelle langue souhaitez-vous communiquer ?",
+      "header": "Langue",
+      "options": [
+        {"label": "Français (Recommandé)", "description": "Toutes les interactions et documents en français"},
+        {"label": "English", "description": "All interactions and documents in English"},
+        {"label": "Italiano", "description": "Tutte le interazioni e i documenti in italiano"},
+        {"label": "Deutsch", "description": "Alle Interaktionen und Dokumente auf Deutsch"}
+      ],
+      "multiSelect": false
+    }
+  ]
+}
+```
+
+Map selection to `{language}`:
+- "Français" → `fr`
+- "English" → `en`
+- "Italiano" → `it`
+- "Deutsch" → `de`
+
+**Default:** `fr` (si non spécifié)
+
+---
+
 ### 6. Generate Feature ID
 
 ```bash
@@ -233,8 +287,26 @@ Create initial context file with state variables:
 | application_name | {{application_name}} |
 | module_name | {{module_name}} |
 | context | business |
+| language | {{language}} |
+| mcp_available | {{mcp_available}} |
 | permission_base | business.{{application_name}}.{{module_name}} |
 
+## Discovery Metadata (updated by step-01)
+
+| Variable | Value |
+|----------|-------|
+| feature_type | (TBD in step-01) |
+| mcp_available | {{mcp_available}} |
+| categories_loaded | (TBD in step-01) |
+
+## Risk Register (updated by step-01)
+
+(TBD in step-01)
+
+## Codebase Context Summary (updated by step-01)
+
+(TBD in step-01)
+
 ## Acceptance Criteria
 
 To be defined in step-01-discover.
@@ -257,6 +329,7 @@ Update `.business-analyse/config.json`:
   "project": "{ProjectName}",
   "lastFeatureId": {NEW_ID},
   "context": "business",
+  "language": "{language}",
   "standards": ["BABOK-v3", "IEEE-830"],
   "contact": "support@atlshub.ch"
 }
@@ -267,14 +340,16 @@ Update `.business-analyse/config.json`:
 ### 10. Display Summary and Load Next Step
 
 **Display:**
-```
-INIT - {{feature_id}}
-├── Application: business/{{application_name}}
-├── Module: {{module_name}}
-├── Output: {{output_dir}}
-├── Mode: {{auto_mode ? "Autonomous" : "Interactive"}}
-└── Next: step-01-discover (ULTRATHINK elicitation)
-```
+
+| Field | Value |
+|-------|-------|
+| Step | INIT |
+| Feature | {{feature_id}} |
+| Application | business/{{application_name}} |
+| Module | {{module_name}} |
+| Output | {{output_dir}} |
+| Mode | {{auto_mode ? "Autonomous" : "Interactive"}} |
+| Next | step-01-discover (ULTRATHINK elicitation) |
 
 **Load next step:**
 ```
@@ -283,7 +358,7 @@ Read and execute: steps/step-01-discover.md
 
 ---
 
-## OUTPUT
+## OUTPUT FORMAT:
 
 This step produces:
 - `.business-analyse/config.json` (updated)
@@ -291,3 +366,22 @@ This step produces:
 - `{output_dir}/tracking/` directories (created)
 
 State variables persisted for next steps.
+
+## ERROR HANDLING:
+
+**If resume feature not found:**
+1. List available features in `.business-analyse/`
+2. Ask user to select or start new analysis
+
+**If config.json missing or corrupted:**
+1. Create fresh config.json with defaults
+2. Set lastFeatureId to 0
+3. Warn user: "Config reset to defaults"
+
+**If directory creation fails:**
+1. Check write permissions
+2. Suggest running with elevated privileges
+
+## NEXT STEP:
+
+After completion, proceed to `steps/step-01-discover.md`