@atlashub/smartstack-cli 1.13.2 → 1.14.1

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

@@ -0,0 +1,223 @@
+---
+name: business-analyse
+description: Business Analysis - Complete business analysis workflow (BABOK/IEEE 830) with progressive step loading and context refresh.
+argument-hint: "[-a] [-s] [-e] [-r <task-id>] <feature description>"
+---
+
+<objective>
+Execute systematic business analysis workflows following BABOK v3 and IEEE 830 standards.
+This skill uses progressive step loading to minimize context usage and maintain fresh context throughout the workflow.
+</objective>
+
+<quick_start>
+**Basic usage:**
+
+```bash
+/business-analyse Module de gestion des clients
+```
+
+**Recommended workflow (autonomous with save):**
+
+```bash
+/business-analyse -a -s Gestion des commandes avec workflow validation
+```
+
+**Resume a previous analysis:**
+
+```bash
+/business-analyse -r FEAT-001
+```
+
+**Flags:**
+
+- `-a` (auto): Skip confirmations
+- `-s` (save): Save outputs to `.business-analyse/`
+- `-e` (economy): No subagents, direct tool usage
+- `-r` (resume): Resume from a previous FEAT-ID
+
+See `<parameters>` for complete flag list.
+</quick_start>
+
+<parameters>
+
+<flags>
+**Enable flags (turn ON):**
+| Short | Long | Description |
+|-------|------|-------------|
+| `-a` | `--auto` | Autonomous mode: skip confirmations, auto-approve |
+| `-s` | `--save` | Save mode: output to `.business-analyse/` (default: true) |
+| `-e` | `--economy` | Economy mode: no subagents, save tokens |
+| `-r` | `--resume` | Resume mode: continue from a previous FEAT-ID |
+| `-i` | `--interactive` | Interactive mode: configure flags via AskUserQuestion |
+
+**Disable flags (turn OFF):**
+| Short | Long | Description |
+|-------|------|-------------|
+| `-A` | `--no-auto` | Disable auto mode |
+| `-S` | `--no-save` | Disable save mode |
+| `-E` | `--no-economy` | Disable economy mode |
+</flags>
+
+<examples>
+```bash
+# Basic usage
+/business-analyse Module gestion clients
+
+# Autonomous mode (no confirmations)
+/business-analyse -a Module gestion clients
+
+# Economy mode (save tokens)
+/business-analyse -e Module gestion clients
+
+# Resume a previous feature
+/business-analyse -r FEAT-001
+/business-analyse -r 001  # Partial match supported
+
+# Combined flags
+/business-analyse -a -e Module gestion clients
+```
+</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. Feature ID generated as `FEAT-NNN`
+</parsing_rules>
+
+</parameters>
+
+<output_structure>
+**When `{save_mode}` = true (default):**
+
+All outputs saved to PROJECT directory:
+```
+.business-analyse/business/{app}/modules/{module}/features/{FEAT-NNN}/
+├── 00-context.md              # Params, user request, timestamp, progress
+├── 1-discovery.md             # Phase 1: Discovery findings
+├── 2-business-requirements.md # Phase 2: BRD
+├── 3-functional-specification.md # Phase 3: FRD
+├── validation.json            # Phase 4: Validation gate
+├── 4-development-handoff.md   # Phase 5: Dev prompt
+└── tracking/
+    ├── changes/
+    ├── bugs/
+    └── hotfixes/
+```
+</output_structure>
+
+<resume_workflow>
+**Resume mode (`-r {FEAT-ID}`):**
+
+When provided, step-00 will:
+
+1. Locate the feature folder in `.business-analyse/`
+2. Read `00-context.md` to restore state
+3. Find the last completed step
+4. Continue from the next step
+</resume_workflow>
+
+<workflow>
+**Standard flow:**
+1. Parse flags and feature description
+2. If `-r`: Execute resume workflow
+3. Create output folder and 00-context.md
+4. Load step-01-discover.md -> elicitation with ULTRATHINK
+5. Load step-02-analyse.md -> BRD + business rules
+6. Load step-03-specify.md -> FRD + use cases
+7. Load step-04-validate.md -> validation gate
+8. Load step-05-handoff.md -> development prompt
+9. Load step-06-doc-html.md -> React documentation (optional)
+</workflow>
+
+<state_variables>
+**Persist throughout all steps:**
+
+| Variable                | Type    | Description                                            |
+| ----------------------- | ------- | ------------------------------------------------------ |
+| `{feature_description}` | string  | What to analyze (flags removed)                        |
+| `{feature_id}`          | string  | Unique identifier (e.g., `FEAT-001`)                   |
+| `{application_name}`    | string  | Target application name                                |
+| `{module_name}`         | string  | Target module name                                     |
+| `{context}`             | string  | Always "business" for BA                               |
+| `{auto_mode}`           | boolean | Skip confirmations                                     |
+| `{save_mode}`           | boolean | Save outputs (default: true)                           |
+| `{economy_mode}`        | boolean | No subagents, direct tool usage only                   |
+| `{output_dir}`          | string  | Full path to feature output directory                  |
+
+</state_variables>
+
+<entry_point>
+
+**FIRST ACTION:** Load `steps/step-00-init.md`
+
+</entry_point>
+
+<step_files>
+**Progressive loading - only load current step:**
+
+| Step | File                         | Model  | Purpose                                              |
+| ---- | ---------------------------- | ------ | ---------------------------------------------------- |
+| 00   | `steps/step-00-init.md`      | Haiku  | Parse flags, create structure, initialize state      |
+| 01   | `steps/step-01-discover.md`  | Opus   | Elicitation with ULTRATHINK (load questionnaire)     |
+| 02   | `steps/step-02-analyse.md`   | Sonnet | BRD + business rules formalization                   |
+| 03   | `steps/step-03-specify.md`   | Sonnet | FRD + use cases + permissions                        |
+| 04   | `steps/step-04-validate.md`  | Haiku  | Validation gate (APPROVED/REJECTED)                  |
+| 05   | `steps/step-05-handoff.md`   | Opus   | Development prompt generation                        |
+| 06   | `steps/step-06-doc-html.md`  | Sonnet | React documentation (optional)                       |
+
+</step_files>
+
+<questionnaire_files>
+**Progressive questionnaire loading (step-01 only):**
+
+Load ONLY relevant categories based on feature type:
+
+| Category | File                                | When to load |
+| -------- | ----------------------------------- | ------------ |
+| 01       | `questionnaire/01-context.md`       | Always       |
+| 02       | `questionnaire/02-stakeholders.md`  | Always       |
+| 03       | `questionnaire/03-scope.md`         | Always       |
+| 04       | `questionnaire/04-data.md`          | If data-centric |
+| 05       | `questionnaire/05-integrations.md`  | If integrations |
+| 06       | `questionnaire/06-security.md`      | Always (minimal) |
+| 07       | `questionnaire/07-ui.md`            | If UI-centric |
+| 08       | `questionnaire/08-performance.md`   | If performance-critical |
+| 09       | `questionnaire/09-constraints.md`   | If constraints exist |
+| 10       | `questionnaire/10-documentation.md` | If doc required |
+
+</questionnaire_files>
+
+<template_files>
+**Progressive template loading:**
+
+| Template | File                          | Used in step |
+| -------- | ----------------------------- | ------------ |
+| discovery | `templates/frd-discovery.md` | 01           |
+| brd       | `templates/frd-brd.md`       | 02           |
+| frd       | `templates/frd-spec.md`      | 03           |
+| handoff   | `templates/frd-handoff.md`   | 05           |
+
+</template_files>
+
+<execution_rules>
+
+- **Load one step at a time** - Only load the current step file
+- **ULTRATHINK** for phases 01, 02, 03, 05 (critical thinking)
+- **Persist state variables** across all steps via 00-context.md
+- **Follow next_step directive** at end of each step
+- **Save outputs** immediately after each phase
+- **Use parallel agents** for exploration (unless economy_mode)
+- **Context: business only** - Reject platform/personal/system contexts
+</execution_rules>
+
+<success_criteria>
+
+- Each step loaded progressively (max 300-400 lines/step)
+- All outputs saved to feature folder
+- Validation gate passed (APPROVED)
+- Development handoff ready for `/implement`
+- Clear completion summary with next steps
+</success_criteria>

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

