@atlashub/smartstack-cli 2.1.0 → 2.3.0

package/templates/skills/business-analyse/patterns/suggestion-catalog.md

@@ -0,0 +1,478 @@
+# Proactive Suggestion Catalog
+
+> **Version:** 3.0.0
+> **Usage:** Loaded by step-01-analyse after scope definition to suggest complementary modules/sections.
+> **Protocol:** Match feature type against patterns, present via AskUserQuestion (multiSelect: true).
+> **Purpose:** Guide users toward complete feature design by suggesting companion modules and standard sections.
+
+---
+
+## 1. Module Patterns
+
+Suggests companion modules based on primary module type:
+
+| Module Type | Keywords | Suggested Modules | Rationale |
+|-------------|----------|-------------------|-----------|
+| **Orders/Commandes** | order, commande, purchase, sales order | Invoices, Shipping, Returns, OrderLines, Customers | Orders are complete business objects; need billing, logistics, and related tables |
+| **Clients/Customers** | client, customer, contact, account, party | Contacts, Addresses, Contracts, Documents, CRM | Customers have multiple contact types, billing addresses, legal relationships |
+| **Products/Articles** | product, article, item, catalog, sku | Categories, Inventory, Pricing, Suppliers, Images | Products need organization, stock tracking, and multiple pricing strategies |
+| **Employees/HR** | employee, staff, personnel, team, workforce | Leaves, TimeTracking, Evaluations, Documents, Departments | Employees have time off needs, performance management, and asset allocation |
+| **Tickets/Support** | ticket, support, incident, issue, case | SLA, Escalation, KnowledgeBase, Categories, Notifications | Support systems need SLA tracking, knowledge base, and routing logic |
+| **Projects** | project, task, milestone, workplan, roadmap | Tasks, Milestones, Resources, Budgets, Timeline | Projects decompose into work items, need resource allocation, and progress tracking |
+| **Invoices/Billing** | invoice, billing, payment, receipt, statement | Payments, CreditNotes, Dunning, Taxes, Subscriptions | Invoicing is incomplete without payment tracking, refunds, and tax handling |
+| **Inventory/Stock** | inventory, stock, warehouse, goods, warehouse | StockMovements, Locations, Transfers, Alerts, AuditLog | Stock control needs movement tracking, multi-location support, and alerts |
+| **Documents** | document, file, attachment, media, archive | Categories, Versions, Sharing, Templates, Workflow | Document management requires metadata, versioning, and access control |
+| **Contracts** | contract, agreement, legal, terms, service level | Parties, Obligations, Milestones, Renewal, Templates | Contracts involve multiple parties, obligations tracking, and lifecycle management |
+| **Permissions/Security** | permission, role, access, authority, rbac | UserRoles, Groups, Policies, Audit, Delegation | Permission systems need fine-grained control, group policies, and audit trails |
+| **Notifications** | notification, alert, email, message, broadcast | Templates, Channels, Scheduling, Preferences | Notification systems need template management, multi-channel support, scheduling |
+| **Reporting** | report, dashboard, analytics, BI, metrics | Dashboards, Exports, Scheduling, AlertRules | Reporting needs visualization, scheduled distribution, and data export |
+
+---
+
+## 2. Section Patterns (cross-module)
+
+Suggests standard sections based on detected conditions:
+
+| Condition | Suggested Section | Reason | Implementation |
+|-----------|-------------------|--------|-----------------|
+| **Volume > 100 entries mentioned** | BulkImport | Large datasets need import capability | Add section with template format (CSV), validation rules, progress tracking |
+| **Export mentioned or data analysis** | Export (PDF/Excel) | Common need for business data | Add section with export formats, filtering, custom reports |
+| **Multiple user roles (≥3)** | Dashboard | Role-specific views improve UX | Add section with role-based dashboards, KPI cards, drill-downs |
+| **Time-sensitive data** | Notifications | Alert users of important changes | Add section with alert rules, channels (email, in-app), scheduling |
+| **Approval workflow mentioned** | Validation/Approval | Structured approval process | Add section with approval states, reviewer assignment, audit trail |
+| **Historical data important** | AuditLog | Track changes for compliance | Add section with change tracking, versioning, retention policy |
+| **Multi-language content** | Translation Management | Content i18n beyond UI labels | Add section with content i18n, translation workflow, versioning |
+| **Scheduled processing** | Background Jobs | Deferred/periodic processing | Add section with job scheduling, retry logic, error handling |
+| **Data archival needed** | Archive/Cleanup | Long-term data management | Add section with archival policy, retention rules, restore capability |
+| **Report generation** | Reporting Engine | Automated business reporting | Add section with template library, scheduling, distribution |
+| **External integrations** | Integration Layer | System-to-system communication | Add section with API specifications, webhook handling, sync strategy |
+| **Regulatory compliance** | Compliance & Audit | Legal/industry requirements | Add section with audit logging, data retention, retention periods |
+
+---
+
+## 3. Integration Patterns
+
+Suggests system integrations based on requirements:
+
+| Condition | Suggested Integration | Reason | Technical Approach |
+|-----------|----------------------|--------|-------------------|
+| **Email mentioned** | Workflow: SendEmail | Transactional email automation | Add section with email templates, trigger rules, delivery confirmation |
+| **External system referenced** | API Integration | Structured external data flow | Add section with API specs, auth strategy, sync frequency, error handling |
+| **Real-time updates needed** | SignalR Integration | Live data push to frontend | Add section with connection management, broadcast strategy, client handling |
+| **Scheduled processing** | Hangfire Background Jobs | Deferred/periodic processing | Add section with job scheduling, retry policy, monitoring |
+| **AI/ML classification** | AICompletion Service | Intelligent data processing | Add section with model specs, training data, API integration |
+| **Document generation** | Templating Engine | Dynamic document creation | Add section with template library, variable mapping, output formats |
+| **Payment processing** | Payment Gateway | Financial transaction handling | Add section with provider integration, security, reconciliation |
+| **Geographical features** | Maps/Location Service | Spatial data handling | Add section with provider selection, geocoding, distance calculation |
+| **Data synchronization** | Event Bus/Messaging | Async data consistency | Add section with message types, subscription strategy, retry logic |
+| **File storage** | Cloud Storage Integration | Large file handling | Add section with provider selection, access control, cleanup policy |
+
+---
+
+## 4. Usage Protocol
+
+### 4.1 Trigger Point
+
+After step-01-analyse completes scope definition (scope.mustHave + scope.shouldHave populated):
+
+```
+Step-01: Analyse → Define Scope → Load Suggestion Catalog → Present Suggestions
+```
+
+### 4.2 Suggestion Algorithm
+
+```
+Input: feature.json.scope.* (module name, keywords, must-haves, should-haves)
+
+1. Read scope.mustHave + scope.shouldHave (user-defined features)
+2. Extract primary keywords (module type) from scope.description
+3. Match against Module Patterns table → Suggested Modules
+4. Analyze scope.mustHave + scope.shouldHave for conditions → Suggested Sections
+5. Detect mentions of integrations → Suggested Integrations
+6. Filter out already-present modules/sections
+7. Rank by relevance (keyword match > condition confidence)
+8. Present top 3-4 suggestions to user
+9. Store results in feature.json.suggestions[]
+```
+
+### 4.3 Implementation Code
+
+```typescript
+// Pseudo-code for suggestion logic
+
+function suggestComplementaryModules(feature: Feature): Suggestion[] {
+  const suggestions: Suggestion[] = [];
+
+  // 1. Extract primary keywords
+  const keywords = extractKeywords(feature.scope.description);
+  const primaryType = matchModuleType(keywords);
+
+  // 2. Load suggestion catalog
+  const catalog = loadCatalog();
+
+  // 3. Suggest companion modules
+  if (catalog.modulePatterns[primaryType]) {
+    const suggestedModules = catalog.modulePatterns[primaryType].suggestedModules;
+
+    suggestedModules.forEach(module => {
+      if (!featureIncludesModule(feature, module)) {
+        suggestions.push({
+          type: "module",
+          name: module,
+          rationale: catalog.modulePatterns[primaryType].rationale,
+          priority: "high",
+          acceptance: `If accepted, adds ${module} as companion feature`
+        });
+      }
+    });
+  }
+
+  // 4. Suggest sections based on conditions
+  catalog.sectionPatterns.forEach(pattern => {
+    if (evaluateCondition(feature, pattern.condition)) {
+      if (!featureIncludesSection(feature, pattern.suggestedSection)) {
+        suggestions.push({
+          type: "section",
+          name: pattern.suggestedSection,
+          rationale: pattern.reason,
+          priority: "medium",
+          acceptance: `If accepted, adds ${pattern.suggestedSection} section to spec`
+        });
+      }
+    }
+  });
+
+  // 5. Suggest integrations based on mentions
+  catalog.integrationPatterns.forEach(pattern => {
+    if (feature.scope.description.includes(pattern.keyword)) {
+      if (!featureIncludesIntegration(feature, pattern.suggestedIntegration)) {
+        suggestions.push({
+          type: "integration",
+          name: pattern.suggestedIntegration,
+          rationale: pattern.reason,
+          priority: "medium",
+          acceptance: `If accepted, adds ${pattern.suggestedIntegration} to architecture`
+        });
+      }
+    }
+  });
+
+  // 6. Rank and filter top suggestions
+  const ranked = suggestions
+    .sort((a, b) => priorityScore(a) - priorityScore(b))
+    .slice(0, 4);
+
+  return ranked;
+}
+
+// Evaluate condition: Volume > 100
+function evaluateCondition(feature: Feature, condition: string): boolean {
+  if (condition === "Volume > 100 entries") {
+    const mentions = feature.scope.description.match(/(bulk|import|high.*volume|large.*dataset)/gi);
+    return mentions && mentions.length > 0;
+  }
+  // ... other conditions
+}
+```
+
+### 4.4 User Presentation
+
+Present suggestions to user via AskUserQuestion (multiSelect: true):
+
+```
+✓ Analysis complete. I've identified some complementary modules & sections.
+
+Would you like to add any of these to your feature?
+
+Companion Modules:
+  □ Customers (ships with Orders) → Need to manage customer relationships
+  □ Shipping (logistics) → Need to track delivery
+  □ Invoices (billing) → Need financial records
+  □ Returns (warranty) → Need reverse logistics
+
+Standard Sections:
+  □ BulkImport → You mentioned "1000+ orders per month"
+  □ Notifications → For order status alerts
+  □ Dashboard → For manager oversight
+  □ Audit Log → For order history tracking
+
+Select all that apply: [ ] [ ] [ ] [ ]
+
+[Add Selected] [Skip] [Customize]
+```
+
+### 4.5 User Selection Processing
+
+When user selects suggestions:
+
+1. **Add Selected Modules:** Update scope.mustHave with new modules
+2. **Add Selected Sections:** Update specification.sections (in step-02)
+3. **Add Selected Integrations:** Update specification.integrations
+4. **Store Decisions:** Log in feature.json.suggestions[]
+5. **Continue:** Proceed to step-02-specify with expanded scope
+
+```json
+{
+  "suggestions": [
+    {
+      "id": "SUGG-001",
+      "type": "module",
+      "name": "Customers",
+      "source": "Module Pattern: Orders → Customers",
+      "accepted": true,
+      "acceptedAt": "2025-02-01T09:30:00Z",
+      "acceptedBy": "user_email@company.com"
+    },
+    {
+      "id": "SUGG-002",
+      "type": "section",
+      "name": "BulkImport",
+      "source": "Section Pattern: Volume > 100",
+      "accepted": true,
+      "acceptedAt": "2025-02-01T09:30:00Z"
+    },
+    {
+      "id": "SUGG-003",
+      "type": "integration",
+      "name": "Email Notifications",
+      "source": "Integration Pattern: Email mentioned",
+      "accepted": false,
+      "rejectionReason": "Out of scope for MVP"
+    }
+  ]
+}
+```
+
+---
+
+## 5. Customization & Feedback Loop
+
+### 5.1 Customize Suggestions
+
+Allow user to modify or customize suggestions:
+
+```
+Option: [Customize]
+
+Edit suggestion "Customers":
+  Name: Customers
+  Type: Module
+  Rationale: [user can edit]
+  Include in scope: [Yes/No]
+
+[Apply] [Cancel]
+```
+
+### 5.2 Feedback Loop
+
+Track suggestion effectiveness:
+
+```json
+{
+  "suggestionFeedback": {
+    "catalogVersion": "1.0.0",
+    "suggestionSessionId": "sess-12345",
+    "presentedCount": 4,
+    "acceptedCount": 2,
+    "acceptanceRate": 0.5,
+    "userFeedback": "Perfect - saved us from missing Customer module!"
+  }
+}
+```
+
+---
+
+## 6. Catalog Maintenance
+
+### 6.1 Update Triggers
+
+Update suggestion catalog when:
+
+1. **New patterns discovered** - Team identifies common module combinations
+2. **Industry changes** - New regulations, technologies, best practices
+3. **User feedback** - Customers request new suggestions
+4. **Version upgrades** - New SmartStack capabilities
+
+### 6.2 Catalog Format
+
+Suggestion catalog stored as structured data:
+
+```yaml
+# templates/patterns/suggestion-catalog.yaml
+
+version: "1.0.0"
+updated: "2025-02-01"
+
+modulePatterns:
+  Orders/Commandes:
+    keywords: ["order", "commande", "purchase", "sales order"]
+    suggestedModules: ["Invoices", "Shipping", "Returns", "OrderLines", "Customers"]
+    rationale: "Orders are complete business objects..."
+
+  Customers:
+    keywords: ["client", "customer", "contact", "account"]
+    suggestedModules: ["Contacts", "Addresses", "Contracts", "Documents"]
+    rationale: "Customers have multiple contact types..."
+
+sectionPatterns:
+  - condition: "Volume > 100 entries mentioned"
+    suggestedSection: "BulkImport"
+    reason: "Large datasets need import capability"
+    implementation: "Template format (CSV), validation rules, progress tracking"
+
+  - condition: "Export mentioned or data analysis"
+    suggestedSection: "Export"
+    reason: "Common need for business data"
+    implementation: "Export formats (PDF, Excel), filtering, custom reports"
+
+integrationPatterns:
+  - condition: "Email mentioned"
+    suggestedIntegration: "Workflow: SendEmail"
+    reason: "Transactional email automation"
+    approach: "Email templates, trigger rules, delivery confirmation"
+
+  - condition: "External system referenced"
+    suggestedIntegration: "API Integration"
+    reason: "Structured external data flow"
+    approach: "API specs, auth strategy, sync frequency, error handling"
+```
+
+---
+
+## 7. Limitations & Edge Cases
+
+### 7.1 When Suggestions Don't Apply
+
+Skip suggestions if:
+
+- **Micro mode:** Skip all suggestions (keep MVP minimal)
+- **Refactoring mode:** Skip module suggestions (only affect feature sections)
+- **User explicitly declines:** Respect user's scope boundary
+- **Budget/timeline constraints:** User indicated fixed scope
+
+```
+Suggested modules: Customers, Shipping, Invoices, Returns
+
+But you indicated:
+  - Timeline: 2 weeks (MVP only)
+  - Budget: 1 developer
+
+Suggestion: Start with Orders + Customers (minimal), defer others.
+
+[OK] [Adjust scope] [Ignore suggestions]
+```
+
+### 7.2 Conflicting Suggestions
+
+Handle cases where suggestions conflict:
+
+```
+Suggestion: BulkImport (volume > 100)
+Suggestion: Manual creation only (for quality control)
+
+Conflict: Bulk operations vs. controlled creation.
+
+Recommendation: Add BulkImport with validation workflow.
+
+[Accept both] [Choose one] [Skip both]
+```
+
+### 7.3 Chained Dependencies
+
+Track cascading dependencies:
+
+```
+User accepted: Customers
+Auto-suggest: Addresses (depends on Customers)
+Auto-suggest: Contracts (depends on Customers + Addresses)
+
+Cascade depth limit: 2 levels (prevent scope explosion)
+
+Auto-added:
+  ✓ Customers (user selected)
+  ✓ Addresses (dependency of Customers)
+  ⚠ Contracts (optional, user confirm?)
+
+[Accept all] [Customize] [Clear cascade]
+```
+
+---
+
+## 8. Examples
+
+### 8.1 Example: Order Management
+
+**Input:**
+- Module: "Orders"
+- Description: "Manage customer purchase orders, 5000+ orders/month"
+- Scope: [Scope definition with "bulk", "export", "approval"]
+
+**Suggestions Generated:**
+1. ✓ **Module: Customers** - Orders need customer relationship
+2. ✓ **Module: Shipping** - Orders need fulfillment tracking
+3. ✓ **Section: BulkImport** - 5000+ orders/month detected
+4. ✓ **Section: Export** - Explicit mention in scope
+5. ✓ **Section: Dashboard** - 3+ roles (User, Manager, Admin)
+6. ✓ **Section: Audit Log** - Order modifications tracked
+7. ✓ **Integration: Email Notifications** - Order status alerts
+8. ✗ **Module: Invoices** - Deferred (nice-to-have)
+
+**Presented to User (top 4):**
+1. Customers - High relevance (module pattern match)
+2. BulkImport - High relevance (volume > 100)
+3. Dashboard - Medium relevance (multi-role)
+4. Email Notifications - Medium relevance (status updates mentioned)
+
+---
+
+### 8.2 Example: Customer Management
+
+**Input:**
+- Module: "Customers"
+- Description: "Manage customer master data with contacts and addresses"
+
+**Suggestions Generated:**
+1. ✓ **Module: Contacts** - Customer subcomponent
+2. ✓ **Module: Addresses** - Multiple addresses per customer
+3. ✓ **Module: Contracts** - Customer agreements
+4. ✓ **Section: Merge** - Duplicate customer handling
+5. ✓ **Section: Import** - Master data cleanup
+6. ✓ **Integration: API Integration** - External CRM sync
+
+**Presented (top 3):**
+1. Contacts - High relevance (decomposition)
+2. Addresses - High relevance (decomposition)
+3. Merge - Medium relevance (data quality)
+
+---
+
+### 8.3 Example: HR/Employees
+
+**Input:**
+- Module: "Employees"
+- Description: "Manage employee records and leave requests"
+
+**Suggestions Generated:**
+1. ✓ **Module: Leaves** - Leave management system
+2. ✓ **Module: TimeTracking** - Time & attendance
+3. ✓ **Module: Evaluations** - Performance management
+4. ✓ **Section: Calendar** - Leave calendar view
+5. ✓ **Section: Reports** - HR analytics and reports
+6. ✓ **Integration: Background Jobs** - Payroll processing
+
+**Presented (top 4):**
+1. Leaves - High relevance (mentioned in description)
+2. TimeTracking - High relevance (related feature)
+3. Calendar - Medium relevance (leave visualization)
+4. Reports - Medium relevance (HR analytics)
+
+---
+
+## 9. Versioning & Updates
+
+**Catalog Version:** 1.0.0
+**Last Updated:** 2025-02-01
+**Next Review:** 2025-05-01
+**Maintained By:** SmartStack Team
+
+Changes will be tracked in `templates/patterns/suggestion-catalog-changelog.md`.

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

