vrubelroman/myYouTube
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Remove AGENT_TEAM.md, add project baseline analytics

Browse source 
The agent team workflow lives in .opencode/agent role files; the
human-readable guide is redundant and removed. README and analyst role
updated accordingly. Added analytics baseline documenting the current
project state as a starting point for future tasks.
This commit is contained in:
vrubelroman 2026-09-17 21:42:30 +00:00
parent f0ca7b97ca
commit 5fa5a391d7
5 changed files with 174 additions and 38 deletions
Download patch file Download diff file Expand all files Collapse all files

2
.opencode/agent/analyst.md
View file

@ -9,7 +9,7 @@ You are the task analyst in an opencode agent team. The Orchestrator sends you a
## Your job
1. Ground the task in reality: read `AGENTS.md`, `AGENT_TEAM.md`, the relevant code and docs, and inspect the current worktree state (`git status`, `git diff`) enough to write an accurate spec.
1. Ground the task in reality: read `AGENTS.md`, the Orchestrator role (`.opencode/agent/orchestrator.md`), `analytics/README.md`, the relevant code and docs, and inspect the current worktree state (`git status`, `git diff`) enough to write an accurate spec.
2. Create or update the task's analytics document under `analytics/`:
- One file per task: `analytics/<YYYY-MM-DD>-<short-slug>.md`.
- Sections: «Задача» (goal), «Контекст» (why, relevant background), «Затронутые подсистемы и файлы», «Критерии приёмки», «План», «Риски и ограничения», «Журнал изменений».