@@ -0,0 +1,258 @@
+# Business Analysis - Shared Functions (v2 - Progressive Loading)
+
+> **Ref:** This file contains common functions for all BA phases.
+> **Version:** 2.0 - Optimized for progressive loading
+
+---
+
+## Architecture Progressive
+
+Le skill BusinessAnalyse utilise le **chargement progressif** pour minimiser le contexte:
+
+```
+SKILL.md (entry point)
+    ↓
+steps/step-00-init.md (parse flags, create state)
+    ↓
+steps/step-01-discover.md (charge questionnaire/XX.md on-demand)
+    ↓
+steps/step-02-analyse.md (charge templates/frd-brd.md)
+    ↓
+steps/step-03-specify.md (charge templates/frd-spec.md)
+    ↓
+steps/step-04-validate.md (validation gate)
+    ↓
+steps/step-05-handoff.md (charge templates/frd-handoff.md)
+    ↓
+steps/step-06-doc-html.md (charge react/*.md on-demand)
+```
+
+**Benefit:** ~70% context reduction per phase
+
+---
+
+## Business Context Validation
+
+```
+validate_business_context(context):
+  IF context IN ['platform', 'personal', 'system'] THEN
+    ERROR "BA restricted to 'business' context. Contact: support@atlshub.ch"
+    RETURN false
+  END IF
+  RETURN true
+```
+
+**CRITICAL:** BusinessAnalyze works ONLY for the `business` context.
+
+---
+
+## Feature Directory Structure
+
+```
+.business-analyse/
+├── config.json                    # Global config
+└── business/
+    └── {application}/
+        └── modules/
+            └── {module}/
+                └── features/
+                    └── {FEAT-NNN}/
+                        ├── 00-context.md      # State persistence
+                        ├── 1-discovery.md
+                        ├── 2-business-requirements.md
+                        ├── 3-functional-specification.md
+                        ├── validation.json
+                        ├── 4-development-handoff.md
+                        └── tracking/
+                            ├── changes/
+                            ├── bugs/
+                            └── hotfixes/
+```
+
+---
+
+## Feature ID Generation
+
+```
+generate_feature_id():
+  last_id = read_config(".business-analyse/config.json", "lastFeatureId") OR 0
+  new_id = last_id + 1
+  update_config(".business-analyse/config.json", "lastFeatureId", new_id)
+  RETURN format("FEAT-%03d", new_id)
+```
+
+---
+
+## Models by Phase (Step)
+
+| Step | Model | Reason |
+|------|-------|--------|
+| 00-init | Haiku | Quick structure setup |
+| 01-discover | **Opus** | ULTRATHINK elicitation |
+| 02-analyse | Sonnet | BRD modeling |
+| 03-specify | Sonnet | FRD + Use Cases |
+| 04-validate | Haiku | Binary gate |
+| 05-handoff | **Opus** | Zero-ambiguity prompt |
+| 06-doc-html | Sonnet | React + Context7 |
+
+---
+
+## ULTRATHINK
+
+Behavioral mode for critical phases (01, 02, 03, 05):
+
+```
+ULTRATHINK MODE:
+- Consider ALL edge cases
+- Challenge EVERY assumption
+- Anticipate UNEXPRESSED needs
+- Validate completeness before output
+
+DO NOT:
+- Accept vague answers
+- Skip question categories
+- Assume stakeholder thought of everything
+```
+
+**DO NOT invoke** as a skill/tool - it is a thinking mode.
+
+---
+
+## Context7 (Step 06)
+
+```
+Prompt pattern:
+"use context7 with /facebook/react and /i18next/react-i18next
+ to generate {component} following SmartStack patterns"
+```
+
+Libraries:
+- `/facebook/react` - React 19 patterns
+- `/i18next/react-i18next` - Internationalization
+- `/remix-run/react-router` - React Router v7
+- `/lucide-icons/lucide-react` - Icons
+
+---
+
+## Permission Path Format
+
+**Format:** `business.{application}.{module}.{action}`
+
+| Action | Permission | Usage |
+|--------|------------|-------|
+| Read | `.read` | GET endpoints |
+| Create | `.create` | POST endpoints |
+| Update | `.update` | PUT endpoints |
+| Delete | `.delete` | DELETE endpoints |
+| Export | `.export` | Export data |
+| Import | `.import` | Import data |
+| Admin | `.admin` | Administrative |
+
+---
+
+## i18n (4 required languages)
+
+| Language | File | Code |
+|----------|------|------|
+| French | `fr/docs-{app}-{module}.json` | fr |
+| English | `en/docs-{app}-{module}.json` | en |
+| Italian | `it/docs-{app}-{module}.json` | it |
+| German | `de/docs-{app}-{module}.json` | de |
+
+---
+
+## Output Paths
+
+| Type | Path |
+|------|------|
+| Documentation | `web/smartstack-web/src/pages/docs/business/{app}/{module}/` |
+| i18n | `web/smartstack-web/src/i18n/locales/{lang}/` |
+| Route | `/docs/business/{app}/{module}` |
+
+---
+
+## State Persistence
+
+The `00-context.md` file persists state between steps:
+
+```markdown
+# Business Analysis: {{feature_id}}
+
+## Progress
+| Step | Status | Started | Completed |
+|------|--------|---------|-----------|
+| 00-init | Complete | ... | ... |
+| 01-discover | In Progress | ... | - |
+...
+
+## State Variables
+| Variable | Value |
+|----------|-------|
+| feature_id | FEAT-001 |
+| application_name | Sales |
+...
+```
+
+**Read:** Each step starts by reading 00-context.md
+**Write:** Each step updates 00-context.md at the end
+
+---
+
+## Resume Workflow
+
+```
+resume_workflow(task_id):
+  1. Search .business-analyse/ for matching feature
+  2. Read 00-context.md
+  3. Find last "Complete" step in Progress table
+  4. Return next step to load
+
+Example:
+  /business-analyse -r FEAT-001
+  → Reads .business-analyse/.../FEAT-001/00-context.md
+  → Finds "01-discover: Complete, 02-analyse: Pending"
+  → Loads step-02-analyse.md
+```
+
+---
+
+## Standard Summary (End of Step)
+
+```
+{STEP_NAME} - {feature_id}
+├── Status: {Complete/In Progress}
+├── Key metric: {value}
+├── Output: {file created}
+└── Next: {next step name}
+```
+
+---
+
+## Config Template
+
+```json
+{
+  "project": "{Name}",
+  "lastFeatureId": 0,
+  "context": "business",
+  "standards": ["BABOK-v3", "IEEE-830"],
+  "contact": "support@atlshub.ch"
+}
+```
+
+---
+
+## Progressive Loading Benefits
+
+| Aspect | Before | After | Gain |
+|--------|--------|-------|------|
+| Questionnaire | 283 L (all) | 40-60 L (per category) | ~75% |
+| FRD Templates | 477 L (all) | 80-150 L (per type) | ~70% |
+| React Templates | 580 L (all) | 250-350 L (per need) | ~45% |
+| **Total/step** | ~1,340 L | ~300-400 L | **~70%** |
+
+---
+
+## Support
+
+Contact: **support@atlshub.ch**

