Public Access
52 lines
2.5 KiB
Markdown
52 lines
2.5 KiB
Markdown
## MODIFIED Requirements
|
|
### Requirement: Agents can use project context tools
|
|
Meeting Assistant SHALL expose tools that allow agents to look up project information, retrieve keyword-relevant context, and inspect meeting-derived knowledge.
|
|
|
|
Project tools SHALL treat each direct subfolder of the configured projects folder as one project. A meeting note binds projects by listing those subfolder names in the `projects` frontmatter field.
|
|
|
|
The summary agent SHALL expose these project tools:
|
|
|
|
- `list_projects`
|
|
- `list_projectfiles`
|
|
- `read_projectfile`
|
|
- `write_projectfile`
|
|
- `list_past_project_meetings`
|
|
- `read_past_project_meeting_summary`
|
|
- `search`
|
|
|
|
The settings/logs agent SHALL expose project tools that operate across all existing project folders under the configured projects folder:
|
|
|
|
- `list_projects`
|
|
- `list_projectfiles`
|
|
- `read_projectfile`
|
|
- `write_projectfile`
|
|
- `search_projects`
|
|
- `create_project`
|
|
|
|
The settings/logs `create_project` tool SHALL create one new direct project subfolder by project name.
|
|
|
|
The settings/logs `create_project` tool SHALL support a recommended seed that writes `AGENTS.md` from the bundled `Project-AGENTS.md` content file and creates starter `PROJECT.md`, `JOURNAL.md`, and `DECISIONS.md` files.
|
|
|
|
The settings/logs `create_project` tool SHALL support writing caller-supplied `AGENTS.md` content directly instead of the recommended seed.
|
|
|
|
The settings/logs project read/write/search tools SHALL refuse project names that do not already exist, except for `create_project`.
|
|
|
|
The `search` and `search_projects` tools SHALL support an optional glob file pattern that limits searched project files.
|
|
|
|
#### Scenario: Settings/logs agent creates a recommended project
|
|
- **WHEN** the settings/logs agent creates project `Alpha` with the recommended seed
|
|
- **THEN** Meeting Assistant creates the `Alpha` project folder
|
|
- **AND** writes `AGENTS.md` from the bundled `Project-AGENTS.md`
|
|
- **AND** writes starter `PROJECT.md`, `JOURNAL.md`, and `DECISIONS.md` files
|
|
|
|
#### Scenario: Settings/logs agent writes direct project instructions
|
|
- **WHEN** the settings/logs agent creates project `Beta` with direct `AGENTS.md` content
|
|
- **THEN** Meeting Assistant creates the `Beta` project folder
|
|
- **AND** writes that content to `AGENTS.md`
|
|
|
|
#### Scenario: Settings/logs agent searches existing projects by file glob
|
|
- **GIVEN** existing projects contain markdown and non-markdown files
|
|
- **WHEN** the settings/logs agent searches projects with file pattern `*.md`
|
|
- **THEN** Meeting Assistant returns matches from matching markdown files
|
|
- **AND** excludes non-matching files
|