Add project-knowledge structure and templates

- Introduced new maps for navigating project knowledge, including "Current Work," "Fidelity Domain," "Fidelity Apps," "Work Items," and "People."
- Created base files for daily notes, decisions, people, systems, work items, and workstreams with defined properties and views.
- Developed templates for daily notes, decisions, meeting notes, persons, systems, work items, and workstreams to standardize documentation.
- Updated scripts and prompts to reflect the new project-knowledge directory structure.
- Removed outdated onboarding and start-here documents, consolidating relevant information into the new maps.
- Ensured all references in workflows and scripts point to the new project-knowledge paths.
This commit is contained in:
2026-04-17 15:52:08 -06:00
parent 11fdb17fcb
commit dbc1894e27
175 changed files with 1163 additions and 914 deletions

View File

@@ -0,0 +1,35 @@
---
type: agent-behavior
status: active
updated: 2026-04-17
tags:
- agent
- self-maintenance
---
# Agent Self-Maintenance
The agent must keep the workspace behavior aligned with recurring user corrections.
---
## Rules
- If a correction changes future output, update the file that controls that output.
- Update `.opencode/commands/` for slash-command behavior.
- Update `prompts/` for reusable drafting shape.
- Update `.opencode/agents/` and `AGENTS.md` for default agent behavior.
- Update `.opencode/skills/` for specialized workflows.
- Update `agent-memory/` for reusable agent operating rules.
- Update `project-knowledge/` only when the correction changes project knowledge or project-facing process documentation.
---
## Do Not Store As Project Knowledge
- Sync failures.
- Tool dependency errors.
- Agent implementation chatter.
- Generic preference notes that only affect agent behavior.
- Duplicate summaries of already-correct project facts.