@@ -12,16 +12,7 @@
 | 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 triggered this need? (urgency, regulation, roadmap) | Trigger type |
-| Q1.8 | What is the expected delivery timeline? | Timeline |
+| Q1.4 | What triggered this need? (urgency, regulation, roadmap) | Trigger type |
 
 ---
 
@@ -34,9 +25,7 @@
 | Q1.1 (problem) | User describes a solution, not a problem | "Oublions la solution un instant — quel problème rencontrez-vous concrètement aujourd'hui ?" |
 | Q1.2 (AS-IS) | No concrete workflow described | "Décrivez-moi une journée type : vous arrivez, vous ouvrez l'outil — que faites-vous en premier ?" |
 | Q1.3 (TO-BE) | Vague ("ça ira mieux") | "Concrètement, quel geste ou tâche sera différent ? Combien de clics/minutes en moins ?" |
-| Q1.4 (KPIs) | No measurable metric | "Comment saurez-vous dans 3 mois que cette fonctionnalité a réussi ? Quel chiffre regarderez-vous ?" |
-| Q1.5 (ROI) | "I don't know" | "Combien de temps passez-vous sur ce processus aujourd'hui par semaine ? À combien de personnes ?" |
-| Q1.7 (trigger) | Vague ("c'est utile") | "Quel événement ou quelle situation a déclenché ce besoin maintenant ? Obligation, inefficacité, opportunité ?" |
+| Q1.4 (trigger) | Vague ("c'est utile") | "Quel événement ou quelle situation a déclenché ce besoin maintenant ? Obligation, inefficacité, opportunité ?" |
 
 ### Anti-patterns to Detect
 
