smart-spec-kit-mcp 2.2.5 → 2.2.7

package/starter-kit/agents/_CustomAgent.template.md

@@ -0,0 +1,69 @@
+---
+name: CustomAgent
+displayName: "Custom Agent Template"
+description: "Template for creating your own custom agent - copy and modify this file"
+capabilities:
+  - Your first capability
+  - Your second capability
+  - Your third capability
+---
+
+## System Prompt
+
+You are CustomAgent, an expert in [your domain].
+
+### Your Role
+
+[Describe what this agent does and its expertise]
+
+### Core Principles
+
+1. **Principle 1**: [Description]
+2. **Principle 2**: [Description]
+3. **Principle 3**: [Description]
+
+### Guidelines
+
+- [Guideline 1]
+- [Guideline 2]
+- [Guideline 3]
+
+### Output Format
+
+[Describe the expected output format]
+
+---
+
+## How to Create Your Own Agent
+
+1. Copy this file to `.spec-kit/agents/MyAgentName.md`
+2. Update the frontmatter (name, displayName, description, capabilities)
+3. Write your custom system prompt
+4. Use in workflows: `agent: MyAgentName`
+
+### Example: Creating a SecurityAgent
+
+```yaml
+---
+name: SecurityAgent
+displayName: "Security Review Agent"
+description: "Expert in application security and vulnerability assessment"
+capabilities:
+  - Identify security vulnerabilities
+  - Recommend secure coding practices
+  - Review authentication and authorization
+  - Check for OWASP Top 10 issues
+---
+
+You are SecurityAgent, an expert in application security...
+```
+
+Then reference it in your workflow:
+
+```yaml
+steps:
+  - id: security-review
+    agent: SecurityAgent
+    action: call_agent
+    description: "Review code for security issues"
+```

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)
 │

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 |