@atlashub/smartstack-cli 2.1.0 → 2.3.0

package/templates/skills/business-analyse/questionnaire/12-migration.md

@@ -55,4 +55,4 @@
 | "On saisira tout à la main" | **Migration non planifiée** | Si > 100 enregistrements, l'import automatisé est indispensable |
 | Pas de validation post-migration | **Données non vérifiées** | Prévoir un rapport de migration : importés / rejetés / à corriger |
 | Aucun rollback plan | **Risque de perte de données** | Toujours faire un backup avant migration + possibilité de rollback |
-| "On migrera plus tard" | **Dette technique** | Si la migration est nécessaire, la planifier dès la v1 même si simplifiée |
+| "On migrera plus tard" | **Dette technique** | Si la migration est nécessaire, la planifier dès le départ même si simplifiée |

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

@@ -1,35 +1,36 @@
 # Elicitation Questionnaire - Business Analysis
 
-> **Usage:** Structured questions for phase 2-discover
-> **Standard:** BABOK v3 - Elicitation Techniques
+> **Usage:** Structured questions for step-01-analyse
+> **Standard:** BABOK v3 - Elicitation Techniques (VibeCoding-focused)
 > **Model:** OPUS with ULTRATHINK
+> **Total:** ~60 targeted questions (dev-relevant only)
 
 ---
 
 ## ULTRATHINK RULE
 
 ```
-╔══════════════════════════════════════════════════════════════════════════════╗
-║  ULTRATHINK: Deep thinking mode for exhaustive elicitation                   ║
-╠══════════════════════════════════════════════════════════════════════════════╣
-║                                                                              ║
-║  During the discover phase, Claude MUST:                                     ║
-║  • Consider ALL edge cases before formulating a question                      ║
-║  • Challenge EVERY stakeholder assumption                                     ║
-║  • Anticipate unexpressed needs                                              ║
-║  • Validate completeness before moving to next question                      ║
-║                                                                              ║
-║  DO NOT:                                                                     ║
-║  • Accept vague answers                                                      ║
-║  • Skip question categories                                                  ║
-║  • Assume stakeholder has thought of everything                              ║
-║                                                                              ║
-╚══════════════════════════════════════════════════════════════════════════════╝
++==============================================================================+
+|  ULTRATHINK: Deep thinking mode for exhaustive elicitation                   |
++==============================================================================+
+|                                                                              |
+|  During the analyse phase, Claude MUST:                                      |
+|  - Consider ALL edge cases before formulating a question                     |
+|  - Challenge EVERY stakeholder assumption                                    |
+|  - Anticipate unexpressed needs                                              |
+|  - Validate completeness before moving to next question                      |
+|                                                                              |
+|  DO NOT:                                                                     |
+|  - Accept vague answers                                                      |
+|  - Skip question categories                                                  |
+|  - Assume stakeholder has thought of everything                              |
+|                                                                              |
++==============================================================================+
 ```
 
 ---
 
-## Category 1: Business Context
+## Category 1: Business Context (4 questions)
 
 ### 1.1 Fundamental Need
 
@@ -38,20 +39,13 @@
 | 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 |
+| Q1.4 | What happens if this module is NOT developed? | Impact |
 
-### 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 |
+> **Trimmed:** KPIs, ROI, savings, timeline (project management scope)
 
 ---
 
-## Category 2: Stakeholders
+## Category 2: Stakeholders (8 questions)
 
 ### 2.1 Identification
 
@@ -73,7 +67,7 @@
 
 ---
 
-## Category 3: Functional Scope
+## Category 3: Functional Scope (8 questions)
 
 ### 3.1 Functionality
 
@@ -95,7 +89,7 @@
 
 ---
 
-## Category 4: Data
+## Category 4: Data (8 questions)
 
 ### 4.1 Entities
 
@@ -117,7 +111,7 @@
 
 ---
 
-## Category 5: Integrations
+## Category 5: Integrations (8 questions)
 
 ### 5.1 Existing Systems
 
@@ -139,7 +133,7 @@
 
 ---
 
-## Category 6: Security & Permissions
+## Category 6: Security & Permissions (8 questions)
 
 ### 6.1 Access
 
@@ -161,7 +155,7 @@
 
 ---
 
-## Category 7: User Interface
+## Category 7: User Interface (8 questions)
 
 ### 7.1 Experience
 
@@ -183,29 +177,22 @@
 
 ---
 
-## Category 8: Performance & Quality
+## Category 8: Performance & Quality (4 questions)
 
-### 8.1 Performance
+### 8.1 Performance & Quality
 
 | # | Question | Answer Type |
 |---|----------|-------------|
 | Q8.1 | Acceptable response time? | Milliseconds |
