meeting-assistant/openspec/changes/archive/2026-06-02-generalize-settings-and-logs-agent/specs/meeting-summary/spec.md

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.

The settings/logs agent SHALL be able to list recent meeting summary notes from the configured summaries folder ordered newest first by meeting start time, falling back to file modification time when summary frontmatter has no parseable start time.

The settings/logs agent SHALL be able to read and search meeting summaries, transcripts, meeting notes, and assistant context files from their configured vault folders so it can help post-process notes for the user.

The settings/logs agent SHALL be able to create and update meeting summaries, transcripts, meeting notes, and assistant context files inside their configured vault folders.

The settings/logs agent SHALL provide frontmatter-specific write tools for meeting summaries, transcripts, meeting notes, and assistant context files that replace YAML frontmatter while preserving the markdown body.

Settings/logs meeting artifact read tools 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.

Settings/logs meeting artifact search tools SHALL support an optional glob file pattern that limits searched markdown 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

Scenario: Settings/logs agent lists and reads recent meeting artifacts

• GIVEN the configured summary folder contains multiple summary notes with start times
• WHEN the settings/logs agent lists recent summaries
• THEN Meeting Assistant returns the summary notes newest first
• AND includes relative paths for the linked meeting note, transcript, and assistant context when those links resolve to configured artifact folders
• WHEN the settings/logs agent reads one of those artifact paths with tail
• THEN Meeting Assistant returns only the requested last lines

Scenario: Settings/logs agent searches meeting artifacts

• GIVEN meeting summaries, transcripts, notes, and assistant context files contain searchable text
• WHEN the settings/logs agent searches the relevant artifact class
• THEN Meeting Assistant returns relative path:line matches from that configured artifact folder
• AND refuses read paths that escape their configured artifact folder

Scenario: Settings/logs agent repairs meeting artifact files

• GIVEN an existing meeting note with YAML frontmatter and a markdown body
• WHEN the settings/logs agent writes replacement frontmatter for that note
• THEN Meeting Assistant validates the supplied frontmatter YAML
• AND replaces only the frontmatter while preserving the body
• WHEN the settings/logs agent writes a summary, transcript, meeting note, or assistant context path outside the configured folder
• THEN Meeting Assistant refuses the write