-
Notifications
You must be signed in to change notification settings - Fork 1
feat: implement meeting scheduler and event-triggered meetings #264
Copy link
Copy link
Closed
Labels
prio:mediumShould do, but not blockingShould do, but not blockingscope:medium1-3 days of work1-3 days of workspec:agent-systemDESIGN_SPEC Section 3 - Agent SystemDESIGN_SPEC Section 3 - Agent Systemspec:communicationDESIGN_SPEC Section 5 - Communication ArchitectureDESIGN_SPEC Section 5 - Communication Architecturespec:human-interactionDESIGN_SPEC Section 13 - Human Interaction LayerDESIGN_SPEC Section 13 - Human Interaction Layertype:featNew feature implementationNew feature implementation
Metadata
Metadata
Assignees
Labels
prio:mediumShould do, but not blockingShould do, but not blockingscope:medium1-3 days of work1-3 days of workspec:agent-systemDESIGN_SPEC Section 3 - Agent SystemDESIGN_SPEC Section 3 - Agent Systemspec:communicationDESIGN_SPEC Section 5 - Communication ArchitectureDESIGN_SPEC Section 5 - Communication Architecturespec:human-interactionDESIGN_SPEC Section 13 - Human Interaction LayerDESIGN_SPEC Section 13 - Human Interaction Layertype:featNew feature implementationNew feature implementation
Summary
Meeting config models support
frequency(e.g. per_sprint_day, bi_weekly) andtrigger(e.g. on_pr) fields onMeetingTypeConfig, and the meeting protocols/orchestrator exist, but there is no scheduler that actually triggers meetings at configured intervals or in response to events.Design Spec Reference
Scope
MeetingsConfigfrequency(e.g. daily standup, bi-weekly sprint planning)trigger(e.g. on_pr → code review meeting)MeetingOrchestratorfor actual meeting execution