-| Q8.2 | Number of concurrent users? | Estimation |
-| Q8.3 | Expected load peaks? | When + volume |
-| Q8.4 | Required availability? (SLA) | Percentage |
+| Q8.2 | Expected load peaks? | When + volume |
+| Q8.3 | Specific tests required? | Types |
+| Q8.4 | Overall acceptance criteria? | List |
 
-### 8.2 Quality
-
-| # | Question | Answer Type |
-|---|----------|-------------|
-| Q8.5 | Acceptable error rate? | Percentage |
-| Q8.6 | Specific tests required? | Types |
-| Q8.7 | Available test environments? | List |
-| Q8.8 | Overall acceptance criteria? | List |
+> **Trimmed:** Concurrent users, SLA, error rate, test environments (ops/infra scope)
 
 ---
 
-## Category 9: Constraints
+## Category 9: Constraints (4 questions)
 
 ### 9.1 Technical
 
@@ -216,18 +203,11 @@
 | Q9.3 | Technology dependencies? | List |
 | Q9.4 | Compatibility constraints? | List |
 
-### 9.2 Organizational
-
-| # | Question | Answer Type |
-|---|----------|-------------|
-| Q9.5 | Available budget? | Amount |
-| Q9.6 | Fixed or flexible deadline? | Date + flexibility |
-| Q9.7 | Available resources? | Team |
-| Q9.8 | Approval process? | Steps |
+> **Trimmed:** Budget, deadline, resources, approval process (PM scope)
 
 ---
 
-## Category 10: Documentation & Support
+## Category 10: Documentation & Support (4 questions)
 
 ### 10.1 Documentation
 
@@ -238,25 +218,32 @@
 | Q10.3 | User training planned? | Plan |
 | Q10.4 | Knowledge base to create? | Scope |
 
-### 10.2 Support
+> **Trimmed:** Support level, L1/L2, escalation, monitoring (ops scope)
 
-| # | Question | Answer Type |
-|---|----------|-------------|
-| Q10.5 | Expected support level? | SLA |
-| Q10.6 | Who provides level 1 support? | Team |
-| Q10.7 | Escalation to level 2? | Process |
-| Q10.8 | Monitoring and alerts required? | List |
+---
+
+## Conditional Categories (loaded only if relevant)
+
+### Category 11: Data Lifecycle (questionnaire/11-data-lifecycle.md)
+> Loaded if: entities have retention/archival/GDPR requirements
+
+### Category 12: Migration (questionnaire/12-migration.md)
+> Loaded if: data migration from existing system needed
+
+### Category 13: Cross-Module Impact (questionnaire/13-cross-module.md)
+> Loaded if: feature interacts with existing modules
 
 ---
 
 ## Questionnaire Usage
 
-### Discovery Phase
+### Analyse Phase
 
 1. **Start:** Begin with Category 1 (Business Context)
 2. **Adapt:** Skip questions not relevant to the context
 3. **Deepen:** Ask follow-up questions on vague answers
 4. **Challenge:** Don't accept "we'll see later" on Must-Have
+5. **Batch:** Present 3-5 questions per interaction (AskUserQuestion)
 
 ### Follow-up Questions
 
@@ -266,18 +253,27 @@ For each vague answer, use:
 - "What happens if this rule is not respected?"
 - "Who is impacted by this decision?"
 
-### Documentation
+### Dev-Relevance Filter
 
-Each answer should be documented with:
-- Source (who answered)
-- Date
-- Confidence level (Confirmed/To validate/Hypothesis)
-- Open follow-up questions
+Each question kept passes this test:
+> "Does the answer change something in the generated code?"
+> Yes -> Keep | No -> Remove
 
 ---
 
-## Support
-
-> **Questions about requirements elicitation?**
->
-> 📧 **support@atlshub.ch**
+## Summary
+
+| Category | Questions | Focus |
+|----------|-----------|-------|
+| 1. Business Context | 4 | Problem + AS-IS/TO-BE |
+| 2. Stakeholders | 8 | Roles + needs |
+| 3. Functional Scope | 8 | MoSCoW + flows |
+| 4. Data | 8 | Entities + rules |
+| 5. Integrations | 8 | Systems + flows |
+| 6. Security | 8 | Permissions + restrictions |
+| 7. UI | 8 | Screens + experience |
+| 8. Performance | 4 | Response time + tests |
+| 9. Constraints | 4 | Tech stack + deps |
+| 10. Documentation | 4 | User + tech docs |
+| **Total Core** | **64** | |
+| 11-13 (conditional) | ~24 | Lifecycle, migration, cross-module |