Public Access
24 lines
1.3 KiB
Markdown
24 lines
1.3 KiB
Markdown
## MODIFIED Requirements
|
|
### Requirement: Meeting Assistant generates meeting outputs
|
|
Meeting Assistant SHALL generate a summary, decisions, and next steps from the meeting transcript, metadata, user notes, and assistant-discovered context.
|
|
|
|
All summary-agent read tools that return file-like content SHALL support reading the whole file, reading a clamped inclusive 1-based line range when `from` and `to` are supplied, or reading the last `tail` lines when `tail` is supplied without a line range.
|
|
|
|
The `write_summary` tool SHALL return the written summary filename after writing the summary note.
|
|
|
|
The summary-agent `search` tool SHALL support an optional glob file pattern that limits searched project files.
|
|
|
|
#### Scenario: Summary read tools support tail
|
|
- **WHEN** the summary agent reads a transcript with `tail` set to `2`
|
|
- **THEN** Meeting Assistant returns the last two transcript lines
|
|
|
|
#### Scenario: Summary write returns filename
|
|
- **WHEN** the summary agent writes the current meeting summary
|
|
- **THEN** Meeting Assistant returns the written summary filename
|
|
|
|
#### Scenario: Summary search is limited by file pattern
|
|
- **GIVEN** a bound project has `PROJECT.md` and `scratch.txt`
|
|
- **WHEN** the summary agent searches with file pattern `*.md`
|
|
- **THEN** Meeting Assistant searches `PROJECT.md`
|
|
- **AND** excludes `scratch.txt`
|