smart-spec-kit-mcp 2.2.7 → 2.2.9

package/starter-kit/github-prompts/speckit.help.prompt.md

@@ -1,46 +1,73 @@
+````prompt
 ---
-description: "Obtenir de l'aide sur l'utilisation de Spec-Kit"
+description: "Afficher l'aide et les commandes Spec-Kit disponibles"
 mode: "agent"
 tools: ["mcp_spec-kit_speckit_help"]
 ---
 
 # Spec-Kit: Aide
 
-Vous utilisez **Spec-Kit** pour obtenir de l'aide sur le framework.
-
-## Instructions
-
-Appelez l'outil MCP `speckit_help` pour obtenir de l'aide.
+## Arguments utilisateur
 
 ```
 $ARGUMENTS
 ```
 
-## Sujets d'aide disponibles
+## Instructions
 
-- **workflows** : Comment créer et personnaliser des workflows
-- **templates** : Comment utiliser et personnaliser les templates
-- **prompts** : Comment modifier les prompts des commandes
-- **customization** : Personnalisation avancée de Spec-Kit
-- **troubleshooting** : Résolution de problèmes courants
+Affiche l'aide Spec-Kit. Si un sujet est fourni, donne des détails sur ce sujet.
 
-## Commandes Spec-Kit
+## 🚀 Commandes Slash Disponibles
 
-| Commande | Description |
+| Commande | Description | Exemple |
+|----------|-------------|---------|
+| `/speckit.specify` | Créer une spécification | `/speckit.specify système de login` |
+| `/speckit.plan` | Créer un plan d'implémentation | `/speckit.plan` |
+| `/speckit.tasks` | Générer les tâches | `/speckit.tasks` |
+| `/speckit.implement` | Implémenter les tâches | `/speckit.implement` ou `/speckit.implement task 3` |
+| `/speckit.clarify` | Clarifier les exigences | `/speckit.clarify` |
+| `/speckit.validate` | Valider conformité (sécurité, RGPD) | `/speckit.validate security` |
+| `/speckit.memory` | Gérer la mémoire projet | `/speckit.memory list` |
+| `/speckit.workflow` | Démarrer un workflow automatisé | `/speckit.workflow feature-standard` |
+| `/speckit.help` | Cette aide | `/speckit.help workflows` |
+
+## 📋 Workflows Automatisés
+
+| Workflow | Description |
 |----------|-------------|
-| `/speckit.specify` | Créer une spécification |
-| `/speckit.plan` | Créer un plan d'implémentation |
-| `/speckit.tasks` | Générer les tâches |
-| `/speckit.implement` | Implémenter les tâches |
-| `/speckit.clarify` | Clarifier les exigences |
-| `/speckit.validate` | Valider la conformité |
-| `/speckit.memory` | Gérer la mémoire projet |
-| `/speckit.help` | Cette aide |
+| `feature-quick` | Rapide: spec → implement |
+| `feature-standard` | Standard: spec → plan → tasks → implement |
+| `feature-full` | Complet avec validations sécurité/RGPD |
+| `bugfix` | Correction de bug |
+
+**Usage:** `/speckit.workflow feature-standard Mon Feature`
 
-## Workflow typique
+## 🔄 Workflow Typique
 
 ```
 specify → plan → tasks → implement
     ↑
   clarify (si nécessaire)
 ```
+
+## 📁 Structure du Projet
+
+```
+.spec-kit/
+├── prompts/      # Personnaliser les commandes
+├── templates/    # Templates des documents
+├── memory/       # Constitution projet
+├── rules/        # Règles de validation
+└── workflows/    # Workflows custom
+specs/            # Specs générées
+```
+
+## 🎯 Sujets d'Aide
+
+- **workflows** : Créer et personnaliser des workflows
+- **templates** : Utiliser et modifier les templates
+- **prompts** : Modifier le comportement des commandes
+- **customization** : Personnalisation avancée
+- **troubleshooting** : Résolution de problèmes
+
+````

package/starter-kit/github-prompts/speckit.workflow.prompt.md

