Implement self-contained runtime: install runtime tree, git-root memory, canonical agent paths, + 4 suites
- install.sh: install runtime tree under OPENCODE_DEV_AGENT_TEAM (bin/, 12 skills, improvements/, install-manifest.json), idempotent shell-rc export, --uninstall (preserves improvements/ user data) and --migrate; preserves 13-agent copy, .backup retention, KEEP_BACKUPS=5, count gate, cmp -s integrity, install-time permission gate - memory-lifecycle.sh: resolve MEMORY_DIR from project git root + OPENCODE_MEMORY_DIR - all 13 agents: canonical runtime sentence + env-resolved runtime paths; project-scoped refs unchanged - tests: new test-install (15), test-runtime (10), test-path-resolution (12), test-memory-isolation (12); TEAM_ROOT override on existing 4 suites; test-all.sh registers 8 suites (100 checks total)
This commit is contained in:
+8
-6
@@ -49,7 +49,7 @@ UNDERSTAND AUDIENCE → ASSESS EXISTING DOCS → PLAN STRUCTURE → WRITE → VA
|
||||
## Repository Intelligence
|
||||
|
||||
This repository may have a `.opencode/` knowledge layer generated by
|
||||
`repo-bootstrap.sh`. Before writing, read `.opencode/AGENTS.md` and
|
||||
`"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/repo-bootstrap.sh`. Before writing, read `.opencode/AGENTS.md` and
|
||||
`.opencode/skills/conventions/SKILL.md`. Treat this knowledge as context —
|
||||
verify it against the actual repository when it contradicts what you observe.
|
||||
|
||||
@@ -82,16 +82,18 @@ Your primary evidence is the source material: the reports and files consulted, w
|
||||
|
||||
Stop when your deliverable is complete and verified per your Completion Rule; escalate when the evidence needed for accuracy is missing.
|
||||
|
||||
Global runtime: always resolve via `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"`. Runtime-owned artifacts live under `bin/` (scripts), `skills/` (12 skills), `improvements/`. Project-scoped artifacts (`memory/`, `.opencode/`, `./AgentsReport/`) stay relative to this project.
|
||||
|
||||
## Memory & Skills Awareness
|
||||
|
||||
Before writing, check project memory for relevant context:
|
||||
- `scripts/memory-lifecycle.sh recall decisions <keywords>` — for architectural decisions to document
|
||||
- `scripts/memory-lifecycle.sh recall lessons <keywords>` — for proven documentation patterns
|
||||
- `scripts/memory-lifecycle.sh recall architecture <keywords>` — for system structure to describe
|
||||
- `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh recall decisions <keywords>` — for architectural decisions to document
|
||||
- `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh recall lessons <keywords>` — for proven documentation patterns
|
||||
- `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh recall architecture <keywords>` — for system structure to describe
|
||||
|
||||
After completing documentation, store durable findings:
|
||||
- Architecture documented → `scripts/memory-lifecycle.sh store architecture <file>`
|
||||
- Documentation lesson learned → `scripts/memory-lifecycle.sh store lessons <file>`
|
||||
- Architecture documented → `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh store architecture <file>`
|
||||
- Documentation lesson learned → `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh store lessons <file>`
|
||||
|
||||
Load relevant skills when your brief includes a skill path.
|
||||
Do NOT re-derive documentation patterns already documented in skills.
|
||||
|
||||
Reference in New Issue
Block a user