@sppg2001/atomize 0.0.1
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/.env.example +3 -0
- package/LICENSE +21 -0
- package/README.md +17 -0
- package/dist/cli/index.js +113341 -0
- package/package.json +81 -0
- package/templates/backend.yaml +124 -0
- package/templates/frontend.yaml +123 -0
- package/templates/fullstack.yaml +169 -0
package/package.json
ADDED
|
@@ -0,0 +1,81 @@
|
|
|
1
|
+
{
|
|
2
|
+
"name": "@sppg2001/atomize",
|
|
3
|
+
"version": "0.0.1",
|
|
4
|
+
"description": "⚛️ Automatically generate tasks from user stories with smart templates",
|
|
5
|
+
"type": "module",
|
|
6
|
+
"main": "./dist/cli/index.js",
|
|
7
|
+
"bin": {
|
|
8
|
+
"atomize": "./dist/cli/index.js",
|
|
9
|
+
"atom": "./dist/cli/index.js"
|
|
10
|
+
},
|
|
11
|
+
"publishConfig": {
|
|
12
|
+
"access": "public",
|
|
13
|
+
"tag": "latest"
|
|
14
|
+
},
|
|
15
|
+
"files": [
|
|
16
|
+
"dist",
|
|
17
|
+
"templates",
|
|
18
|
+
"README.md",
|
|
19
|
+
"LICENSE",
|
|
20
|
+
".env.example"
|
|
21
|
+
],
|
|
22
|
+
"scripts": {
|
|
23
|
+
"dev": "bun run src/cli/index.ts",
|
|
24
|
+
"build": "npm run typecheck && npm run build:bun",
|
|
25
|
+
"postbuild": "node make-executable.js",
|
|
26
|
+
"build:bun": " bun build ./src/cli/index.ts --outdir ./dist/cli --target node --format esm && node make-executable.js",
|
|
27
|
+
"build:standalone": "bun build src/cli/index.ts --compile --outfile atomize",
|
|
28
|
+
"prepublishOnly": "npm run build",
|
|
29
|
+
"test": "bun test",
|
|
30
|
+
"test:unit": "bun test tests/unit",
|
|
31
|
+
"test:integration": "bun test tests/integration.test.ts",
|
|
32
|
+
"test:watch": "bun test --watch",
|
|
33
|
+
"test:coverage": "bun test --coverage",
|
|
34
|
+
"typecheck": "tsc --noEmit",
|
|
35
|
+
"validate": "bun run src/cli/index.ts validate",
|
|
36
|
+
"check": "bun typecheck && bun test"
|
|
37
|
+
},
|
|
38
|
+
"keywords": [
|
|
39
|
+
"devops",
|
|
40
|
+
"azure-devops",
|
|
41
|
+
"task-automation",
|
|
42
|
+
"task-generation",
|
|
43
|
+
"agile",
|
|
44
|
+
"scrum",
|
|
45
|
+
"sprint-planning",
|
|
46
|
+
"cli",
|
|
47
|
+
"automation",
|
|
48
|
+
"productivity"
|
|
49
|
+
],
|
|
50
|
+
"repository": {
|
|
51
|
+
"type": "git",
|
|
52
|
+
"url": "https://github.com/Simao-Pereira-Gomes/atomize.git"
|
|
53
|
+
},
|
|
54
|
+
"bugs": {
|
|
55
|
+
"url": "https://github.com/Simao-Pereira-Gomes/atomize/issues"
|
|
56
|
+
},
|
|
57
|
+
"author": "Simão Pereira Gomes",
|
|
58
|
+
"license": "MIT",
|
|
59
|
+
"devDependencies": {
|
|
60
|
+
"@types/bun": "1.3.5",
|
|
61
|
+
"@types/inquirer": "^9.0.9",
|
|
62
|
+
"@types/node": "^25.0.3",
|
|
63
|
+
"chalk": "^5.6.2"
|
|
64
|
+
},
|
|
65
|
+
"peerDependencies": {
|
|
66
|
+
"typescript": "^5.9.3"
|
|
67
|
+
},
|
|
68
|
+
"dependencies": {
|
|
69
|
+
"azure-devops-node-api": "^15.1.2",
|
|
70
|
+
"commander": "^14.0.2",
|
|
71
|
+
"dotenv": "^17.2.3",
|
|
72
|
+
"inquirer": "^13.1.0",
|
|
73
|
+
"ts-pattern": "^5.9.0",
|
|
74
|
+
"winston": "^3.19.0",
|
|
75
|
+
"yaml": "^2.8.2",
|
|
76
|
+
"zod": "^4.2.1"
|
|
77
|
+
},
|
|
78
|
+
"engines": {
|
|
79
|
+
"node": ">=18.0.0"
|
|
80
|
+
}
|
|
81
|
+
}
|
|
@@ -0,0 +1,124 @@
|
|
|
1
|
+
version: "1.0"
|
|
2
|
+
name: "Backend API Feature"
|
|
3
|
+
description: "Standard tasks for backend API development"
|
|
4
|
+
author: "Atomize"
|
|
5
|
+
tags: ["backend", "api", "standard"]
|
|
6
|
+
|
|
7
|
+
# Filter to identify applicable User Stories
|
|
8
|
+
filter:
|
|
9
|
+
workItemTypes:
|
|
10
|
+
- "User Story"
|
|
11
|
+
- "Product Backlog Item"
|
|
12
|
+
states:
|
|
13
|
+
- "New"
|
|
14
|
+
- "Approved"
|
|
15
|
+
- "Active"
|
|
16
|
+
tags:
|
|
17
|
+
include:
|
|
18
|
+
- "backend"
|
|
19
|
+
- "api"
|
|
20
|
+
excludeIfHasTasks: true
|
|
21
|
+
|
|
22
|
+
# Task template with estimation percentages
|
|
23
|
+
tasks:
|
|
24
|
+
- id: "design-api"
|
|
25
|
+
title: "Design API Specification"
|
|
26
|
+
description: |
|
|
27
|
+
Design RESTful API endpoints following company standards:
|
|
28
|
+
- Define request/response models
|
|
29
|
+
- Document in OpenAPI/Swagger
|
|
30
|
+
- Review with team architect
|
|
31
|
+
estimationPercent: 10
|
|
32
|
+
tags: ["design", "api"]
|
|
33
|
+
activity: "Design"
|
|
34
|
+
|
|
35
|
+
- id: "database-schema"
|
|
36
|
+
title: "Database Schema Changes"
|
|
37
|
+
description: |
|
|
38
|
+
Design and implement database changes:
|
|
39
|
+
- Create/update migrations
|
|
40
|
+
- Define models and relationships
|
|
41
|
+
- Index optimization
|
|
42
|
+
estimationPercent: 20
|
|
43
|
+
tags: ["database", "backend"]
|
|
44
|
+
activity: "Development"
|
|
45
|
+
|
|
46
|
+
- id: "implement-logic"
|
|
47
|
+
title: "Implement Business Logic"
|
|
48
|
+
description: |
|
|
49
|
+
Core API implementation:
|
|
50
|
+
- Implement service layer
|
|
51
|
+
- Add validation logic
|
|
52
|
+
- Error handling
|
|
53
|
+
- Logging
|
|
54
|
+
estimationPercent: 35
|
|
55
|
+
tags: ["implementation", "backend"]
|
|
56
|
+
activity: "Development"
|
|
57
|
+
dependsOn:
|
|
58
|
+
- "design-api"
|
|
59
|
+
- "database-schema"
|
|
60
|
+
|
|
61
|
+
- id: "unit-tests"
|
|
62
|
+
title: "Unit & Integration Tests"
|
|
63
|
+
description: |
|
|
64
|
+
Comprehensive test coverage:
|
|
65
|
+
- Unit tests (80%+ coverage)
|
|
66
|
+
- Integration tests
|
|
67
|
+
- Mock external dependencies
|
|
68
|
+
estimationPercent: 20
|
|
69
|
+
tags: ["testing", "quality"]
|
|
70
|
+
activity: "Testing"
|
|
71
|
+
dependsOn:
|
|
72
|
+
- "implement-logic"
|
|
73
|
+
|
|
74
|
+
- id: "documentation"
|
|
75
|
+
title: "API Documentation"
|
|
76
|
+
description: |
|
|
77
|
+
Update documentation:
|
|
78
|
+
- API endpoint documentation
|
|
79
|
+
- Update README
|
|
80
|
+
- Code comments
|
|
81
|
+
- Postman collection
|
|
82
|
+
estimationPercent: 5
|
|
83
|
+
tags: ["documentation"]
|
|
84
|
+
activity: "Documentation"
|
|
85
|
+
|
|
86
|
+
- id: "code-review"
|
|
87
|
+
title: "Code Review & Refinement"
|
|
88
|
+
description: |
|
|
89
|
+
Review and refine:
|
|
90
|
+
- Create pull request
|
|
91
|
+
- Address review feedback
|
|
92
|
+
- Final testing
|
|
93
|
+
estimationPercent: 10
|
|
94
|
+
tags: ["review", "quality"]
|
|
95
|
+
activity: "Design"
|
|
96
|
+
|
|
97
|
+
# Estimation strategy
|
|
98
|
+
estimation:
|
|
99
|
+
strategy: "percentage"
|
|
100
|
+
source: "Microsoft.VSTS.Scheduling.StoryPoints"
|
|
101
|
+
rounding: "nearest"
|
|
102
|
+
minimumTaskPoints: 0.5
|
|
103
|
+
|
|
104
|
+
# Validation rules
|
|
105
|
+
validation:
|
|
106
|
+
totalEstimationMustBe: 100
|
|
107
|
+
minTasks: 4
|
|
108
|
+
maxTasks: 10
|
|
109
|
+
|
|
110
|
+
# Metadata
|
|
111
|
+
metadata:
|
|
112
|
+
category: "Backend Development"
|
|
113
|
+
difficulty: "intermediate"
|
|
114
|
+
recommendedFor:
|
|
115
|
+
- "API features"
|
|
116
|
+
- "Microservices"
|
|
117
|
+
- "Backend services"
|
|
118
|
+
estimationGuidelines: |
|
|
119
|
+
Use this template for stories sized 3-13 points.
|
|
120
|
+
For larger stories, consider breaking down first.
|
|
121
|
+
examples:
|
|
122
|
+
- "User authentication API"
|
|
123
|
+
- "Payment processing endpoint"
|
|
124
|
+
- "Data export service"
|
|
@@ -0,0 +1,123 @@
|
|
|
1
|
+
version: "1.0"
|
|
2
|
+
name: "Frontend React Feature"
|
|
3
|
+
description: "Standard tasks for React component development"
|
|
4
|
+
author: "Atomize"
|
|
5
|
+
tags: ["frontend", "react", "ui"]
|
|
6
|
+
|
|
7
|
+
filter:
|
|
8
|
+
workItemTypes:
|
|
9
|
+
- "User Story"
|
|
10
|
+
states:
|
|
11
|
+
- "New"
|
|
12
|
+
- "Approved"
|
|
13
|
+
tags:
|
|
14
|
+
include:
|
|
15
|
+
- "frontend"
|
|
16
|
+
- "react"
|
|
17
|
+
excludeIfHasTasks: true
|
|
18
|
+
|
|
19
|
+
tasks:
|
|
20
|
+
- id: "ui-design-review"
|
|
21
|
+
title: " UI/UX Design Review"
|
|
22
|
+
description: |
|
|
23
|
+
Review designs and create implementation plan:
|
|
24
|
+
- Review Figma/design specs
|
|
25
|
+
- Identify reusable components
|
|
26
|
+
- Plan component hierarchy
|
|
27
|
+
- Clarify interactions and states
|
|
28
|
+
estimationPercent: 10
|
|
29
|
+
tags: ["design", "planning"]
|
|
30
|
+
activity: "Design"
|
|
31
|
+
|
|
32
|
+
- id: "component-structure"
|
|
33
|
+
title: "Component Structure & Setup"
|
|
34
|
+
description: |
|
|
35
|
+
Set up component architecture:
|
|
36
|
+
- Create component files
|
|
37
|
+
- Define props interfaces
|
|
38
|
+
- Set up state management
|
|
39
|
+
- Configure routing (if needed)
|
|
40
|
+
estimationPercent: 15
|
|
41
|
+
tags: ["setup", "architecture"]
|
|
42
|
+
activity: "Development"
|
|
43
|
+
|
|
44
|
+
- id: "component-logic"
|
|
45
|
+
title: "Component Logic Implementation"
|
|
46
|
+
description: |
|
|
47
|
+
Implement core functionality:
|
|
48
|
+
- Business logic
|
|
49
|
+
- Event handlers
|
|
50
|
+
- API integration
|
|
51
|
+
- Form validation
|
|
52
|
+
estimationPercent: 30
|
|
53
|
+
tags: ["implementation", "logic"]
|
|
54
|
+
activity: "Development"
|
|
55
|
+
dependsOn:
|
|
56
|
+
- "component-structure"
|
|
57
|
+
|
|
58
|
+
- id: "styling"
|
|
59
|
+
title: "Styling & Responsive Design"
|
|
60
|
+
description: |
|
|
61
|
+
Apply styles and ensure responsiveness:
|
|
62
|
+
- CSS/Tailwind implementation
|
|
63
|
+
- Mobile responsiveness
|
|
64
|
+
- Theme integration
|
|
65
|
+
- Dark mode (if applicable)
|
|
66
|
+
estimationPercent: 20
|
|
67
|
+
tags: ["styling", "css", "responsive"]
|
|
68
|
+
activity: "Development"
|
|
69
|
+
|
|
70
|
+
- id: "accessibility"
|
|
71
|
+
title: "Accessibility Testing"
|
|
72
|
+
description: |
|
|
73
|
+
Ensure WCAG 2.1 AA compliance:
|
|
74
|
+
- Keyboard navigation
|
|
75
|
+
- Screen reader testing
|
|
76
|
+
- ARIA labels
|
|
77
|
+
- Color contrast
|
|
78
|
+
- Focus management
|
|
79
|
+
estimationPercent: 10
|
|
80
|
+
tags: ["accessibility", "a11y", "quality"]
|
|
81
|
+
activity: "Testing"
|
|
82
|
+
|
|
83
|
+
- id: "component-tests"
|
|
84
|
+
title: "Component Testing"
|
|
85
|
+
description: |
|
|
86
|
+
Write comprehensive tests:
|
|
87
|
+
- Jest unit tests
|
|
88
|
+
- React Testing Library
|
|
89
|
+
- Test user interactions
|
|
90
|
+
- Snapshot tests
|
|
91
|
+
estimationPercent: 15
|
|
92
|
+
tags: ["testing", "quality"]
|
|
93
|
+
activity: "Testing"
|
|
94
|
+
dependsOn:
|
|
95
|
+
- "component-logic"
|
|
96
|
+
|
|
97
|
+
# Estimation configuration
|
|
98
|
+
estimation:
|
|
99
|
+
strategy: "percentage"
|
|
100
|
+
source: "Microsoft.VSTS.Scheduling.StoryPoints"
|
|
101
|
+
rounding: "nearest"
|
|
102
|
+
minimumTaskPoints: 0.5
|
|
103
|
+
|
|
104
|
+
# Validation
|
|
105
|
+
validation:
|
|
106
|
+
totalEstimationMustBe: 100
|
|
107
|
+
minTasks: 4
|
|
108
|
+
|
|
109
|
+
# Metadata
|
|
110
|
+
metadata:
|
|
111
|
+
category: "Frontend Development"
|
|
112
|
+
difficulty: "intermediate"
|
|
113
|
+
recommendedFor:
|
|
114
|
+
- "React components"
|
|
115
|
+
- "UI features"
|
|
116
|
+
- "User interfaces"
|
|
117
|
+
estimationGuidelines: |
|
|
118
|
+
Best for stories sized 3-8 points.
|
|
119
|
+
Complex UIs with animations may need additional tasks.
|
|
120
|
+
examples:
|
|
121
|
+
- "User profile page"
|
|
122
|
+
- "Data table component"
|
|
123
|
+
- "Form wizard"
|
|
@@ -0,0 +1,169 @@
|
|
|
1
|
+
version: "1.0"
|
|
2
|
+
name: "Fullstack Feature"
|
|
3
|
+
description: "Complete fullstack feature with frontend and backend tasks"
|
|
4
|
+
author: "Atomize"
|
|
5
|
+
tags: ["fullstack", "frontend", "backend"]
|
|
6
|
+
|
|
7
|
+
filter:
|
|
8
|
+
workItemTypes:
|
|
9
|
+
- "User Story"
|
|
10
|
+
states:
|
|
11
|
+
- "New"
|
|
12
|
+
- "Active"
|
|
13
|
+
tags:
|
|
14
|
+
include:
|
|
15
|
+
- "fullstack"
|
|
16
|
+
excludeIfHasTasks: true
|
|
17
|
+
|
|
18
|
+
# Variables for conditionals
|
|
19
|
+
variables:
|
|
20
|
+
hasDatabase: true
|
|
21
|
+
hasAuth: false
|
|
22
|
+
|
|
23
|
+
tasks:
|
|
24
|
+
# Design Phase
|
|
25
|
+
- id: "design-overview"
|
|
26
|
+
title: "Technical Design"
|
|
27
|
+
description: |
|
|
28
|
+
Create comprehensive technical design:
|
|
29
|
+
- Architecture diagram
|
|
30
|
+
- API contract definition
|
|
31
|
+
- Data models
|
|
32
|
+
- UI/UX flow
|
|
33
|
+
estimationPercent: 10
|
|
34
|
+
tags: ["design", "planning"]
|
|
35
|
+
activity: "Design"
|
|
36
|
+
|
|
37
|
+
# Backend Tasks
|
|
38
|
+
- id: "backend-api"
|
|
39
|
+
title: " Backend API Implementation"
|
|
40
|
+
description: |
|
|
41
|
+
Implement backend API:
|
|
42
|
+
- API endpoints
|
|
43
|
+
- Business logic
|
|
44
|
+
- Validation
|
|
45
|
+
- Error handling
|
|
46
|
+
estimationPercent: 20
|
|
47
|
+
tags: ["backend", "api"]
|
|
48
|
+
activity: "Development"
|
|
49
|
+
dependsOn: ["design-overview"]
|
|
50
|
+
|
|
51
|
+
- id: "database"
|
|
52
|
+
title: "Database Implementation"
|
|
53
|
+
description: |
|
|
54
|
+
Database changes:
|
|
55
|
+
- Schema migrations
|
|
56
|
+
- Models
|
|
57
|
+
- Queries
|
|
58
|
+
- Indexes
|
|
59
|
+
estimationPercent: 15
|
|
60
|
+
tags: ["database", "backend"]
|
|
61
|
+
activity: "Development"
|
|
62
|
+
condition: "${variables.hasDatabase}"
|
|
63
|
+
|
|
64
|
+
- id: "backend-tests"
|
|
65
|
+
title: "Backend Tests"
|
|
66
|
+
description: |
|
|
67
|
+
Backend test coverage:
|
|
68
|
+
- Unit tests (80%+)
|
|
69
|
+
- Integration tests
|
|
70
|
+
- API endpoint tests
|
|
71
|
+
estimationPercent: 10
|
|
72
|
+
tags: ["testing", "backend"]
|
|
73
|
+
activity: "Testing"
|
|
74
|
+
dependsOn: ["backend-api"]
|
|
75
|
+
|
|
76
|
+
# Frontend Tasks
|
|
77
|
+
- id: "frontend-components"
|
|
78
|
+
title: "Frontend Components"
|
|
79
|
+
description: |
|
|
80
|
+
Build React components:
|
|
81
|
+
- Component structure
|
|
82
|
+
- Props interfaces
|
|
83
|
+
- State management
|
|
84
|
+
- Event handlers
|
|
85
|
+
estimationPercent: 20
|
|
86
|
+
tags: ["frontend", "react"]
|
|
87
|
+
activity: "Development"
|
|
88
|
+
dependsOn: ["design-overview"]
|
|
89
|
+
|
|
90
|
+
- id: "frontend-styling"
|
|
91
|
+
title: "Styling & Responsive Design"
|
|
92
|
+
description: |
|
|
93
|
+
Apply styles:
|
|
94
|
+
- CSS/Tailwind
|
|
95
|
+
- Mobile responsive
|
|
96
|
+
- Theme integration
|
|
97
|
+
estimationPercent: 10
|
|
98
|
+
tags: ["frontend", "styling"]
|
|
99
|
+
activity: "Development"
|
|
100
|
+
|
|
101
|
+
- id: "frontend-tests"
|
|
102
|
+
title: "Frontend Tests"
|
|
103
|
+
description: |
|
|
104
|
+
Frontend test coverage:
|
|
105
|
+
- Component tests
|
|
106
|
+
- User interaction tests
|
|
107
|
+
- Snapshot tests
|
|
108
|
+
estimationPercent: 8
|
|
109
|
+
tags: ["testing", "frontend"]
|
|
110
|
+
activity: "Testing"
|
|
111
|
+
dependsOn: ["frontend-components"]
|
|
112
|
+
|
|
113
|
+
# Integration
|
|
114
|
+
- id: "integration"
|
|
115
|
+
title: "Frontend-Backend Integration"
|
|
116
|
+
description: |
|
|
117
|
+
Connect frontend to backend:
|
|
118
|
+
- API integration
|
|
119
|
+
- Error handling
|
|
120
|
+
- Loading states
|
|
121
|
+
- Data flow testing
|
|
122
|
+
estimationPercent: 12
|
|
123
|
+
tags: ["integration"]
|
|
124
|
+
activity: "Development"
|
|
125
|
+
dependsOn: ["backend-api", "frontend-components"]
|
|
126
|
+
|
|
127
|
+
# Documentation & Review
|
|
128
|
+
- id: "documentation"
|
|
129
|
+
title: "Documentation"
|
|
130
|
+
description: |
|
|
131
|
+
Complete documentation:
|
|
132
|
+
- API documentation
|
|
133
|
+
- Component documentation
|
|
134
|
+
- README updates
|
|
135
|
+
- Deployment guide
|
|
136
|
+
estimationPercent: 5
|
|
137
|
+
tags: ["documentation"]
|
|
138
|
+
activity: "Documentation"
|
|
139
|
+
|
|
140
|
+
# Estimation configuration
|
|
141
|
+
estimation:
|
|
142
|
+
strategy: "percentage"
|
|
143
|
+
source: "Microsoft.VSTS.Scheduling.StoryPoints"
|
|
144
|
+
rounding: "nearest"
|
|
145
|
+
minimumTaskPoints: 0.5
|
|
146
|
+
|
|
147
|
+
# Validation
|
|
148
|
+
validation:
|
|
149
|
+
totalEstimationRange:
|
|
150
|
+
min: 95
|
|
151
|
+
max: 105
|
|
152
|
+
minTasks: 5
|
|
153
|
+
|
|
154
|
+
# Metadata
|
|
155
|
+
metadata:
|
|
156
|
+
category: "Fullstack Development"
|
|
157
|
+
difficulty: "advanced"
|
|
158
|
+
recommendedFor:
|
|
159
|
+
- "Full features with UI and API"
|
|
160
|
+
- "Complete user flows"
|
|
161
|
+
- "End-to-end features"
|
|
162
|
+
estimationGuidelines: |
|
|
163
|
+
Best for stories sized 5-13 points.
|
|
164
|
+
This template covers both frontend and backend.
|
|
165
|
+
Adjust tasks based on complexity.
|
|
166
|
+
examples:
|
|
167
|
+
- "User registration flow"
|
|
168
|
+
- "Dashboard with data visualization"
|
|
169
|
+
- "Search and filter feature"
|