@@ -0,0 +1,48 @@
+````prompt
+---
+description: "Démarrer un workflow Spec-Kit automatisé"
+mode: "agent"
+tools: ["mcp_spec-kit_start_workflow", "mcp_spec-kit_workflow_status", "mcp_spec-kit_abort_workflow"]
+---
+
+# Spec-Kit: Workflows
+
+Démarre un workflow automatisé multi-étapes.
+
+## Arguments utilisateur
+
+```
+$ARGUMENTS
+```
+
+## Comment interpréter
+
+1. **Si l'utilisateur donne un nom de workflow** → Démarrer ce workflow avec `start_workflow`
+2. **Si l'utilisateur dit "list"** → Lister les workflows disponibles
+3. **Si l'utilisateur dit "status"** → Vérifier le statut avec `workflow_status`
+4. **Si l'utilisateur dit "stop" ou "abort"** → Annuler avec `abort_workflow`
+
+## Workflows disponibles
+
+| Nom | Description |
+|-----|-------------|
+| `feature-quick` | Quick win (spec → implement) |
+| `feature-standard` | Standard (spec → plan → tasks → implement) |
+| `feature-full` | Avec validations sécurité/RGPD |
+| `bugfix` | Correction de bug |
+
+## Exemples
+
+- `/speckit.workflow feature-standard Multi-View` → `start_workflow` avec `workflow_name="feature-standard"`, `context_id="Multi-View"`
+- `/speckit.workflow list` → Afficher la liste des workflows
+- `/speckit.workflow status` → Vérifier le statut
+
+## Simplification
+
+Si l'utilisateur tape juste un nom de workflow sans "start":
+- `/speckit.workflow feature-standard` → Démarrer feature-standard
+- `/speckit.workflow bugfix` → Démarrer bugfix
+
+Le texte après le nom du workflow devient le `context_id`.
+
+````

package/starter-kit/workflows/feature-full.yaml

@@ -1,17 +1,17 @@
-# Full Feature Workflow with Governance
-# Complete workflow with all validation checkpoints
+# Feature Full Workflow
+# Complete workflow with validation checkpoints
 
 name: feature-full
-displayName: "Feature with Full Governance"
-description: "Complete feature workflow including RGPD, Security, Architecture, Design System, and Testing validations"
+displayName: "Feature with Validation"
+description: "Complete feature workflow with security and RGPD validations"
 
 metadata:
-  version: "1.0"
+  version: "2.0"
   author: "Spec-Kit"
   tags:
     - feature
     - governance
-    - enterprise
+    - validation
 
 template: functional-spec.md
 defaultAgent: SpecAgent
@@ -20,86 +20,40 @@ steps:
   # ═══════════════════════════════════════════════════════════════
   # PHASE 1: SPECIFICATION
   # ═══════════════════════════════════════════════════════════════
-  
-  - id: fetch-requirements
-    name: "1.1 Fetch Requirements"
-    action: fetch_ado
-    description: |
-      Retrieve the Feature work item and all linked items from Azure DevOps.
-      
-      Extract:
-      - Title and description
-      - Acceptance criteria
-      - Parent Epic context
-      - Linked User Stories
-      - Attachments (mockups, documents)
-    outputs:
-      - workitem_data
-      - linked_items
-      - attachments
 
-  - id: write-spec
-    name: "1.2 Write Functional Specification"
+  - id: create-spec
+    name: "1. Create Specification"
     action: call_agent
     agent: SpecAgent
     description: |
-      Generate a comprehensive functional specification including:
+      Create a comprehensive functional specification.
       
-      **Functional Requirements**
+      Include:
+      - Feature summary and objectives
       - User stories with acceptance criteria
-      - Business rules
+      - Functional requirements
+      - Non-functional requirements
       - Data requirements
+      - Dependencies and constraints
       
-      **Non-Functional Requirements**
-      - Performance targets
-      - Availability requirements
-      - Scalability needs
-      
-      Mark uncertain sections with [TO FILL] for human review.
+      Mark unclear sections with [NEEDS CLARIFICATION] for review.
     inputs:
-      source: "workitem_data"
+      - name: requirements
+        description: "Feature description from user"
+        required: true
     outputs:
-      - functional_spec
+      - spec_document
 
   # ═══════════════════════════════════════════════════════════════
-  # PHASE 2: VALIDATION GATES
+  # PHASE 2: VALIDATION
   # ═══════════════════════════════════════════════════════════════
 
-  - id: rgpd-review
-    name: "2.1 🛡️ RGPD Compliance Review"
-    action: review
-    agent: GovAgent
-    description: |
-      Validate GDPR/RGPD compliance:
-      
-      **Data Collection**
-      - [ ] Personal data identified and documented
-      - [ ] Legal basis for processing defined
-      - [ ] Data minimization principle applied
-      
-      **User Rights**
-      - [ ] Right to access implemented
-      - [ ] Right to rectification supported
-      - [ ] Right to erasure (RTBF) supported
-      - [ ] Data portability considered
-      
-      **Security & Governance**
-      - [ ] Data retention period defined
-      - [ ] Third-party processors identified
-      - [ ] Privacy by design applied
-      - [ ] DPIA required? (if high risk)
-    inputs:
-      spec: "functional_spec"
-    outputs:
-      - rgpd_report
-      - rgpd_status
-
   - id: security-review