@@ -44,5 +33,4 @@
 |--------|-------------|--------|
 | "Il faudrait un bouton/écran/champ..." | **Solution disguised as need** | Apply Solution → Problem Reframing |
 | "C'est évident", "tout le monde sait" | **Implicit assumption** | "Pouvez-vous le formuler explicitement pour que je puisse le documenter ?" |
-| KPIs are feelings ("ça sera mieux") | **Non-measurable success** | "Quel chiffre regarderez-vous pour savoir si c'est réussi ?" |
-| Q1.7 = "Opportunité" sans urgence | **Déclencheur à clarifier** | "Quel gain concret attendez-vous ? Comment mesurerez-vous l'amélioration ?" |
+| Q1.4 = "Opportunité" sans urgence | **Déclencheur à clarifier** | "Quel gain concret attendez-vous ? Comment mesurerez-vous l'amélioration ?" |

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

@@ -12,7 +12,7 @@
 | 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 | Any known constraints limiting v1 scope? | List of constraints |
+| Q3.4 | Any known constraints limiting scope? | List of constraints |
 
 ## 3.2 Business Process
 
@@ -29,10 +29,10 @@
 
 | 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 | Deferred — will be considered for future versions |
+| Must | Without this feature, the module has no value — implement first |
+| Should | Brings significant value — implement right after Must items |
+| Could | Nice-to-have — implement if no technical blocker |
+| Won't | Out of scope for this feature — belongs to a different module or feature |
 
 ## Elicitation Guide
 