package/templates/skills/business-analyse/questionnaire/01-context.md

@@ -0,0 +1,33 @@
+# Category 1: Business Context
+
+> **Usage:** Fundamental questions about the business need
+> **When to load:** ALWAYS (core)
+
+---
+
+## 1.1 Fundamental Need
+
+| # | Question | Answer Type |
+|---|----------|-------------|
+| Q1.1 | What business problem should this module/feature solve? | Free text |
+| Q1.2 | What is the current situation (AS-IS)? | Description |
+| Q1.3 | What is the target situation (TO-BE)? | Description |
+| Q1.4 | What are the measurable success KPIs? | List + values |
+
+## 1.2 Business Value
+
+| # | Question | Answer Type |
+|---|----------|-------------|
+| Q1.5 | What ROI do you expect? (time, money, efficiency) | Quantitative |
+| Q1.6 | What savings or gains will this module bring? | Estimation |
+| Q1.7 | What happens if this module is NOT developed? | Impact |
+| Q1.8 | What is the priority compared to other needs? | High/Medium/Low |
+
+---
+
+## Follow-up Questions
+
+For each vague answer:
+- "Can you give a concrete example?"
+- "How do you measure that today?"
+- "What happens if this rule is not respected?"

package/templates/skills/business-analyse/questionnaire/02-stakeholders.md

