smart-spec-kit-mcp 2.1.1 → 2.1.3

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

@@ -0,0 +1,344 @@
+# Full Feature Workflow with Governance
+# Complete workflow with all validation checkpoints
+
+name: feature-full
+displayName: "Feature with Full Governance"
+description: "Complete feature workflow including RGPD, Security, Architecture, Design System, and Testing validations"
+
+metadata:
+  version: "1.0"
+  author: "Spec-Kit"
+  tags:
+    - feature
+    - governance
+    - enterprise
+
+template: functional-spec.md
+defaultAgent: SpecAgent
+
+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"
+    action: call_agent
+    agent: SpecAgent
+    description: |
+      Generate a comprehensive functional specification including:
+      
+      **Functional Requirements**
+      - User stories with acceptance criteria
+      - Business rules
+      - Data requirements
+      
+      **Non-Functional Requirements**
+      - Performance targets
+      - Availability requirements
+      - Scalability needs
+      
+      Mark uncertain sections with [TO FILL] for human review.
+    inputs:
+      source: "workitem_data"
+    outputs:
+      - functional_spec
+
+  # ═══════════════════════════════════════════════════════════════
+  # PHASE 2: VALIDATION GATES
+  # ═══════════════════════════════════════════════════════════════
+
+  - 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"
+    action: review
+    agent: GovAgent
+    description: |
+      Security assessment checklist:
+      
+      **Authentication & Authorization**
+      - [ ] Auth mechanism defined
+      - [ ] Role-based access control
+      - [ ] Session management
+      
+      **Data Protection**
+      - [ ] Encryption at rest
+      - [ ] Encryption in transit (TLS)
+      - [ ] Sensitive data handling
+      
+      **Input/Output Security**
+      - [ ] Input validation strategy
+      - [ ] Output encoding
+      - [ ] SQL injection prevention
+      - [ ] XSS prevention
+      - [ ] CSRF protection
+      
+      **Infrastructure**
+      - [ ] Secrets management
+      - [ ] Logging (without PII)
+      - [ ] Rate limiting
+      - [ ] DDoS considerations
+    inputs:
+      spec: "functional_spec"
+    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"
+    action: review
+    agent: GovAgent
+    description: |
+      Design System compliance (if UI involved):
+      
+      **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
+      
+      **Responsive Design**
+      - [ ] Mobile breakpoints defined
+      - [ ] Touch targets adequate
+      - [ ] Dark mode support (if applicable)
+    inputs:
+      spec: "functional_spec"
+    outputs:
+      - design_report
+      - design_status
+
+  # ═══════════════════════════════════════════════════════════════
+  # PHASE 3: TECHNICAL PLANNING
+  # ═══════════════════════════════════════════════════════════════
+
+  - id: technical-plan
+    name: "3.1 Technical Planning"
+    action: call_agent
+    agent: PlanAgent
+    description: |
+      Create detailed technical plan:
+      
+      **Architecture Decisions**
+      - 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
+    inputs:
+      spec: "functional_spec"
+      plan: "technical_plan"
+    outputs:
+      - test_strategy
+      - test_cases
+
+  # ═══════════════════════════════════════════════════════════════
+  # PHASE 4: DOCUMENTATION & FINALIZATION
+  # ═══════════════════════════════════════════════════════════════
+
+  - id: documentation
+    name: "4.1 📚 Documentation Plan"
+    action: generate_content
+    description: |
+      Identify documentation needs:
+      
+      **User Documentation**
+      - [ ] User guide updates
+      - [ ] FAQ additions
+      - [ ] Tutorial/walkthrough
+      
+      **Technical Documentation**
+      - [ ] API documentation
+      - [ ] Architecture Decision Record (ADR)
+      - [ ] Runbook updates
+      - [ ] README updates
+      
+      **Release Documentation**
+      - [ ] Changelog entry
+      - [ ] Release notes
+      - [ ] Migration guide (if breaking changes)
+    inputs:
+      spec: "functional_spec"
+      plan: "technical_plan"
+    outputs:
+      - documentation_plan
+
+  - 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
+
+  - id: create-tasks
+    name: "4.3 Create ADO Work Items"
+    action: create_file
+    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.
+    inputs:
+      tasks: "task_list"
+      feature_id: "context_id"
+    outputs:
+      - ado_work_items

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

@@ -0,0 +1,69 @@
+# Feature Quick Workflow
+# Lightweight workflow for simple features / quick wins
+
+name: feature-quick
+displayName: "Quick Feature (Quick Win)"
+description: "Lightweight workflow for simple features that don't need full specification"
+
+metadata:
+  version: "1.0"
+  author: "Spec-Kit"
+  tags:
+    - feature
+    - quick-win
+    - lightweight
+
+template: functional-spec.md
+defaultAgent: SpecAgent
+
+steps:
+  - id: quick-spec
+    name: "Quick Specification"
+    action: call_agent
+    agent: SpecAgent
+    description: |
+      Create a minimal specification with:
+      - Feature summary (2-3 sentences)
+      - User story (As a... I want... So that...)
+      - Acceptance criteria (3-5 bullet points)
+      - Technical notes (if any)
+      
+      Keep it simple and actionable. No lengthy documentation needed.
+    inputs:
+      - name: requirements
+        description: "Feature description from user"
+        required: true
+    outputs:
+      - quick_spec
+
+  - id: implement
+    name: "Implement"
+    action: call_agent
+    agent: SpecAgent
+    description: |
+      Implement the feature directly based on the quick spec.
+      
+      Guidelines:
+      - Follow project conventions from constitution
+      - Write clean, tested code
+      - Keep changes minimal and focused
+    inputs:
+      source: "quick_spec"
+    outputs:
+      - implementation
+
+  - id: auto-memory
+    name: "Update Memory"
+    action: call_agent
+    agent: SpecAgent
+    description: |
+      Automatically enrich project memory with:
+      - What was implemented (brief summary)
+      - Any technical decisions made
+      - Patterns or conventions used
+      
+      Save to .spec-kit/memory/learnings.md or appropriate category.
+    inputs:
+      source: "implementation"
+    outputs:
+      - memory_update

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