@@ -40,9 +40,9 @@
 
 | Question | If answer is vague/insufficient | Probe |
 |----------|-------------------------------|-------|
-| Q3.1 (Must-Have) | > 10 items listed | "Si vous ne pouviez en garder que 3 pour la v1, lesquels ? Les autres sont peut-être Should-Have." |
+| Q3.1 (Must-Have) | > 10 items listed | "Si vous ne pouviez en garder que 3 à implémenter en premier, lesquels ? Les autres sont peut-être Should-Have." |
 | Q3.1 (Must-Have) | Mélange CRUD + complexe | "Le CRUD de base (liste, création, modification, suppression) est-il un Must, ou certaines actions sont Could ?" |
-| Q3.2 (Should-Have) | Vide | "Y a-t-il des fonctionnalités utiles mais qui peuvent attendre une v2 ? Export, filtres avancés, notifications ?" |
+| Q3.2 (Should-Have) | Vide | "Y a-t-il des fonctionnalités utiles mais moins critiques ? Export, filtres avancés, notifications ?" |
 | Q3.4 (limites) | Vide | "Y a-t-il des contraintes connues qui pourraient limiter le périmètre ? (budget, délai, dépendance)" |
 | Q3.5 (main flow) | < 3 étapes | "Détaillez : l'utilisateur arrive sur l'écran → que voit-il ? → que clique-t-il ? → que se passe-t-il ?" |
 | Q3.7 (alt flows) | "Il n'y en a pas" | "Que se passe-t-il si l'utilisateur annule ? S'il n'a pas la permission ? Si les données sont invalides ?" |

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