@@ -0,0 +1,35 @@
+# Category 2: Stakeholders
+
+> **Usage:** Identification of stakeholders and their needs
+> **When to load:** ALWAYS (core)
+
+---
+
+## 2.1 Identification
+
+| # | Question | Answer Type |
+|---|----------|-------------|
+| Q2.1 | Who are the direct end users? | List of roles |
+| Q2.2 | Who are the indirect beneficiaries? | List |
+| Q2.3 | Who is the sponsor/final decision maker? | Name + role |
+| Q2.4 | Who can block the project? | List + reasons |
+
+## 2.2 Needs by Role
+
+| # | Question | Answer Type |
+|---|----------|-------------|
+| Q2.5 | For each role: What tasks should they accomplish? | Per role |
+| Q2.6 | What frequency of use per role? | Daily/Weekly/Monthly |
+| Q2.7 | What level of technical expertise per role? | Novice/Intermediate/Expert |
+| Q2.8 | What current frustrations per role? | List of pain points |
+
+---
+
+## Role -> Permission Mapping
+
+| Discovered Role | SmartStack Permission |
+|-----------------|----------------------|
+| Admin | `*.admin` |
+| Manager | `*.read,create,update` |
+| User | `*.read,create` |
+| ReadOnly | `*.read` |

package/templates/skills/business-analyse/questionnaire/03-scope.md