@@ -0,0 +1,92 @@
+# Feature Standard Workflow
+# Used for creating functional specifications from Azure DevOps Feature work items
+
+name: feature-standard
+displayName: "Feature Specification"
+description: "Creates a complete functional specification document from an Azure DevOps Feature work item"
+
+metadata:
+  version: "1.0"
+  author: "Spec-Kit"
+  tags:
+    - feature
+    - specification
+    - functional
+
+template: functional-spec.md
+defaultAgent: SpecAgent
+
+steps:
+  - id: fetch-workitem
+    name: "Fetch Azure DevOps Work Item"
+    action: fetch_ado
+    description: |
+      Retrieve the Feature work item from Azure DevOps.
+      Extract: Title, Description, Acceptance Criteria, Tags, Links, and Parent/Child relationships.
+    outputs:
+      - workitem_data
+      - linked_items
+
+  - id: analyze-requirements
+    name: "Analyze Requirements"
+    action: call_agent
+    agent: SpecAgent
+    description: |
+      Analyze the work item data to identify:
+      - Core functional requirements
+      - Non-functional requirements (performance, security, etc.)
+      - User personas and use cases
+      - Dependencies and constraints
+      - Risks and assumptions
+    inputs:
+      source: "workitem_data"
+    outputs:
+      - requirements_analysis
+
+  - id: generate-spec
+    name: "Generate Specification Document"
+    action: generate_content
+    agent: SpecAgent
+    description: |
+      Using the template and analyzed requirements, generate the functional specification.
+      
+      Guidelines:
+      - Fill all sections with available data
+      - Mark unclear sections with [TO FILL] for human review
+      - Include traceability links to Azure DevOps
+      - Follow the template structure strictly
+    inputs:
+      template: "functional-spec.md"
+      data: "requirements_analysis"
+    outputs:
+      - spec_document
+
+  - id: review-spec
+    name: "Review & Validate"
+    action: review
+    agent: GovAgent
+    description: |
+      Review the generated specification for:
+      - Completeness (all required sections filled)
+      - Consistency (no contradictions)
+      - Clarity (understandable by all stakeholders)
+      - Traceability (links to source requirements)
+      
+      Suggest improvements if needed.
+    inputs:
+      document: "spec_document"
+    outputs:
+      - review_feedback
+      - validated_spec
+
+  - id: create-file
+    name: "Save Specification"
+    action: create_file
+    description: |
+      Save the validated specification as a Markdown file.
+      Suggested location: `specs/{workitem_id}-functional-spec.md`
+    inputs:
+      content: "validated_spec"
+      filename_pattern: "{context_id}-functional-spec.md"
+    outputs:
+      - file_path

package/workflows/feature-quick.yaml

@@ -0,0 +1,69 @@
+# Feature Quick Workflow
+# Lightweight workflow for simple features / quick wins
+
+name: feature-quick
+displayName: "Quick Feature (Quick Win)"
+description: "Lightweight workflow for simple features that don't need full specification"
+
+metadata:
+  version: "1.0"
+  author: "Spec-Kit"
+  tags:
+    - feature
+    - quick-win
+    - lightweight
+
+template: functional-spec.md
+defaultAgent: SpecAgent
+
+steps:
+  - id: quick-spec
+    name: "Quick Specification"
+    action: call_agent
+    agent: SpecAgent
+    description: |
+      Create a minimal specification with:
+      - Feature summary (2-3 sentences)
+      - User story (As a... I want... So that...)
+      - Acceptance criteria (3-5 bullet points)
+      - Technical notes (if any)
+      
+      Keep it simple and actionable. No lengthy documentation needed.
+    inputs:
+      - name: requirements
+        description: "Feature description from user"
+        required: true
+    outputs:
+      - quick_spec
+
+  - id: implement
+    name: "Implement"
+    action: call_agent
+    agent: SpecAgent
+    description: |
+      Implement the feature directly based on the quick spec.
+      
+      Guidelines:
+      - Follow project conventions from constitution
+      - Write clean, tested code
+      - Keep changes minimal and focused
+    inputs:
+      source: "quick_spec"
+    outputs:
+      - implementation
+
+  - id: auto-memory
+    name: "Update Memory"
+    action: call_agent
+    agent: SpecAgent
+    description: |
+      Automatically enrich project memory with:
+      - What was implemented (brief summary)
+      - Any technical decisions made
+      - Patterns or conventions used
+      
+      Save to .spec-kit/memory/learnings.md or appropriate category.
+    inputs:
+      source: "implementation"
+    outputs:
+      - memory_update