@@ -5,23 +5,14 @@
 
 ---
 
-## 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 |
-
-## 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 |
+| Q8.2 | Expected load peaks? | When + volume |
+| Q8.3 | Specific tests required? | Types |
+| Q8.4 | Overall acceptance criteria? | List |
 
 ---
 
@@ -31,8 +22,6 @@
 |--------|---------------------|
 | API response time | < 200ms (P95) |
 | Page load | < 2s |
-| Concurrent users | Per license |
-| Uptime | 99.5% |
 
 ## Elicitation Guide
 
@@ -41,16 +30,13 @@
 | Question | If answer is vague/insufficient | Probe |
 |----------|-------------------------------|-------|
 | Q8.1 (response time) | "Rapide" | "< 1 seconde ? < 200ms ? Différence acceptable entre liste et détail ?" |
-| Q8.2 (concurrent users) | "Pas beaucoup" | "Combien d'utilisateurs se connectent en même temps le matin ? Aux heures de pointe ?" |
-| Q8.3 (peaks) | "Non" | "Pas de clôture mensuelle ? Pas de période de saisie massive ? Pas d'import batch ?" |
-| Q8.4 (SLA) | "100% dispo" | "100% n'existe pas. 99.9% = ~8h d'indisponibilité/an. 99.5% est le standard de la plateforme." |
-| Q8.6 (tests) | "Tests normaux" | "Tests unitaires ? Intégration ? E2E ? Tests de charge ? Tests de sécurité (OWASP) ?" |
-| Q8.8 (acceptance) | Vide | "Quels critères pour que le PO valide la livraison ? Performance, fonctionnel, UX ?" |
+| Q8.2 (peaks) | "Non" | "Pas de clôture mensuelle ? Pas de période de saisie massive ? Pas d'import batch ?" |
+| Q8.3 (tests) | "Tests normaux" | "Tests unitaires ? Intégration ? E2E ? Tests de charge ? Tests de sécurité (OWASP) ?" |
+| Q8.4 (acceptance) | Vide | "Quels critères pour que le PO valide la livraison ? Performance, fonctionnel, UX ?" |
 
 ### Anti-patterns to Detect
 
 | Signal | Anti-pattern | Action |
 |--------|-------------|--------|
