@jungjaehoon/mama-os 0.9.2 → 0.9.4
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/README.md +41 -7
- package/dist/agent/agent-loop.d.ts.map +1 -1
- package/dist/agent/agent-loop.js +2 -3
- package/dist/agent/agent-loop.js.map +1 -1
- package/dist/agent/claude-cli-wrapper.d.ts +4 -4
- package/dist/agent/claude-cli-wrapper.d.ts.map +1 -1
- package/dist/agent/claude-cli-wrapper.js +17 -5
- package/dist/agent/claude-cli-wrapper.js.map +1 -1
- package/dist/agent/claude-client.js +3 -3
- package/dist/agent/claude-client.js.map +1 -1
- package/dist/agent/codex-mcp-process.d.ts +10 -0
- package/dist/agent/codex-mcp-process.d.ts.map +1 -1
- package/dist/agent/codex-mcp-process.js +226 -58
- package/dist/agent/codex-mcp-process.js.map +1 -1
- package/dist/agent/gateway-tool-executor.d.ts +15 -1
- package/dist/agent/gateway-tool-executor.d.ts.map +1 -1
- package/dist/agent/gateway-tool-executor.js +37 -3
- package/dist/agent/gateway-tool-executor.js.map +1 -1
- package/dist/agent/gateway-tools.md +1 -0
- package/dist/agent/persistent-cli-process.d.ts +2 -0
- package/dist/agent/persistent-cli-process.d.ts.map +1 -1
- package/dist/agent/persistent-cli-process.js +15 -0
- package/dist/agent/persistent-cli-process.js.map +1 -1
- package/dist/agent/types.d.ts +3 -3
- package/dist/agent/types.d.ts.map +1 -1
- package/dist/agent/types.js.map +1 -1
- package/dist/api/graph-api.d.ts.map +1 -1
- package/dist/api/graph-api.js +31 -5
- package/dist/api/graph-api.js.map +1 -1
- package/dist/cli/commands/start.d.ts.map +1 -1
- package/dist/cli/commands/start.js +91 -6
- package/dist/cli/commands/start.js.map +1 -1
- package/dist/cli/commands/stop.d.ts +7 -1
- package/dist/cli/commands/stop.d.ts.map +1 -1
- package/dist/cli/commands/stop.js +49 -0
- package/dist/cli/commands/stop.js.map +1 -1
- package/dist/cli/config/config-manager.d.ts.map +1 -1
- package/dist/cli/config/config-manager.js +60 -15
- package/dist/cli/config/config-manager.js.map +1 -1
- package/dist/cli/config/types.d.ts +19 -5
- package/dist/cli/config/types.d.ts.map +1 -1
- package/dist/cli/config/types.js +3 -3
- package/dist/cli/config/types.js.map +1 -1
- package/dist/gateways/image-analyzer.js +1 -1
- package/dist/gateways/image-analyzer.js.map +1 -1
- package/dist/gateways/slack.d.ts.map +1 -1
- package/dist/gateways/slack.js +8 -19
- package/dist/gateways/slack.js.map +1 -1
- package/dist/multi-agent/agent-process-manager.d.ts +15 -1
- package/dist/multi-agent/agent-process-manager.d.ts.map +1 -1
- package/dist/multi-agent/agent-process-manager.js +121 -22
- package/dist/multi-agent/agent-process-manager.js.map +1 -1
- package/dist/multi-agent/background-task-manager.d.ts +2 -2
- package/dist/multi-agent/background-task-manager.js +2 -2
- package/dist/multi-agent/bmad-templates.d.ts +67 -0
- package/dist/multi-agent/bmad-templates.d.ts.map +1 -0
- package/dist/multi-agent/bmad-templates.js +248 -0
- package/dist/multi-agent/bmad-templates.js.map +1 -0
- package/dist/multi-agent/council-engine.d.ts +60 -0
- package/dist/multi-agent/council-engine.d.ts.map +1 -0
- package/dist/multi-agent/council-engine.js +284 -0
- package/dist/multi-agent/council-engine.js.map +1 -0
- package/dist/multi-agent/multi-agent-base.d.ts +18 -9
- package/dist/multi-agent/multi-agent-base.d.ts.map +1 -1
- package/dist/multi-agent/multi-agent-base.js +116 -33
- package/dist/multi-agent/multi-agent-base.js.map +1 -1
- package/dist/multi-agent/multi-agent-discord.d.ts +3 -35
- package/dist/multi-agent/multi-agent-discord.d.ts.map +1 -1
- package/dist/multi-agent/multi-agent-discord.js +81 -302
- package/dist/multi-agent/multi-agent-discord.js.map +1 -1
- package/dist/multi-agent/multi-agent-slack.d.ts +2 -25
- package/dist/multi-agent/multi-agent-slack.d.ts.map +1 -1
- package/dist/multi-agent/multi-agent-slack.js +173 -253
- package/dist/multi-agent/multi-agent-slack.js.map +1 -1
- package/dist/multi-agent/runtime-process.d.ts +3 -0
- package/dist/multi-agent/runtime-process.d.ts.map +1 -1
- package/dist/multi-agent/runtime-process.js +4 -0
- package/dist/multi-agent/runtime-process.js.map +1 -1
- package/dist/multi-agent/shared-context.d.ts.map +1 -1
- package/dist/multi-agent/shared-context.js +4 -4
- package/dist/multi-agent/shared-context.js.map +1 -1
- package/dist/multi-agent/system-reminder.d.ts +1 -1
- package/dist/multi-agent/system-reminder.js +1 -1
- package/dist/multi-agent/types.d.ts +31 -15
- package/dist/multi-agent/types.d.ts.map +1 -1
- package/dist/multi-agent/types.js +1 -3
- package/dist/multi-agent/types.js.map +1 -1
- package/dist/multi-agent/ultrawork-state.d.ts +57 -0
- package/dist/multi-agent/ultrawork-state.d.ts.map +1 -0
- package/dist/multi-agent/ultrawork-state.js +191 -0
- package/dist/multi-agent/ultrawork-state.js.map +1 -0
- package/dist/multi-agent/ultrawork.d.ts +37 -19
- package/dist/multi-agent/ultrawork.d.ts.map +1 -1
- package/dist/multi-agent/ultrawork.js +587 -41
- package/dist/multi-agent/ultrawork.js.map +1 -1
- package/dist/multi-agent/workflow-engine.d.ts +7 -0
- package/dist/multi-agent/workflow-engine.d.ts.map +1 -1
- package/dist/multi-agent/workflow-engine.js +238 -33
- package/dist/multi-agent/workflow-engine.js.map +1 -1
- package/dist/multi-agent/workflow-types.d.ts +74 -1
- package/dist/multi-agent/workflow-types.d.ts.map +1 -1
- package/dist/onboarding/complete-autonomous-prompt.d.ts +1 -1
- package/dist/onboarding/complete-autonomous-prompt.d.ts.map +1 -1
- package/dist/onboarding/complete-autonomous-prompt.js +27 -10
- package/dist/onboarding/complete-autonomous-prompt.js.map +1 -1
- package/dist/onboarding/phase-7-integrations.d.ts.map +1 -1
- package/dist/onboarding/phase-7-integrations.js +23 -3
- package/dist/onboarding/phase-7-integrations.js.map +1 -1
- package/dist/onboarding/phase-9-finalization.d.ts.map +1 -1
- package/dist/onboarding/phase-9-finalization.js +33 -0
- package/dist/onboarding/phase-9-finalization.js.map +1 -1
- package/dist/setup/setup-prompt.d.ts +1 -1
- package/dist/setup/setup-prompt.d.ts.map +1 -1
- package/dist/setup/setup-prompt.js +1 -1
- package/package.json +1 -1
- package/public/viewer/js/modules/settings.js +110 -15
- package/public/viewer/js/utils/format.js +10 -7
- package/public/viewer/src/modules/settings.ts +133 -16
- package/public/viewer/src/utils/api.ts +2 -1
- package/public/viewer/src/utils/format.ts +10 -7
- package/public/viewer/viewer.html +1 -0
- package/templates/bmad/LICENSE +28 -0
- package/templates/bmad/architecture.md +343 -0
- package/templates/bmad/bmm-workflow-status.template.yaml +66 -0
- package/templates/bmad/prd.md +198 -0
- package/templates/bmad/product-brief.md +149 -0
- package/templates/bmad/sprint-status.template.yaml +35 -0
- package/templates/bmad/tech-spec.md +151 -0
- package/templates/personas/architect.md +70 -0
- package/templates/personas/conductor.md +373 -0
- package/templates/personas/developer.md +20 -7
- package/templates/personas/pm.md +49 -33
- package/templates/personas/reviewer.md +18 -5
- package/dist/multi-agent/pr-review-poller.d.ts +0 -197
- package/dist/multi-agent/pr-review-poller.d.ts.map +0 -1
- package/dist/multi-agent/pr-review-poller.js +0 -972
- package/dist/multi-agent/pr-review-poller.js.map +0 -1
- package/templates/personas/sisyphus-builtin-en.md +0 -161
- package/templates/personas/sisyphus.md +0 -218
|
@@ -0,0 +1,343 @@
|
|
|
1
|
+
# System Architecture: {{project_name}}
|
|
2
|
+
|
|
3
|
+
**Date:** {{date}}
|
|
4
|
+
**Architect:** {{user_name}}
|
|
5
|
+
**Version:** 1.0
|
|
6
|
+
**Project Type:** {{project_type}}
|
|
7
|
+
**Project Level:** {{project_level}}
|
|
8
|
+
**Status:** Draft
|
|
9
|
+
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
## Document Overview
|
|
13
|
+
|
|
14
|
+
This document defines the system architecture for {{project_name}}. It provides the technical blueprint for implementation, addressing all functional and non-functional requirements from the PRD.
|
|
15
|
+
|
|
16
|
+
**Related Documents:**
|
|
17
|
+
|
|
18
|
+
- Product Requirements Document: {{prd_path}}
|
|
19
|
+
- Product Brief: {{product_brief_path}}
|
|
20
|
+
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
## Executive Summary
|
|
24
|
+
|
|
25
|
+
{{executive_summary}}
|
|
26
|
+
|
|
27
|
+
---
|
|
28
|
+
|
|
29
|
+
## Architectural Drivers
|
|
30
|
+
|
|
31
|
+
These requirements heavily influence architectural decisions:
|
|
32
|
+
|
|
33
|
+
{{architectural_drivers}}
|
|
34
|
+
|
|
35
|
+
---
|
|
36
|
+
|
|
37
|
+
## System Overview
|
|
38
|
+
|
|
39
|
+
### High-Level Architecture
|
|
40
|
+
|
|
41
|
+
{{high_level_architecture}}
|
|
42
|
+
|
|
43
|
+
### Architecture Diagram
|
|
44
|
+
|
|
45
|
+
{{architecture_diagram}}
|
|
46
|
+
|
|
47
|
+
### Architectural Pattern
|
|
48
|
+
|
|
49
|
+
**Pattern:** {{architectural_pattern}}
|
|
50
|
+
|
|
51
|
+
**Rationale:** {{pattern_rationale}}
|
|
52
|
+
|
|
53
|
+
---
|
|
54
|
+
|
|
55
|
+
## Technology Stack
|
|
56
|
+
|
|
57
|
+
### Frontend
|
|
58
|
+
|
|
59
|
+
{{frontend_stack}}
|
|
60
|
+
|
|
61
|
+
### Backend
|
|
62
|
+
|
|
63
|
+
{{backend_stack}}
|
|
64
|
+
|
|
65
|
+
### Database
|
|
66
|
+
|
|
67
|
+
{{database_stack}}
|
|
68
|
+
|
|
69
|
+
### Infrastructure
|
|
70
|
+
|
|
71
|
+
{{infrastructure_stack}}
|
|
72
|
+
|
|
73
|
+
### Third-Party Services
|
|
74
|
+
|
|
75
|
+
{{third_party_services}}
|
|
76
|
+
|
|
77
|
+
### Development & Deployment
|
|
78
|
+
|
|
79
|
+
{{dev_deployment_stack}}
|
|
80
|
+
|
|
81
|
+
---
|
|
82
|
+
|
|
83
|
+
## System Components
|
|
84
|
+
|
|
85
|
+
{{system_components}}
|
|
86
|
+
|
|
87
|
+
---
|
|
88
|
+
|
|
89
|
+
## Data Architecture
|
|
90
|
+
|
|
91
|
+
### Data Model
|
|
92
|
+
|
|
93
|
+
{{data_model}}
|
|
94
|
+
|
|
95
|
+
### Database Design
|
|
96
|
+
|
|
97
|
+
{{database_design}}
|
|
98
|
+
|
|
99
|
+
### Data Flow
|
|
100
|
+
|
|
101
|
+
{{data_flow}}
|
|
102
|
+
|
|
103
|
+
---
|
|
104
|
+
|
|
105
|
+
## API Design
|
|
106
|
+
|
|
107
|
+
### API Architecture
|
|
108
|
+
|
|
109
|
+
{{api_architecture}}
|
|
110
|
+
|
|
111
|
+
### Endpoints
|
|
112
|
+
|
|
113
|
+
{{api_endpoints}}
|
|
114
|
+
|
|
115
|
+
### Authentication & Authorization
|
|
116
|
+
|
|
117
|
+
{{api_auth}}
|
|
118
|
+
|
|
119
|
+
---
|
|
120
|
+
|
|
121
|
+
## Non-Functional Requirements Coverage
|
|
122
|
+
|
|
123
|
+
### NFR-001: {{nfr_001_name}}
|
|
124
|
+
|
|
125
|
+
**Requirement:** {{nfr_001_requirement}}
|
|
126
|
+
|
|
127
|
+
**Architecture Solution:** {{nfr_001_solution}}
|
|
128
|
+
|
|
129
|
+
---
|
|
130
|
+
|
|
131
|
+
{{additional_nfrs}}
|
|
132
|
+
|
|
133
|
+
---
|
|
134
|
+
|
|
135
|
+
## Security Architecture
|
|
136
|
+
|
|
137
|
+
### Authentication
|
|
138
|
+
|
|
139
|
+
{{auth_design}}
|
|
140
|
+
|
|
141
|
+
### Authorization
|
|
142
|
+
|
|
143
|
+
{{authz_design}}
|
|
144
|
+
|
|
145
|
+
### Data Encryption
|
|
146
|
+
|
|
147
|
+
{{encryption_design}}
|
|
148
|
+
|
|
149
|
+
### Security Best Practices
|
|
150
|
+
|
|
151
|
+
{{security_practices}}
|
|
152
|
+
|
|
153
|
+
---
|
|
154
|
+
|
|
155
|
+
## Scalability & Performance
|
|
156
|
+
|
|
157
|
+
### Scaling Strategy
|
|
158
|
+
|
|
159
|
+
{{scaling_strategy}}
|
|
160
|
+
|
|
161
|
+
### Performance Optimization
|
|
162
|
+
|
|
163
|
+
{{performance_optimization}}
|
|
164
|
+
|
|
165
|
+
### Caching Strategy
|
|
166
|
+
|
|
167
|
+
{{caching_strategy}}
|
|
168
|
+
|
|
169
|
+
### Load Balancing
|
|
170
|
+
|
|
171
|
+
{{load_balancing}}
|
|
172
|
+
|
|
173
|
+
---
|
|
174
|
+
|
|
175
|
+
## Reliability & Availability
|
|
176
|
+
|
|
177
|
+
### High Availability Design
|
|
178
|
+
|
|
179
|
+
{{ha_design}}
|
|
180
|
+
|
|
181
|
+
### Disaster Recovery
|
|
182
|
+
|
|
183
|
+
{{dr_design}}
|
|
184
|
+
|
|
185
|
+
### Backup Strategy
|
|
186
|
+
|
|
187
|
+
{{backup_strategy}}
|
|
188
|
+
|
|
189
|
+
### Monitoring & Alerting
|
|
190
|
+
|
|
191
|
+
{{monitoring_alerting}}
|
|
192
|
+
|
|
193
|
+
---
|
|
194
|
+
|
|
195
|
+
## Integration Architecture
|
|
196
|
+
|
|
197
|
+
### External Integrations
|
|
198
|
+
|
|
199
|
+
{{external_integrations}}
|
|
200
|
+
|
|
201
|
+
### Internal Integrations
|
|
202
|
+
|
|
203
|
+
{{internal_integrations}}
|
|
204
|
+
|
|
205
|
+
### Message/Event Architecture (if applicable)
|
|
206
|
+
|
|
207
|
+
{{messaging_architecture}}
|
|
208
|
+
|
|
209
|
+
---
|
|
210
|
+
|
|
211
|
+
## Development Architecture
|
|
212
|
+
|
|
213
|
+
### Code Organization
|
|
214
|
+
|
|
215
|
+
{{code_organization}}
|
|
216
|
+
|
|
217
|
+
### Module Structure
|
|
218
|
+
|
|
219
|
+
{{module_structure}}
|
|
220
|
+
|
|
221
|
+
### Testing Strategy
|
|
222
|
+
|
|
223
|
+
{{testing_strategy}}
|
|
224
|
+
|
|
225
|
+
### CI/CD Pipeline
|
|
226
|
+
|
|
227
|
+
{{cicd_pipeline}}
|
|
228
|
+
|
|
229
|
+
---
|
|
230
|
+
|
|
231
|
+
## Deployment Architecture
|
|
232
|
+
|
|
233
|
+
### Environments
|
|
234
|
+
|
|
235
|
+
{{environments}}
|
|
236
|
+
|
|
237
|
+
### Deployment Strategy
|
|
238
|
+
|
|
239
|
+
{{deployment_strategy}}
|
|
240
|
+
|
|
241
|
+
### Infrastructure as Code
|
|
242
|
+
|
|
243
|
+
{{iac}}
|
|
244
|
+
|
|
245
|
+
---
|
|
246
|
+
|
|
247
|
+
## Requirements Traceability
|
|
248
|
+
|
|
249
|
+
### Functional Requirements Coverage
|
|
250
|
+
|
|
251
|
+
{{fr_traceability}}
|
|
252
|
+
|
|
253
|
+
### Non-Functional Requirements Coverage
|
|
254
|
+
|
|
255
|
+
{{nfr_traceability}}
|
|
256
|
+
|
|
257
|
+
---
|
|
258
|
+
|
|
259
|
+
## Trade-offs & Decision Log
|
|
260
|
+
|
|
261
|
+
{{tradeoffs}}
|
|
262
|
+
|
|
263
|
+
---
|
|
264
|
+
|
|
265
|
+
## Open Issues & Risks
|
|
266
|
+
|
|
267
|
+
{{open_issues}}
|
|
268
|
+
|
|
269
|
+
---
|
|
270
|
+
|
|
271
|
+
## Assumptions & Constraints
|
|
272
|
+
|
|
273
|
+
{{assumptions}}
|
|
274
|
+
|
|
275
|
+
---
|
|
276
|
+
|
|
277
|
+
## Future Considerations
|
|
278
|
+
|
|
279
|
+
{{future_considerations}}
|
|
280
|
+
|
|
281
|
+
---
|
|
282
|
+
|
|
283
|
+
## Approval & Sign-off
|
|
284
|
+
|
|
285
|
+
**Review Status:**
|
|
286
|
+
|
|
287
|
+
- [ ] Technical Lead
|
|
288
|
+
- [ ] Product Owner
|
|
289
|
+
- [ ] Security Architect (if applicable)
|
|
290
|
+
- [ ] DevOps Lead
|
|
291
|
+
|
|
292
|
+
---
|
|
293
|
+
|
|
294
|
+
## Revision History
|
|
295
|
+
|
|
296
|
+
| Version | Date | Author | Changes |
|
|
297
|
+
| ------- | -------- | ------------- | -------------------- |
|
|
298
|
+
| 1.0 | {{date}} | {{user_name}} | Initial architecture |
|
|
299
|
+
|
|
300
|
+
---
|
|
301
|
+
|
|
302
|
+
## Next Steps
|
|
303
|
+
|
|
304
|
+
### Phase 4: Sprint Planning & Implementation
|
|
305
|
+
|
|
306
|
+
Run `/sprint-planning` to:
|
|
307
|
+
|
|
308
|
+
- Break epics into detailed user stories
|
|
309
|
+
- Estimate story complexity
|
|
310
|
+
- Plan sprint iterations
|
|
311
|
+
- Begin implementation following this architectural blueprint
|
|
312
|
+
|
|
313
|
+
**Key Implementation Principles:**
|
|
314
|
+
|
|
315
|
+
1. Follow component boundaries defined in this document
|
|
316
|
+
2. Implement NFR solutions as specified
|
|
317
|
+
3. Use technology stack as defined
|
|
318
|
+
4. Follow API contracts exactly
|
|
319
|
+
5. Adhere to security and performance guidelines
|
|
320
|
+
|
|
321
|
+
---
|
|
322
|
+
|
|
323
|
+
**This document was created using BMAD Method v6 - Phase 3 (Solutioning)**
|
|
324
|
+
|
|
325
|
+
_To continue: Run `/workflow-status` to see your progress and next recommended workflow._
|
|
326
|
+
|
|
327
|
+
---
|
|
328
|
+
|
|
329
|
+
## Appendix A: Technology Evaluation Matrix
|
|
330
|
+
|
|
331
|
+
{{tech_evaluation_matrix}}
|
|
332
|
+
|
|
333
|
+
---
|
|
334
|
+
|
|
335
|
+
## Appendix B: Capacity Planning
|
|
336
|
+
|
|
337
|
+
{{capacity_planning}}
|
|
338
|
+
|
|
339
|
+
---
|
|
340
|
+
|
|
341
|
+
## Appendix C: Cost Estimation
|
|
342
|
+
|
|
343
|
+
{{cost_estimation}}
|
|
@@ -0,0 +1,66 @@
|
|
|
1
|
+
# BMAD Method Workflow Status
|
|
2
|
+
# Generated: {{TIMESTAMP}}
|
|
3
|
+
# Project: {{PROJECT_NAME}}
|
|
4
|
+
|
|
5
|
+
project_name: "{{PROJECT_NAME}}"
|
|
6
|
+
project_type: "{{PROJECT_TYPE}}"
|
|
7
|
+
project_level: "{{PROJECT_LEVEL}}"
|
|
8
|
+
communication_language: "English"
|
|
9
|
+
output_language: "English"
|
|
10
|
+
last_updated: "{{TIMESTAMP}}"
|
|
11
|
+
|
|
12
|
+
# Workflow Status Tracking
|
|
13
|
+
# Status values:
|
|
14
|
+
# - "required" - Must be completed
|
|
15
|
+
# - "optional" - Can be skipped
|
|
16
|
+
# - "recommended" - Strongly suggested
|
|
17
|
+
# - "conditional" - Required based on project level
|
|
18
|
+
# - "{file-path}" - Completed (path to output file)
|
|
19
|
+
# - "skipped" - Explicitly skipped
|
|
20
|
+
|
|
21
|
+
workflow_status:
|
|
22
|
+
# Phase 1: Analysis (Optional but recommended)
|
|
23
|
+
- name: product-brief
|
|
24
|
+
phase: 1
|
|
25
|
+
status: "optional"
|
|
26
|
+
description: "Create comprehensive product brief"
|
|
27
|
+
|
|
28
|
+
- name: brainstorm-project
|
|
29
|
+
phase: 1
|
|
30
|
+
status: "optional"
|
|
31
|
+
description: "Structured brainstorming session"
|
|
32
|
+
|
|
33
|
+
- name: research
|
|
34
|
+
phase: 1
|
|
35
|
+
status: "optional"
|
|
36
|
+
description: "Market and competitive research"
|
|
37
|
+
|
|
38
|
+
# Phase 2: Planning (Required - choose one based on project level)
|
|
39
|
+
- name: prd
|
|
40
|
+
phase: 2
|
|
41
|
+
status: "{{PRD_STATUS}}" # required for level 2+, recommended for level 1
|
|
42
|
+
description: "Product Requirements Document"
|
|
43
|
+
|
|
44
|
+
- name: tech-spec
|
|
45
|
+
phase: 2
|
|
46
|
+
status: "{{TECH_SPEC_STATUS}}" # required for level 0-1, optional for 2+
|
|
47
|
+
description: "Technical Specification"
|
|
48
|
+
|
|
49
|
+
- name: create-ux-design
|
|
50
|
+
phase: 2
|
|
51
|
+
status: "optional"
|
|
52
|
+
description: "UX/UI design workflow"
|
|
53
|
+
|
|
54
|
+
# Phase 3: Solutioning (Conditional on project level)
|
|
55
|
+
- name: architecture
|
|
56
|
+
phase: 3
|
|
57
|
+
status: "{{ARCHITECTURE_STATUS}}" # required for level 2+
|
|
58
|
+
description: "System architecture design"
|
|
59
|
+
|
|
60
|
+
- name: solutioning-gate-check
|
|
61
|
+
phase: 3
|
|
62
|
+
status: "optional"
|
|
63
|
+
description: "Validate architecture against requirements"
|
|
64
|
+
|
|
65
|
+
# Phase 4: Implementation (Required)
|
|
66
|
+
# Note: Implementation tracked in sprint-status.yaml
|
|
@@ -0,0 +1,198 @@
|
|
|
1
|
+
# Product Requirements Document: {{project_name}}
|
|
2
|
+
|
|
3
|
+
**Date:** {{date}}
|
|
4
|
+
**Author:** {{user_name}}
|
|
5
|
+
**Version:** 1.0
|
|
6
|
+
**Project Type:** {{project_type}}
|
|
7
|
+
**Project Level:** {{project_level}}
|
|
8
|
+
**Status:** Draft
|
|
9
|
+
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
## Document Overview
|
|
13
|
+
|
|
14
|
+
This Product Requirements Document (PRD) defines the functional and non-functional requirements for {{project_name}}. It serves as the source of truth for what will be built and provides traceability from requirements through implementation.
|
|
15
|
+
|
|
16
|
+
**Related Documents:**
|
|
17
|
+
|
|
18
|
+
- Product Brief: {{product_brief_path}}
|
|
19
|
+
|
|
20
|
+
---
|
|
21
|
+
|
|
22
|
+
## Executive Summary
|
|
23
|
+
|
|
24
|
+
{{executive_summary}}
|
|
25
|
+
|
|
26
|
+
---
|
|
27
|
+
|
|
28
|
+
## Product Goals
|
|
29
|
+
|
|
30
|
+
### Business Objectives
|
|
31
|
+
|
|
32
|
+
{{business_objectives}}
|
|
33
|
+
|
|
34
|
+
### Success Metrics
|
|
35
|
+
|
|
36
|
+
{{success_metrics}}
|
|
37
|
+
|
|
38
|
+
---
|
|
39
|
+
|
|
40
|
+
## Functional Requirements
|
|
41
|
+
|
|
42
|
+
Functional Requirements (FRs) define **what** the system does - specific features and behaviors.
|
|
43
|
+
|
|
44
|
+
Each requirement includes:
|
|
45
|
+
|
|
46
|
+
- **ID**: Unique identifier (FR-001, FR-002, etc.)
|
|
47
|
+
- **Priority**: Must Have / Should Have / Could Have / Won't Have (MoSCoW)
|
|
48
|
+
- **Description**: What the system should do
|
|
49
|
+
- **Acceptance Criteria**: How to verify it's complete
|
|
50
|
+
|
|
51
|
+
---
|
|
52
|
+
|
|
53
|
+
{{functional_requirements}}
|
|
54
|
+
|
|
55
|
+
---
|
|
56
|
+
|
|
57
|
+
## Non-Functional Requirements
|
|
58
|
+
|
|
59
|
+
Non-Functional Requirements (NFRs) define **how** the system performs - quality attributes and constraints.
|
|
60
|
+
|
|
61
|
+
---
|
|
62
|
+
|
|
63
|
+
{{non_functional_requirements}}
|
|
64
|
+
|
|
65
|
+
---
|
|
66
|
+
|
|
67
|
+
## Epics
|
|
68
|
+
|
|
69
|
+
Epics are logical groupings of related functionality that will be broken down into user stories during sprint planning (Phase 4).
|
|
70
|
+
|
|
71
|
+
Each epic maps to multiple functional requirements and will generate 2-10 stories.
|
|
72
|
+
|
|
73
|
+
---
|
|
74
|
+
|
|
75
|
+
{{epics}}
|
|
76
|
+
|
|
77
|
+
---
|
|
78
|
+
|
|
79
|
+
## User Stories (High-Level)
|
|
80
|
+
|
|
81
|
+
User stories follow the format: "As a [user type], I want [goal] so that [benefit]."
|
|
82
|
+
|
|
83
|
+
These are preliminary stories. Detailed stories will be created in Phase 4 (Implementation).
|
|
84
|
+
|
|
85
|
+
---
|
|
86
|
+
|
|
87
|
+
{{user_stories}}
|
|
88
|
+
|
|
89
|
+
---
|
|
90
|
+
|
|
91
|
+
## User Personas
|
|
92
|
+
|
|
93
|
+
{{user_personas}}
|
|
94
|
+
|
|
95
|
+
---
|
|
96
|
+
|
|
97
|
+
## User Flows
|
|
98
|
+
|
|
99
|
+
{{user_flows}}
|
|
100
|
+
|
|
101
|
+
---
|
|
102
|
+
|
|
103
|
+
## Dependencies
|
|
104
|
+
|
|
105
|
+
### Internal Dependencies
|
|
106
|
+
|
|
107
|
+
{{internal_dependencies}}
|
|
108
|
+
|
|
109
|
+
### External Dependencies
|
|
110
|
+
|
|
111
|
+
{{external_dependencies}}
|
|
112
|
+
|
|
113
|
+
---
|
|
114
|
+
|
|
115
|
+
## Assumptions
|
|
116
|
+
|
|
117
|
+
{{assumptions}}
|
|
118
|
+
|
|
119
|
+
---
|
|
120
|
+
|
|
121
|
+
## Out of Scope
|
|
122
|
+
|
|
123
|
+
{{out_of_scope}}
|
|
124
|
+
|
|
125
|
+
---
|
|
126
|
+
|
|
127
|
+
## Open Questions
|
|
128
|
+
|
|
129
|
+
{{open_questions}}
|
|
130
|
+
|
|
131
|
+
---
|
|
132
|
+
|
|
133
|
+
## Approval & Sign-off
|
|
134
|
+
|
|
135
|
+
### Stakeholders
|
|
136
|
+
|
|
137
|
+
{{stakeholders}}
|
|
138
|
+
|
|
139
|
+
### Approval Status
|
|
140
|
+
|
|
141
|
+
- [ ] Product Owner
|
|
142
|
+
- [ ] Engineering Lead
|
|
143
|
+
- [ ] Design Lead
|
|
144
|
+
- [ ] QA Lead
|
|
145
|
+
|
|
146
|
+
---
|
|
147
|
+
|
|
148
|
+
## Revision History
|
|
149
|
+
|
|
150
|
+
| Version | Date | Author | Changes |
|
|
151
|
+
| ------- | -------- | ------------- | ----------- |
|
|
152
|
+
| 1.0 | {{date}} | {{user_name}} | Initial PRD |
|
|
153
|
+
|
|
154
|
+
---
|
|
155
|
+
|
|
156
|
+
## Next Steps
|
|
157
|
+
|
|
158
|
+
### Phase 3: Architecture
|
|
159
|
+
|
|
160
|
+
Run `/architecture` to create system architecture based on these requirements.
|
|
161
|
+
|
|
162
|
+
The architecture will address:
|
|
163
|
+
|
|
164
|
+
- All functional requirements (FRs)
|
|
165
|
+
- All non-functional requirements (NFRs)
|
|
166
|
+
- Technical stack decisions
|
|
167
|
+
- Data models and APIs
|
|
168
|
+
- System components
|
|
169
|
+
|
|
170
|
+
### Phase 4: Sprint Planning
|
|
171
|
+
|
|
172
|
+
After architecture is complete, run `/sprint-planning` to:
|
|
173
|
+
|
|
174
|
+
- Break epics into detailed user stories
|
|
175
|
+
- Estimate story complexity
|
|
176
|
+
- Plan sprint iterations
|
|
177
|
+
- Begin implementation
|
|
178
|
+
|
|
179
|
+
---
|
|
180
|
+
|
|
181
|
+
**This document was created using BMAD Method v6 - Phase 2 (Planning)**
|
|
182
|
+
|
|
183
|
+
_To continue: Run `/workflow-status` to see your progress and next recommended workflow._
|
|
184
|
+
|
|
185
|
+
---
|
|
186
|
+
|
|
187
|
+
## Appendix A: Requirements Traceability Matrix
|
|
188
|
+
|
|
189
|
+
| Epic ID | Epic Name | Functional Requirements | Story Count (Est.) |
|
|
190
|
+
| ------- | --------- | ----------------------- | ------------------ |
|
|
191
|
+
|
|
192
|
+
{{traceability_matrix}}
|
|
193
|
+
|
|
194
|
+
---
|
|
195
|
+
|
|
196
|
+
## Appendix B: Prioritization Details
|
|
197
|
+
|
|
198
|
+
{{prioritization_details}}
|