-    name: "2.2 🔒 Security Review"
+    name: "2.1 🔒 Security Review"
     action: review
     agent: GovAgent
     description: |
-      Security assessment checklist:
+      Security assessment based on the specification:
       
       **Authentication & Authorization**
       - [ ] Auth mechanism defined
@@ -107,238 +61,109 @@ steps:
       - [ ] Session management
       
       **Data Protection**
-      - [ ] Encryption at rest
-      - [ ] Encryption in transit (TLS)
+      - [ ] Encryption requirements
       - [ ] Sensitive data handling
       
       **Input/Output Security**
       - [ ] Input validation strategy
       - [ ] Output encoding
-      - [ ] SQL injection prevention
-      - [ ] XSS prevention
-      - [ ] CSRF protection
+      - [ ] Injection prevention
       
-      **Infrastructure**
-      - [ ] Secrets management
-      - [ ] Logging (without PII)
-      - [ ] Rate limiting
-      - [ ] DDoS considerations
+      Identify any security concerns and recommendations.
     inputs:
-      spec: "functional_spec"
+      spec: "spec_document"
     outputs:
       - security_report
-      - security_status
 
-  - id: architecture-review
-    name: "2.3 🏗️ Architecture Review"
-    action: review
-    agent: GovAgent
-    description: |
-      Architecture validation:
-      
-      **Consistency**
-      - [ ] Aligns with existing architecture
-      - [ ] Follows established patterns
-      - [ ] Uses approved technologies
-      
-      **Quality Attributes**
-      - [ ] Scalability addressed
-      - [ ] Performance requirements met
-      - [ ] Reliability/Availability design
-      - [ ] Maintainability considered
-      
-      **Technical Debt**
-      - [ ] No unnecessary complexity
-      - [ ] Reuses existing components
-      - [ ] Technical debt acceptable
-      
-      **Integration**
-      - [ ] API contracts defined
-      - [ ] Event/message schemas
-      - [ ] Database changes documented
-    inputs:
-      spec: "functional_spec"
-    outputs:
-      - architecture_report
-      - architecture_status
-
-  - id: design-review
-    name: "2.4 🎨 Design System Review"
+  - id: rgpd-review
+    name: "2.2 🛡️ RGPD Review"
     action: review
     agent: GovAgent
     description: |
-      Design System compliance (if UI involved):
+      GDPR/RGPD compliance check:
       
-      **Components**
-      - [ ] Uses Design System components
-      - [ ] No unauthorized custom components
-      - [ ] Proper component composition
-      
-      **Visual Consistency**
-      - [ ] Color tokens used correctly
-      - [ ] Typography follows guidelines
-      - [ ] Spacing uses standard scale
-      - [ ] Icons from approved library
-      
-      **Accessibility (WCAG 2.1 AA)**
-      - [ ] Color contrast ratios
-      - [ ] Keyboard navigation
-      - [ ] Screen reader support
-      - [ ] Focus indicators
+      **Data Collection**
+      - [ ] Personal data identified
+      - [ ] Legal basis for processing
+      - [ ] Data minimization applied
       
-      **Responsive Design**
-      - [ ] Mobile breakpoints defined
-      - [ ] Touch targets adequate
-      - [ ] Dark mode support (if applicable)
+      **User Rights**
+      - [ ] Right to access
+      - [ ] Right to rectification
+      - [ ] Right to erasure
+      
+      **Governance**
+      - [ ] Data retention period
+      - [ ] Third-party processors
+      - [ ] Privacy by design
     inputs:
-      spec: "functional_spec"
+      spec: "spec_document"
     outputs:
-      - design_report
-      - design_status
+      - rgpd_report
 
   # ═══════════════════════════════════════════════════════════════
-  # PHASE 3: TECHNICAL PLANNING
+  # PHASE 3: PLANNING
   # ═══════════════════════════════════════════════════════════════
 
-  - id: technical-plan
-    name: "3.1 Technical Planning"
+  - id: create-plan
+    name: "3. Create Implementation Plan"
     action: call_agent
     agent: PlanAgent
     description: |
-      Create detailed technical plan:
+      Create a detailed implementation plan incorporating validation feedback.
       
-      **Architecture Decisions**
+      Include:
+      - Technical approach
       - Components to create/modify
