You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/agents/generate-feature.agent.md
+64-11Lines changed: 64 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,60 @@ Provide a Jira ticket number as input to this agent.
25
25
26
26
You are a senior software engineer implementing a feature that automates the full processing of Jira tickets using multiple MCP (Model Context Protocol) servers. Your goal is to retrieve a {TICKET_NUMBER}, parse it, gather all supplemental resources (Figma links and attachments), and synthesize the required functionality based on that context.
27
27
28
-
### Step 0: Read Repository Skills (Required Before All Other Steps)
28
+
### Step 0: Create Feature Implementation Todo List
29
+
30
+
Use `manage_todo_list` to create a checklist before starting implementation.
31
+
32
+
```javascript
33
+
manage_todo_list({
34
+
todoList: [
35
+
{
36
+
id:1,
37
+
title:'Read repository skills',
38
+
status:'not-started'
39
+
},
40
+
{
41
+
id:2,
42
+
title:'Retrieve Jira ticket',
43
+
status:'not-started'
44
+
},
45
+
{
46
+
id:3,
47
+
title:'Parse ticket content for Figma links and attachments',
48
+
status:'not-started'
49
+
},
50
+
{
51
+
id:4,
52
+
title:'Gather supplementary information (Figma/attachments)',
53
+
status:'not-started'
54
+
},
55
+
{
56
+
id:5,
57
+
title:'Synthesize and recreate ticket context',
58
+
status:'not-started'
59
+
},
60
+
{
61
+
id:6,
62
+
title:'Extract behavioral requirements table',
63
+
status:'not-started'
64
+
},
65
+
{
66
+
id:7,
67
+
title:'Implement ticket logic',
68
+
status:'not-started'
69
+
},
70
+
{
71
+
id:8,
72
+
title:'Run validation workflow',
73
+
status:'not-started'
74
+
}
75
+
]
76
+
})
77
+
```
78
+
79
+
Mark each task as `in-progress` before starting it, complete the work, then mark it `completed` immediately. Do not batch completion updates.
80
+
81
+
### Step 1: Read Repository Skills (Required Before All Other Steps)
29
82
30
83
Before any implementation, read all skills in `.github/skills/`.
31
84
@@ -36,23 +89,23 @@ Output the following table summarizing what you found:
description: Validate implementations for runtime errors, accessibility, and API compliance. Use when reviewing implementations, syncing designs, or auditing visual accuracy before committing code.
3
+
description: Validate implementations for runtime errorsand proper functionality. Use when reviewing implementations, syncing designs, or auditing before committing code.
4
4
---
5
5
6
6
# Skill: Validate Implementation
7
7
8
-
This skill validates code implementations before marking features complete to catch runtime errors, accessibility issues, and API violations.
8
+
This skill validates code implementations before marking features complete to catch runtime errors, test failures, and browser console issues.
9
9
10
10
## When to Use
11
11
@@ -18,11 +18,72 @@ Use before committing feature implementations, especially:
18
18
## What This Skill Does
19
19
20
20
1. Runs static analysis (TypeScript and ESLint)
21
-
2. Checks browser console for runtime errors and warnings
22
-
3. Identifies common runtime errors automatically
23
-
4. Checks accessibility compliance for dialogs, selects, and forms
24
-
5. Runs automated test suite (unit and E2E)
25
-
6. Validates API usage patterns
21
+
2. Runs automated test suite
22
+
3. Uses Playwright MCP to validate implementation in the browser
23
+
4. Checks browser console for runtime errors and warnings
24
+
25
+
## Step 0: Create Validation Todo List
26
+
27
+
Use `manage_todo_list` to create a checklist before starting validation.
28
+
29
+
```javascript
30
+
manage_todo_list({
31
+
todoList: [
32
+
{
33
+
id:1,
34
+
title:'Run TypeScript type checking',
35
+
status:'not-started'
36
+
},
37
+
{
38
+
id:2,
39
+
title:'Run ESLint checks',
40
+
status:'not-started'
41
+
},
42
+
{
43
+
id:3,
44
+
title:'Run unit tests',
45
+
status:'not-started'
46
+
},
47
+
{
48
+
id:4,
49
+
title:'Activate Playwright MCP tools',
50
+
status:'not-started'
51
+
},
52
+
{
53
+
id:5,
54
+
title:'Navigate to feature page',
55
+
status:'not-started'
56
+
},
57
+
{
58
+
id:6,
59
+
title:'Take accessibility snapshot',
60
+
status:'not-started'
61
+
},
62
+
{
63
+
id:7,
64
+
title:'Test user interactions',
65
+
status:'not-started'
66
+
},
67
+
{
68
+
id:8,
69
+
title:'Verify expected behavior',
70
+
status:'not-started'
71
+
},
72
+
{
73
+
id:9,
74
+
title:'Check browser console messages',
75
+
status:'not-started'
76
+
},
77
+
{
78
+
id:10,
79
+
title:'Document validation results',
80
+
status:'not-started'
81
+
}
82
+
]
83
+
})
84
+
```
85
+
86
+
Mark each task as `in-progress` before starting it, complete the work, then mark it `completed` immediately. Do not batch completion updates.
26
87
27
88
## Validation Steps
28
89
@@ -36,44 +97,44 @@ npm run lint
36
97
37
98
Fix any errors before proceeding.
38
99
39
-
### 2. Browser Console Check
100
+
### 2. Automated Tests
40
101
41
-
Start dev server and check console:
102
+
Run unit tests:
42
103
```bash
43
-
npm run dev
104
+
npm test
44
105
```
45
106
46
-
1. Open browser DevTools Console
47
-
2. Navigate to the feature
48
-
3. Check for errors (red), warnings (yellow), or unexpected logs
49
-
4. Fix any errors found before proceeding
107
+
Fix any test failures before proceeding.
50
108
51
-
### 3. Accessibility Checks
109
+
### 3. Playwright MCP Browser Validation
52
110
53
-
#### Dialog/Modal Components
54
-
Verify:
55
-
- DialogTitle is present (or wrapped with VisuallyHidden)
56
-
- DialogDescription is present (or aria-describedby attribute)
57
-
- Proper ARIA labels for screen readers
111
+
Activate Playwright MCP tools and validate the feature in the browser:
58
112
59
-
#### Select Components
60
-
Verify:
61
-
- No empty string values in options
62
-
- Use placeholder for "no selection" state
63
-
- All selects have proper labels
113
+
1. Activate web interaction tools if not already available
114
+
2. Navigate to the feature page
115
+
3. Interact with the implementation (click, type, select, etc.)
116
+
4. Verify expected behavior occurs
117
+
5. Document any issues found
118
+
119
+
Example workflow:
120
+
```
121
+
1. Navigate to feature page
122
+
2. Take accessibility snapshot to understand page structure
123
+
3. Perform user interactions (click buttons, fill forms, etc.)
124
+
4. Verify state changes and UI updates
125
+
5. Take screenshot if needed for documentation
126
+
```
64
127
65
-
#### Form Inputs
66
-
Verify:
67
-
- All inputs have labels (visible or aria-label)
68
-
- Error messages are accessible
128
+
### 4. Browser Console Check
69
129
70
-
### 4. Automated Tests
130
+
Check console for errors and warnings:
71
131
72
-
Run tests and fix failures:
73
-
```bash
74
-
npm test
75
-
npm run test:e2e
76
-
```
132
+
1. Use Playwright MCP `mcp_playwright_browser_console_messages` with level "info"
133
+
2. Review output for:
134
+
- Errors (red): Critical issues that must be fixed
135
+
- Warnings (yellow): Issues that should be addressed
136
+
- Unexpected logs: Debug statements that should be removed
137
+
3. Fix any errors found before proceeding
77
138
78
139
## Quick Checklist
79
140
@@ -82,51 +143,34 @@ Complete steps in order. Cannot proceed to next step until previous step is docu
82
143
```markdown
83
144
-[ ] npm run typecheck passes
84
145
-[ ] npm run lint passes
85
-
-[ ] npm run dev started
86
-
-[ ] Browser console opened and checked
146
+
-[ ] npm test passes
147
+
-[ ] Playwright MCP browser validation completed:
148
+
Feature page: ___
149
+
User interactions tested: ___
150
+
Expected behavior verified: ___
151
+
-[ ] Browser console checked via Playwright MCP
87
152
-[ ] Browser console output documented:
88
153
Errors (red): ___
89
154
Warnings (yellow): ___
90
155
-[ ] Zero browser console errors
91
-
-[ ] npm test passes
92
-
-[ ] npm run test:e2e passes (if applicable)
93
156
```
94
157
95
158
Validation is complete only when all items above are checked in sequence.
0 commit comments