cardosofelipe/syndarix
1
0
Fork 0
forked from cardosofelipe/fast-next-template
Code Issues 18 Pull Requests Wiki Activity

docs: Add missing architecture flow and update roadmap for dashboard/onboarding

Browse Source 
Requirements:
- Add 6.4.3 Architecture Spike & Proposal Flow diagram
- Documents the flow from approved requirements → collaborative brainstorm →
  proposal → client approval → ADRs → sprint planning

Implementation Roadmap:
- Add Phase 1.5: Main Dashboard & Onboarding section
- Add issues #47-50 for main dashboard and project creation wizard
- Update progress summary (Phase 1 now at ~75%)
- Add blocking items for new design work

Related Issues:
- #47: [DESIGN] Main Dashboard / Projects List Page
- #48: Implement Main Dashboard / Projects List Page
- #49: [DESIGN] Project Creation Wizard
- #50: Implement Project Creation Wizard

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Felipe Cardoso
2025-12-30 18:32:31 +01:00
parent cea97afe25
commit 29309e5cfd
2 changed files with 110 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
docs/architecture/IMPLEMENTATION_ROADMAP.md
View File

@@ -75,14 +75,26 @@ This roadmap outlines the phased implementation approach for Syndarix, prioritiz
- [x] Basic navigation and layout (implemented)
- [ ] Production implementations (#40-43) - Blocked by design approvals
### 1.5 Main Dashboard & Onboarding (NEW)
- [ ] Main Dashboard / Projects List (design) - #47
- [ ] Main Dashboard / Projects List (implementation) - #48, blocked by #47
- [ ] Project Creation Wizard (design) - #49
- [ ] Project Creation Wizard (implementation) - #50, blocked by #49
**Note:** The Project Creation Wizard includes a placeholder for Phase 4 agent chat integration.
Full onboarding workflow (FR-301, FR-302) will be implemented in Phase 4.
### Deliverables
- [x] CRUD operations for all core entities
- [x] Real-time event streaming working
- [ ] Basic admin UI for configuration (blocked by design approvals)
- [ ] Main dashboard with projects list and activity feed
- [ ] Project creation wizard (simplified, no agent chat)
### Blocking Items
- Issues #36-39: UI prototypes awaiting user approval
- Issues #40-43: Frontend implementations blocked by #36-39
- Issues #47-50: Main dashboard and project wizard (new)
---
@@ -294,7 +306,7 @@ This roadmap outlines the phased implementation approach for Syndarix, prioritiz
| Phase | Status | Completion |
|-------|--------|------------|
| Phase 0: Foundation | ✅ Complete | 100% |
| Phase 1: Core Platform | 🔄 In Progress | ~88% |
| Phase 1: Core Platform | 🔄 In Progress | ~75% |
| Phase 2: MCP Integration | 📋 Not Started | 0% |
| Phase 3: Agent Orchestration | 📋 Not Started | 0% |
| Phase 4: Workflow Engine | 📋 Not Started | 0% |
@@ -305,11 +317,14 @@ This roadmap outlines the phased implementation approach for Syndarix, prioritiz
- Data Model: ✅ 100% (all entities, CRUD, migrations)
- API Layer: ✅ 100% (all endpoints implemented)
- Real-time: ✅ 100% (EventBus, SSE, client hooks)
- Frontend: 🔄 50% (prototypes done, implementations blocked)
- Frontend Foundation: 🔄 50% (prototypes done, implementations blocked)
- Main Dashboard & Onboarding: 📋 0% (issues created, design pending)
### Blocking Items
1. **UI Design Approvals (#36-39)**: Prototypes complete, awaiting user review
2. **Frontend Implementations (#40-43)**: Blocked by design approvals
3. **Main Dashboard Design (#47)**: New, needs prototype
4. **Project Wizard Design (#49)**: New, needs prototype
---

93
docs/requirements/SYNDARIX_REQUIREMENTS.md
View File

@@ -1427,6 +1427,99 @@ def create_issue(
+----------+
```
#### 6.4.3 Architecture Spike & Proposal Flow
```
+----------+ +----------+
|Approved | 1. Trigger Spike | PO |
|Require- |-------------------------->| Agent |
|ments | +----------+
+----------+ |
2. Summarize
Context
|
v
+----------+ 3. Requirements +---------------+
| BA |<---------------------| Spike Start |
| Agent | Handoff | Workflow |
+----------+ +---------------+
| |
4. Deep 5. Invite
Analysis Architect
| |
v v
+----------+ +----------+
| Domain | |Architect |
| Model | | Agent |
+----------+ +----------+
| |
+---------------+---------------------+
|
6. Collaborative
Brainstorm
|
v
+---------------+
| Tech Stack |
| Discussion |
+---------------+
|
7. Generate
Proposal
|
v
+---------------+
| Architecture |
| Proposal Doc |
+---------------+
|
8. Create ADRs
|
v
+---------------+
| ADRs |
| (Decisions) |
+---------------+
|
9. Present
to Client
|
v
+--------+ 10. Review +---------------+
| Client |<------------------| Approval |
+--------+ | Request |
| +---------------+
|
+-------------------+
| |
v v
+--------+ +--------+
|Approve | |Request |
+--------+ |Changes |
| +--------+
| |
v v
+----------+ +----------+
| Sprint | | Iterate |
| Planning | | Proposal |
+----------+ +----------+
|
+---> (Back to Step 6)
```
**Flow Description:**
1. **Trigger**: Requirements approval triggers architecture spike
2. **Context Summary**: PO summarizes client goals and constraints
3. **Requirements Handoff**: BA receives context for deep analysis
4. **Domain Analysis**: BA creates domain model and identifies technical needs
5. **Architect Involvement**: Architect agent invited to spike
6. **Collaborative Brainstorm**: PO, BA, and Architect discuss approaches
7. **Proposal Generation**: Architecture proposal document created
8. **ADR Creation**: Key decisions documented as ADRs
9. **Client Presentation**: Proposal presented with rationale
10. **Client Decision**: Approve or request changes (iterate if needed)
---
## 7. Data Requirements