Files
fegger bf8191b013 Planung und Skills für den Wissensbasis-RAG-Agenten
planung.md: Architektur (schlanker RAG-Service, SQLite-Index, Hybrid-Retrieval),
verbindliche Grounding-Regeln, Modell-Bake-off M3 (qwen3.8:27b, qwen3:32b,
gemma3:27b, mistral-small3.2:24b, qwen3:14b als Latenz-Untergrenze),
Meilensteine M1-M4 und Odoo-Integrationsoptionen.

.agents: neuer Skill pv-rag-agent (verbindliche Regeln für die Implementierung)
sowie bestehende Projekt-Skills (agent-memory, wissensbasis,
odoo19-development, opendataloader-pdf).
2026-09-14 16:34:13 +02:00

1.8 KiB

name, description, disable-model-invocation
name description disable-model-invocation
agent-memory Persistent handoff memory for multi-session agent work on the odoo-at-payroll project. Read this skill at the start of every new agent conversation so the current thread can bootstrap context from the repository rather than from chat history. false

Always read at the start of a new conversation

  1. AGENTS.md — mandatory project workflow.
  2. This skill (agent-memory/SKILL.md).
  3. .agents/MEMORY.md — current handoff log.
  4. All other skills applicable to the task (see AGENTS.md skill selection).

Purpose

Zed agent threads do not share conversation history. This project therefore keeps the shared state in the repository itself:

  • .agents/MEMORY.md — rolling handoff log: current focus, completed work, open blockers, decisions, files that matter.
  • <domain>/RUNBOOK.md — operational memory for recurring workflows (imports, validation, deployment).

Both files are ordinary markdown under git, so their history is preserved.

After significant work

Update .agents/MEMORY.md:

  • Current focus: one-line summary of what the thread was working on.
  • Completed: concrete outcomes, file paths, commits.
  • Open issues / blockers: anything unresolved at the end of the thread.
  • Decisions & conventions: choices that future threads must respect.
  • Files that matter right now: paths the next thread should read first.

Update a domain RUNBOOK.md when the task reveals a reusable observation:

  • non-obvious mappings or workarounds;
  • validation steps that caught errors;
  • commands or snippets that should be reused.

When starting a new thread

Paste a brief handoff if helpful, but do not rely on it. Always verify the actual current state from the memory files, git log, and the relevant code.