-| SLA irréaliste (100%, < 10ms) | **Exigences impossibles** | Rappeler les seuils de la plateforme et le coût de chaque 9 supplémentaire |
 | Aucune mention de volume de données | **Scalabilité non planifiée** | "Avec 1M de lignes dans 2 ans, la recherche sera-t-elle toujours performante ?" |
 | Pas de tests mentionnés | **Qualité non vérifiable** | Au minimum : tests unitaires services + tests intégration API |

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

@@ -14,15 +14,6 @@
 | 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 |
-
 ---
 
 ## Platform Constraints
@@ -45,14 +36,10 @@
 |----------|-------------------------------|-------|
 | Q9.1 (tech stack) | Propose une technologie hors plateforme | "La plateforme impose .NET 8 + React 19. Cette contrainte est-elle compatible avec votre besoin ?" |
 | Q9.2 (infrastructure) | "Cloud" sans précision | "Azure, AWS, on-premise ? Contraintes de localisation des données (pays) ?" |
-| Q9.5 (budget) | "Pas de budget défini" | "Y a-t-il un nombre de jours maximum ? Une enveloppe à ne pas dépasser ?" |
-| Q9.6 (deadline) | "Le plus vite possible" | "Y a-t-il une date métier impérative ? (réglementaire, événement, fin de contrat)" |
-| Q9.8 (approval) | "Le chef valide" | "Validation technique (code review) + validation fonctionnelle (PO) + validation sécurité (OWASP) ?" |
 
 ### Anti-patterns to Detect
 
 | Signal | Anti-pattern | Action |
 |--------|-------------|--------|
 | Technologie imposée hors stack | **Incompatibilité plateforme** | Clarifier : est-ce une intégration (OK) ou un remplacement de composant (risqué) ? |
