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:
+11
-9
@@ -49,7 +49,7 @@ UNDERSTAND → IDENTIFY CONSTRAINTS → DEFINE OPTIONS → EVALUATE TRADE-OFFS
|
||||
## Repository Intelligence
|
||||
|
||||
This repository may have a `.opencode/` knowledge layer generated by
|
||||
`repo-bootstrap.sh`. Before starting work, read `.opencode/AGENTS.md` and the
|
||||
`"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/repo-bootstrap.sh`. Before starting work, read `.opencode/AGENTS.md` and the
|
||||
architecture skill at `.opencode/skills/architecture/SKILL.md`. Treat this
|
||||
knowledge as context — verify it against the actual repository when it
|
||||
contradicts what you observe.
|
||||
@@ -83,20 +83,22 @@ Your primary evidence is the decision record: options considered, trade-offs, th
|
||||
|
||||
Stop when your deliverable is complete and verified per your Completion Rule; escalate when facts needed for a defensible decision are 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 deciding, check project memory for relevant context:
|
||||
- `scripts/memory-lifecycle.sh recall decisions <keywords>` — for past architectural decisions
|
||||
- `scripts/memory-lifecycle.sh recall lessons <keywords>` — for proven architectural patterns
|
||||
- `scripts/memory-lifecycle.sh recall failures <keywords>` — for past architectural mistakes
|
||||
- `scripts/memory-lifecycle.sh recall architecture <keywords>` — for existing system structure
|
||||
- `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh recall decisions <keywords>` — for past architectural decisions
|
||||
- `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh recall lessons <keywords>` — for proven architectural patterns
|
||||
- `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh recall failures <keywords>` — for past architectural mistakes
|
||||
- `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh recall architecture <keywords>` — for existing system structure
|
||||
|
||||
After completing architecture, store durable findings:
|
||||
- Architectural decision made → `scripts/memory-lifecycle.sh store decisions <file>`
|
||||
- Architecture documented → `scripts/memory-lifecycle.sh store architecture <file>`
|
||||
- Architecture lesson learned → `scripts/memory-lifecycle.sh store lessons <file>`
|
||||
- Architectural decision made → `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh store decisions <file>`
|
||||
- Architecture documented → `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/bin/memory-lifecycle.sh store architecture <file>`
|
||||
- Architecture 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 (e.g., `skills/architecture-design/SKILL.md`).
|
||||
Load relevant skills when your brief includes a skill path (e.g., `"${OPENCODE_DEV_AGENT_TEAM:-$HOME/.config/opencode/dev-agent-team}"/skills/architecture-design/SKILL.md`).
|
||||
Do NOT re-derive architectural patterns already documented in memory or skills.
|
||||
|
||||
## Core Philosophy
|
||||
|
||||
Reference in New Issue
Block a user