smart-spec-kit-mcp 2.1.1 → 2.1.2

package/README.md

@@ -8,7 +8,7 @@ Plateforme d'orchestration automatisée pour le **développement piloté par les
 ## ✨ Fonctionnalités
 
 - **🤖 Commandes Naturelles**: Utilisez `speckit: spec`, `speckit: plan`, etc. directement dans Copilot Chat
-- **📝 Prompt-as-Code**: Prompts versionnés et personnalisables dans `.spec-kit/prompts/`
+- **📝 Prompts Versionnés**: Prompts personnalisables et versionnables dans `.spec-kit/prompts/`
 - **🔄 Workflows YAML**: Processus personnalisables étape par étape
 - **📋 Templates**: Spécifications fonctionnelles, plans d'implémentation, rapports de bugs
 - **🛡️ Gouvernance Intégrée**: Constitution projet, principes de développement
@@ -26,6 +26,7 @@ npx smart-spec-kit-mcp setup
 ```
 
 Cette commande configure automatiquement:
+
 - ✅ VS Code settings.json (MCP server)
 - ✅ `.github/copilot-instructions.md` (guide Copilot)
 - ✅ `.spec-kit/` avec prompts, templates et workflows
@@ -55,7 +56,7 @@ Puis rechargez VS Code: `Ctrl+Shift+P` → "Developer: Reload Window"
 
 Après installation, votre projet contient:
 
-```
+```text
 votre-projet/
 ├── .github/
 │   └── copilot-instructions.md   # Guide Copilot sur l'utilisation de Spec-Kit
@@ -119,25 +120,25 @@ Utilisez ces phrases dans Copilot Chat pour déclencher les outils MCP:
 
 ### 2. Créer une spécification
 
-```
+```text
 speckit: spec pour un système de notifications push
 ```
 
 ### 3. Planifier l'implémentation
 
-```
+```text
 speckit: plan
 ```
 
 ### 4. Générer les tâches
 
-```
+```text
 speckit: tasks
 ```
 
 ### 5. Implémenter
 
-```
+```text
 speckit: implement
 ```
 
@@ -194,15 +195,15 @@ steps:
 
 Demandez de l'aide directement dans Copilot Chat:
 
-```
+```text
 speckit: help comment créer un nouveau workflow ?
 ```
 
-```
+```text
 speckit: help comment personnaliser les templates ?
 ```
 
-```
+```text
 speckit: help quels sont les agents disponibles ?
 ```
 
@@ -234,7 +235,8 @@ Pour récupérer automatiquement les work items:
 ```
 
 Puis utilisez:
-```
+
+```text
 speckit: spec pour le work item #12345
 ```
 

package/dist/tools/promptTools.d.ts

