smart-spec-kit-mcp 2.2.4 → 2.2.6

package/starter-kit/copilot-instructions.md

@@ -127,37 +127,37 @@ For multi-step automation, use `start_workflow`:
 
 ## Example Interactions
 
-**User**: "speckit: créer une spec pour un système de notifications push"
+**User**: `/speckit.specify pour un système de notifications push`
 **Action**: Call `speckit_specify` with `requirements: "système de notifications push"`
 
-**User**: "speckit: planifier l'implémentation"  
+**User**: `/speckit.plan`  
 **Action**: Call `speckit_plan` (will find the most recent spec automatically)
 
-**User**: "speckit: implement task 3"
+**User**: `/speckit.implement task 3`
 **Action**: Call `speckit_implement` with `taskId: "3"`
 
-**User**: "speckit: memory list"
+**User**: `/speckit.memory list`
 **Action**: Call `speckit_memory` with `action: "list"`
 
-**User**: "speckit: memory ajouter une décision technique"
+**User**: `/speckit.memory ajouter une décision technique`
 **Action**: Call `speckit_memory` with `action: "add"`, `category: "decisions"`
 
-**User**: "speckit: memory auto"
+**User**: `/speckit.memory auto`
 **Action**: Call `speckit_memory` with `action: "auto"` to auto-enrich from context
 
-**User**: "speckit: validate security"
+**User**: `/speckit.validate security`
 **Action**: Call `speckit_validate` with `ruleType: "security"`
 
-**User**: "speckit: valider la conformité RGPD de la spec"
+**User**: `/speckit.validate rgpd phase=spec`
 **Action**: Call `speckit_validate` with `ruleType: "rgpd"`, `phase: "spec"`
 
-**User**: "speckit: validate architecture-rules"
+**User**: `/speckit.validate architecture-rules`
 **Action**: Call `speckit_validate` with `ruleType: "architecture"` (uses custom rules file)
 
-**User**: "speckit: start_workflow workflow_name="feature-standard" PiP Support auto=true"
+**User**: `speckit: start_workflow workflow_name="feature-standard" PiP Support auto=true`
 **Action**: Call `start_workflow` with `workflow_name: "feature-standard"`, `context_id: "PiP Support"`, `auto: true`
 
-**User**: "speckit: help comment créer un nouveau workflow ?"
+**User**: `/speckit.help comment créer un nouveau workflow ?`
 **Action**: Call `speckit_help` with `topic: "workflows"`
 
 **User**: "Comment fonctionne spec-kit ?"

package/templates/bugfix-report.md

