smart-spec-kit-mcp 2.2.6 → 2.2.8

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

@@ -0,0 +1,90 @@
+````prompt
+---
+description: "Gérer les workflows Spec-Kit (lister, démarrer, statut)"
+mode: "agent"
+tools: ["mcp_spec-kit_speckit_workflow", "mcp_spec-kit_start_workflow", "mcp_spec-kit_workflow_status"]
+---
+
+# Spec-Kit: Gestion des Workflows
+
+Vous utilisez **Spec-Kit** pour gérer les workflows multi-étapes.
+
+## Instructions
+
+1. **Appeler l'outil MCP** `speckit_workflow` pour gérer les workflows
+2. **Interpréter les arguments** fournis par l'utilisateur
+
+```
+$ARGUMENTS
+```
+
+## Actions disponibles
+
+### Lister les workflows
+```
+action: "list"
+```
+
+Affiche tous les workflows disponibles (locaux et intégrés).
+
+### Démarrer un workflow
+```
+action: "start"
+workflow_name: "feature-standard"
+context_id: "MonFeature"      # Optionnel
+auto: false                    # Optionnel (true = automatique)
+```
+
+Démarre un workflow multi-étapes. Le workflow guide automatiquement à travers les étapes.
+
+### Vérifier le statut
+```
+action: "status"
+```
+
+Affiche l'état du workflow actif (étape en cours, actions complétées).
+
+## Workflows intégrés
+
+| Workflow | Description |
+|----------|-------------|
+| `feature-quick` | Feature rapide (léger, sans breakdown de tâches) |
+| `feature-standard` | Feature standard (spec → plan → tasks → implement) |
+| `feature-full` | Feature complète avec validation et tests |
+| `bugfix` | Correction de bug avec reproduction |
+
+## Exemples d'utilisation
+
+### Utilisateur : "speckit: workflow list"
+→ Appeler `speckit_workflow` avec `action: "list"`
+
+### Utilisateur : "speckit: workflow start feature-standard"
+→ Appeler `speckit_workflow` avec `action: "start"`, `workflow_name: "feature-standard"`
+
+### Utilisateur : "speckit: workflow start feature-full MyFeature auto"
+→ Appeler `speckit_workflow` avec:
+- `action: "start"`
+- `workflow_name: "feature-full"`
+- `context_id: "MyFeature"`
+- `auto: true`
+
+### Utilisateur : "speckit: workflow status"
+→ Appeler `speckit_workflow` avec `action: "status"`
+
+## Mode automatique
+
+Par défaut, les workflows demandent une approbation à chaque étape. 
+
+En mode automatique (`auto: true`), le workflow s'exécute sans interruption.
+
+## Workflow typique
+
+```
+specify → plan → tasks → implement
+    ↑
+  clarify (si nécessaire)
+```
+
+Les workflows orchestrent ces commandes automatiquement.
+
+````

package/starter-kit/templates/bugfix-report.md

@@ -14,9 +14,11 @@ severity: "[Critical/High/Medium/Low]"
 ## 1. Bug Summary
 
 ### 1.1 Description
+
 [TO FILL: Clear, concise description of the bug]
 
 ### 1.2 Impact
+
 - **Severity**: [Critical/High/Medium/Low]
 - **Affected Users**: [TO FILL: Who is affected]
 - **Business Impact**: [TO FILL: How this affects the business]
@@ -26,6 +28,7 @@ severity: "[Critical/High/Medium/Low]"
 ## 2. Reproduction
 
 ### 2.1 Environment
+
 | Component | Value |
 |-----------|-------|
 | OS | [TO FILL] |
@@ -33,18 +36,22 @@ severity: "[Critical/High/Medium/Low]"
 | Version | [TO FILL] |
 
 ### 2.2 Steps to Reproduce
+
 1. [TO FILL: Step 1]
 2. [TO FILL: Step 2]
 3. [TO FILL: Step 3]
 
 ### 2.3 Expected Behavior
+
 [TO FILL: What should happen]
 
 ### 2.4 Actual Behavior
+
 [TO FILL: What actually happens]
 
 ### 2.5 Evidence
-```
+
+```text
 [TO FILL: Error messages, logs, screenshots]
 ```
 
@@ -53,13 +60,16 @@ severity: "[Critical/High/Medium/Low]"
 ## 3. Root Cause Analysis
 
 ### 3.1 Investigation
+
 [TO FILL: What was investigated and findings]
 
 ### 3.2 Root Cause
+
 [TO FILL: The underlying cause of the bug]
 
 ### 3.3 Related Code
-```
+
+```text
 File: [path/to/file]
 Line: [line numbers]
 ```
@@ -69,14 +79,17 @@ Line: [line numbers]
 ## 4. Fix Proposal
 
 ### 4.1 Solution
+
 [TO FILL: Proposed fix approach]
 
 ### 4.2 Changes Required
+
 | File | Change |
 |------|--------|
 | [TO FILL] | [TO FILL] |
 
 ### 4.3 Risks
+
 - [TO FILL: Any risks with the proposed fix]
 
 ---
@@ -84,12 +97,14 @@ Line: [line numbers]
 ## 5. Testing
 
 ### 5.1 Test Cases
+
 | ID | Scenario | Expected Result |
 |----|----------|-----------------|
 | TC-001 | [TO FILL: Original bug scenario] | Bug no longer occurs |
 | TC-002 | [TO FILL: Regression test] | Existing functionality intact |
 
 ### 5.2 Verification Steps