@@ -1,7 +1,7 @@
 /**
  * Prompt Tools for Spec-Kit
  *
- * MCP tools that load and execute prompt-as-code files from .spec-kit/prompts/
+ * MCP tools that load and execute customizable prompts from .spec-kit/prompts/
  * These tools are callable via natural language in Copilot Chat.
  */
 import type { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";

package/dist/tools/promptTools.js

@@ -1,7 +1,7 @@
 /**
  * Prompt Tools for Spec-Kit
  *
- * MCP tools that load and execute prompt-as-code files from .spec-kit/prompts/
+ * MCP tools that load and execute customizable prompts from .spec-kit/prompts/
  * These tools are callable via natural language in Copilot Chat.
  */
 import * as fs from "node:fs/promises";
@@ -89,7 +89,7 @@ The memory tool helps you enrich project context:
 
 \`\`\`
 .spec-kit/
-├── prompts/      # Prompt-as-Code files (customize behavior)
+├── prompts/      # Customizable prompts (read by MCP tools)
 ├── templates/    # Document templates (customize format)
 ├── memory/       # Project constitution (your principles)
 └── workflows/    # YAML workflows (multi-step processes)

package/dist/utils/starterKitInstaller.js

@@ -238,7 +238,7 @@ export function formatInstallReport(result, projectPath) {
     report += "├── .github/\n";
     report += "│   └── copilot-instructions.md  # Instructions for Copilot\n";
     report += "├── .spec-kit/\n";
-    report += "│   ├── prompts/             # Prompt-as-code files (read by MCP)\n";
+    report += "│   ├── prompts/             # Customizable prompts (read by MCP)\n";
     report += "│   │   ├── specify.md\n";
     report += "│   │   ├── plan.md\n";
     report += "│   │   ├── tasks.md\n";

package/docs/DOCUMENTATION.md

@@ -4,7 +4,7 @@ This is the comprehensive documentation for Spec-Kit. Copilot can read this file
 
 ## Overview
 
-Spec-Kit is an MCP (Model Context Protocol) server that provides **Prompt-as-Code** functionality for specification-driven development. It integrates with GitHub Copilot in VS Code to guide developers through creating specifications, plans, tasks, and implementation.
+Spec-Kit is an MCP (Model Context Protocol) server that provides **customizable prompts** and workflow orchestration for specification-driven development. It integrates with GitHub Copilot in VS Code to guide developers through creating specifications, plans, tasks, and implementation.
 
 ## Architecture
 
@@ -20,9 +20,9 @@ Spec-Kit is an MCP (Model Context Protocol) server that provides **Prompt-as-Cod
    - Defines command keywords and aliases
 
 3. **Prompts** (`.spec-kit/prompts/`)
-   - Prompt-as-Code files read by MCP tools
+   - Customizable prompt files read by MCP tools
    - Define behavior for each command
-   - Customizable per project
+   - Versioned and maintainable in your project
 
 4. **Templates** (`.spec-kit/templates/`)
    - Document templates for specs, plans, tasks
@@ -50,6 +50,7 @@ Spec-Kit is an MCP (Model Context Protocol) server that provides **Prompt-as-Cod
 **Triggers**: `speckit: spec`, `speckit: specify`, `créer une spec`
 
 **Parameters** (all optional):
+
 - `requirements`: What you want to build. Can be:
   - A feature description: "user authentication with email/password"
   - A user story: "As a user, I want to..."
@@ -57,13 +58,15 @@ Spec-Kit is an MCP (Model Context Protocol) server that provides **Prompt-as-Cod
 - `contextId`: ID for the specification filename
 
 **Examples**:
-```
+
+```text
 speckit: spec
 speckit: spec pour un système de notifications push
 speckit: spec user authentication with OAuth
 ```
 
 **Behavior**:
+
 1. Loads prompt from `.spec-kit/prompts/specify.md`
 2. Loads constitution from `.spec-kit/memory/constitution.md`
 3. Loads template from `.spec-kit/templates/functional-spec.md`
@@ -77,15 +80,18 @@ speckit: spec user authentication with OAuth
 **Triggers**: `speckit: plan`, `planifier`, `créer un plan`
 
 **Parameters** (all optional):
+
 - `specPath`: Path to specification file (auto-detects most recent if not provided)
 
 **Examples**:
-```
+
+```text
 speckit: plan
 speckit: plan pour la spec specs/auth-spec.md
 ```
 
 **Behavior**:
+
 1. Finds the most recent specification in `specs/`
 2. Loads prompt from `.spec-kit/prompts/plan.md`
 3. Returns context for generating the plan
@@ -98,15 +104,18 @@ speckit: plan pour la spec specs/auth-spec.md
 **Triggers**: `speckit: tasks`, `générer les tâches`, `créer les tâches`
 
 **Parameters** (all optional):
+
 - `planPath`: Path to plan file (auto-detects most recent if not provided)
 
 **Examples**:
-```
+
+```text
 speckit: tasks
 speckit: générer les tâches
 ```
 
 **Behavior**:
+
 1. Finds the most recent plan in `specs/`
 2. Loads prompt from `.spec-kit/prompts/tasks.md`
 3. Returns context for generating tasks
@@ -119,16 +128,19 @@ speckit: générer les tâches
 **Triggers**: `speckit: implement`, `implémenter`, `coder`
 
 **Parameters** (all optional):
+
 - `taskId`: Specific task ID to implement (picks next pending if not provided)
 
 **Examples**:
-```
+
+```text
 speckit: implement
 speckit: implement task 3
 speckit: implémenter la tâche 5
 ```
 
 **Behavior**:
+
 1. Loads tasks from `specs/tasks.md`
 2. Finds next pending task (or specified task)
 3. Loads prompt from `.spec-kit/prompts/implement.md`
@@ -142,16 +154,19 @@ speckit: implémenter la tâche 5
 **Triggers**: `speckit: clarify`, `clarifier`, `préciser`
 
 **Parameters** (all optional):
+
 - `specPath`: Path to specification (auto-detects if not provided)
 - `questions`: Specific questions to clarify
 
 **Examples**:
-```
+
+```text
 speckit: clarify
 speckit: clarifier les critères d'acceptation
 ```
 
 **Behavior**:
+
 1. Finds `[NEEDS CLARIFICATION]` markers
 2. Loads prompt from `.spec-kit/prompts/clarify.md`
 3. Returns targeted questions for stakeholders
@@ -163,16 +178,19 @@ speckit: clarifier les critères d'acceptation
 **Triggers**: `speckit: help`, `aide sur speckit`
 
 **Parameters** (all optional):
+
 - `topic`: Specific topic to get help on
 
 **Examples**:
-```
+
+```text
 speckit: help
 speckit: help workflows
 speckit: help comment créer un template ?
 ```
 
 **Topics covered**:
+
 - Commands and usage
 - Customization (prompts, templates, workflows)
 - Troubleshooting
@@ -185,6 +203,7 @@ speckit: help comment créer un template ?
 **Triggers**: `speckit: memory`, `enrichir la mémoire`, `ajouter au contexte`
 
 **Parameters** (all optional):
+
 - `action`: Action to perform
   - `add` - Add new memory file (default)
   - `update` - Update existing memory file
@@ -195,7 +214,8 @@ speckit: help comment créer un template ?
 - `category`: Category for organizing (`decisions`, `conventions`, `architecture`, `learnings`, `context`)
 
 **Examples**:
-```
+
+```text
 speckit: memory list
 speckit: memory add decisions
 speckit: memory auto
@@ -204,6 +224,7 @@ speckit: memory ajouter une décision technique
 ```
 
 **Memory Categories**:
+
 - **decisions** - Technical and architectural decisions
 - **conventions** - Coding standards and patterns
 - **architecture** - System design and structure  
@@ -212,6 +233,7 @@ speckit: memory ajouter une décision technique
 - **glossary** - Domain terms and definitions
 
 **Behavior**:
+
 1. Lists, creates, or updates files in `.spec-kit/memory/`
 2. Structures content with dates and context
 3. Auto mode analyzes conversation to extract insights
@@ -288,12 +310,14 @@ steps:
 ```
 
 **Available actions**:
+
 - `call_agent` - Call an AI agent
 - `fetch_ado` - Fetch Azure DevOps work item
 - `save_artifact` - Save to file
 - `validate` - Validate output
 
 **Available agents**:
+
 - `SpecAgent` - Writes specifications
 - `PlanAgent` - Creates plans
 - `GovAgent` - Validates governance
@@ -336,6 +360,7 @@ The constitution defines project principles. Edit `.spec-kit/memory/constitution
 ### Commands Not Working
 
 1. **Check MCP configuration** in `.vscode/settings.json`:
+
 ```json
 {
   "mcp": {
@@ -356,6 +381,7 @@ The constitution defines project principles. Edit `.spec-kit/memory/constitution
 ### Setup Not Finding Files
 
 Run setup with the project path:
+
 ```bash
 npx smart-spec-kit-mcp setup --project /path/to/project
 ```
@@ -365,6 +391,7 @@ npx smart-spec-kit-mcp setup --project /path/to/project
 1. Check files exist in `.spec-kit/prompts/`
 2. Ensure valid Markdown format
 3. Run setup again to reinstall:
+
 ```bash
 npx smart-spec-kit-mcp setup --project . --force
 ```
@@ -383,6 +410,7 @@ npx smart-spec-kit-mcp setup --project . --force
 Standard feature specification workflow.
 
 **Steps**:
+
 1. Fetch requirements
 2. Generate specification
 3. Create plan
@@ -394,6 +422,7 @@ Standard feature specification workflow.
 Complete workflow with governance.
 
 **Steps**:
+
 1. Fetch requirements
 2. Generate specification
 3. Security review
@@ -410,6 +439,7 @@ Complete workflow with governance.
 Bug fix workflow.
 
 **Steps**:
+
 1. Fetch bug report
 2. Root cause analysis
 3. Fix plan

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "smart-spec-kit-mcp",
-  "version": "2.1.1",
+  "version": "2.1.2",
   "description": "AI-driven specification platform using MCP (Model Context Protocol) for VS Code & GitHub Copilot",
   "main": "dist/index.js",
   "type": "module",

package/starter-kit/copilot-instructions.md

@@ -45,12 +45,13 @@ speckit_specify → speckit_plan → speckit_tasks → speckit_implement
 
 ```
 .spec-kit/
-├── prompts/           # Prompt-as-code files (read by MCP tools)
+├── prompts/           # Customizable prompts (define command behavior)
 │   ├── specify.md
 │   ├── plan.md
 │   ├── tasks.md
 │   ├── implement.md
-│   └── clarify.md
+│   ├── clarify.md
+│   └── memory.md
 ├── templates/         # Document templates
 │   ├── functional-spec.md
 │   ├── plan-template.md