Public Access
Add project sync guidance for corrected notes
PR and Push Build/Test / build-and-test (push) Failing after 9m54s
PR and Push Build/Test / build-and-test (push) Failing after 9m54s
This commit is contained in:
@@ -0,0 +1,14 @@
|
||||
## Why
|
||||
|
||||
Meeting notes are often corrected after the original summary run. When a corrected note is tied to project knowledge, the settings/logs assistant should carry those corrections through to the affected project files instead of leaving project knowledge stale.
|
||||
|
||||
## What Changes
|
||||
|
||||
- Add settings/logs assistant instructions for post-correction project synchronization.
|
||||
- Require the assistant to follow a referenced project's `AGENTS.md` when present.
|
||||
- Require the assistant to use judgment when no project instructions exist, with broader review for newly added project references and targeted review for corrections to existing references.
|
||||
|
||||
## Impact
|
||||
|
||||
- Affects the built-in settings/logs assistant prompt.
|
||||
- No new tool surface is required; the assistant already has meeting artifact and project read/write tools.
|
||||
@@ -0,0 +1,18 @@
|
||||
## MODIFIED Requirements
|
||||
### Requirement: Meeting Assistant generates meeting outputs
|
||||
The settings/logs agent SHALL instruct meeting-note correction workflows to keep project knowledge consistent when the corrected meeting note has project references.
|
||||
|
||||
When a corrected meeting note adds a new project reference, the settings/logs agent SHALL inspect the corrected note broadly enough to find project-relevant information that should be written to that project.
|
||||
|
||||
When a corrected meeting note changes specific content for an existing project reference, the settings/logs agent SHALL check whether corresponding project knowledge needs the same correction.
|
||||
|
||||
For each affected project, when an `AGENTS.md` file exists directly in the project folder, the settings/logs agent SHALL follow those project instructions before updating the project. When no project `AGENTS.md` exists, the settings/logs agent SHALL use judgment to decide what project file updates are warranted by the note correction.
|
||||
|
||||
#### Scenario: Settings/logs agent syncs corrected meeting notes to projects
|
||||
- **GIVEN** the settings/logs agent corrects a meeting note with project references
|
||||
- **WHEN** a referenced project has an `AGENTS.md`
|
||||
- **THEN** the settings/logs instructions tell the agent to follow that project's instructions before updating the project
|
||||
- **WHEN** a corrected note adds a new project reference
|
||||
- **THEN** the instructions tell the agent to review the corrected note for project-relevant information to add to that project
|
||||
- **WHEN** a corrected note changes specific information for an existing project reference
|
||||
- **THEN** the instructions tell the agent to check whether project knowledge needs a matching correction
|
||||
@@ -0,0 +1,4 @@
|
||||
- [x] 1. Add OpenSpec scenario for syncing project knowledge after corrected meeting notes.
|
||||
- [x] 2. Add a focused instruction-builder test for the new settings/logs guidance.
|
||||
- [x] 3. Update the built-in settings/logs assistant instructions.
|
||||
- [x] 4. Run focused tests and `openspec validate sync-projects-after-note-corrections --strict`.
|
||||
Reference in New Issue
Block a user