@sppg2001/atomize 0.0.1 → 1.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 -3
- package/LICENSE +21 -21
- package/README.md +504 -17
- package/dist/cli/index.js +49494 -44659
- package/{templates → examples}/backend.yaml +123 -123
- package/examples/conditional-dependencies-template.yaml +122 -0
- package/{templates → examples}/frontend.yaml +122 -122
- package/{templates → examples}/fullstack.yaml +168 -168
- package/package.json +85 -79
- package/templates/presets/backend-api.yaml +60 -0
- package/templates/presets/bug-fix.yaml +44 -0
- package/templates/presets/custom.yaml +89 -0
- package/templates/presets/frontend-feature.yaml +52 -0
|
@@ -1,124 +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"
|
|
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
124
|
- "Data export service"
|
|
@@ -0,0 +1,122 @@
|
|
|
1
|
+
version: "1.0"
|
|
2
|
+
name: "Full-Stack Development with Conditional Tasks"
|
|
3
|
+
description: "Template demonstrating conditional tasks and dependencies"
|
|
4
|
+
|
|
5
|
+
filter:
|
|
6
|
+
workItemTypes:
|
|
7
|
+
- "User Story"
|
|
8
|
+
tags:
|
|
9
|
+
include:
|
|
10
|
+
- "development"
|
|
11
|
+
|
|
12
|
+
estimation:
|
|
13
|
+
rounding: "nearest"
|
|
14
|
+
minimumTaskPoints: 0.5
|
|
15
|
+
|
|
16
|
+
tasks:
|
|
17
|
+
# Phase 1: Design (always runs)
|
|
18
|
+
- id: "design"
|
|
19
|
+
title: "UI/UX Design and Mockups"
|
|
20
|
+
description: "Create design mockups for ${story.title}"
|
|
21
|
+
estimationPercent: 15
|
|
22
|
+
activity: "Design"
|
|
23
|
+
assignTo: "@ParentAssignee"
|
|
24
|
+
tags:
|
|
25
|
+
- "design"
|
|
26
|
+
|
|
27
|
+
# Phase 2: Backend (conditional - only if story has backend tag)
|
|
28
|
+
- id: "backend-api"
|
|
29
|
+
title: "Backend API Implementation"
|
|
30
|
+
description: "Implement REST API endpoints for ${story.title}"
|
|
31
|
+
estimationPercent: 30
|
|
32
|
+
activity: "Development"
|
|
33
|
+
dependsOn: ["design"]
|
|
34
|
+
condition: '${story.tags} CONTAINS "backend"'
|
|
35
|
+
tags:
|
|
36
|
+
- "backend"
|
|
37
|
+
- "api"
|
|
38
|
+
|
|
39
|
+
# Phase 3: Frontend (conditional - only if story has frontend tag)
|
|
40
|
+
- id: "frontend-ui"
|
|
41
|
+
title: "Frontend UI Implementation"
|
|
42
|
+
description: "Build user interface for ${story.title}"
|
|
43
|
+
estimationPercent: 35
|
|
44
|
+
activity: "Development"
|
|
45
|
+
dependsOn: ["design"]
|
|
46
|
+
condition: '${story.tags} CONTAINS "frontend"'
|
|
47
|
+
tags:
|
|
48
|
+
- "frontend"
|
|
49
|
+
|
|
50
|
+
# Accessibility testing (conditional - only for frontend stories without legacy tag)
|
|
51
|
+
- id: "accessibility-testing"
|
|
52
|
+
title: "Accessibility Testing (WCAG)"
|
|
53
|
+
description: "Ensure UI meets accessibility standards for ${story.title}"
|
|
54
|
+
estimationPercent: 7
|
|
55
|
+
activity: "Testing"
|
|
56
|
+
dependsOn: ["frontend-ui"]
|
|
57
|
+
condition: '${story.tags} CONTAINS "frontend" OR ${story.tags} NOT CONTAINS "legacy"'
|
|
58
|
+
tags:
|
|
59
|
+
- "accessibility"
|
|
60
|
+
- "testing"
|
|
61
|
+
|
|
62
|
+
# Security tasks (conditional - only for high-priority stories with security tag)
|
|
63
|
+
- id: "security-review"
|
|
64
|
+
title: "Security Review and Audit"
|
|
65
|
+
description: "Perform security review for ${story.title}"
|
|
66
|
+
estimationPercent: 8
|
|
67
|
+
activity: "Testing"
|
|
68
|
+
dependsOn: ["backend-api", "frontend-ui"]
|
|
69
|
+
condition: '${story.tags} CONTAINS "security" AND ${story.priority} <= 2'
|
|
70
|
+
priority: 1
|
|
71
|
+
tags:
|
|
72
|
+
- "security"
|
|
73
|
+
|
|
74
|
+
# Phase 4: Testing (depends on what was implemented)
|
|
75
|
+
- id: "unit-tests"
|
|
76
|
+
title: "Unit Tests"
|
|
77
|
+
description: "Write unit tests for ${story.title}"
|
|
78
|
+
estimationPercent: 15
|
|
79
|
+
activity: "Testing"
|
|
80
|
+
dependsOn: ["backend-api", "frontend-ui"]
|
|
81
|
+
tags:
|
|
82
|
+
- "testing"
|
|
83
|
+
|
|
84
|
+
- id: "integration-tests"
|
|
85
|
+
title: "Integration Tests"
|
|
86
|
+
description: "Write integration tests for ${story.title}"
|
|
87
|
+
estimationPercent: 12
|
|
88
|
+
activity: "Testing"
|
|
89
|
+
dependsOn: ["unit-tests"]
|
|
90
|
+
tags:
|
|
91
|
+
- "testing"
|
|
92
|
+
|
|
93
|
+
# Performance testing (conditional - only for stories with high estimation)
|
|
94
|
+
- id: "performance-tests"
|
|
95
|
+
title: "Performance and Load Testing"
|
|
96
|
+
description: "Conduct performance testing for ${story.title}"
|
|
97
|
+
estimationPercent: 10
|
|
98
|
+
activity: "Testing"
|
|
99
|
+
dependsOn: ["integration-tests"]
|
|
100
|
+
condition: '${story.estimation} >= 13'
|
|
101
|
+
tags:
|
|
102
|
+
- "performance"
|
|
103
|
+
|
|
104
|
+
# Phase 5: Documentation (always runs, depends on everything)
|
|
105
|
+
- id: "documentation"
|
|
106
|
+
title: "Technical Documentation"
|
|
107
|
+
description: "Write technical documentation for ${story.title}"
|
|
108
|
+
estimationPercent: 8
|
|
109
|
+
activity: "Documentation"
|
|
110
|
+
dependsOn: ["unit-tests"]
|
|
111
|
+
tags:
|
|
112
|
+
- "documentation"
|
|
113
|
+
|
|
114
|
+
# Deployment (final step, depends on all testing)
|
|
115
|
+
- id: "deployment"
|
|
116
|
+
title: "Deploy to Staging"
|
|
117
|
+
description: "Deploy ${story.title} to staging environment"
|
|
118
|
+
estimationPercent: 5
|
|
119
|
+
activity: "Deployment"
|
|
120
|
+
dependsOn: ["integration-tests", "documentation"]
|
|
121
|
+
tags:
|
|
122
|
+
- "deployment"
|
|
@@ -1,123 +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"
|
|
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
123
|
- "Form wizard"
|