@@ -0,0 +1,35 @@
+# Category 3: Functional Scope
+
+> **Usage:** Scope definition with MoSCoW
+> **When to load:** ALWAYS (core)
+
+---
+
+## 3.1 Functionality (MoSCoW)
+
+| # | Question | Answer Type |
+|---|----------|-------------|
+| Q3.1 | List ESSENTIAL features (Must-Have) | List |
+| Q3.2 | List DESIRED features (Should-Have) | List |
+| Q3.3 | List OPTIONAL features (Could-Have) | List |
+| Q3.4 | What is EXPLICITLY excluded? | List of exclusions |
+
+## 3.2 Business Process
+
+| # | Question | Answer Type |
+|---|----------|-------------|
+| Q3.5 | Describe the main user flow | Steps |
+| Q3.6 | What are the decision points in the flow? | List |
+| Q3.7 | What alternative flows exist? | Per condition |
+| Q3.8 | What are the possible error cases? | List |
+
+---
+
+## Prioritization
+
+| Priority | Criterion |
+|----------|-----------|
+| Must | Without this feature, the module has no value |
+| Should | Brings significant value but can wait for v2 |
+| Could | Nice-to-have, can be implemented if time available |
+| Won't | Explicitly excluded from scope |

package/templates/skills/business-analyse/questionnaire/04-data.md

