Public Access
Implement meeting assistant v1
This commit is contained in:
@@ -0,0 +1,24 @@
|
||||
# project-knowledge Specification
|
||||
|
||||
## Purpose
|
||||
TBD - created by archiving change define-meeting-assistant-v1. Update Purpose after archive.
|
||||
## Requirements
|
||||
### Requirement: Meeting Assistant maintains project knowledge
|
||||
Meeting Assistant SHALL maintain project knowledge based on meeting content and future generic information sources.
|
||||
|
||||
Project knowledge SHALL support retrieval by project context and relevant keywords.
|
||||
|
||||
Project knowledge SHALL be stored under the configured projects folder, where each direct subfolder is a project identified by its folder name.
|
||||
|
||||
#### Scenario: Meeting has project context
|
||||
- **WHEN** a meeting note identifies a project
|
||||
- **THEN** Meeting Assistant can associate transcript-derived and summary-derived knowledge with that project
|
||||
|
||||
#### Scenario: Meeting binds project folders
|
||||
- **WHEN** the meeting note `projects` frontmatter lists configured project subfolder names
|
||||
- **THEN** Meeting Assistant treats those subfolders as the projects available to meeting agents
|
||||
|
||||
#### Scenario: Agent retrieves project context
|
||||
- **WHEN** an agent needs context for a meeting or follow-up task
|
||||
- **THEN** Meeting Assistant can retrieve relevant project knowledge and source references
|
||||
|
||||
Reference in New Issue
Block a user