smart-spec-kit-mcp 2.2.7 → 2.2.9

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (12) hide show
  1. package/README.md +2 -0
  2. package/TROUBLESHOOTING.md +121 -0
  3. package/dist/tools/promptTools.d.ts.map +1 -1
  4. package/dist/tools/promptTools.js +154 -0
  5. package/dist/tools/promptTools.js.map +1 -1
  6. package/docs/DOCUMENTATION.md +82 -0
  7. package/package.json +3 -5
  8. package/starter-kit/copilot-instructions.md +21 -24
  9. package/starter-kit/github-prompts/speckit.help.prompt.md +50 -23
  10. package/starter-kit/github-prompts/speckit.workflow.prompt.md +48 -0
  11. package/starter-kit/workflows/feature-full.yaml +87 -262
  12. package/starter-kit/workflows/feature-standard.yaml +62 -58
package/starter-kit/workflows/feature-standard.yaml CHANGED
@@ -1,92 +1,96 @@
1
1
  # Feature Standard Workflow
2
- # Used for creating functional specifications from Azure DevOps Feature work items
2
+ # Standard workflow: spec → plan → tasks → implement
3
3
 
4
4
  name: feature-standard
5
- displayName: "Feature Specification"
6
- description: "Creates a complete functional specification document from an Azure DevOps Feature work item"
5
+ displayName: "Standard Feature"
6
+ description: "Standard feature workflow: specification → plan → tasks → implementation"
7
7
 
8
8
  metadata:
9
- version: "1.0"
9
+ version: "2.0"
10
10
  author: "Spec-Kit"
11
11
  tags:
12
12
  - feature
13
13
  - specification
14
- - functional
14
+ - standard
15
15
 
16
16
  template: functional-spec.md
17
17
  defaultAgent: SpecAgent
18
18
 
19
19
  steps:
20
- - id: fetch-workitem
21
- name: "Fetch Azure DevOps Work Item"
22
- action: fetch_ado
23
- description: |
24
- Retrieve the Feature work item from Azure DevOps.
25
- Extract: Title, Description, Acceptance Criteria, Tags, Links, and Parent/Child relationships.
26
- outputs:
27
- - workitem_data
28
- - linked_items
29
-
30
- - id: analyze-requirements
31
- name: "Analyze Requirements"
20
+ # Step 1: Create Specification
21
+ - id: create-spec
22
+ name: "1. Create Specification"
32
23
  action: call_agent
33
24
  agent: SpecAgent
34
25
  description: |
35
- Analyze the work item data to identify:
36
- - Core functional requirements
37
- - Non-functional requirements (performance, security, etc.)
38
- - User personas and use cases
26
+ Create a functional specification based on user requirements.
27
+
28
+ Include:
29
+ - Feature summary and objectives
30
+ - User stories with acceptance criteria
31
+ - Functional requirements
32
+ - Non-functional requirements (if applicable)
39
33
  - Dependencies and constraints
40
- - Risks and assumptions
34
+
35
+ Mark unclear sections with [NEEDS CLARIFICATION] for review.
41
36
  inputs:
42
- source: "workitem_data"
37
+ - name: requirements
38
+ description: "Feature description from user"
39
+ required: true
43
40
  outputs:
44
- - requirements_analysis
41
+ - spec_document
45
42
 
46
- - id: generate-spec
47
- name: "Generate Specification Document"
48
- action: generate_content
49
- agent: SpecAgent
43
+ # Step 2: Create Implementation Plan
44
+ - id: create-plan
45
+ name: "2. Create Implementation Plan"
46
+ action: call_agent
47
+ agent: PlanAgent
50
48
  description: |
51
- Using the template and analyzed requirements, generate the functional specification.
49
+ Create a detailed implementation plan based on the specification.
52
50
 
53
- Guidelines:
54
- - Fill all sections with available data
55
- - Mark unclear sections with [TO FILL] for human review
56
- - Include traceability links to Azure DevOps
57
- - Follow the template structure strictly
51
+ Include:
52
+ - Technical approach
53
+ - Components to create/modify
54
+ - Dependencies and order
55
+ - Risk assessment
56
+ - Estimated effort
58
57
  inputs:
59
- template: "functional-spec.md"
60
- data: "requirements_analysis"
58
+ source: "spec_document"
61
59
  outputs:
62
- - spec_document
60
+ - plan_document
63
61
 
64
- - id: review-spec
65
- name: "Review & Validate"
66
- action: review
67
- agent: GovAgent
62
+ # Step 3: Generate Task Breakdown
63
+ - id: generate-tasks
64
+ name: "3. Generate Tasks"
65
+ action: call_agent
66
+ agent: PlanAgent
68
67
  description: |
69
- Review the generated specification for:
70
- - Completeness (all required sections filled)
71
- - Consistency (no contradictions)
72
- - Clarity (understandable by all stakeholders)
73
- - Traceability (links to source requirements)
68
+ Break down the plan into atomic, actionable tasks.
74
69
 
75
- Suggest improvements if needed.
70
+ Each task should:
71
+ - Be completable in 1-2 hours
72
+ - Have clear acceptance criteria
73
+ - Be independent when possible
74
+ - Include file paths if known
76
75
  inputs:
77
- document: "spec_document"
76
+ source: "plan_document"
78
77
  outputs:
79
- - review_feedback
80
- - validated_spec
78
+ - tasks_document
81
79
 
82
- - id: create-file
83
- name: "Save Specification"
84
- action: create_file
80
+ # Step 4: Implement
81
+ - id: implement
82
+ name: "4. Implement"
83
+ action: call_agent
84
+ agent: SpecAgent
85
85
  description: |
86
- Save the validated specification as a Markdown file.
87
- Suggested location: `specs/{workitem_id}-functional-spec.md`
86
+ Implement the tasks one by one.
87
+
88
+ For each task:
89
+ - Read the task description
90
+ - Implement following project conventions
91
+ - Update task status when complete
92
+ - Proceed to next task
88
93
  inputs:
89
- content: "validated_spec"
90
- filename_pattern: "{context_id}-functional-spec.md"
94
+ source: "tasks_document"
91
95
  outputs:
92
- - file_path
96
+ - implementation