mdan-cli 2.5.0 → 2.6.0
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/AGENTS.md +28 -0
- package/README.md +152 -5
- package/agents/auto-orchestrator.md +343 -0
- package/agents/devops.md +511 -94
- package/cli/mdan.js +1 -1
- package/cli/mdan.py +75 -4
- package/cli/mdan.sh +1 -1
- package/core/debate-protocol.md +454 -0
- package/core/universal-envelope.md +113 -0
- package/memory/CONTEXT-SAVE-FORMAT.md +328 -0
- package/memory/MEMORY-AUTO.json +66 -0
- package/memory/RESUME-PROTOCOL.md +379 -0
- package/package.json +1 -1
- package/phases/auto-01-load.md +165 -0
- package/phases/auto-02-discover.md +207 -0
- package/phases/auto-03-plan.md +509 -0
- package/phases/auto-04-architect.md +567 -0
- package/phases/auto-05-implement.md +713 -0
- package/phases/auto-06-test.md +559 -0
- package/phases/auto-07-deploy.md +510 -0
- package/phases/auto-08-doc.md +970 -0
- package/skills/azure-devops/skill.md +1757 -0
- package/templates/dotnet-blazor/README.md +415 -0
- package/templates/external-services/ExampleService.cs +361 -0
- package/templates/external-services/IService.cs +113 -0
- package/templates/external-services/README.md +325 -0
- package/templates/external-services/ServiceBase.cs +492 -0
- package/templates/external-services/ServiceProvider.cs +243 -0
- package/templates/prompts/devops-agent.yaml +327 -0
- package/templates/prompts.json +15 -1
- package/templates/sql-server/README.md +37 -0
- package/templates/sql-server/functions.sql +158 -0
- package/templates/sql-server/schema.sql +188 -0
- package/templates/sql-server/stored-procedures.sql +284 -0
|
@@ -0,0 +1,207 @@
|
|
|
1
|
+
# Auto Phase 2: DISCOVER
|
|
2
|
+
|
|
3
|
+
> Analyze requirements and define user stories
|
|
4
|
+
|
|
5
|
+
## Objective
|
|
6
|
+
|
|
7
|
+
Analyze requirements, define user stories, and create acceptance criteria for the project.
|
|
8
|
+
|
|
9
|
+
## Tasks
|
|
10
|
+
|
|
11
|
+
### 2.1 Analyze Requirements
|
|
12
|
+
|
|
13
|
+
- Review loaded requirements
|
|
14
|
+
- Identify key features
|
|
15
|
+
- Prioritize features
|
|
16
|
+
- Define MVP scope
|
|
17
|
+
|
|
18
|
+
### 2.2 Define User Stories
|
|
19
|
+
|
|
20
|
+
- Create user stories for each feature
|
|
21
|
+
- Format: "As a [role], I want [feature], so that [benefit]"
|
|
22
|
+
- Assign priority (Must Have, Should Have, Could Have, Won't Have)
|
|
23
|
+
- Estimate complexity
|
|
24
|
+
|
|
25
|
+
### 2.3 Define Acceptance Criteria
|
|
26
|
+
|
|
27
|
+
- Create acceptance criteria for each user story
|
|
28
|
+
- Define measurable outcomes
|
|
29
|
+
- Identify edge cases
|
|
30
|
+
- Specify constraints
|
|
31
|
+
|
|
32
|
+
### 2.4 Identify Dependencies
|
|
33
|
+
|
|
34
|
+
- Map dependencies between stories
|
|
35
|
+
- Identify external dependencies
|
|
36
|
+
- Define integration points
|
|
37
|
+
- Note blocking issues
|
|
38
|
+
|
|
39
|
+
### 2.5 Create Feature List
|
|
40
|
+
|
|
41
|
+
- Compile all features
|
|
42
|
+
- Organize by priority
|
|
43
|
+
- Group by functionality
|
|
44
|
+
- Estimate effort
|
|
45
|
+
|
|
46
|
+
## Output
|
|
47
|
+
|
|
48
|
+
Generate `docs/discover.md`:
|
|
49
|
+
|
|
50
|
+
```markdown
|
|
51
|
+
# Discover Phase
|
|
52
|
+
|
|
53
|
+
## Project Overview
|
|
54
|
+
|
|
55
|
+
[Project description and goals]
|
|
56
|
+
|
|
57
|
+
## Features
|
|
58
|
+
|
|
59
|
+
### Must Have (MVP)
|
|
60
|
+
|
|
61
|
+
#### Feature 1: [Feature Name]
|
|
62
|
+
|
|
63
|
+
**User Story**:
|
|
64
|
+
As a [role], I want [feature], so that [benefit].
|
|
65
|
+
|
|
66
|
+
**Acceptance Criteria**:
|
|
67
|
+
- [ ] [Criterion 1]
|
|
68
|
+
- [ ] [Criterion 2]
|
|
69
|
+
- [ ] [Criterion 3]
|
|
70
|
+
|
|
71
|
+
**Priority**: Must Have
|
|
72
|
+
**Complexity**: [Low/Medium/High]
|
|
73
|
+
**Dependencies**: [None/Feature X]
|
|
74
|
+
|
|
75
|
+
---
|
|
76
|
+
|
|
77
|
+
#### Feature 2: [Feature Name]
|
|
78
|
+
|
|
79
|
+
[Same structure]
|
|
80
|
+
|
|
81
|
+
---
|
|
82
|
+
|
|
83
|
+
### Should Have
|
|
84
|
+
|
|
85
|
+
[Features for v1.1]
|
|
86
|
+
|
|
87
|
+
### Could Have
|
|
88
|
+
|
|
89
|
+
[Features for future versions]
|
|
90
|
+
|
|
91
|
+
### Won't Have
|
|
92
|
+
|
|
93
|
+
[Features explicitly out of scope]
|
|
94
|
+
|
|
95
|
+
## Dependencies
|
|
96
|
+
|
|
97
|
+
### Internal Dependencies
|
|
98
|
+
|
|
99
|
+
- Feature A depends on Feature B
|
|
100
|
+
- Feature C depends on Feature D
|
|
101
|
+
|
|
102
|
+
### External Dependencies
|
|
103
|
+
|
|
104
|
+
- [External service 1]
|
|
105
|
+
- [External service 2]
|
|
106
|
+
|
|
107
|
+
## Integration Points
|
|
108
|
+
|
|
109
|
+
- [Integration point 1]
|
|
110
|
+
- [Integration point 2]
|
|
111
|
+
|
|
112
|
+
## Technical Considerations
|
|
113
|
+
|
|
114
|
+
- [Consideration 1]
|
|
115
|
+
- [Consideration 2]
|
|
116
|
+
|
|
117
|
+
## Risks and Mitigations
|
|
118
|
+
|
|
119
|
+
| Risk | Impact | Mitigation |
|
|
120
|
+
|------|--------|------------|
|
|
121
|
+
| [Risk 1] | [High/Medium/Low] | [Mitigation] |
|
|
122
|
+
| [Risk 2] | [High/Medium/Low] | [Mitigation] |
|
|
123
|
+
|
|
124
|
+
## MVP Scope
|
|
125
|
+
|
|
126
|
+
**Included**:
|
|
127
|
+
- [Feature 1]
|
|
128
|
+
- [Feature 2]
|
|
129
|
+
- [Feature 3]
|
|
130
|
+
|
|
131
|
+
**Excluded**:
|
|
132
|
+
- [Feature 4]
|
|
133
|
+
- [Feature 5]
|
|
134
|
+
|
|
135
|
+
## Next Steps
|
|
136
|
+
|
|
137
|
+
Proceed to PLAN phase.
|
|
138
|
+
```
|
|
139
|
+
|
|
140
|
+
## Quality Gates
|
|
141
|
+
|
|
142
|
+
- [ ] All user stories defined
|
|
143
|
+
- [ ] Acceptance criteria clear
|
|
144
|
+
- [ ] Dependencies identified
|
|
145
|
+
- [ ] MVP scope defined
|
|
146
|
+
|
|
147
|
+
## Success Criteria
|
|
148
|
+
|
|
149
|
+
- User stories cover all requirements
|
|
150
|
+
- Acceptance criteria are measurable
|
|
151
|
+
- Dependencies are mapped
|
|
152
|
+
- MVP scope is realistic
|
|
153
|
+
|
|
154
|
+
## Error Handling
|
|
155
|
+
|
|
156
|
+
### Unclear Requirements
|
|
157
|
+
|
|
158
|
+
- Log warning
|
|
159
|
+
- Make reasonable assumptions
|
|
160
|
+
- Document assumptions
|
|
161
|
+
- Continue with note
|
|
162
|
+
|
|
163
|
+
### Conflicting Requirements
|
|
164
|
+
|
|
165
|
+
- Trigger debate
|
|
166
|
+
- Resolve conflict
|
|
167
|
+
- Document decision
|
|
168
|
+
- Continue
|
|
169
|
+
|
|
170
|
+
### Missing Information
|
|
171
|
+
|
|
172
|
+
- Log warning
|
|
173
|
+
- Use defaults
|
|
174
|
+
- Document gaps
|
|
175
|
+
- Continue
|
|
176
|
+
|
|
177
|
+
## Token Management
|
|
178
|
+
|
|
179
|
+
Track token usage:
|
|
180
|
+
- Requirements analysis: ~2,000 tokens
|
|
181
|
+
- User story creation: ~3,000 tokens
|
|
182
|
+
- Acceptance criteria: ~2,000 tokens
|
|
183
|
+
- Dependencies: ~1,000 tokens
|
|
184
|
+
|
|
185
|
+
Total: ~8,000 tokens
|
|
186
|
+
|
|
187
|
+
## Logging
|
|
188
|
+
|
|
189
|
+
```
|
|
190
|
+
[timestamp] Starting DISCOVER phase
|
|
191
|
+
[timestamp] Analyzing requirements...
|
|
192
|
+
[timestamp] Defining user stories...
|
|
193
|
+
[timestamp] Creating acceptance criteria...
|
|
194
|
+
[timestamp] Identifying dependencies...
|
|
195
|
+
[timestamp] Token usage: X / 128,000 (X%)
|
|
196
|
+
[timestamp] DISCOVER phase complete
|
|
197
|
+
```
|
|
198
|
+
|
|
199
|
+
## Completion Signal
|
|
200
|
+
|
|
201
|
+
```
|
|
202
|
+
PHASE 2 COMPLETE ✅
|
|
203
|
+
```
|
|
204
|
+
|
|
205
|
+
## Version
|
|
206
|
+
|
|
207
|
+
MDAN-AUTO Phase 2: DISCOVER v1.0
|
|
@@ -0,0 +1,509 @@
|
|
|
1
|
+
# Auto Phase 3: PLAN
|
|
2
|
+
|
|
3
|
+
> Create detailed implementation plan
|
|
4
|
+
|
|
5
|
+
## Objective
|
|
6
|
+
|
|
7
|
+
Create a detailed implementation plan with phased approach, breaking down features into implementable steps.
|
|
8
|
+
|
|
9
|
+
## Tasks
|
|
10
|
+
|
|
11
|
+
### 3.1 Create Implementation Plan
|
|
12
|
+
|
|
13
|
+
- Break down features into tasks
|
|
14
|
+
- Organize tasks into phases (#PHASE1, #PHASE2, etc.)
|
|
15
|
+
- Define task dependencies
|
|
16
|
+
- Estimate effort per task
|
|
17
|
+
|
|
18
|
+
### 3.2 Define Phase Structure
|
|
19
|
+
|
|
20
|
+
- #PHASE1: Foundation and Setup
|
|
21
|
+
- #PHASE2: Core Features
|
|
22
|
+
- #PHASE3: Advanced Features
|
|
23
|
+
- #PHASE4: Integration
|
|
24
|
+
- #PHASE5: Testing and Polish
|
|
25
|
+
|
|
26
|
+
### 3.3 Create Task List
|
|
27
|
+
|
|
28
|
+
For each phase, define:
|
|
29
|
+
- Task description
|
|
30
|
+
- Acceptance criteria
|
|
31
|
+
- Dependencies
|
|
32
|
+
- Estimated effort
|
|
33
|
+
- Owner (agent)
|
|
34
|
+
|
|
35
|
+
### 3.4 Define Milestones
|
|
36
|
+
|
|
37
|
+
- Identify key milestones
|
|
38
|
+
- Define milestone criteria
|
|
39
|
+
- Set milestone dates (if applicable)
|
|
40
|
+
- Link milestones to phases
|
|
41
|
+
|
|
42
|
+
### 3.5 Create Risk Plan
|
|
43
|
+
|
|
44
|
+
- Identify implementation risks
|
|
45
|
+
- Define mitigation strategies
|
|
46
|
+
- Create contingency plans
|
|
47
|
+
- Set risk triggers
|
|
48
|
+
|
|
49
|
+
## Output
|
|
50
|
+
|
|
51
|
+
Generate `docs/plan.md`:
|
|
52
|
+
|
|
53
|
+
```markdown
|
|
54
|
+
# Implementation Plan
|
|
55
|
+
|
|
56
|
+
## Overview
|
|
57
|
+
|
|
58
|
+
This plan breaks down the project into 5 phases, each with specific tasks and deliverables.
|
|
59
|
+
|
|
60
|
+
## Phase Structure
|
|
61
|
+
|
|
62
|
+
- #PHASE1: Foundation and Setup
|
|
63
|
+
- #PHASE2: Core Features
|
|
64
|
+
- #PHASE3: Advanced Features
|
|
65
|
+
- #PHASE4: Integration
|
|
66
|
+
- #PHASE5: Testing and Polish
|
|
67
|
+
|
|
68
|
+
---
|
|
69
|
+
|
|
70
|
+
#PHASE1: Foundation and Setup
|
|
71
|
+
|
|
72
|
+
## Tasks
|
|
73
|
+
|
|
74
|
+
### Task 1.1: Project Initialization
|
|
75
|
+
|
|
76
|
+
**Description**: Set up .NET project structure and configuration
|
|
77
|
+
|
|
78
|
+
**Acceptance Criteria**:
|
|
79
|
+
- [ ] Solution created with correct structure
|
|
80
|
+
- [ ] Projects configured for Blazor Server
|
|
81
|
+
- [ ] NuGet packages installed
|
|
82
|
+
- [ ] Configuration files set up
|
|
83
|
+
|
|
84
|
+
**Dependencies**: None
|
|
85
|
+
**Effort**: 2 hours
|
|
86
|
+
**Owner**: Dev Agent
|
|
87
|
+
|
|
88
|
+
---
|
|
89
|
+
|
|
90
|
+
### Task 1.2: Database Setup
|
|
91
|
+
|
|
92
|
+
**Description**: Set up SQL Server database and schema
|
|
93
|
+
|
|
94
|
+
**Acceptance Criteria**:
|
|
95
|
+
- [ ] Database created
|
|
96
|
+
- [ ] Tables created with correct schema
|
|
97
|
+
- [ ] Indexes created
|
|
98
|
+
- [ ] Seed data populated
|
|
99
|
+
|
|
100
|
+
**Dependencies**: Task 1.1
|
|
101
|
+
**Effort**: 4 hours
|
|
102
|
+
**Owner**: Dev Agent
|
|
103
|
+
|
|
104
|
+
---
|
|
105
|
+
|
|
106
|
+
### Task 1.3: Authentication Setup
|
|
107
|
+
|
|
108
|
+
**Description**: Implement authentication with Azure AD
|
|
109
|
+
|
|
110
|
+
**Acceptance Criteria**:
|
|
111
|
+
- [ ] Azure AD app registered
|
|
112
|
+
- [ ] Authentication middleware configured
|
|
113
|
+
- [ ] Login/logout implemented
|
|
114
|
+
- [ ] User roles defined
|
|
115
|
+
|
|
116
|
+
**Dependencies**: Task 1.1
|
|
117
|
+
**Effort**: 6 hours
|
|
118
|
+
**Owner**: Security Agent
|
|
119
|
+
|
|
120
|
+
---
|
|
121
|
+
|
|
122
|
+
## Phase 1 Deliverables
|
|
123
|
+
|
|
124
|
+
- [ ] Project structure
|
|
125
|
+
- [ ] Database schema
|
|
126
|
+
- [ ] Authentication system
|
|
127
|
+
- [ ] Configuration files
|
|
128
|
+
|
|
129
|
+
## Phase 1 Success Criteria
|
|
130
|
+
|
|
131
|
+
- All tasks completed
|
|
132
|
+
- Application builds successfully
|
|
133
|
+
- Authentication works
|
|
134
|
+
- Database accessible
|
|
135
|
+
|
|
136
|
+
---
|
|
137
|
+
|
|
138
|
+
#PHASE2: Core Features
|
|
139
|
+
|
|
140
|
+
## Tasks
|
|
141
|
+
|
|
142
|
+
### Task 2.1: User Management
|
|
143
|
+
|
|
144
|
+
**Description**: Implement user CRUD operations
|
|
145
|
+
|
|
146
|
+
**Acceptance Criteria**:
|
|
147
|
+
- [ ] User list page
|
|
148
|
+
- [ ] User create/edit forms
|
|
149
|
+
- [ ] User deletion
|
|
150
|
+
- [ ] User search/filter
|
|
151
|
+
|
|
152
|
+
**Dependencies**: #PHASE1
|
|
153
|
+
**Effort**: 8 hours
|
|
154
|
+
**Owner**: Dev Agent
|
|
155
|
+
|
|
156
|
+
---
|
|
157
|
+
|
|
158
|
+
### Task 2.2: External Service Integration
|
|
159
|
+
|
|
160
|
+
**Description**: Implement generic external service framework
|
|
161
|
+
|
|
162
|
+
**Acceptance Criteria**:
|
|
163
|
+
- [ ] Generic service framework implemented
|
|
164
|
+
- [ ] Retry logic working
|
|
165
|
+
- [ ] Circuit breaker working
|
|
166
|
+
- [ ] Rate limiting working
|
|
167
|
+
- [ ] Caching working
|
|
168
|
+
- [ ] Error handling
|
|
169
|
+
|
|
170
|
+
**Dependencies**: #PHASE1
|
|
171
|
+
**Effort**: 12 hours
|
|
172
|
+
**Owner**: Dev Agent
|
|
173
|
+
|
|
174
|
+
---
|
|
175
|
+
|
|
176
|
+
## Phase 2 Deliverables
|
|
177
|
+
|
|
178
|
+
- [ ] User management system
|
|
179
|
+
- [ ] External service integration
|
|
180
|
+
- [ ] Core UI components
|
|
181
|
+
|
|
182
|
+
## Phase 2 Success Criteria
|
|
183
|
+
|
|
184
|
+
- All core features working
|
|
185
|
+
- External service integration functional
|
|
186
|
+
- UI responsive and usable
|
|
187
|
+
|
|
188
|
+
---
|
|
189
|
+
|
|
190
|
+
#PHASE3: Advanced Features
|
|
191
|
+
|
|
192
|
+
## Tasks
|
|
193
|
+
|
|
194
|
+
### Task 3.1: Service Activity History
|
|
195
|
+
|
|
196
|
+
**Description**: Implement service activity history and reporting
|
|
197
|
+
|
|
198
|
+
**Acceptance Criteria**:
|
|
199
|
+
- [ ] Service activity list page
|
|
200
|
+
- [ ] Activity details
|
|
201
|
+
- [ ] Filtering and search
|
|
202
|
+
- [ ] Export functionality
|
|
203
|
+
|
|
204
|
+
**Dependencies**: #PHASE2
|
|
205
|
+
**Effort**: 10 hours
|
|
206
|
+
**Owner**: Dev Agent
|
|
207
|
+
|
|
208
|
+
---
|
|
209
|
+
|
|
210
|
+
### Task 3.2: Notifications
|
|
211
|
+
|
|
212
|
+
**Description**: Implement notification system
|
|
213
|
+
|
|
214
|
+
**Acceptance Criteria**:
|
|
215
|
+
- [ ] Real-time notifications
|
|
216
|
+
- [ ] Notification history
|
|
217
|
+
- [ ] Notification preferences
|
|
218
|
+
- [ ] Email notifications
|
|
219
|
+
|
|
220
|
+
**Dependencies**: #PHASE2
|
|
221
|
+
**Effort**: 8 hours
|
|
222
|
+
**Owner**: Dev Agent
|
|
223
|
+
|
|
224
|
+
---
|
|
225
|
+
|
|
226
|
+
### Task 3.3: Analytics Dashboard
|
|
227
|
+
|
|
228
|
+
**Description**: Create analytics dashboard
|
|
229
|
+
|
|
230
|
+
**Acceptance Criteria**:
|
|
231
|
+
- [ ] Dashboard with charts
|
|
232
|
+
- [ ] Key metrics displayed
|
|
233
|
+
- [ ] Date range filters
|
|
234
|
+
- [ ] Export reports
|
|
235
|
+
|
|
236
|
+
**Dependencies**: #PHASE3
|
|
237
|
+
**Effort**: 12 hours
|
|
238
|
+
**Owner**: Dev Agent
|
|
239
|
+
|
|
240
|
+
---
|
|
241
|
+
|
|
242
|
+
## Phase 3 Deliverables
|
|
243
|
+
|
|
244
|
+
- [ ] Service activity history
|
|
245
|
+
- [ ] Notification system
|
|
246
|
+
- [ ] Analytics dashboard
|
|
247
|
+
- [ ] Advanced UI components
|
|
248
|
+
|
|
249
|
+
## Phase 3 Success Criteria
|
|
250
|
+
|
|
251
|
+
- All advanced features working
|
|
252
|
+
- Dashboard displays correct data
|
|
253
|
+
- Notifications delivered
|
|
254
|
+
|
|
255
|
+
---
|
|
256
|
+
|
|
257
|
+
#PHASE4: Integration
|
|
258
|
+
|
|
259
|
+
## Tasks
|
|
260
|
+
|
|
261
|
+
### Task 4.1: API Integration
|
|
262
|
+
|
|
263
|
+
**Description**: Integrate all external APIs
|
|
264
|
+
|
|
265
|
+
**Acceptance Criteria**:
|
|
266
|
+
- [ ] All APIs connected
|
|
267
|
+
- [ ] Error handling robust
|
|
268
|
+
- [ ] Rate limiting implemented
|
|
269
|
+
- [ ] Logging configured
|
|
270
|
+
|
|
271
|
+
**Dependencies**: #PHASE3
|
|
272
|
+
**Effort**: 8 hours
|
|
273
|
+
**Owner**: Dev Agent
|
|
274
|
+
|
|
275
|
+
---
|
|
276
|
+
|
|
277
|
+
### Task 4.2: Azure Integration
|
|
278
|
+
|
|
279
|
+
**Description**: Configure Azure services
|
|
280
|
+
|
|
281
|
+
**Acceptance Criteria**:
|
|
282
|
+
- [ ] App Service configured
|
|
283
|
+
- [ ] SQL Database connected
|
|
284
|
+
- [ ] Key Vault integrated
|
|
285
|
+
- [ ] Monitoring set up
|
|
286
|
+
|
|
287
|
+
**Dependencies**: #PHASE3
|
|
288
|
+
**Effort**: 6 hours
|
|
289
|
+
**Owner**: DevOps Agent
|
|
290
|
+
|
|
291
|
+
---
|
|
292
|
+
|
|
293
|
+
### Task 4.3: CI/CD Pipeline
|
|
294
|
+
|
|
295
|
+
**Description**: Set up CI/CD pipeline
|
|
296
|
+
|
|
297
|
+
**Acceptance Criteria**:
|
|
298
|
+
- [ ] Build pipeline configured
|
|
299
|
+
- [ ] Test pipeline configured
|
|
300
|
+
- [ ] Deployment pipeline configured
|
|
301
|
+
- [ ] Automated deployments working
|
|
302
|
+
|
|
303
|
+
**Dependencies**: #PHASE4
|
|
304
|
+
**Effort**: 8 hours
|
|
305
|
+
**Owner**: DevOps Agent
|
|
306
|
+
|
|
307
|
+
---
|
|
308
|
+
|
|
309
|
+
## Phase 4 Deliverables
|
|
310
|
+
|
|
311
|
+
- [ ] All integrations working
|
|
312
|
+
- [ ] Azure services configured
|
|
313
|
+
- [ ] CI/CD pipeline operational
|
|
314
|
+
- [ ] Monitoring active
|
|
315
|
+
|
|
316
|
+
## Phase 4 Success Criteria
|
|
317
|
+
|
|
318
|
+
- All integrations tested
|
|
319
|
+
- Deployment automated
|
|
320
|
+
- Monitoring functional
|
|
321
|
+
|
|
322
|
+
---
|
|
323
|
+
|
|
324
|
+
#PHASE5: Testing and Polish
|
|
325
|
+
|
|
326
|
+
## Tasks
|
|
327
|
+
|
|
328
|
+
### Task 5.1: Unit Tests
|
|
329
|
+
|
|
330
|
+
**Description**: Write comprehensive unit tests
|
|
331
|
+
|
|
332
|
+
**Acceptance Criteria**:
|
|
333
|
+
- [ ] 80%+ code coverage
|
|
334
|
+
- [ ] All business logic tested
|
|
335
|
+
- [ ] Edge cases covered
|
|
336
|
+
- [ ] Tests passing
|
|
337
|
+
|
|
338
|
+
**Dependencies**: #PHASE4
|
|
339
|
+
**Effort**: 16 hours
|
|
340
|
+
**Owner**: Test Agent
|
|
341
|
+
|
|
342
|
+
---
|
|
343
|
+
|
|
344
|
+
### Task 5.2: Integration Tests
|
|
345
|
+
|
|
346
|
+
**Description**: Write integration tests
|
|
347
|
+
|
|
348
|
+
**Acceptance Criteria**:
|
|
349
|
+
- [ ] API endpoints tested
|
|
350
|
+
- [ ] Database operations tested
|
|
351
|
+
- [ ] External integrations tested
|
|
352
|
+
- [ ] Tests passing
|
|
353
|
+
|
|
354
|
+
**Dependencies**: #PHASE4
|
|
355
|
+
**Effort**: 12 hours
|
|
356
|
+
**Owner**: Test Agent
|
|
357
|
+
|
|
358
|
+
---
|
|
359
|
+
|
|
360
|
+
### Task 5.3: UI Polish
|
|
361
|
+
|
|
362
|
+
**Description**: Polish UI/UX
|
|
363
|
+
|
|
364
|
+
**Acceptance Criteria**:
|
|
365
|
+
- [ ] Consistent styling
|
|
366
|
+
- [ ] Responsive design
|
|
367
|
+
- [ ] Accessibility improvements
|
|
368
|
+
- [ ] Performance optimized
|
|
369
|
+
|
|
370
|
+
**Dependencies**: #PHASE4
|
|
371
|
+
**Effort**: 8 hours
|
|
372
|
+
**Owner**: UX Agent
|
|
373
|
+
|
|
374
|
+
---
|
|
375
|
+
|
|
376
|
+
### Task 5.4: Documentation
|
|
377
|
+
|
|
378
|
+
**Description**: Create documentation
|
|
379
|
+
|
|
380
|
+
**Acceptance Criteria**:
|
|
381
|
+
- [ ] README complete
|
|
382
|
+
- [ ] API documentation
|
|
383
|
+
- [ ] User guide
|
|
384
|
+
- [ ] Deployment guide
|
|
385
|
+
|
|
386
|
+
**Dependencies**: #PHASE5
|
|
387
|
+
**Effort**: 8 hours
|
|
388
|
+
**Owner**: Doc Agent
|
|
389
|
+
|
|
390
|
+
---
|
|
391
|
+
|
|
392
|
+
## Phase 5 Deliverables
|
|
393
|
+
|
|
394
|
+
- [ ] Comprehensive test suite
|
|
395
|
+
- [ ] Polished UI
|
|
396
|
+
- [ ] Complete documentation
|
|
397
|
+
- [ ] Production-ready code
|
|
398
|
+
|
|
399
|
+
## Phase 5 Success Criteria
|
|
400
|
+
|
|
401
|
+
- All tests passing
|
|
402
|
+
- Coverage ≥80%
|
|
403
|
+
- Documentation complete
|
|
404
|
+
- UI polished
|
|
405
|
+
|
|
406
|
+
---
|
|
407
|
+
|
|
408
|
+
## Milestones
|
|
409
|
+
|
|
410
|
+
| Milestone | Phase | Criteria | Date |
|
|
411
|
+
|-----------|-------|----------|------|
|
|
412
|
+
| M1: Foundation Complete | #PHASE1 | All Phase 1 tasks complete | [Date] |
|
|
413
|
+
| M2: Core Features Complete | #PHASE2 | All Phase 2 tasks complete | [Date] |
|
|
414
|
+
| M3: Advanced Features Complete | #PHASE3 | All Phase 3 tasks complete | [Date] |
|
|
415
|
+
| M4: Integration Complete | #PHASE4 | All Phase 4 tasks complete | [Date] |
|
|
416
|
+
| M5: Production Ready | #PHASE5 | All Phase 5 tasks complete | [Date] |
|
|
417
|
+
|
|
418
|
+
## Risk Plan
|
|
419
|
+
|
|
420
|
+
| Risk | Impact | Probability | Mitigation | Trigger |
|
|
421
|
+
|------|--------|-------------|------------|---------|
|
|
422
|
+
| API changes | High | Medium | Version APIs, implement adapters | API version change |
|
|
423
|
+
| Performance issues | High | Low | Load testing, optimization | Slow response times |
|
|
424
|
+
| Security vulnerabilities | High | Low | Security reviews, penetration testing | Security scan findings |
|
|
425
|
+
| Integration failures | Medium | Medium | Comprehensive testing, fallbacks | Integration test failures |
|
|
426
|
+
|
|
427
|
+
## Total Effort Estimate
|
|
428
|
+
|
|
429
|
+
- #PHASE1: 12 hours
|
|
430
|
+
- #PHASE2: 32 hours
|
|
431
|
+
- #PHASE3: 30 hours
|
|
432
|
+
- #PHASE4: 22 hours
|
|
433
|
+
- #PHASE5: 44 hours
|
|
434
|
+
|
|
435
|
+
**Total**: 140 hours (~17.5 days)
|
|
436
|
+
|
|
437
|
+
## Next Steps
|
|
438
|
+
|
|
439
|
+
Proceed to ARCHITECT phase.
|
|
440
|
+
```
|
|
441
|
+
|
|
442
|
+
## Quality Gates
|
|
443
|
+
|
|
444
|
+
- [ ] All phases defined
|
|
445
|
+
- [ ] Tasks broken down
|
|
446
|
+
- [ ] Dependencies mapped
|
|
447
|
+
- [ ] Effort estimated
|
|
448
|
+
|
|
449
|
+
## Success Criteria
|
|
450
|
+
|
|
451
|
+
- Plan covers all features
|
|
452
|
+
- Tasks are actionable
|
|
453
|
+
- Dependencies are clear
|
|
454
|
+
- Effort is realistic
|
|
455
|
+
|
|
456
|
+
## Error Handling
|
|
457
|
+
|
|
458
|
+
### Unclear Requirements
|
|
459
|
+
|
|
460
|
+
- Log warning
|
|
461
|
+
- Make reasonable assumptions
|
|
462
|
+
- Document assumptions
|
|
463
|
+
- Continue
|
|
464
|
+
|
|
465
|
+
### Too Many Tasks
|
|
466
|
+
|
|
467
|
+
- Group related tasks
|
|
468
|
+
- Create sub-phases
|
|
469
|
+
- Reorganize plan
|
|
470
|
+
- Continue
|
|
471
|
+
|
|
472
|
+
### Unrealistic Estimates
|
|
473
|
+
|
|
474
|
+
- Adjust estimates
|
|
475
|
+
- Add buffer time
|
|
476
|
+
- Document assumptions
|
|
477
|
+
- Continue
|
|
478
|
+
|
|
479
|
+
## Token Management
|
|
480
|
+
|
|
481
|
+
Track token usage:
|
|
482
|
+
- Plan creation: ~5,000 tokens
|
|
483
|
+
- Task breakdown: ~4,000 tokens
|
|
484
|
+
- Risk analysis: ~2,000 tokens
|
|
485
|
+
- Effort estimation: ~2,000 tokens
|
|
486
|
+
|
|
487
|
+
Total: ~13,000 tokens
|
|
488
|
+
|
|
489
|
+
## Logging
|
|
490
|
+
|
|
491
|
+
```
|
|
492
|
+
[timestamp] Starting PLAN phase
|
|
493
|
+
[timestamp] Creating implementation plan...
|
|
494
|
+
[timestamp] Defining phases...
|
|
495
|
+
[timestamp] Breaking down tasks...
|
|
496
|
+
[timestamp] Creating risk plan...
|
|
497
|
+
[timestamp] Token usage: X / 128,000 (X%)
|
|
498
|
+
[timestamp] PLAN phase complete
|
|
499
|
+
```
|
|
500
|
+
|
|
501
|
+
## Completion Signal
|
|
502
|
+
|
|
503
|
+
```
|
|
504
|
+
PHASE 3 COMPLETE ✅
|
|
505
|
+
```
|
|
506
|
+
|
|
507
|
+
## Version
|
|
508
|
+
|
|
509
|
+
MDAN-AUTO Phase 3: PLAN v1.0
|