chore: align opencode memory docs with .memory project

This commit is contained in:
alex
2026-03-11 11:08:39 +00:00
parent ffd0d31fa5
commit f7a1aac68b
12 changed files with 40 additions and 142 deletions

View File

@@ -379,4 +379,4 @@ This is a ~30-second mental check, not a full review. If something looks obvious
- For every completed project change set, documentation must be created or updated.
- Minimum required documentation coverage: `README` + relevant `docs/*` files + `AGENTS.md` when project conventions, commands, architecture, workflow, policies, or agent behavior changes.
- **Documentation is a completion gate, not a follow-up task.** Do not declare a task done, ask "what's next?", or proceed to commit until doc coverage is handled or explicitly deferred by the user. Waiting for the user to ask is a failure.
- **Always delegate to `librarian`** for documentation coverage checks and cross-tool instruction file maintenance. The librarian is the specialist — do not skip it or handle docs inline when the librarian can be dispatched.
- **Always delegate to `librarian`** for documentation coverage checks and `AGENTS.md` maintenance. The librarian is the specialist — do not skip it or handle docs inline when the librarian can be dispatched.

View File

@@ -15,7 +15,7 @@ You are the Librarian subagent.
Purpose:
- Ensure project documentation and knowledge artifacts are created, updated, and accurate.
- Maintain the instruction file (`AGENTS.md`) and its symlinks.
- Maintain the instruction file (`AGENTS.md`) as the single source of truth.
- Keep basic-memory guidance and project notes accurate and useful as the project evolves.
- Ensure all memory references use the `main` vs per-repo project split correctly.
@@ -35,7 +35,7 @@ Maintain `AGENTS.md` as the single source of truth:
- **Update when project knowledge changes**: architecture, conventions, commands, structure
- **Content should include**: project purpose, tech stack, architecture, conventions, build/test/lint commands, project structure
- **Verify symlinks exist**: `CLAUDE.md`, `.cursorrules`, `.github/copilot-instructions.md` should all point to `AGENTS.md`
- **Keep guidance centralized**: repo instruction guidance belongs in `AGENTS.md` only
- **Do NOT duplicate memory project contents** — instruction file is for "how to work here", not "what we're doing"
- **Ensure the repo's basic-memory project name is documented** in `AGENTS.md` (e.g., `opencode-config`)
@@ -63,4 +63,4 @@ Ensure memory guidance consistently reflects the `main` vs per-repo project spli
- Summarize documentation changes first.
- List updated files and why each was changed.
- Explicitly call out any deferred documentation debt.
- Confirm instruction file symlinks are correct (or note if they're missing).
- Confirm repo instruction guidance lives in `AGENTS.md` only.