@@ -0,0 +1,36 @@
+# Category 4: Data
+
+> **Usage:** Definition of entities and data rules
+> **When to load:** If feature is data-centric or full module
+
+---
+
+## 4.1 Entities
+
+| # | Question | Answer Type |
+|---|----------|-------------|
+| Q4.1 | What are the main entities handled? | List |
+| Q4.2 | For each entity: important attributes? | Per entity |
+| Q4.3 | What relationships exist between entities? | Text schema |
+| Q4.4 | Expected data volume? | Estimation |
+
+## 4.2 Data Rules
+
+| # | Question | Answer Type |
+|---|----------|-------------|
+| Q4.5 | What validations on data? | List of rules |
+| Q4.6 | Which fields are required vs optional? | Per field |
+| Q4.7 | What specific formats/constraints? | List |
+| Q4.8 | Sensitive data to protect? | List + level |
+
+---
+
+## SmartStack Mapping
+
+| Business Concept | SmartStack |
+|-----------------|------------|
+| Main entity | Domain Entity |
+| Required attribute | `[Required]` |
+| Unique attribute | `HasIndex().IsUnique()` |
+| 1:N relationship | Navigation property |
+| Sensitive data | Encryption + audit |

package/templates/skills/business-analyse/questionnaire/05-integrations.md

@@ -0,0 +1,36 @@
+# Category 5: Integrations
+
+> **Usage:** Connections with internal and external systems
+> **When to load:** If feature involves integrations
+
+---
+
+## 5.1 Existing Systems
+
+| # | Question | Answer Type |
+|---|----------|-------------|
+| Q5.1 | What internal systems should we integrate with? | List |
+| Q5.2 | What external systems? | List |
+| Q5.3 | Existing APIs to use? | Documentation |
+| Q5.4 | Data to import from another system? | List + format |
+
+## 5.2 Data Flows
+
+| # | Question | Answer Type |
+|---|----------|-------------|
+| Q5.5 | Flow direction? (inbound/outbound/bidirectional) | Per system |
+| Q5.6 | Synchronization frequency? | Real-time/Batch |
+| Q5.7 | Data conflict management? | Strategy |
+| Q5.8 | Fallback if external system unavailable? | Behavior |
+
+---
+
+## SmartStack Patterns
+
+| Integration Type | Pattern |
+|-----------------|---------|
+| REST API | HttpClient + Polly |
+| Message Queue | MassTransit |
+| Webhook | Controller endpoint |
+| Real-time | SignalR |
+| Batch import | Background job |

package/templates/skills/business-analyse/questionnaire/06-security.md

@@ -0,0 +1,40 @@
+# Category 6: Security & Permissions
+
+> **Usage:** Definition of access and restrictions
+> **When to load:** ALWAYS (core, minimal)
+
+---
+
+## 6.1 Access
+
+| # | Question | Answer Type |
+|---|----------|-------------|
+| Q6.1 | Who can VIEW data? | List of roles |
+| Q6.2 | Who can CREATE entries? | List of roles |
+| Q6.3 | Who can MODIFY? | List of roles |
+| Q6.4 | Who can DELETE? | List of roles |
+
+## 6.2 Restrictions
+
+| # | Question | Answer Type |
+|---|----------|-------------|
+| Q6.5 | Geographic restrictions? | Countries/regions |
+| Q6.6 | Time-based restrictions? (hours, periods) | Ranges |
+| Q6.7 | Audit trail required? Which actions? | List |
+| Q6.8 | Regulatory compliance? (GDPR, etc.) | List of standards |
+
+---
+
+## SmartStack Permission
+
+**Format:** `business.{application}.{module}.{action}`
+
+| Action | Permission |
+|--------|------------|
+| Read | `.read` |
+| Create | `.create` |
+| Update | `.update` |
+| Delete | `.delete` |
+| Export | `.export` |
+| Import | `.import` |
+| Admin | `.admin` |