From b1b59ef25d5710d238e3ec5e5ebc20327253072b Mon Sep 17 00:00:00 2001 From: William Valentin Date: Mon, 23 Feb 2026 18:49:44 -0800 Subject: [PATCH] docs(agents): require diagram review on every code change --- AGENTS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index a44d660..456da7f 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -11,7 +11,7 @@ - **Branch + merge workflow:** Do work on a feature branch (`git switch -c feature/`). Keep branches rebased onto `main` (avoid merge commits). When finished: `git rebase main`, then fast-forward merge back to main: `git switch main && git merge --ff-only feature/`, then delete the merged feature branch: `git branch -d feature/`. - **Update state.json:** After every feature implementation, modification, or significant change, update `docs/plans/state.json` accordingly — add new phases/entries, update test counts, adjust the `overall_progress` section, and update the `feature_gap_scorecard` if the gap analysis is affected. Commit state.json alongside the feature change, not as a separate afterthought. - **Keep docs + diagrams current:** When behavior, config keys, APIs, or architecture changes, update the relevant docs in the same change (README + `docs/`). If the change affects a documented flow, also update the corresponding Mermaid diagrams (e.g. `docs/architecture/AGENT_DIAGRAM.md`, `docs/architecture/GATEWAY_SESSIONS_AND_QUEUE.md`, `docs/api/PROTOCOL.md`) so they stay source-of-truth. -- **AI-optimized diagram updates are mandatory on flow changes:** Any change to auth/token lifecycle, model routing/fallback/retry behavior, provider execution semantics, gateway queue/session behavior, or config profile generation MUST include matching Mermaid diagram updates in the same PR. +- **AI-optimized diagram updates are mandatory on any code change:** Any code added or modified MUST include diagram review and updates in the same PR for `docs/architecture/AGENT_DIAGRAM.md`, `docs/architecture/GATEWAY_SESSIONS_AND_QUEUE.md`, and `docs/api/PROTOCOL.md` (or an explicit note in the PR/commit message explaining why no diagram change was needed). - **Track OpenClaw evolution:** Review OpenClaw updates (repo + docs + ecosystem) on a regular cadence (at least monthly, and before major Flynn planning cycles) to identify high-value assistant patterns and candidate features for Flynn. Capture actionable findings in `docs/plans/` and reflect prioritized gaps in `docs/plans/state.json`. ## Build, Lint, and Test Commands