david.delagneau/fidelity-ai-workspace
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: Update standup prompt and related documentation for clarity and improved context handling

Browse Source
This commit is contained in:
David Delagneau
2026-04-21 08:11:07 -06:00
parent f68fd4da9c
commit b264d380bc
5 changed files with 107 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
agent-memory/behavior/agent-behavior.md
View File

@@ -1,7 +1,7 @@
---
type: agent-behavior
status: active
updated: 2026-04-17
updated: 2026-04-21
tags: [process, memory, agent]
---
@@ -29,6 +29,9 @@ This applies to:
The agent should not wait for a separate promotion command when the right update is already clear.
- When editing `project-knowledge/`, write as a human engineer maintaining shared project documentation.
- Keep agent-operating logic out of `project-knowledge/`; store that logic in prompts, commands, skills, agents, or `agent-memory/`.
---
## Learning Sessions

5
agent-memory/memory/context-maintenance.md
View File

@@ -1,7 +1,7 @@
---
type: agent-memory
status: active
updated: 2026-04-17
updated: 2026-04-21
tags:
- process
- memory
@@ -18,6 +18,9 @@ Keep this workspace useful as living memory instead of a pile of disconnected no
- Update canonical context when a durable fact changes.
- Prefer correcting stale context over appending contradictory notes.
- Keep `project-knowledge/` human-facing and project-facing: write it as an engineer maintaining shared project notes, not as an AI maintaining its own operating instructions.
- Do not place agent-only logic, output contracts, prompting tactics, evaluation heuristics, or command-behavior rules in `project-knowledge/` unless a human engineer on the project would reasonably want that exact guidance there.
- Put agent behavior, prompt logic, formatting contracts, and slash-command rules in `agent-memory/`, `.opencode/commands/`, `prompts/`, `.opencode/agents/`, or `.opencode/skills/` instead of `project-knowledge/`.
- If a canonical note appears in an Obsidian Base, update its frontmatter properties together with the prose content.
- When changing frontmatter properties on existing canonical notes, prefer Obsidian CLI property operations through `scripts/obsidian/cli.sh` when available so YAML spacing and property formatting stay clean; fall back to direct Markdown edits only when the CLI is unavailable or the operation is unsupported.
- Keep templates under `project-knowledge/09-templates/` out of real-note Bases by filtering the template folder.