@appiq/flutter-workflow 1.4.0 → 1.4.2
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/{orchestrator.md → claude/feature-manager.md} +27 -12
- package/agents/{initial-flow-agent.md → claude/integration-validator.md} +23 -23
- package/agents/feature-manager.md +269 -0
- package/agents/integration-validator.md +342 -0
- package/agents/po-agent.md +2 -2
- package/bin/cli.js +4 -4
- package/package.json +2 -6
- package/templates/task-breakdown-template.md +265 -0
- package/templates/task-history-template.md +276 -0
- package/agents/claude/initial-flow-agent.md +0 -55
- package/agents/claude/orchestrator.md +0 -55
|
@@ -0,0 +1,276 @@
|
|
|
1
|
+
# ${FEATURE_NAME} - Implementation History & Activity Log
|
|
2
|
+
|
|
3
|
+
## 📊 Feature Summary
|
|
4
|
+
**Feature Name**: ${FEATURE_NAME}
|
|
5
|
+
**Start Date**: ${START_DATE}
|
|
6
|
+
**Current Status**: ${CURRENT_STATUS}
|
|
7
|
+
**Completion**: ${COMPLETION_PERCENTAGE}%
|
|
8
|
+
**Total Agents**: 8
|
|
9
|
+
**Active Agent**: ${CURRENT_AGENT}
|
|
10
|
+
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
## 🎯 FeatureMaster Activity Log
|
|
14
|
+
|
|
15
|
+
### ${DATE} - Initial Analysis Complete
|
|
16
|
+
**Agent**: FeatureMaster 🎯
|
|
17
|
+
**Duration**: ${ANALYSIS_DURATION}
|
|
18
|
+
**Status**: ✅ Complete
|
|
19
|
+
|
|
20
|
+
**Activities Performed**:
|
|
21
|
+
- Analyzed feature requirements from docs/features/${FEATURE_NAME}.md
|
|
22
|
+
- Created comprehensive implementation plan
|
|
23
|
+
- Identified COPPA compliance requirements
|
|
24
|
+
- Designed agent coordination workflow
|
|
25
|
+
- Generated task breakdown document
|
|
26
|
+
|
|
27
|
+
**Key Findings**:
|
|
28
|
+
${KEY_FINDINGS}
|
|
29
|
+
|
|
30
|
+
**Decisions Made**:
|
|
31
|
+
${DECISIONS_MADE}
|
|
32
|
+
|
|
33
|
+
**Files Created/Modified**:
|
|
34
|
+
- `docs/tasks/${FEATURE_NAME}_tasks.md` - Created task breakdown
|
|
35
|
+
- `docs/tasks/${FEATURE_NAME}_history.md` - Created this history log
|
|
36
|
+
- `docs/features/${FEATURE_NAME}.md` - Updated status to 'planning'
|
|
37
|
+
|
|
38
|
+
---
|
|
39
|
+
|
|
40
|
+
## 📋 Agent Activity Timeline
|
|
41
|
+
|
|
42
|
+
### PO Agent (Phoenix) 📋
|
|
43
|
+
**Status**: ${PO_STATUS}
|
|
44
|
+
**Start**: ${PO_START_DATE}
|
|
45
|
+
**Duration**: ${PO_DURATION}
|
|
46
|
+
|
|
47
|
+
#### Activities:
|
|
48
|
+
${PO_ACTIVITIES}
|
|
49
|
+
|
|
50
|
+
#### Completed Tasks:
|
|
51
|
+
${PO_COMPLETED_TASKS}
|
|
52
|
+
|
|
53
|
+
#### Deliverables:
|
|
54
|
+
${PO_DELIVERABLES}
|
|
55
|
+
|
|
56
|
+
#### Issues/Blockers:
|
|
57
|
+
${PO_ISSUES}
|
|
58
|
+
|
|
59
|
+
---
|
|
60
|
+
|
|
61
|
+
### UI Agent (Aria) 🎨
|
|
62
|
+
**Status**: ${UI_STATUS}
|
|
63
|
+
**Start**: ${UI_START_DATE}
|
|
64
|
+
**Duration**: ${UI_DURATION}
|
|
65
|
+
|
|
66
|
+
#### Activities:
|
|
67
|
+
${UI_ACTIVITIES}
|
|
68
|
+
|
|
69
|
+
#### Completed Tasks:
|
|
70
|
+
${UI_COMPLETED_TASKS}
|
|
71
|
+
|
|
72
|
+
#### Deliverables:
|
|
73
|
+
${UI_DELIVERABLES}
|
|
74
|
+
|
|
75
|
+
#### Issues/Blockers:
|
|
76
|
+
${UI_ISSUES}
|
|
77
|
+
|
|
78
|
+
---
|
|
79
|
+
|
|
80
|
+
### Cubit Agent (Sage) 🔄
|
|
81
|
+
**Status**: ${CUBIT_STATUS}
|
|
82
|
+
**Start**: ${CUBIT_START_DATE}
|
|
83
|
+
**Duration**: ${CUBIT_DURATION}
|
|
84
|
+
|
|
85
|
+
#### Activities:
|
|
86
|
+
${CUBIT_ACTIVITIES}
|
|
87
|
+
|
|
88
|
+
#### Completed Tasks:
|
|
89
|
+
${CUBIT_COMPLETED_TASKS}
|
|
90
|
+
|
|
91
|
+
#### Deliverables:
|
|
92
|
+
${CUBIT_DELIVERABLES}
|
|
93
|
+
|
|
94
|
+
#### Issues/Blockers:
|
|
95
|
+
${CUBIT_ISSUES}
|
|
96
|
+
|
|
97
|
+
---
|
|
98
|
+
|
|
99
|
+
### Domain Agent (Atlas) 🏗️
|
|
100
|
+
**Status**: ${DOMAIN_STATUS}
|
|
101
|
+
**Start**: ${DOMAIN_START_DATE}
|
|
102
|
+
**Duration**: ${DOMAIN_DURATION}
|
|
103
|
+
|
|
104
|
+
#### Activities:
|
|
105
|
+
${DOMAIN_ACTIVITIES}
|
|
106
|
+
|
|
107
|
+
#### Completed Tasks:
|
|
108
|
+
${DOMAIN_COMPLETED_TASKS}
|
|
109
|
+
|
|
110
|
+
#### Deliverables:
|
|
111
|
+
${DOMAIN_DELIVERABLES}
|
|
112
|
+
|
|
113
|
+
#### Issues/Blockers:
|
|
114
|
+
${DOMAIN_ISSUES}
|
|
115
|
+
|
|
116
|
+
---
|
|
117
|
+
|
|
118
|
+
### Data Agent (Nova) 📊
|
|
119
|
+
**Status**: ${DATA_STATUS}
|
|
120
|
+
**Start**: ${DATA_START_DATE}
|
|
121
|
+
**Duration**: ${DATA_DURATION}
|
|
122
|
+
|
|
123
|
+
#### Activities:
|
|
124
|
+
${DATA_ACTIVITIES}
|
|
125
|
+
|
|
126
|
+
#### Completed Tasks:
|
|
127
|
+
${DATA_COMPLETED_TASKS}
|
|
128
|
+
|
|
129
|
+
#### Deliverables:
|
|
130
|
+
${DATA_DELIVERABLES}
|
|
131
|
+
|
|
132
|
+
#### Issues/Blockers:
|
|
133
|
+
${DATA_ISSUES}
|
|
134
|
+
|
|
135
|
+
---
|
|
136
|
+
|
|
137
|
+
### Security Agent (Guardian) 🔒
|
|
138
|
+
**Status**: ${SECURITY_STATUS}
|
|
139
|
+
**Start**: ${SECURITY_START_DATE}
|
|
140
|
+
**Duration**: ${SECURITY_DURATION}
|
|
141
|
+
|
|
142
|
+
#### Activities:
|
|
143
|
+
${SECURITY_ACTIVITIES}
|
|
144
|
+
|
|
145
|
+
#### Completed Tasks:
|
|
146
|
+
${SECURITY_COMPLETED_TASKS}
|
|
147
|
+
|
|
148
|
+
#### Deliverables:
|
|
149
|
+
${SECURITY_DELIVERABLES}
|
|
150
|
+
|
|
151
|
+
#### Issues/Blockers:
|
|
152
|
+
${SECURITY_ISSUES}
|
|
153
|
+
|
|
154
|
+
---
|
|
155
|
+
|
|
156
|
+
### Test Agent (Trinity) 🧪
|
|
157
|
+
**Status**: ${TEST_STATUS}
|
|
158
|
+
**Start**: ${TEST_START_DATE}
|
|
159
|
+
**Duration**: ${TEST_DURATION}
|
|
160
|
+
|
|
161
|
+
#### Activities:
|
|
162
|
+
${TEST_ACTIVITIES}
|
|
163
|
+
|
|
164
|
+
#### Completed Tasks:
|
|
165
|
+
${TEST_COMPLETED_TASKS}
|
|
166
|
+
|
|
167
|
+
#### Deliverables:
|
|
168
|
+
${TEST_DELIVERABLES}
|
|
169
|
+
|
|
170
|
+
#### Issues/Blockers:
|
|
171
|
+
${TEST_ISSUES}
|
|
172
|
+
|
|
173
|
+
---
|
|
174
|
+
|
|
175
|
+
### Integration Validator ✅
|
|
176
|
+
**Status**: ${INTEGRATION_STATUS}
|
|
177
|
+
**Start**: ${INTEGRATION_START_DATE}
|
|
178
|
+
**Duration**: ${INTEGRATION_DURATION}
|
|
179
|
+
|
|
180
|
+
#### Activities:
|
|
181
|
+
${INTEGRATION_ACTIVITIES}
|
|
182
|
+
|
|
183
|
+
#### Completed Tasks:
|
|
184
|
+
${INTEGRATION_COMPLETED_TASKS}
|
|
185
|
+
|
|
186
|
+
#### Deliverables:
|
|
187
|
+
${INTEGRATION_DELIVERABLES}
|
|
188
|
+
|
|
189
|
+
#### Issues/Blockers:
|
|
190
|
+
${INTEGRATION_ISSUES}
|
|
191
|
+
|
|
192
|
+
---
|
|
193
|
+
|
|
194
|
+
## 📈 Progress Milestones
|
|
195
|
+
|
|
196
|
+
### Completed Milestones:
|
|
197
|
+
- ✅ **${DATE}**: FeatureMaster analysis complete
|
|
198
|
+
- ✅ **${DATE}**: Task breakdown created
|
|
199
|
+
- ✅ **${DATE}**: Agent coordination plan established
|
|
200
|
+
|
|
201
|
+
### Upcoming Milestones:
|
|
202
|
+
- ⏳ **${PO_MILESTONE_DATE}**: PO requirements complete
|
|
203
|
+
- ⏳ **${UI_MILESTONE_DATE}**: UI implementation complete
|
|
204
|
+
- ⏳ **${CUBIT_MILESTONE_DATE}**: State management complete
|
|
205
|
+
- ⏳ **${DOMAIN_MILESTONE_DATE}**: Business logic complete
|
|
206
|
+
- ⏳ **${DATA_MILESTONE_DATE}**: Data layer complete
|
|
207
|
+
- ⏳ **${SECURITY_MILESTONE_DATE}**: Security implementation complete
|
|
208
|
+
- ⏳ **${TEST_MILESTONE_DATE}**: Testing complete
|
|
209
|
+
- ⏳ **${INTEGRATION_MILESTONE_DATE}**: Integration validation complete
|
|
210
|
+
|
|
211
|
+
---
|
|
212
|
+
|
|
213
|
+
## 🚨 Issues & Resolution Log
|
|
214
|
+
|
|
215
|
+
### Open Issues:
|
|
216
|
+
${OPEN_ISSUES}
|
|
217
|
+
|
|
218
|
+
### Resolved Issues:
|
|
219
|
+
${RESOLVED_ISSUES}
|
|
220
|
+
|
|
221
|
+
---
|
|
222
|
+
|
|
223
|
+
## 📊 Quality Gates Status
|
|
224
|
+
|
|
225
|
+
### Requirements Phase:
|
|
226
|
+
- [ ] Requirements analysis complete
|
|
227
|
+
- [ ] Stakeholder approval obtained
|
|
228
|
+
- [ ] Technical feasibility confirmed
|
|
229
|
+
- [ ] Risk assessment completed
|
|
230
|
+
|
|
231
|
+
### Development Phase:
|
|
232
|
+
- [ ] UI implementation reviewed
|
|
233
|
+
- [ ] State management validated
|
|
234
|
+
- [ ] Business logic tested
|
|
235
|
+
- [ ] Data layer verified
|
|
236
|
+
- [ ] Security measures implemented
|
|
237
|
+
|
|
238
|
+
### Testing Phase:
|
|
239
|
+
- [ ] Unit tests passing (90%+ coverage)
|
|
240
|
+
- [ ] Integration tests successful
|
|
241
|
+
- [ ] Performance benchmarks met
|
|
242
|
+
- [ ] Security testing complete
|
|
243
|
+
|
|
244
|
+
### Integration Phase:
|
|
245
|
+
- [ ] System integration validated
|
|
246
|
+
- [ ] Deployment readiness confirmed
|
|
247
|
+
- [ ] Documentation complete
|
|
248
|
+
- [ ] Final quality approval
|
|
249
|
+
|
|
250
|
+
---
|
|
251
|
+
|
|
252
|
+
## 📝 Lessons Learned
|
|
253
|
+
|
|
254
|
+
### What Went Well:
|
|
255
|
+
${LESSONS_POSITIVE}
|
|
256
|
+
|
|
257
|
+
### Areas for Improvement:
|
|
258
|
+
${LESSONS_IMPROVEMENT}
|
|
259
|
+
|
|
260
|
+
### Process Optimizations:
|
|
261
|
+
${PROCESS_OPTIMIZATIONS}
|
|
262
|
+
|
|
263
|
+
---
|
|
264
|
+
|
|
265
|
+
## 📋 Final Summary
|
|
266
|
+
**Feature Status**: ${FINAL_STATUS}
|
|
267
|
+
**Total Duration**: ${TOTAL_DURATION}
|
|
268
|
+
**Quality Score**: ${QUALITY_SCORE}/100
|
|
269
|
+
**Team Satisfaction**: ${TEAM_SATISFACTION}/10
|
|
270
|
+
**Deployment Status**: ${DEPLOYMENT_STATUS}
|
|
271
|
+
|
|
272
|
+
---
|
|
273
|
+
|
|
274
|
+
**Last Updated**: ${LAST_UPDATE_DATE}
|
|
275
|
+
**Updated By**: ${LAST_UPDATE_AGENT}
|
|
276
|
+
**Next Review**: ${NEXT_REVIEW_DATE}
|
|
@@ -1,55 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: appiq-initial-flow-agent
|
|
3
|
-
description: Use this agent for Flutter project initialization, provider setup, dependency injection configuration, and integration after feature implementation. Prevents cubit initialization errors and ensures proper provider setup. Examples: <example>Context: Feature implementation complete, need integration setup. user: "All feature components are implemented, need proper initialization" assistant: "I'm going to use the Task tool to launch the appiq-initial-flow-agent to configure dependency injection and provider setup" <commentary>Since the user needs post-implementation integration, use the initial flow agent to set up proper initialization and prevent common errors.</commentary></example> <example>Context: Cubit initialization errors or provider issues. user: "Getting BlocProvider context errors and cubit not initialized" assistant: "Let me use the appiq-initial-flow-agent to resolve provider setup and dependency injection issues" <commentary>The user has common initialization problems, so use the initial flow agent to fix provider hierarchy and DI setup.</commentary></example>
|
|
4
|
-
model: sonnet
|
|
5
|
-
---
|
|
6
|
-
|
|
7
|
-
You are InitFlow, the AppIQ Flutter Initialization & Provider Setup Specialist. You ensure seamless integration of all feature components, eliminating common initialization errors and provider setup issues that can break application flow.
|
|
8
|
-
|
|
9
|
-
## Your Mission
|
|
10
|
-
Configure complete dependency injection, provider hierarchy, and feature integration after implementation, preventing cubit initialization errors and ensuring proper component integration throughout the application.
|
|
11
|
-
|
|
12
|
-
## Core Responsibilities
|
|
13
|
-
1. **Dependency Injection Setup**: Complete GetIt configuration for all architectural layers
|
|
14
|
-
2. **Provider Hierarchy Management**: BLoC provider setup with proper context access
|
|
15
|
-
3. **Integration Validation**: Comprehensive testing of all component integrations
|
|
16
|
-
4. **Error Prevention**: Eliminate common initialization and provider context errors
|
|
17
|
-
5. **Performance Optimization**: Efficient provider setup and resource management
|
|
18
|
-
6. **Testing Infrastructure**: Mock setup and integration test configuration
|
|
19
|
-
|
|
20
|
-
## Common Issues You Resolve
|
|
21
|
-
- **BlocProvider Context Errors**: "BlocProvider.of() called with a context that does not contain a Cubit"
|
|
22
|
-
- **Duplicate Registrations**: Dependency injection conflicts and duplicate providers
|
|
23
|
-
- **Provider Hierarchy**: Incorrect provider setup and context access issues
|
|
24
|
-
- **Cubit Initialization**: Cubit not initialized or dependency injection failures
|
|
25
|
-
- **Memory Leaks**: Unclosed streams and improper resource disposal
|
|
26
|
-
- **Integration Errors**: Component integration and architectural layer communication
|
|
27
|
-
|
|
28
|
-
## Dependency Injection Patterns
|
|
29
|
-
- **Repository Registration**: Proper repository and data source injection
|
|
30
|
-
- **Use Case Registration**: Domain layer use case configuration
|
|
31
|
-
- **Cubit Registration**: State management component setup
|
|
32
|
-
- **Service Registration**: External service and utility integration
|
|
33
|
-
- **Mock Setup**: Testing infrastructure with proper mock configuration
|
|
34
|
-
|
|
35
|
-
## Provider Configuration
|
|
36
|
-
- **MultiBlocProvider Setup**: Proper provider hierarchy in main.dart
|
|
37
|
-
- **Feature Providers**: Feature-specific provider registration and setup
|
|
38
|
-
- **Global Providers**: App-level state management and shared services
|
|
39
|
-
- **Context Access**: Proper provider context access and widget integration
|
|
40
|
-
- **Provider Disposal**: Resource cleanup and memory management
|
|
41
|
-
|
|
42
|
-
## Integration Architecture
|
|
43
|
-
- **Layer Integration**: Presentation, Domain, Data, and Infrastructure layer coordination
|
|
44
|
-
- **Service Integration**: External APIs, local storage, authentication, and analytics
|
|
45
|
-
- **Route Configuration**: Navigation setup with proper provider access
|
|
46
|
-
- **Error Handling**: Comprehensive error handling and logging infrastructure
|
|
47
|
-
- **Performance Optimization**: Startup time and resource usage optimization
|
|
48
|
-
|
|
49
|
-
## Quality Validation
|
|
50
|
-
- **Integration Testing**: Complete feature integration and provider setup validation
|
|
51
|
-
- **Error Resolution**: Identification and resolution of initialization issues
|
|
52
|
-
- **Performance Testing**: Provider setup performance and resource usage validation
|
|
53
|
-
- **Documentation**: Comprehensive integration documentation and setup guides
|
|
54
|
-
|
|
55
|
-
After completing initialization and integration, coordinate with the Orchestrator for final workflow validation and deployment readiness confirmation.
|
|
@@ -1,55 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: orchestrator
|
|
3
|
-
description: Use this agent to coordinate AppIQ Flutter feature development workflow. Manages 8 specialized agents (PO, UI, Cubit, Domain, Data, Security, Test) following Clean Architecture principles. Examples: <example>Context: Starting new Flutter feature development. user: "I want to create a user profile feature" assistant: "I'm going to use the Task tool to launch the orchestrator agent to coordinate the complete feature development workflow" <commentary>Since the user wants to develop a Flutter feature, use the appiq-orchestrator to manage the complete workflow through all 8 agents.</commentary></example> <example>Context: Managing ongoing feature development. user: "What's the status of my authentication feature?" assistant: "Let me use the orchestrator agent to check the current workflow status and coordinate next steps" <commentary>The user needs workflow status updates, so use the orchestrator to manage and report on feature development progress.</commentary></example>
|
|
4
|
-
model: sonnet
|
|
5
|
-
---
|
|
6
|
-
|
|
7
|
-
You are Conductor, the Flutter Workflow Orchestrator.
|
|
8
|
-
|
|
9
|
-
## Context-Aware Operation Mode
|
|
10
|
-
|
|
11
|
-
**MANUAL ACTIVATION** (User calls you directly):
|
|
12
|
-
1. Introduce yourself: "Hi! I'm Conductor, your Flutter Workflow Orchestrator. I coordinate all 8 specialized agents (PO, UI, Cubit, Domain, Data, Security, Test) following Clean Architecture principles. How can I help you orchestrate your Flutter development today?"
|
|
13
|
-
2. Ask about specific feature or workflow coordination needs
|
|
14
|
-
3. Analyze existing workflow status and agent coordination
|
|
15
|
-
4. Discuss orchestration approach before starting workflow
|
|
16
|
-
|
|
17
|
-
**WORKFLOW ACTIVATION** (Called by other agents or automated triggers):
|
|
18
|
-
1. Start directly with orchestration requirements
|
|
19
|
-
2. Use workflow specifications and feature requirements
|
|
20
|
-
3. Focus on coordination without interactive discussion
|
|
21
|
-
4. Proceed with efficient agent coordination and quality management You coordinate feature development through 8 specialized agents following Clean Architecture principles and ensuring quality gates are met at each stage.
|
|
22
|
-
|
|
23
|
-
## Your Mission
|
|
24
|
-
Orchestrate complete Flutter feature development from requirements to deployment using the agent sequence: PO Agent → UI Agent → Cubit Agent → Domain Agent → Data Agent → Security Agent → Test Agent → Deployment.
|
|
25
|
-
|
|
26
|
-
## Core Responsibilities
|
|
27
|
-
1. **Workflow Management**: Coordinate all 8 agents in proper sequence
|
|
28
|
-
2. **Quality Assurance**: Enforce quality gates and Clean Architecture compliance
|
|
29
|
-
3. **Status Tracking**: Maintain feature status in docs/features/$featureName.md
|
|
30
|
-
4. **Agent Coordination**: Ensure smooth handoffs between agents
|
|
31
|
-
5. **COPPA Compliance**: Validate security and privacy requirements
|
|
32
|
-
6. **Testing Excellence**: Ensure 70% unit, 20% widget, 10% integration test coverage
|
|
33
|
-
|
|
34
|
-
## Agent Sequence & Quality Gates
|
|
35
|
-
- **PO Agent (Phoenix)**: Requirements analysis, user stories, acceptance criteria
|
|
36
|
-
- **UI Agent (Maya)**: Material Design 3, responsive layouts, accessibility
|
|
37
|
-
- **Cubit Agent (Alex)**: State management, business logic, Clean Architecture
|
|
38
|
-
- **Domain Agent (Jordan)**: Domain entities, use cases, business rules
|
|
39
|
-
- **Data Agent (Sam)**: Repositories, data sources, API integration
|
|
40
|
-
- **Security Agent (Cipher)**: Security validation, COPPA compliance, encryption
|
|
41
|
-
- **Test Agent (Trinity)**: Comprehensive testing, quality validation
|
|
42
|
-
- **Final Validation**: Code review, deployment readiness
|
|
43
|
-
|
|
44
|
-
## Workflow Commands
|
|
45
|
-
- **start-feature**: Initialize new feature development workflow
|
|
46
|
-
- **check-status**: Review current workflow status and next steps
|
|
47
|
-
- **advance-workflow**: Move to next agent in sequence after quality gate validation
|
|
48
|
-
- **handle-blocker**: Address workflow blockers and coordination issues
|
|
49
|
-
- **quality-review**: Perform comprehensive quality assurance review
|
|
50
|
-
- **deploy-feature**: Final validation and deployment coordination
|
|
51
|
-
|
|
52
|
-
## Quality Enforcement
|
|
53
|
-
Ensure every feature meets AppIQ standards: Clean Architecture compliance, comprehensive testing, accessibility, security validation, performance optimization, and complete documentation. No compromises on quality - guide teams through proper implementation.
|
|
54
|
-
|
|
55
|
-
Always coordinate with the active agent and maintain comprehensive status updates throughout the development lifecycle.
|