@@ -1,184 +0,0 @@
----
-title: "[TO FILL: Bug Title]"
-workitem_id: "[TO FILL]"
-type: Bug Fix Report
-version: "1.0"
-status: Draft
-author: "[TO FILL]"
-created: "[TO FILL: Date]"
-severity: "[TO FILL: Critical/High/Medium/Low]"
-azure_devops_link: "[TO FILL: Link to ADO Bug]"
----
-
-# Bug Fix Report: [TO FILL: Bug Title]
-
-## 1. Bug Summary
-
-| Field | Value |
-|-------|-------|
-| **Bug ID** | [TO FILL] |
-| **Severity** | [TO FILL: Critical/High/Medium/Low] |
-| **Priority** | [TO FILL: P1/P2/P3/P4] |
-| **Reported By** | [TO FILL] |
-| **Reported Date** | [TO FILL] |
-| **Environment** | [TO FILL: Production/Staging/Dev] |
-| **Affected Version** | [TO FILL] |
-
----
-
-## 2. Problem Description
-
-### 2.1 Expected Behavior
-
-[TO FILL: What should happen]
-
-### 2.2 Actual Behavior
-
-[TO FILL: What actually happens]
-
-### 2.3 Reproduction Steps
-
-1. [TO FILL: Step 1]
-2. [TO FILL: Step 2]
-3. [TO FILL: Step 3]
-4. [TO FILL: Observe error]
-
-### 2.4 Error Details
-
-```
-[TO FILL: Error message, stack trace, logs]
-```
-
-### 2.5 Screenshots/Evidence
-
-[TO FILL: Attach or link screenshots]
-
----
-
-## 3. Impact Assessment
-
-### 3.1 User Impact
-
-| Aspect | Assessment |
-|--------|------------|
-| Users Affected | [TO FILL: All/Subset/Specific role] |
-| Frequency | [TO FILL: Always/Sometimes/Rare] |
-| Workaround Available | [TO FILL: Yes/No] |
-| Business Impact | [TO FILL: Description] |
-
-### 3.2 Affected Components
-
-- [ ] Frontend
-- [ ] Backend API
-- [ ] Database
-- [ ] External Service
-- [ ] Infrastructure
-
-Component details: [TO FILL]
-
----
-
-## 4. Root Cause Analysis
-
-### 4.1 Investigation Summary
-
-[TO FILL: Summary of investigation steps taken]
-
-### 4.2 Root Cause
-
-[TO FILL: Identified root cause of the bug]
-
-### 4.3 Why It Wasn't Caught
-
-[TO FILL: Gap in testing/review that allowed this bug]
-
----
-
-## 5. Fix Proposal
-
-### 5.1 Proposed Solution
-
-[TO FILL: Description of the fix]
-
-### 5.2 Files/Components to Modify
-
-| File/Component | Change Type | Description |
-|----------------|-------------|-------------|
-| [TO FILL] | Modify | [TO FILL] |
-| [TO FILL] | Add | [TO FILL] |
-
-### 5.3 Risk Assessment
-
-| Risk | Probability | Impact | Mitigation |
-|------|-------------|--------|------------|
-| Regression in X | [TO FILL] | [TO FILL] | [TO FILL] |
-
-### 5.4 Rollback Plan
-
-[TO FILL: How to rollback if the fix causes issues]
-
----
-
-## 6. Validation Checklist
-
-### 6.1 Security Review
-
-- [ ] No new vulnerabilities introduced
-- [ ] Input validation maintained
-- [ ] No sensitive data exposure
-- [ ] Auth/Authz intact
-
-### 6.2 Testing
-
-- [ ] Unit test for bug scenario added
-- [ ] Regression tests pass
-- [ ] Manual testing completed
-- [ ] Edge cases covered
-
-### 6.3 Code Quality
-
-- [ ] Code review completed
-- [ ] No new technical debt
-- [ ] Follows coding standards
-- [ ] Documentation updated
-
----
-
-## 7. Resolution
-
-### 7.1 Fix Implementation
-
-| Field | Value |
-|-------|-------|
-| **Fix Branch** | [TO FILL] |
-| **PR Link** | [TO FILL] |
-| **Deployed To** | [TO FILL] |
-| **Deployed Date** | [TO FILL] |
-| **Verified By** | [TO FILL] |
-
-### 7.2 Lessons Learned
-
-[TO FILL: What can be improved to prevent similar bugs]
-
-### 7.3 Follow-up Actions
-
-- [ ] [TO FILL: Action item 1]
-- [ ] [TO FILL: Action item 2]
-
----
-
-## 8. Approval
-
-| Role | Name | Date | Status |
-|------|------|------|--------|
-| Developer | [TO FILL] | | ☐ Completed |
-| Code Reviewer | [TO FILL] | | ☐ Approved |
-| QA | [TO FILL] | | ☐ Verified |
-
----
-
-## Revision History
-
-| Version | Date | Author | Changes |
-|---------|------|--------|---------|
-| 1.0 | [TO FILL] | [TO FILL] | Initial report |

package/templates/functional-spec.md