-      - Database schema changes
-      - API endpoints
-      - Integration points
-      
-      **Task Breakdown**
-      - Granular tasks (1-3 days each)
-      - Clear acceptance criteria
-      - Dependencies mapped
-      - Effort estimates (S/M/L/XL)
-      
-      **Risk Mitigation**
-      - Technical risks identified
-      - Mitigation strategies
-      - Spike tasks if needed
-    inputs:
-      spec: "functional_spec"
-      reviews: ["rgpd_report", "security_report", "architecture_report"]
-    outputs:
-      - technical_plan
-      - task_list
-
-  - id: test-strategy
-    name: "3.2 🧪 Test Strategy"
-    action: call_agent
-    agent: TestAgent
-    description: |
-      Define comprehensive test strategy:
-      
-      **Unit Tests**
-      - Critical business logic
-      - Edge cases
-      - Error handling
-      - Target: >80% coverage
-      
-      **Integration Tests**
-      - API contracts
-      - Database operations
-      - External service mocks
-      
-      **E2E Tests**
-      - Critical user journeys
-      - Happy path scenarios
-      - Key error scenarios
-      
-      **Non-Functional Tests**
-      - Performance benchmarks
-      - Load testing thresholds
-      - Security scan requirements
+      - Security measures to implement
+      - RGPD compliance measures
+      - Dependencies and order
+      - Risk assessment
     inputs:
-      spec: "functional_spec"
-      plan: "technical_plan"
+      spec: "spec_document"
+      reviews: ["security_report", "rgpd_report"]
     outputs:
-      - test_strategy
-      - test_cases
+      - plan_document
 
   # ═══════════════════════════════════════════════════════════════
-  # PHASE 4: DOCUMENTATION & FINALIZATION
+  # PHASE 4: TASKS
   # ═══════════════════════════════════════════════════════════════
 
-  - id: documentation
-    name: "4.1 📚 Documentation Plan"
-    action: generate_content
+  - id: generate-tasks
+    name: "4. Generate Tasks"
+    action: call_agent
+    agent: PlanAgent
     description: |
-      Identify documentation needs:
-      
-      **User Documentation**
-      - [ ] User guide updates
-      - [ ] FAQ additions
-      - [ ] Tutorial/walkthrough
+      Break down the plan into atomic tasks.
       
-      **Technical Documentation**
-      - [ ] API documentation
-      - [ ] Architecture Decision Record (ADR)
-      - [ ] Runbook updates
-      - [ ] README updates
-      
-      **Release Documentation**
-      - [ ] Changelog entry
-      - [ ] Release notes
-      - [ ] Migration guide (if breaking changes)
+      Each task should:
+      - Be completable in 1-2 hours
+      - Have clear acceptance criteria
+      - Include security/RGPD considerations
+      - Be independently testable
     inputs:
-      spec: "functional_spec"
-      plan: "technical_plan"
+      source: "plan_document"
     outputs:
-      - documentation_plan
+      - tasks_document
 
-  - id: final-approval
-    name: "4.2 ✅ Final Approval Gate"
-    action: review
-    agent: GovAgent
-    description: |
-      Final checklist before development starts:
-      
-      **Specification**
-      - [ ] Functional spec complete and approved
-      - [ ] All [TO FILL] sections resolved
-      - [ ] Stakeholder sign-off obtained
-      
-      **Compliance**
-      - [ ] RGPD review: PASSED
-      - [ ] Security review: PASSED
-      - [ ] Architecture review: PASSED
-      - [ ] Design review: PASSED (if applicable)
-      
-      **Planning**
-      - [ ] Technical plan approved
-      - [ ] Tasks created in ADO
-      - [ ] Test strategy defined
-      - [ ] Documentation plan ready
-      
-      **Ready for Development** ✅
-    inputs:
-      all_artifacts: true
-    outputs:
-      - final_approval
-      - development_ready
+  # ═══════════════════════════════════════════════════════════════
+  # PHASE 5: IMPLEMENTATION
+  # ═══════════════════════════════════════════════════════════════
 
-  - id: create-tasks
-    name: "4.3 Create ADO Work Items"
-    action: create_file
+  - id: implement
+    name: "5. Implement"
+    action: call_agent
+    agent: SpecAgent
     description: |
-      Generate Azure DevOps work items:
-      - Create Tasks from technical plan
-      - Link to parent Feature
-      - Set estimates and priorities
-      - Assign to sprint
-      
-      Output format ready for ADO import or manual creation.
+      Implement the tasks following security and RGPD guidelines.
+      
+      For each task:
+      - Implement following project conventions
+      - Apply security measures
+      - Ensure RGPD compliance
+      - Write appropriate tests
+      - Update task status when complete
     inputs:
-      tasks: "task_list"
-      feature_id: "context_id"
+      source: "tasks_document"
     outputs:
-      - ado_work_items
+      - implementation