-| Pas de deadline | **Priorité floue** | "Sans deadline, comment prioriser par rapport aux autres demandes ?" |
 | "Pas de contrainte" | **Contraintes implicites oubliées** | Multi-tenant, RGPD, audit, i18n sont des contraintes de la plateforme obligatoires |

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

@@ -14,15 +14,6 @@
 | Q10.3 | User training planned? | Plan |
 | Q10.4 | Knowledge base to create? | Scope |
 
-## 10.2 Support
-
-| # | 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 |
-
 ---
 
 ## Documentation
@@ -44,13 +35,9 @@
 | Q10.1 (user doc) | "Oui" sans détail | "Guide pas-à-pas ? FAQ ? Vidéo tutoriel ? Tooltips in-app ? Quel public cible ?" |
 | Q10.2 (tech doc) | "Non" | "Pas de documentation API ? Pas de schéma de données pour les développeurs futurs ?" |
 | Q10.3 (training) | "Pas prévu" | "Comment les utilisateurs apprendront-ils ? Formation, doc, auto-apprentissage ?" |
-| Q10.5 (support SLA) | "Support normal" | "Temps de réponse N1 attendu ? Heures ouvrées ou 24/7 ? Canal (email, ticket, chat) ?" |
-| Q10.8 (monitoring) | "Non" | "Pas d'alerte si le service est down ? Pas de suivi des erreurs (Application Insights) ?" |
 
 ### Anti-patterns to Detect
 
 | Signal | Anti-pattern | Action |
 |--------|-------------|--------|
 | "La doc se fera après" | **Documentation en dette** | Le FRD EST la doc. `/business-analyse:6-doc-html` la génère automatiquement. |
-| Aucun monitoring prévu | **Angle mort opérationnel** | Au minimum : health check endpoint + Application Insights |
-| Support = "le développeur" | **Pas de séparation N1/N2** | N1 = support fonctionnel (utilisateur), N2 = support technique (dev) |