@cleverpeople/my-skills 1.3.3 → 1.3.5
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.
- package/Defect-Risk-Analyzer/SKILL.md +86 -86
- package/README.md +303 -17
- package/Requirement-Summarizer/SKILL.md +88 -88
- package/Test-Case-Generator/SKILL.md +90 -90
- package/package.json +19 -15
|
@@ -1,87 +1,87 @@
|
|
|
1
|
-
# Defect Risk Analyzer
|
|
2
|
-
|
|
3
|
-
## Description
|
|
4
|
-
|
|
5
|
-
Analyze testing quality metrics and determine project risk level before release.
|
|
6
|
-
|
|
7
|
-
## Purpose
|
|
8
|
-
|
|
9
|
-
Provide data-driven risk assessment and release readiness recommendations.
|
|
10
|
-
|
|
11
|
-
---
|
|
12
|
-
|
|
13
|
-
## Input Schema
|
|
14
|
-
|
|
15
|
-
{
|
|
16
|
-
"project_name": "string",
|
|
17
|
-
"total_test_cases": "number",
|
|
18
|
-
"passed_test_cases": "number",
|
|
19
|
-
"failed_test_cases": "number",
|
|
20
|
-
"blocked_test_cases": "number",
|
|
21
|
-
"test_coverage_percentage": "number",
|
|
22
|
-
"critical_defects": "number",
|
|
23
|
-
"major_defects": "number",
|
|
24
|
-
"minor_defects": "number"
|
|
25
|
-
}
|
|
26
|
-
|
|
27
|
-
### Field Description
|
|
28
|
-
|
|
29
|
-
- project_name: Project identifier
|
|
30
|
-
- total_test_cases: Total test count
|
|
31
|
-
- passed_test_cases: Successful executions
|
|
32
|
-
- failed_test_cases: Failed executions
|
|
33
|
-
- blocked_test_cases: Blocked executions
|
|
34
|
-
- test_coverage_percentage: Coverage metric
|
|
35
|
-
- critical_defects: Critical severity defects
|
|
36
|
-
- major_defects: Major severity defects
|
|
37
|
-
- minor_defects: Minor severity defects
|
|
38
|
-
|
|
39
|
-
---
|
|
40
|
-
|
|
41
|
-
## Output Schema
|
|
42
|
-
|
|
43
|
-
{
|
|
44
|
-
"risk_score": "number",
|
|
45
|
-
"risk_level": "string",
|
|
46
|
-
"project_health": "string",
|
|
47
|
-
"release_readiness": "string",
|
|
48
|
-
"recommendations": [
|
|
49
|
-
"string"
|
|
50
|
-
]
|
|
51
|
-
}
|
|
52
|
-
|
|
53
|
-
### Field Description
|
|
54
|
-
|
|
55
|
-
- risk_score: Risk score (0-100)
|
|
56
|
-
- risk_level: Low, Medium, High, Critical
|
|
57
|
-
- project_health: Overall health status
|
|
58
|
-
- release_readiness: Ready or Not Ready
|
|
59
|
-
- recommendations: Improvement actions
|
|
60
|
-
|
|
61
|
-
---
|
|
62
|
-
|
|
63
|
-
## Risk Levels
|
|
64
|
-
|
|
65
|
-
0-20 = Low
|
|
66
|
-
|
|
67
|
-
21-50 = Medium
|
|
68
|
-
|
|
69
|
-
51-80 = High
|
|
70
|
-
|
|
71
|
-
81-100 = Critical
|
|
72
|
-
|
|
73
|
-
---
|
|
74
|
-
|
|
75
|
-
## Example Output
|
|
76
|
-
|
|
77
|
-
{
|
|
78
|
-
"risk_score": 78,
|
|
79
|
-
"risk_level": "High",
|
|
80
|
-
"project_health": "At Risk",
|
|
81
|
-
"release_readiness": "Not Ready",
|
|
82
|
-
"recommendations": [
|
|
83
|
-
"Resolve all critical defects",
|
|
84
|
-
"Increase test coverage above 80%",
|
|
85
|
-
"Retest failed test cases"
|
|
86
|
-
]
|
|
1
|
+
# Defect Risk Analyzer
|
|
2
|
+
|
|
3
|
+
## Description
|
|
4
|
+
|
|
5
|
+
Analyze testing quality metrics and determine project risk level before release.
|
|
6
|
+
|
|
7
|
+
## Purpose
|
|
8
|
+
|
|
9
|
+
Provide data-driven risk assessment and release readiness recommendations.
|
|
10
|
+
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
## Input Schema
|
|
14
|
+
|
|
15
|
+
{
|
|
16
|
+
"project_name": "string",
|
|
17
|
+
"total_test_cases": "number",
|
|
18
|
+
"passed_test_cases": "number",
|
|
19
|
+
"failed_test_cases": "number",
|
|
20
|
+
"blocked_test_cases": "number",
|
|
21
|
+
"test_coverage_percentage": "number",
|
|
22
|
+
"critical_defects": "number",
|
|
23
|
+
"major_defects": "number",
|
|
24
|
+
"minor_defects": "number"
|
|
25
|
+
}
|
|
26
|
+
|
|
27
|
+
### Field Description
|
|
28
|
+
|
|
29
|
+
- project_name: Project identifier
|
|
30
|
+
- total_test_cases: Total test count
|
|
31
|
+
- passed_test_cases: Successful executions
|
|
32
|
+
- failed_test_cases: Failed executions
|
|
33
|
+
- blocked_test_cases: Blocked executions
|
|
34
|
+
- test_coverage_percentage: Coverage metric
|
|
35
|
+
- critical_defects: Critical severity defects
|
|
36
|
+
- major_defects: Major severity defects
|
|
37
|
+
- minor_defects: Minor severity defects
|
|
38
|
+
|
|
39
|
+
---
|
|
40
|
+
|
|
41
|
+
## Output Schema
|
|
42
|
+
|
|
43
|
+
{
|
|
44
|
+
"risk_score": "number",
|
|
45
|
+
"risk_level": "string",
|
|
46
|
+
"project_health": "string",
|
|
47
|
+
"release_readiness": "string",
|
|
48
|
+
"recommendations": [
|
|
49
|
+
"string"
|
|
50
|
+
]
|
|
51
|
+
}
|
|
52
|
+
|
|
53
|
+
### Field Description
|
|
54
|
+
|
|
55
|
+
- risk_score: Risk score (0-100)
|
|
56
|
+
- risk_level: Low, Medium, High, Critical
|
|
57
|
+
- project_health: Overall health status
|
|
58
|
+
- release_readiness: Ready or Not Ready
|
|
59
|
+
- recommendations: Improvement actions
|
|
60
|
+
|
|
61
|
+
---
|
|
62
|
+
|
|
63
|
+
## Risk Levels
|
|
64
|
+
|
|
65
|
+
0-20 = Low
|
|
66
|
+
|
|
67
|
+
21-50 = Medium
|
|
68
|
+
|
|
69
|
+
51-80 = High
|
|
70
|
+
|
|
71
|
+
81-100 = Critical
|
|
72
|
+
|
|
73
|
+
---
|
|
74
|
+
|
|
75
|
+
## Example Output
|
|
76
|
+
|
|
77
|
+
{
|
|
78
|
+
"risk_score": 78,
|
|
79
|
+
"risk_level": "High",
|
|
80
|
+
"project_health": "At Risk",
|
|
81
|
+
"release_readiness": "Not Ready",
|
|
82
|
+
"recommendations": [
|
|
83
|
+
"Resolve all critical defects",
|
|
84
|
+
"Increase test coverage above 80%",
|
|
85
|
+
"Retest failed test cases"
|
|
86
|
+
]
|
|
87
87
|
}
|
package/README.md
CHANGED
|
@@ -1,17 +1,303 @@
|
|
|
1
|
-
# My Skills
|
|
2
|
-
|
|
3
|
-
This package contains the shared `SKILL.md` definitions for the included skills, ready to be installed and shared via npm.
|
|
4
|
-
|
|
5
|
-
## Install
|
|
6
|
-
|
|
7
|
-
```powershell
|
|
8
|
-
npm install @cleverpeople/my-skills
|
|
9
|
-
```
|
|
10
|
-
|
|
11
|
-
## Included skills
|
|
12
|
-
|
|
13
|
-
- `
|
|
14
|
-
- `
|
|
15
|
-
- `
|
|
16
|
-
|
|
17
|
-
After installation, the package files are available in your local `node_modules/my-skills/` folder.
|
|
1
|
+
# My Skills
|
|
2
|
+
|
|
3
|
+
This package contains the shared `SKILL.md` definitions for the included skills, ready to be installed and shared via npm.
|
|
4
|
+
|
|
5
|
+
## Install
|
|
6
|
+
|
|
7
|
+
```powershell
|
|
8
|
+
npm install @cleverpeople/my-skills
|
|
9
|
+
```
|
|
10
|
+
|
|
11
|
+
## Included skills
|
|
12
|
+
|
|
13
|
+
- `Requirement-Summarizer`
|
|
14
|
+
- `Test-Case-Generator`
|
|
15
|
+
- `Defect-Risk-Analyzer`
|
|
16
|
+
|
|
17
|
+
After installation, the package files are available in your local `node_modules/my-skills/` folder.
|
|
18
|
+
|
|
19
|
+
## How to use these skills
|
|
20
|
+
|
|
21
|
+
Each skill is published as a folder containing a `SKILL.md` file with structured guidance for a Copilot-style skill. You can:
|
|
22
|
+
|
|
23
|
+
1. Install the package with npm.
|
|
24
|
+
2. Copy or reference the skill folders from `node_modules/@cleverpeople/my-skills/`.
|
|
25
|
+
3. Use the `SKILL.md` definitions in compatible tooling that supports shared skill packages.
|
|
26
|
+
4. Provide the required input payloads for each skill to receive the expected structured output.
|
|
27
|
+
|
|
28
|
+
---
|
|
29
|
+
|
|
30
|
+
## Skill 1: Requirement-Summarizer
|
|
31
|
+
|
|
32
|
+
### Description
|
|
33
|
+
|
|
34
|
+
The Requirement Summarizer analyzes requirements and user stories, extracting key business goals, features, acceptance criteria, and risks.
|
|
35
|
+
|
|
36
|
+
### Purpose
|
|
37
|
+
|
|
38
|
+
Transform lengthy requirement documents into concise and actionable summaries.
|
|
39
|
+
|
|
40
|
+
### Input Schema
|
|
41
|
+
|
|
42
|
+
```json
|
|
43
|
+
{
|
|
44
|
+
"document_title": "string",
|
|
45
|
+
"document_type": "string",
|
|
46
|
+
"requirement_text": "string",
|
|
47
|
+
"project_name": "string",
|
|
48
|
+
"author": "string",
|
|
49
|
+
"created_date": "datetime"
|
|
50
|
+
}
|
|
51
|
+
```
|
|
52
|
+
|
|
53
|
+
### Field Description
|
|
54
|
+
|
|
55
|
+
- `document_title`: Name of the requirement document
|
|
56
|
+
- `document_type`: BRD, FRD, User Story, Epic, etc.
|
|
57
|
+
- `requirement_text`: Full requirement content
|
|
58
|
+
- `project_name`: Associated project
|
|
59
|
+
- `author`: Requirement owner
|
|
60
|
+
- `created_date`: Document creation date
|
|
61
|
+
|
|
62
|
+
### Output Schema
|
|
63
|
+
|
|
64
|
+
```json
|
|
65
|
+
{
|
|
66
|
+
"summary": "string",
|
|
67
|
+
"business_objectives": [
|
|
68
|
+
"string"
|
|
69
|
+
],
|
|
70
|
+
"key_features": [
|
|
71
|
+
"string"
|
|
72
|
+
],
|
|
73
|
+
"acceptance_criteria": [
|
|
74
|
+
"string"
|
|
75
|
+
],
|
|
76
|
+
"risks": [
|
|
77
|
+
"string"
|
|
78
|
+
],
|
|
79
|
+
"assumptions": [
|
|
80
|
+
"string"
|
|
81
|
+
]
|
|
82
|
+
}
|
|
83
|
+
```
|
|
84
|
+
|
|
85
|
+
### Field Description
|
|
86
|
+
|
|
87
|
+
- `summary`: Concise requirement overview
|
|
88
|
+
- `business_objectives`: Primary business goals
|
|
89
|
+
- `key_features`: Main system capabilities
|
|
90
|
+
- `acceptance_criteria`: Conditions for successful implementation
|
|
91
|
+
- `risks`: Potential project risks
|
|
92
|
+
- `assumptions`: Assumptions identified from requirements
|
|
93
|
+
|
|
94
|
+
### Example Output
|
|
95
|
+
|
|
96
|
+
```json
|
|
97
|
+
{
|
|
98
|
+
"summary": "Users can access dashboards after authentication.",
|
|
99
|
+
"business_objectives": [
|
|
100
|
+
"Improve visibility of production data"
|
|
101
|
+
],
|
|
102
|
+
"key_features": [
|
|
103
|
+
"User Authentication",
|
|
104
|
+
"Dashboard Access"
|
|
105
|
+
],
|
|
106
|
+
"acceptance_criteria": [
|
|
107
|
+
"User can log in successfully",
|
|
108
|
+
"Dashboard loads within 3 seconds"
|
|
109
|
+
],
|
|
110
|
+
"risks": [
|
|
111
|
+
"Single Sign-On dependency"
|
|
112
|
+
],
|
|
113
|
+
"assumptions": [
|
|
114
|
+
"Users possess valid credentials"
|
|
115
|
+
]
|
|
116
|
+
}
|
|
117
|
+
```
|
|
118
|
+
|
|
119
|
+
---
|
|
120
|
+
|
|
121
|
+
## Skill 2: Test-Case-Generator
|
|
122
|
+
|
|
123
|
+
### Description
|
|
124
|
+
|
|
125
|
+
Generate test scenarios and test cases from requirements and acceptance criteria.
|
|
126
|
+
|
|
127
|
+
### Purpose
|
|
128
|
+
|
|
129
|
+
Accelerate software testing preparation and improve test coverage.
|
|
130
|
+
|
|
131
|
+
### Input Schema
|
|
132
|
+
|
|
133
|
+
```json
|
|
134
|
+
{
|
|
135
|
+
"requirement_id": "string",
|
|
136
|
+
"requirement_title": "string",
|
|
137
|
+
"summary": "string",
|
|
138
|
+
"acceptance_criteria": [
|
|
139
|
+
"string"
|
|
140
|
+
],
|
|
141
|
+
"application_type": "string",
|
|
142
|
+
"priority": "string"
|
|
143
|
+
}
|
|
144
|
+
```
|
|
145
|
+
|
|
146
|
+
### Field Description
|
|
147
|
+
|
|
148
|
+
- `requirement_id`: Unique requirement identifier
|
|
149
|
+
- `requirement_title`: Requirement title
|
|
150
|
+
- `summary`: Requirement summary
|
|
151
|
+
- `acceptance_criteria`: List of acceptance criteria
|
|
152
|
+
- `application_type`: Web, Mobile, Desktop, API
|
|
153
|
+
- `priority`: High, Medium, Low
|
|
154
|
+
|
|
155
|
+
### Output Schema
|
|
156
|
+
|
|
157
|
+
```json
|
|
158
|
+
{
|
|
159
|
+
"test_cases": [
|
|
160
|
+
{
|
|
161
|
+
"test_case_id": "string",
|
|
162
|
+
"title": "string",
|
|
163
|
+
"priority": "string",
|
|
164
|
+
"pre_conditions": [
|
|
165
|
+
"string"
|
|
166
|
+
],
|
|
167
|
+
"test_steps": [
|
|
168
|
+
"string"
|
|
169
|
+
],
|
|
170
|
+
"expected_results": [
|
|
171
|
+
"string"
|
|
172
|
+
]
|
|
173
|
+
}
|
|
174
|
+
]
|
|
175
|
+
}
|
|
176
|
+
```
|
|
177
|
+
|
|
178
|
+
### Field Description
|
|
179
|
+
|
|
180
|
+
- `test_case_id`: Unique test case identifier
|
|
181
|
+
- `title`: Test case title
|
|
182
|
+
- `priority`: Business priority
|
|
183
|
+
- `pre_conditions`: Required setup
|
|
184
|
+
- `test_steps`: Execution steps
|
|
185
|
+
- `expected_results`: Validation outcomes
|
|
186
|
+
|
|
187
|
+
### Example Output
|
|
188
|
+
|
|
189
|
+
```json
|
|
190
|
+
{
|
|
191
|
+
"test_cases": [
|
|
192
|
+
{
|
|
193
|
+
"test_case_id": "TC001",
|
|
194
|
+
"title": "Verify Successful Login",
|
|
195
|
+
"priority": "High",
|
|
196
|
+
"pre_conditions": [
|
|
197
|
+
"User account exists"
|
|
198
|
+
],
|
|
199
|
+
"test_steps": [
|
|
200
|
+
"Open login page",
|
|
201
|
+
"Enter valid credentials",
|
|
202
|
+
"Click Login"
|
|
203
|
+
],
|
|
204
|
+
"expected_results": [
|
|
205
|
+
"Dashboard displayed successfully"
|
|
206
|
+
]
|
|
207
|
+
}
|
|
208
|
+
]
|
|
209
|
+
}
|
|
210
|
+
```
|
|
211
|
+
|
|
212
|
+
---
|
|
213
|
+
|
|
214
|
+
## Skill 3: Defect-Risk-Analyzer
|
|
215
|
+
|
|
216
|
+
### Description
|
|
217
|
+
|
|
218
|
+
Analyze testing quality metrics and determine project risk level before release.
|
|
219
|
+
|
|
220
|
+
### Purpose
|
|
221
|
+
|
|
222
|
+
Provide data-driven risk assessment and release readiness recommendations.
|
|
223
|
+
|
|
224
|
+
### Input Schema
|
|
225
|
+
|
|
226
|
+
```json
|
|
227
|
+
{
|
|
228
|
+
"project_name": "string",
|
|
229
|
+
"total_test_cases": "number",
|
|
230
|
+
"passed_test_cases": "number",
|
|
231
|
+
"failed_test_cases": "number",
|
|
232
|
+
"blocked_test_cases": "number",
|
|
233
|
+
"test_coverage_percentage": "number",
|
|
234
|
+
"critical_defects": "number",
|
|
235
|
+
"major_defects": "number",
|
|
236
|
+
"minor_defects": "number"
|
|
237
|
+
}
|
|
238
|
+
```
|
|
239
|
+
|
|
240
|
+
### Field Description
|
|
241
|
+
|
|
242
|
+
- `project_name`: Project identifier
|
|
243
|
+
- `total_test_cases`: Total test count
|
|
244
|
+
- `passed_test_cases`: Successful executions
|
|
245
|
+
- `failed_test_cases`: Failed executions
|
|
246
|
+
- `blocked_test_cases`: Blocked executions
|
|
247
|
+
- `test_coverage_percentage`: Coverage metric
|
|
248
|
+
- `critical_defects`: Critical severity defects
|
|
249
|
+
- `major_defects`: Major severity defects
|
|
250
|
+
- `minor_defects`: Minor severity defects
|
|
251
|
+
|
|
252
|
+
### Output Schema
|
|
253
|
+
|
|
254
|
+
```json
|
|
255
|
+
{
|
|
256
|
+
"risk_score": "number",
|
|
257
|
+
"risk_level": "string",
|
|
258
|
+
"project_health": "string",
|
|
259
|
+
"release_readiness": "string",
|
|
260
|
+
"recommendations": [
|
|
261
|
+
"string"
|
|
262
|
+
]
|
|
263
|
+
}
|
|
264
|
+
```
|
|
265
|
+
|
|
266
|
+
### Field Description
|
|
267
|
+
|
|
268
|
+
- `risk_score`: Risk score (0-100)
|
|
269
|
+
- `risk_level`: Low, Medium, High, Critical
|
|
270
|
+
- `project_health`: Overall health status
|
|
271
|
+
- `release_readiness`: Ready or Not Ready
|
|
272
|
+
- `recommendations`: Improvement actions
|
|
273
|
+
|
|
274
|
+
### Risk Levels
|
|
275
|
+
|
|
276
|
+
- `0-20`: Low
|
|
277
|
+
- `21-50`: Medium
|
|
278
|
+
- `51-80`: High
|
|
279
|
+
- `81-100`: Critical
|
|
280
|
+
|
|
281
|
+
### Example Output
|
|
282
|
+
|
|
283
|
+
```json
|
|
284
|
+
{
|
|
285
|
+
"risk_score": 78,
|
|
286
|
+
"risk_level": "High",
|
|
287
|
+
"project_health": "At Risk",
|
|
288
|
+
"release_readiness": "Not Ready",
|
|
289
|
+
"recommendations": [
|
|
290
|
+
"Resolve all critical defects",
|
|
291
|
+
"Increase test coverage above 80%",
|
|
292
|
+
"Retest failed test cases"
|
|
293
|
+
]
|
|
294
|
+
}
|
|
295
|
+
```
|
|
296
|
+
|
|
297
|
+
---
|
|
298
|
+
|
|
299
|
+
## Notes
|
|
300
|
+
|
|
301
|
+
- The project also includes a lightweight HTTP server in `server.js` that exposes the available skills through API endpoints.
|
|
302
|
+
- The `src/skill-loader.js` utility reads each skill folder and loads the content of its `SKILL.md` file.
|
|
303
|
+
- The package currently includes the three skills listed above and is ready to be published or shared as a reusable skill bundle.
|
|
@@ -1,88 +1,88 @@
|
|
|
1
|
-
# Requirement Summarizer
|
|
2
|
-
|
|
3
|
-
## Description
|
|
4
|
-
|
|
5
|
-
The Requirement Summarizer analyzes requirements and user stories, extracting key business goals, features, acceptance criteria, and risks.
|
|
6
|
-
|
|
7
|
-
## Purpose
|
|
8
|
-
|
|
9
|
-
Transform lengthy requirement documents into concise and actionable summaries.
|
|
10
|
-
|
|
11
|
-
---
|
|
12
|
-
|
|
13
|
-
## Input Schema
|
|
14
|
-
|
|
15
|
-
{
|
|
16
|
-
"document_title": "string",
|
|
17
|
-
"document_type": "string",
|
|
18
|
-
"requirement_text": "string",
|
|
19
|
-
"project_name": "string",
|
|
20
|
-
"author": "string",
|
|
21
|
-
"created_date": "datetime"
|
|
22
|
-
}
|
|
23
|
-
|
|
24
|
-
### Field Description
|
|
25
|
-
|
|
26
|
-
- document_title: Name of the requirement document
|
|
27
|
-
- document_type: BRD, FRD, User Story, Epic, etc.
|
|
28
|
-
- requirement_text: Full requirement content
|
|
29
|
-
- project_name: Associated project
|
|
30
|
-
- author: Requirement owner
|
|
31
|
-
- created_date: Document creation date
|
|
32
|
-
|
|
33
|
-
---
|
|
34
|
-
|
|
35
|
-
## Output Schema
|
|
36
|
-
|
|
37
|
-
{
|
|
38
|
-
"summary": "string",
|
|
39
|
-
"business_objectives": [
|
|
40
|
-
"string"
|
|
41
|
-
],
|
|
42
|
-
"key_features": [
|
|
43
|
-
"string"
|
|
44
|
-
],
|
|
45
|
-
"acceptance_criteria": [
|
|
46
|
-
"string"
|
|
47
|
-
],
|
|
48
|
-
"risks": [
|
|
49
|
-
"string"
|
|
50
|
-
],
|
|
51
|
-
"assumptions": [
|
|
52
|
-
"string"
|
|
53
|
-
]
|
|
54
|
-
}
|
|
55
|
-
|
|
56
|
-
### Field Description
|
|
57
|
-
|
|
58
|
-
- summary: Concise requirement overview
|
|
59
|
-
- business_objectives: Primary business goals
|
|
60
|
-
- key_features: Main system capabilities
|
|
61
|
-
- acceptance_criteria: Conditions for successful implementation
|
|
62
|
-
- risks: Potential project risks
|
|
63
|
-
- assumptions: Assumptions identified from requirements
|
|
64
|
-
|
|
65
|
-
---
|
|
66
|
-
|
|
67
|
-
## Example Output
|
|
68
|
-
|
|
69
|
-
{
|
|
70
|
-
"summary": "Users can access dashboards after authentication.",
|
|
71
|
-
"business_objectives": [
|
|
72
|
-
"Improve visibility of production data"
|
|
73
|
-
],
|
|
74
|
-
"key_features": [
|
|
75
|
-
"User Authentication",
|
|
76
|
-
"Dashboard Access"
|
|
77
|
-
],
|
|
78
|
-
"acceptance_criteria": [
|
|
79
|
-
"User can log in successfully",
|
|
80
|
-
"Dashboard loads within 3 seconds"
|
|
81
|
-
],
|
|
82
|
-
"risks": [
|
|
83
|
-
"Single Sign-On dependency"
|
|
84
|
-
],
|
|
85
|
-
"assumptions": [
|
|
86
|
-
"Users possess valid credentials"
|
|
87
|
-
]
|
|
88
|
-
}
|
|
1
|
+
# Requirement Summarizer
|
|
2
|
+
|
|
3
|
+
## Description
|
|
4
|
+
|
|
5
|
+
The Requirement Summarizer analyzes requirements and user stories, extracting key business goals, features, acceptance criteria, and risks.
|
|
6
|
+
|
|
7
|
+
## Purpose
|
|
8
|
+
|
|
9
|
+
Transform lengthy requirement documents into concise and actionable summaries.
|
|
10
|
+
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
## Input Schema
|
|
14
|
+
|
|
15
|
+
{
|
|
16
|
+
"document_title": "string",
|
|
17
|
+
"document_type": "string",
|
|
18
|
+
"requirement_text": "string",
|
|
19
|
+
"project_name": "string",
|
|
20
|
+
"author": "string",
|
|
21
|
+
"created_date": "datetime"
|
|
22
|
+
}
|
|
23
|
+
|
|
24
|
+
### Field Description
|
|
25
|
+
|
|
26
|
+
- document_title: Name of the requirement document
|
|
27
|
+
- document_type: BRD, FRD, User Story, Epic, etc.
|
|
28
|
+
- requirement_text: Full requirement content
|
|
29
|
+
- project_name: Associated project
|
|
30
|
+
- author: Requirement owner
|
|
31
|
+
- created_date: Document creation date
|
|
32
|
+
|
|
33
|
+
---
|
|
34
|
+
|
|
35
|
+
## Output Schema
|
|
36
|
+
|
|
37
|
+
{
|
|
38
|
+
"summary": "string",
|
|
39
|
+
"business_objectives": [
|
|
40
|
+
"string"
|
|
41
|
+
],
|
|
42
|
+
"key_features": [
|
|
43
|
+
"string"
|
|
44
|
+
],
|
|
45
|
+
"acceptance_criteria": [
|
|
46
|
+
"string"
|
|
47
|
+
],
|
|
48
|
+
"risks": [
|
|
49
|
+
"string"
|
|
50
|
+
],
|
|
51
|
+
"assumptions": [
|
|
52
|
+
"string"
|
|
53
|
+
]
|
|
54
|
+
}
|
|
55
|
+
|
|
56
|
+
### Field Description
|
|
57
|
+
|
|
58
|
+
- summary: Concise requirement overview
|
|
59
|
+
- business_objectives: Primary business goals
|
|
60
|
+
- key_features: Main system capabilities
|
|
61
|
+
- acceptance_criteria: Conditions for successful implementation
|
|
62
|
+
- risks: Potential project risks
|
|
63
|
+
- assumptions: Assumptions identified from requirements
|
|
64
|
+
|
|
65
|
+
---
|
|
66
|
+
|
|
67
|
+
## Example Output
|
|
68
|
+
|
|
69
|
+
{
|
|
70
|
+
"summary": "Users can access dashboards after authentication.",
|
|
71
|
+
"business_objectives": [
|
|
72
|
+
"Improve visibility of production data"
|
|
73
|
+
],
|
|
74
|
+
"key_features": [
|
|
75
|
+
"User Authentication",
|
|
76
|
+
"Dashboard Access"
|
|
77
|
+
],
|
|
78
|
+
"acceptance_criteria": [
|
|
79
|
+
"User can log in successfully",
|
|
80
|
+
"Dashboard loads within 3 seconds"
|
|
81
|
+
],
|
|
82
|
+
"risks": [
|
|
83
|
+
"Single Sign-On dependency"
|
|
84
|
+
],
|
|
85
|
+
"assumptions": [
|
|
86
|
+
"Users possess valid credentials"
|
|
87
|
+
]
|
|
88
|
+
}
|
|
@@ -1,91 +1,91 @@
|
|
|
1
|
-
# Test Case Generator
|
|
2
|
-
|
|
3
|
-
## Description
|
|
4
|
-
|
|
5
|
-
Generate test scenarios and test cases from requirements and acceptance criteria.
|
|
6
|
-
|
|
7
|
-
## Purpose
|
|
8
|
-
|
|
9
|
-
Accelerate software testing preparation and improve test coverage.
|
|
10
|
-
|
|
11
|
-
---
|
|
12
|
-
|
|
13
|
-
## Input Schema
|
|
14
|
-
|
|
15
|
-
{
|
|
16
|
-
"requirement_id": "string",
|
|
17
|
-
"requirement_title": "string",
|
|
18
|
-
"summary": "string",
|
|
19
|
-
"acceptance_criteria": [
|
|
20
|
-
"string"
|
|
21
|
-
],
|
|
22
|
-
"application_type": "string",
|
|
23
|
-
"priority": "string"
|
|
24
|
-
}
|
|
25
|
-
|
|
26
|
-
### Field Description
|
|
27
|
-
|
|
28
|
-
- requirement_id: Unique requirement identifier
|
|
29
|
-
- requirement_title: Requirement title
|
|
30
|
-
- summary: Requirement summary
|
|
31
|
-
- acceptance_criteria: List of acceptance criteria
|
|
32
|
-
- application_type: Web, Mobile, Desktop, API
|
|
33
|
-
- priority: High, Medium, Low
|
|
34
|
-
|
|
35
|
-
---
|
|
36
|
-
|
|
37
|
-
## Output Schema
|
|
38
|
-
|
|
39
|
-
{
|
|
40
|
-
"test_cases": [
|
|
41
|
-
{
|
|
42
|
-
"test_case_id": "string",
|
|
43
|
-
"title": "string",
|
|
44
|
-
"priority": "string",
|
|
45
|
-
"pre_conditions": [
|
|
46
|
-
"string"
|
|
47
|
-
],
|
|
48
|
-
"test_steps": [
|
|
49
|
-
"string"
|
|
50
|
-
],
|
|
51
|
-
"expected_results": [
|
|
52
|
-
"string"
|
|
53
|
-
]
|
|
54
|
-
}
|
|
55
|
-
]
|
|
56
|
-
}
|
|
57
|
-
|
|
58
|
-
### Field Description
|
|
59
|
-
|
|
60
|
-
- test_case_id: Unique test case identifier
|
|
61
|
-
- title: Test case title
|
|
62
|
-
- priority: Business priority
|
|
63
|
-
- pre_conditions: Required setup
|
|
64
|
-
- test_steps: Execution steps
|
|
65
|
-
- expected_results: Validation outcomes
|
|
66
|
-
|
|
67
|
-
---
|
|
68
|
-
|
|
69
|
-
## Example Output
|
|
70
|
-
|
|
71
|
-
{
|
|
72
|
-
"test_cases": [
|
|
73
|
-
{
|
|
74
|
-
"test_case_id": "TC001",
|
|
75
|
-
"title": "Verify Successful Login",
|
|
76
|
-
"priority": "High",
|
|
77
|
-
"pre_conditions": [
|
|
78
|
-
"User account exists"
|
|
79
|
-
],
|
|
80
|
-
"test_steps": [
|
|
81
|
-
"Open login page",
|
|
82
|
-
"Enter valid credentials",
|
|
83
|
-
"Click Login"
|
|
84
|
-
],
|
|
85
|
-
"expected_results": [
|
|
86
|
-
"Dashboard displayed successfully"
|
|
87
|
-
]
|
|
88
|
-
}
|
|
89
|
-
]
|
|
90
|
-
}
|
|
1
|
+
# Test Case Generator
|
|
2
|
+
|
|
3
|
+
## Description
|
|
4
|
+
|
|
5
|
+
Generate test scenarios and test cases from requirements and acceptance criteria.
|
|
6
|
+
|
|
7
|
+
## Purpose
|
|
8
|
+
|
|
9
|
+
Accelerate software testing preparation and improve test coverage.
|
|
10
|
+
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
## Input Schema
|
|
14
|
+
|
|
15
|
+
{
|
|
16
|
+
"requirement_id": "string",
|
|
17
|
+
"requirement_title": "string",
|
|
18
|
+
"summary": "string",
|
|
19
|
+
"acceptance_criteria": [
|
|
20
|
+
"string"
|
|
21
|
+
],
|
|
22
|
+
"application_type": "string",
|
|
23
|
+
"priority": "string"
|
|
24
|
+
}
|
|
25
|
+
|
|
26
|
+
### Field Description
|
|
27
|
+
|
|
28
|
+
- requirement_id: Unique requirement identifier
|
|
29
|
+
- requirement_title: Requirement title
|
|
30
|
+
- summary: Requirement summary
|
|
31
|
+
- acceptance_criteria: List of acceptance criteria
|
|
32
|
+
- application_type: Web, Mobile, Desktop, API
|
|
33
|
+
- priority: High, Medium, Low
|
|
34
|
+
|
|
35
|
+
---
|
|
36
|
+
|
|
37
|
+
## Output Schema
|
|
38
|
+
|
|
39
|
+
{
|
|
40
|
+
"test_cases": [
|
|
41
|
+
{
|
|
42
|
+
"test_case_id": "string",
|
|
43
|
+
"title": "string",
|
|
44
|
+
"priority": "string",
|
|
45
|
+
"pre_conditions": [
|
|
46
|
+
"string"
|
|
47
|
+
],
|
|
48
|
+
"test_steps": [
|
|
49
|
+
"string"
|
|
50
|
+
],
|
|
51
|
+
"expected_results": [
|
|
52
|
+
"string"
|
|
53
|
+
]
|
|
54
|
+
}
|
|
55
|
+
]
|
|
56
|
+
}
|
|
57
|
+
|
|
58
|
+
### Field Description
|
|
59
|
+
|
|
60
|
+
- test_case_id: Unique test case identifier
|
|
61
|
+
- title: Test case title
|
|
62
|
+
- priority: Business priority
|
|
63
|
+
- pre_conditions: Required setup
|
|
64
|
+
- test_steps: Execution steps
|
|
65
|
+
- expected_results: Validation outcomes
|
|
66
|
+
|
|
67
|
+
---
|
|
68
|
+
|
|
69
|
+
## Example Output
|
|
70
|
+
|
|
71
|
+
{
|
|
72
|
+
"test_cases": [
|
|
73
|
+
{
|
|
74
|
+
"test_case_id": "TC001",
|
|
75
|
+
"title": "Verify Successful Login",
|
|
76
|
+
"priority": "High",
|
|
77
|
+
"pre_conditions": [
|
|
78
|
+
"User account exists"
|
|
79
|
+
],
|
|
80
|
+
"test_steps": [
|
|
81
|
+
"Open login page",
|
|
82
|
+
"Enter valid credentials",
|
|
83
|
+
"Click Login"
|
|
84
|
+
],
|
|
85
|
+
"expected_results": [
|
|
86
|
+
"Dashboard displayed successfully"
|
|
87
|
+
]
|
|
88
|
+
}
|
|
89
|
+
]
|
|
90
|
+
}
|
|
91
91
|
`
|
package/package.json
CHANGED
|
@@ -1,15 +1,19 @@
|
|
|
1
|
-
{
|
|
2
|
-
"name": "@cleverpeople/my-skills",
|
|
3
|
-
"version": "1.3.
|
|
4
|
-
"private": false,
|
|
5
|
-
"description": "Shared skill definitions bundle for My Skills.",
|
|
6
|
-
"
|
|
7
|
-
|
|
8
|
-
"
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
"
|
|
14
|
-
|
|
15
|
-
|
|
1
|
+
{
|
|
2
|
+
"name": "@cleverpeople/my-skills",
|
|
3
|
+
"version": "1.3.5",
|
|
4
|
+
"private": false,
|
|
5
|
+
"description": "Shared skill definitions bundle for My Skills.",
|
|
6
|
+
"type": "module",
|
|
7
|
+
"scripts": {
|
|
8
|
+
"test": "node --test"
|
|
9
|
+
},
|
|
10
|
+
"files": [
|
|
11
|
+
"Requirement-Summarizer",
|
|
12
|
+
"Test-Case-Generator",
|
|
13
|
+
"Defect-Risk-Analyzer",
|
|
14
|
+
"README.md"
|
|
15
|
+
],
|
|
16
|
+
"publishConfig": {
|
|
17
|
+
"access": "public"
|
|
18
|
+
}
|
|
19
|
+
}
|