+
 1. [TO FILL: How to verify the fix]
 2. [TO FILL: Regression testing steps]
 
@@ -98,12 +113,14 @@ Line: [line numbers]
 ## 6. Deployment
 
 ### 6.1 Deployment Plan
+
 - [ ] Code review completed
 - [ ] Tests passing
 - [ ] Staging verification
 - [ ] Production deployment
 
 ### 6.2 Rollback Plan
+
 [TO FILL: How to rollback if issues occur]
 
 ---
@@ -111,6 +128,7 @@ Line: [line numbers]
 ## 7. Post-Mortem (Optional)
 
 ### 7.1 Timeline
+
 | Time | Event |
 |------|-------|
 | [TO FILL] | Bug reported |
@@ -119,9 +137,11 @@ Line: [line numbers]
 | [TO FILL] | Fix deployed |
 
 ### 7.2 Lessons Learned
+
 - [TO FILL: What can we improve to prevent similar issues]
 
 ### 7.3 Action Items
+
 | Item | Owner | Due Date |
 |------|-------|----------|
 | [TO FILL] | [TO FILL] | [TO FILL] |

package/starter-kit/templates/functional-spec.md

@@ -14,16 +14,21 @@ last_updated: "[TO FILL: Date]"
 ## 1. Overview
 
 ### 1.1 Purpose
+
 [TO FILL: Brief description of the feature's purpose and the problem it solves]
 
 ### 1.2 Scope
+
 **In Scope:**
+
 - [TO FILL: What is included]
 
 **Out of Scope:**
+
 - [TO FILL: What is explicitly excluded]
 
 ### 1.3 Background
+
 [TO FILL: Context and history leading to this feature request]
 
 ---
@@ -79,6 +84,7 @@ Feature: [TO FILL: Feature Name]
 ### 4.1 User Personas
 
 **Persona 1: [TO FILL: Name]**
+
 - Role: [TO FILL]
 - Goals: [TO FILL]
 - Pain Points: [TO FILL]
@@ -92,7 +98,7 @@ Feature: [TO FILL: Feature Name]
 
 ### 4.3 User Flow
 
-```
+```text
 [TO FILL: Describe or link to user flow diagram]
 ┌─────────┐    ┌─────────┐    ┌─────────┐
 │ Step 1  │───▶│ Step 2  │───▶│ Step 3  │
@@ -104,12 +110,15 @@ Feature: [TO FILL: Feature Name]
 ## 5. Technical Considerations
 
 ### 5.1 Dependencies
+
 - [TO FILL: External systems, services, or components this feature depends on]
 
 ### 5.2 Constraints
+
 - [TO FILL: Technical or business constraints]
 
 ### 5.3 Data Requirements
+
 - [TO FILL: Data entities, storage, and access patterns]
 
 ---
@@ -117,11 +126,13 @@ Feature: [TO FILL: Feature Name]
 ## 6. Assumptions & Risks
 
 ### 6.1 Assumptions
+
 | ID | Assumption | Impact if Wrong |
 |----|------------|-----------------|
 | A-001 | [TO FILL] | [TO FILL] |
 
 ### 6.2 Risks
+
 | ID | Risk | Probability | Impact | Mitigation |
 |----|------|-------------|--------|------------|
 | R-001 | [TO FILL] | Medium | High | [TO FILL] |

package/starter-kit/templates/plan-template.md

@@ -9,6 +9,7 @@
 ## Technical Context
 
 ### Tech Stack
+
 | Component | Technology | Version |
 |-----------|------------|---------|
 | Language | [TO FILL] | |
@@ -18,7 +19,7 @@
 
 ### Architecture Overview
 
-```
+```text
 [TO FILL: ASCII diagram or description of architecture]
 
 ┌─────────────┐    ┌─────────────┐    ┌─────────────┐
@@ -50,6 +51,7 @@ tests/
 ## Implementation Phases
 
 ### Phase 0: Research & Design
+
 **Duration**: [X days]
 **Output**: research.md, data-model.md
 
@@ -59,6 +61,7 @@ tests/
 - [ ] Define API contracts
 
 ### Phase 1: Foundation
+
 **Duration**: [X days]
 **Dependencies**: Phase 0
 
@@ -68,6 +71,7 @@ tests/
 - [ ] Set up database schema
 
 ### Phase 2: Core Implementation
+
 **Duration**: [X days]
 **Dependencies**: Phase 1
 
@@ -76,6 +80,7 @@ tests/
 - [ ] Add unit tests
 
 ### Phase 3: Integration & Polish
+
 **Duration**: [X days]
 **Dependencies**: Phase 2
 

package/starter-kit/templates/tasks-template.md

@@ -8,11 +8,12 @@
 
 ## Task Format
 
-```
+```text
 - [ ] T### [P?] [Story?] Description - `path/to/file.ext`
 ```
 
 **Legend**:
+
 - `T###`: Task ID (sequential)
 - `[P]`: Can be executed in parallel with other `[P]` tasks in same phase
 - `[Story?]`: Associated user story ID (optional)
@@ -107,7 +108,7 @@
 
 ## Dependencies & Execution Order
 
-```
+```text
 Phase 1 (Setup)
     │
     ▼
@@ -129,7 +130,7 @@ Phase 3 (US-1)  Phase 4 (US-2)  Phase 5 (US-3)  ← Can run in parallel
 
 Tasks marked `[P]` within the same phase can run simultaneously:
 
-```
+```text
 Phase 3, Story 1:
 ├── T010 Create model (sequential - others depend on this)
 │