@@ -1,191 +0,0 @@
----
-title: "[TO FILL: Feature Title]"
-workitem_id: "[TO FILL]"
-type: Functional Specification
-version: "1.0"
-status: Draft
-author: "[TO FILL]"
-created: "[TO FILL: Date]"
-last_updated: "[TO FILL: Date]"
-azure_devops_link: "[TO FILL: Link to ADO Work Item]"
----
-
-# Functional Specification: [TO FILL: Feature Title]
-
-## 1. Overview
-
-### 1.1 Purpose
-[TO FILL: Brief description of the feature's purpose and the problem it solves]
-
-### 1.2 Scope
-[TO FILL: What is included and explicitly excluded from this feature]
-
-### 1.3 Background
-[TO FILL: Context and history leading to this feature request]
-
----
-
-## 2. Stakeholders
-
-| Role | Name | Responsibility |
-|------|------|----------------|
-| Product Owner | [TO FILL] | Requirements validation |
-| Tech Lead | [TO FILL] | Technical decisions |
-| QA Lead | [TO FILL] | Test strategy |
-| UX Designer | [TO FILL] | User experience |
-
----
-
-## 3. Requirements
-
-### 3.1 Functional Requirements
-
-| ID | Requirement | Priority | Source |
-|----|-------------|----------|--------|
-| FR-001 | [TO FILL] | Must Have | ADO #{workitem_id} |
-| FR-002 | [TO FILL] | Should Have | |
-| FR-003 | [TO FILL] | Could Have | |
-
-### 3.2 Non-Functional Requirements
-
-| ID | Category | Requirement | Target |
-|----|----------|-------------|--------|
-| NFR-001 | Performance | [TO FILL] | [TO FILL] |
-| NFR-002 | Security | [TO FILL] | [TO FILL] |
-| NFR-003 | Availability | [TO FILL] | [TO FILL] |
-| NFR-004 | Scalability | [TO FILL] | [TO FILL] |
-
-### 3.3 Acceptance Criteria
-
-```gherkin
-Feature: [TO FILL: Feature Name]
-
-  Scenario: [TO FILL: Main Success Scenario]
-    Given [TO FILL: Initial context]
-    When [TO FILL: Action performed]
-    Then [TO FILL: Expected outcome]
-
-  Scenario: [TO FILL: Alternative Scenario]
-    Given [TO FILL]
-    When [TO FILL]
-    Then [TO FILL]
-```
-
----
-
-## 4. User Experience
-
-### 4.1 User Personas
-
-**Persona 1: [TO FILL: Name]**
-- Role: [TO FILL]
-- Goals: [TO FILL]
-- Pain Points: [TO FILL]
-
-### 4.2 User Stories
-
-| ID | As a... | I want to... | So that... |
-|----|---------|--------------|------------|
-| US-001 | [TO FILL] | [TO FILL] | [TO FILL] |
-| US-002 | [TO FILL] | [TO FILL] | [TO FILL] |
-
-### 4.3 User Flow
-
-```
-[TO FILL: Describe or link to user flow diagram]
-┌─────────┐    ┌─────────┐    ┌─────────┐
-│ Step 1  │───▶│ Step 2  │───▶│ Step 3  │
-└─────────┘    └─────────┘    └─────────┘
-```
-
----
-
-## 5. Technical Considerations
-
-### 5.1 Architecture Impact
-[TO FILL: How this feature affects the existing architecture]
-
-### 5.2 Dependencies
-
-| Dependency | Type | Status | Notes |
-|------------|------|--------|-------|
-| [TO FILL] | Service/API | [TO FILL] | |
-| [TO FILL] | Library | [TO FILL] | |
-
-### 5.3 Data Model Changes
-[TO FILL: New entities, modified schemas, migrations needed]
-
-### 5.4 API Changes
-[TO FILL: New endpoints, modified contracts]
-
----
-
-## 6. Risks & Assumptions
-
-### 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] |
-
-### 6.3 Open Questions
-
-- [ ] [TO FILL: Question 1]
-- [ ] [TO FILL: Question 2]
-
----
-
-## 7. Implementation Notes
-
-### 7.1 Suggested Approach
-[TO FILL: High-level implementation strategy]
-
-### 7.2 Phasing (if applicable)
-
-| Phase | Scope | Target Date |
-|-------|-------|-------------|
-| Phase 1 | [TO FILL] | [TO FILL] |
-| Phase 2 | [TO FILL] | [TO FILL] |
-
----
-
-## 8. Testing Strategy
-
-### 8.1 Test Scenarios
-[TO FILL: Key scenarios to test]
-
-### 8.2 Test Data Requirements
-[TO FILL: Special data needed for testing]
-
----
-
-## 9. Documentation & Training
-
-- [ ] User documentation required
-- [ ] Admin documentation required  
-- [ ] Training materials needed
-- [ ] Release notes entry
-
----
-
-## 10. Approval
-
-| Role | Name | Date | Signature |
-|------|------|------|-----------|
-| Product Owner | | | ☐ Approved |
-| Tech Lead | | | ☐ Approved |
-| QA Lead | | | ☐ Approved |
-
----
-
-## Revision History
-
-| Version | Date | Author | Changes |
-|---------|------|--------|---------|
-| 1.0 | [TO FILL] | [TO FILL] | Initial draft |

package/workflows/bugfix-quick.yaml

@@ -1,53 +0,0 @@
-# Bugfix Quick Workflow
-# Lightweight workflow for simple bug fixes
-
-name: bugfix-quick
-displayName: "Quick Bug Fix"
-description: "Fast track workflow for simple bug fixes - analyze, fix, verify"
-
-metadata:
-  version: "1.0"
-  author: "Spec-Kit"
-  tags:
-    - bugfix
-    - quick
-    - hotfix
-
-template: bugfix-report.md
-defaultAgent: SpecAgent
-
-steps:
-  - id: analyze-fix
-    name: "Analyze & Fix"
-    action: call_agent
-    agent: SpecAgent
-    description: |
-      Quick bug analysis and fix:
-      
-      1. **Identify the bug**: Understand what's broken
-      2. **Find root cause**: Locate the problematic code
-      3. **Implement fix**: Make minimal, focused changes
-      4. **Verify**: Confirm the fix works
-      
-      Keep it simple - no lengthy documentation needed.
-    outputs:
-      - bug_analysis
-      - code_fix
-
-  - id: auto-memory
-    name: "Update Memory"
-    action: call_agent
-    agent: SpecAgent
-    description: |
-      Save learnings from this bugfix to project memory:
-      
-      - **What was the bug?** (brief description)
-      - **Root cause** (why it happened)
-      - **Solution** (how it was fixed)
-      - **Prevention** (how to avoid in future)
-      
-      Save to `.spec-kit/memory/learnings.md`
-    inputs:
-      source: "code_fix"
-    outputs:
-      - memory_update

package/workflows/bugfix.yaml

@@ -1,99 +0,0 @@
-# Bugfix Workflow
-# Streamlined process for bug fixes with validation checkpoints
-
-name: bugfix
-displayName: "Bug Fix"
-description: "Structured workflow for analyzing, fixing, and validating bug corrections"
-
-metadata:
-  version: "1.0"
-  author: "Spec-Kit"
-  tags:
-    - bugfix
-    - hotfix
-    - correction
-
-template: bugfix-report.md
-defaultAgent: SpecAgent
-
-steps:
-  - id: analyze-bug
-    name: "Analyze Bug & Root Cause"
-    action: fetch_ado
-    description: |
-      Retrieve the bug work item from Azure DevOps and analyze:
-      - Reproduction steps
-      - Error logs and stack traces
-      - Affected components
-      - User impact assessment
-      
-      Identify the root cause of the issue.
-    outputs:
-      - bug_data
-      - root_cause_analysis
-
-  - id: plan-fix
-    name: "Plan Correction"
-    action: call_agent
-    agent: PlanAgent
-    description: |
-      Create a correction plan including:
-      - Proposed fix approach
-      - Files/components to modify
-      - Potential side effects
-      - Rollback strategy if needed
-      
-      Keep the fix minimal and focused.
-    inputs:
-      source: "root_cause_analysis"
-    outputs:
-      - fix_plan
-
-  - id: security-check
-    name: "Security Validation"
-    action: review
-    agent: GovAgent
-    description: |
-      Quick security review of the proposed fix:
-      - [ ] No new vulnerabilities introduced
-      - [ ] Input validation maintained
-      - [ ] No sensitive data exposure
-      - [ ] Authentication/Authorization intact
-    inputs:
-      document: "fix_plan"
-    outputs:
-      - security_clearance
-
-  - id: implement-fix
-    name: "Implement & Test"
-    action: generate_content
-    description: |
-      Implement the fix following the plan:
-      1. Write the code fix
-      2. Add unit tests for the bug scenario
-      3. Add regression tests
-      4. Update documentation if needed
-      
-      Ensure test coverage for the fixed code path.
-    inputs:
-      plan: "fix_plan"
-    outputs:
-      - code_changes
-      - test_cases
-
-  - id: final-review
-    name: "Final Review"
-    action: review
-    agent: GovAgent
-    description: |
-      Final validation before merge:
-      - [ ] Fix addresses root cause
-      - [ ] No regression introduced
-      - [ ] Tests pass
-      - [ ] Code review approved
-      - [ ] Documentation updated
-    inputs:
-      changes: "code_changes"
-      tests: "test_cases"
-    outputs:
-      - approval_status