Public Access
30 lines
1.7 KiB
Markdown
30 lines
1.7 KiB
Markdown
## Why
|
|
|
|
Meeting Assistant should provide a meeting capture workflow that is not tied to a specific online meeting provider. The first version needs to establish the platform-independent core: meeting notes, metadata capture, transcription with speaker attribution, generated summaries and next steps, and a project knowledge base that agents can use for later retrieval and controlled project work.
|
|
|
|
## What Changes
|
|
|
|
- Create Meeting Assistant as a .NET 10 server application in `Manuel/meeting-assistant`.
|
|
- Establish OpenSpec as the source of truth for behavior changes.
|
|
- Define the version 1 meeting flow around Obsidian markdown notes created before transcription starts.
|
|
- Require the core flow to support in-person meetings and not depend on Teams, Zoom, or similar APIs.
|
|
- Add requirements for speaker-attributed transcription, summaries, decisions, and next steps.
|
|
- Define project context capture and retrieval as first-class capabilities.
|
|
- Define a guarded agent tool model for project lookup and controlled project file changes.
|
|
|
|
## Capabilities
|
|
|
|
### New Capabilities
|
|
|
|
- `meeting-session`: creation and lifecycle of meeting notes and metadata.
|
|
- `meeting-transcription`: platform-independent transcription with speaker attribution.
|
|
- `meeting-summary`: generated summaries, decisions, and next steps.
|
|
- `project-knowledge`: project context, retrieval, and knowledge base updates from meetings.
|
|
- `agent-project-tools`: agent tools for lookup, retrieval, and controlled project file updates.
|
|
|
|
## Impact
|
|
|
|
- New .NET 10 solution, service project, tests, README, and OpenSpec structure.
|
|
- Version 1 behavior is documented before feature implementation.
|
|
- Future platform integrations remain optional augmentations instead of hard dependencies.
|