# nodes

id: opencode-multi-agent-orchestration-config
name: OpenCode Multi-Agent Orchestration Config
kind: config
file_refs: ["/home/alex/.config/opencode/opencode.jsonc"]
created_at: 2026-03-06 10:54:11
updated_at: 2026-03-06 15:41:31
summary:
Global OpenCode config uses github-copilot models with `default_agent=lead`, built-in `build/general/explore` disabled, global `websearch` and `question` permissions, and MCP servers (`context7`, `gh_grep`, `playwright`, `megamemory`). The `agent` section now also includes explicit model overrides for `critic` (`github-copilot/claude-opus-4.6`), `sme` (`github-copilot/claude-opus-4.6`), and `designer` (`github-copilot/claude-sonnet-4.6`) for discoverability alongside frontmatter-defined behavior.

why:
Establish a provider-optimized orchestration baseline and replace default primary flow with a dedicated lead agent.


id: lead-and-subagent-role-prompts
name: Lead and Subagent Role Prompts
kind: pattern
file_refs: ["/home/alex/.config/opencode/AGENTS.md"]
created_at: 2026-03-06 10:54:11
updated_at: 2026-03-06 15:41:31
summary:
`AGENTS.md` now explicitly documents swarm-inspired operating policies: agent roster with 10 roles/models, phased workflow (`CLARIFY → DISCOVER → CONSULT → PLAN → CRITIC-GATE → EXECUTE → PHASE-WRAP`), mandatory quality pipeline (`coder → reviewer:correctness → reviewer:security when triggered → tester:standard → tester:adversarial → megamemory verdict`), escalation discipline tiers, SME consultation caching pattern, and megamemory-as-state conventions; existing guidance on delegation, parallelization, Playwright UI validation, worktrees, docs, commits, and GitHub flow remains intact.

why:
Create explicit role boundaries and safe delegation behavior while preserving clarification-first execution.


id: workflow-slash-commands-for-agent-routing
name: Workflow Slash Commands for Agent Routing
kind: feature
created_at: 2026-03-06 10:54:11
updated_at: 2026-03-06 15:41:31
summary:
Command set includes `/research`, `/review`, `/test`, `/status`, `/docs`, `/init`, plus new `/plan` and `/sme` workflows. `/plan` drives phased planning (`CLARIFY → DISCOVER → CONSULT → PLAN → CRITIC-GATE`) with megamemory phase recording, and `/sme` enforces cache-first SME consultation via megamemory before delegating to the `sme` agent and linking guidance to active plans.

why:
Provide repeatable operator workflows and make cross-session status/research/review/testing invocations fast and consistent.

file_refs:
["/home/alex/.config/opencode/commands/research.md","/home/alex/.config/opencode/commands/review.md","/home/alex/.config/opencode/commands/test.md","/home/alex/.config/opencode/commands/status.md","/home/alex/.config/opencode/commands/docs.md","/home/alex/.config/opencode/commands/init.md","/home/alex/.config/opencode/commands/plan.md","/home/alex/.config/opencode/commands/sme.md"]


id: automatic-git-commit-workflow-policy
name: Automatic Git Commit Workflow Policy
kind: decision
file_refs: ["/home/alex/.config/opencode/AGENTS.md"]
created_by_task: Update workflow so that changes are committed automatically when working in a git repo.
created_at: 2026-03-06 13:21:05
updated_at: 2026-03-06 13:21:05
summary:
Updated `/home/alex/.config/opencode/AGENTS.md` by adding `## Git Commit Workflow` rules: in git repositories, automatically create one commit per completed user-requested change set; use Conventional Commit prefixes (`feat:`, `fix:`, `chore:` etc.) with concise reason-focused summaries; and require explicit user confirmation before committing potentially sensitive files such as `.env`, key files, or credentials.

why:
Align runtime workflow with the user-requested default of automatic commits while preserving safety for secrets and consistent commit message style.


id: librarian-documentation-subagent
name: Librarian Documentation Subagent
kind: component
file_refs: ["/home/alex/.config/opencode/agents/librarian.md"]
created_by_task: Add librarian subagent and enforce documentation updates in workflow.
created_at: 2026-03-06 13:26:12
updated_at: 2026-03-06 13:26:12
summary:
Added `agents/librarian.md` as a documentation-focused subagent (mode `subagent`, model `github-copilot/claude-sonnet-4.6`, temperature 0.2) with denied `bash`, `webfetch`, and `websearch`. Responsibilities: query megamemory before docs work, review/update `README`, relevant `docs/*`, and `AGENTS.md` for workflow/policy/agent changes, ask clarifications via `question` when ambiguous, and record outcomes/deferred doc debt in megamemory.

why:
User requested mandatory documentation updates per project change set and suggested a dedicated librarian role.


id: init-command-new-project-bootstrap
name: /init Command — Adaptive Project Initialize/Update
kind: feature
file_refs: ["/home/alex/.config/opencode/commands/init.md"]
created_by_task: Add /init command for starting a new project
created_at: 2026-03-06 13:33:16
updated_at: 2026-03-06 14:06:36
summary:
Slash command at `commands/init.md` supports both new and existing projects via a 6-step flow: (1) delegate to `explorer` to classify project state and detect artifacts; (2) one adaptive clarification round — now includes handling for low-confidence classification itself; (3) delegate scaffold to `coder` with explicit mode — scaffold targets now explicitly include `.gitignore` with mandatory `.megamemory/` entry, and `AGENTS.md` instructions clarify to only add project-specific details (not duplicate global policies); existing-project mode also ensures `.megamemory/` is appended to existing `.gitignore`; (4) always delegate doc review to `librarian`; (5) always initialize/update megamemory — linking instruction now handles brand-new knowledge graphs gracefully (skip if no related concepts); (6) git handling now delegated to `coder` (not Lead, which lacks bash), with `.megamemory/` gitignore enforcement before any commit.

why:
User requested a /init command to standardize and automate new project bootstrapping, ensuring docs and knowledge graph are initialized from day one.


id: critic-plan-gate-subagent
name: Critic Plan-Gate Subagent
kind: component
file_refs: ["/home/alex/.config/opencode/agents/critic.md"]
created_by_task: Create critic.md, sme.md, and designer.md agent definitions for swarm-inspired upgrade
created_at: 2026-03-06 15:39:07
updated_at: 2026-03-06 15:39:07
summary:
Added `agents/critic.md` as a read-only plan-review subagent with model `github-copilot/claude-opus-4.6` (temperature 0.2). It defines two roles: CRITIC-GATE pre-implementation verdicts (`APPROVED|REPHRASE|UNNECESSARY|RESOLVE`) and Tier-2 escalation sounding board checks before user interruption. Workflow enforces `megamemory:understand` → read-only evidence review (`read/glob/grep`) → structured verdict output, and requires recording CRITIC-GATE verdicts back to megamemory as `decision` concepts with rationale and `file_refs`.

why:
User requested swarm-inspired implementation gating with a model-diverse, read-only critic to catch blind spots before coding.


id: sme-domain-consultant-subagent
name: SME Domain Consultant Subagent
kind: component
file_refs: ["/home/alex/.config/opencode/agents/sme.md"]
created_by_task: Create critic.md, sme.md, and designer.md agent definitions for swarm-inspired upgrade
created_at: 2026-03-06 15:39:07
updated_at: 2026-03-06 15:39:07
summary:
Added `agents/sme.md` as a read-only domain expert subagent with model `github-copilot/claude-opus-4.6` (temperature 0.3). It allows `read/glob/grep/webfetch/websearch/codesearch` plus megamemory tools, and enforces a critical caching workflow: check `decision` guidance via `megamemory:understand` first, return cached guidance when present, otherwise research and always persist new guidance as a `decision` concept tagged by domain (for example `SME:security`, `SME:postgres`) with `why: "SME consultation: <domain>"`.

why:
User requested persistent, cross-session SME consultation that avoids repeated research by caching domain guidance in megamemory.


id: designer-uiux-specialist-subagent
name: Designer UI/UX Specialist Subagent
kind: component
file_refs: ["/home/alex/.config/opencode/agents/designer.md"]
created_by_task: Create critic.md, sme.md, and designer.md agent definitions for swarm-inspired upgrade
created_at: 2026-03-06 15:39:07
updated_at: 2026-03-06 15:39:07
summary:
Added `agents/designer.md` as an opt-in, read-only UI/UX guidance subagent with model `github-copilot/claude-sonnet-4.6` (temperature 0.4). It is restricted to `read/glob/grep` and megamemory tools, with no edit/shell/web permissions. The agent is invoked only for frontend/layout/styling/UX-flow decisions and applies a structured lens: visual hierarchy, interaction patterns, WCAG-oriented accessibility basics, consistency with existing design language, and component reusability. It requires caching significant design decisions in megamemory as `decision` concepts with rationale and `file_refs`.

why:
User requested an opt-in design specialist to improve UI/UX decision quality while keeping implementation read-only and memory-backed.


id: swarm-inspired-agent-upgrade
name: Swarm-Inspired Agent Upgrade
kind: feature
created_by_task: Swarm-inspired upgrade: parallel implementation across 4 coder tasks
created_at: 2026-03-06 15:42:08
updated_at: 2026-03-07 12:59:17
summary:
Multi-agent orchestration config for OpenCode with 10 agents (lead, coder, reviewer, tester, explorer, researcher, librarian, critic, sme, designer). Key improvements applied in session: (1) Tiered quality pipeline (3 tiers: Full/Standard/Fast instead of mandatory full pipeline for everything), (2) Fast-track rule for follow-on work (skip CLARIFY/DISCOVER/CONSULT/CRITIC-GATE when context exists), (3) Implementation-first principle with 20% ceremony budget, (4) Megamemory ceremony reduction (recording discipline: only outcomes/decisions/discoveries, not phase transitions; query discipline: top_k=3), (5) DISCOVER dispatches explorer OR researcher based on need, not both by default, (6) Subagent output standards (actionable results, not recaps), (7) Coder self-check against known issues before returning, (8) Realistic testing requirements with worktree/infra-unavailable fallback guidance, (9) Researcher actionable-output-only requirement.

why:
Session analysis of ses_33c4 (Voyage project) revealed workflow consumed entire context on planning/ceremony before reaching implementation. OSRM routing feature was fully planned but never implemented. Ceremony overhead from megamemory phase-tracking, rigid full pipeline for trivial fixes, and duplicate discovery passes wasted tokens.

file_refs:
["/home/alex/.config/opencode/AGENTS.md","/home/alex/.config/opencode/agents/lead.md","/home/alex/.config/opencode/agents/critic.md","/home/alex/.config/opencode/agents/sme.md","/home/alex/.config/opencode/agents/designer.md","/home/alex/.config/opencode/agents/coder.md","/home/alex/.config/opencode/agents/reviewer.md","/home/alex/.config/opencode/agents/tester.md","/home/alex/.config/opencode/opencode.jsonc","/home/alex/.config/opencode/commands/plan.md","/home/alex/.config/opencode/commands/sme.md"]


id: agentsmd-workflow-efficiency-improvements
name: AGENTS.md Workflow Efficiency Improvements
kind: decision
created_by_task: Workflow efficiency improvement based on session ses_33c4 analysis
created_at: 2026-03-07 12:59:27
updated_at: 2026-03-08 02:33:48
summary:
Applied full 5-change upgrade package after freshness-loop integration. (A) Megamemory discipline propagated to subagents: qualified query rules (`top_k=3`, skip when no relevant roots, no re-query of just-created concepts) and explicit recording-discipline line (outcomes/discoveries/decisions only; no ceremony) added across coder/reviewer/tester/critic/explorer/researcher/sme/librarian/designer. coder.md now has explicit structural-discovery recording rule linked to active task concept and forbids started/completed-implementation ceremony records. (B) Reviewer calibration: added confidence scoring (HIGH/MEDIUM/LOW), LOW-confidence cannot be CRITICAL, severity-weighted REVIEW_SCORE rubric (CRITICAL=10, WARNING=3, SUGGESTION=0) with verdict guidance 0=APPROVED, 1-29=CHANGES-REQUESTED, >=30=REJECTED; added `REVIEW_SCORE` and optional `FRESHNESS_NOTES` output fields; added permissions hygiene fix `codesearch: deny`. (C) Tester calibration: added mutation-aware adversarial checks with `MUTATION_ESCAPES`; PARTIAL required when >50% mutation checks escape; flaky-test quarantine (`FLAKY`) excluded from pass/fail totals with PARTIAL when flaky rate >20%; defined high-impact lessons as prior CRITICAL/security/prod-regression linked lessons; expanded bash allowlist for `pnpm test*`, `pnpm run test*`, `bun test*`; output format extended with `FLAKY` and `MUTATION_ESCAPES`. (D) Lead escalation/triggers: added reviewer resolution-rate tracking (`RESOLVED|PERSISTS|DISPUTED`) with drift action when <50% across 3 cycles; Tier2->Tier1 security auto-trigger on auth/tokens/passwords/crypto/permissions/SQL/env/network; adversarial retest auto-trigger on >5 files, validation/error-handling changes, or REVIEW_SCORE>=10; quality-based stopping criteria and stricter PHASE-WRAP retro gating to avoid memory noise. (E) Consistency hooks: critic stale-memory acceptance now requires freshness metadata refs (`last_validated`, `volatility`, `review_after_days`); researcher/sme include cross-reference to lead freshness schema; explorer output contract explicitly marked required. Independent reviewer gates returned APPROVED; one score-range warning fixed by adding explicit 1-9 bracket.

why:
Session analysis revealed that rigid full-pipeline enforcement for all changes, excessive megamemory phase-tracking, duplicate explorer+researcher dispatch, and missing fast-track for follow-on work caused the workflow to spend all available context on ceremony instead of implementation. The user's OSRM routing feature was fully planned but never coded.

file_refs:
["/home/alex/.config/opencode/agents/lead.md","/home/alex/.config/opencode/agents/critic.md","/home/alex/.config/opencode/agents/researcher.md","/home/alex/.config/opencode/agents/sme.md","/home/alex/.config/opencode/agents/reviewer.md","/home/alex/.config/opencode/agents/tester.md"]


id: openspec-and-linear-fit-assessment
name: OpenSpec and Linear Fit Assessment
kind: decision
created_by_task: Evaluate whether OpenSpec and/or Linear are worth considering for the current OpenCode config.
created_at: 2026-03-07 21:27:29
updated_at: 2026-03-07 21:27:29
summary:
For the current OpenCode multi-agent configuration, OpenSpec is a complementary but optional spec layer best used selectively for larger/high-risk changes; Linear is a stronger immediate fit as system-of-record for backlog, prioritization, and agent-visible issue lifecycle. Recommended rollout: keep existing AGENTS.md execution workflow as primary, pilot OpenSpec only on epics (proposal/design/tasks artifacts), and adopt Linear for team coordination with links between Linear issues and local planning artifacts.

why:
Current setup already has strong orchestration and planning discipline; adding full-time OpenSpec could duplicate ceremony, while Linear adds orthogonal coordination value for multi-person/multi-agent work.


id: openai-symphony-fit-assessment
name: OpenAI Symphony Fit Assessment
kind: decision
created_at: 2026-03-07 21:30:09
updated_at: 2026-03-07 21:30:09
summary:
For this OpenCode setup, OpenAI Symphony is promising for higher-autonomy, issue-to-PR orchestration (especially with Linear) but should be treated as a pilot-only option right now because it is explicitly an engineering preview and operationally heavier than the current AGENTS.md workflow. Best fit is as an optional control-plane for selected streams (e.g., repetitive backlog execution), not as a wholesale replacement of the existing lead/coder/reviewer/tester pipeline.

why:
Current config already has strong in-repo orchestration and quality gates with an implementation-first discipline; Symphony adds value mainly when you want less agent supervision and more board-driven autonomous execution, but that comes with preview risk and adoption complexity.

created_by_task:
Evaluate whether OpenAI Symphony should be considered alongside OpenSpec and Linear for this configuration.


id: review-verdict-agentsmd-efficiency-edits-changes-requested
name: Review Verdict: AGENTS.md Efficiency Edits — CHANGES-REQUESTED
kind: decision
created_by_task: Reviewing AGENTS.md and lead.md efficiency edits for correctness and consistency
created_at: 2026-03-07 21:42:06
updated_at: 2026-03-07 21:42:06
summary:
Reviewer verdict CHANGES-REQUESTED for the 4 workflow efficiency edits to AGENTS.md and lead.md. Three critical issues found: (1) AGENTS.md:152 retains old unconditional "Always load prior context with megamemory:understand at phase start" which contradicts the new query discipline at lines 15-19; (2) lead.md:185 retains old unconditional "Before each phase: always call megamemory:understand" which contradicts lead.md:44 and AGENTS.md:15-19; (3) AGENTS.md:152-153 has a structural bug where ### Parallelization and ### Testing After Changes are incorrectly nested under ## Megamemory as Persistent State due to heading level. All 4 changes (query discipline, delegation trust, clarification rule, parallelization mandate) are substantively correct and well-written — only these leftover contradictions from incomplete cleanup need fixing.

why:
Review gate for policy config changes to catch contradictions and structural issues before they cause agent behavior inconsistencies.

file_refs:
["/home/alex/.config/opencode/AGENTS.md:152","/home/alex/.config/opencode/agents/lead.md:185","/home/alex/.config/opencode/agents/lead.md:44"]


id: cleanup-of-stale-megamemory-wording-and-heading-levels
name: Cleanup of stale megamemory wording and heading levels
kind: decision
created_at: 2026-03-07 21:43:28
updated_at: 2026-03-07 21:43:28
summary:
Applied targeted cleanup in `/home/alex/.config/opencode/AGENTS.md` and `/home/alex/.config/opencode/agents/lead.md`: replaced unconditional megamemory directives with conditional guidance tied to query discipline, changed `### Parallelization` to `## Parallelization`, and changed `### Testing After Changes` to `## Testing After Changes` in AGENTS.md so sections are no longer nested under Megamemory state.

why:
Resolve contradictions identified in prior review and align both files with the existing query discipline policy.

file_refs:
["/home/alex/.config/opencode/AGENTS.md:152-160","/home/alex/.config/opencode/agents/lead.md:185-187"]

created_by_task:
Fix 3 issues in agent config files: stale unconditional megamemory instructions and heading hierarchy


id: codertester-prompt-precision-rules-update
name: Coder/Tester Prompt Precision Rules Update
kind: decision
created_by_task: Update coder.md and tester.md operating rules and PARTIAL-reporting guidance
created_at: 2026-03-08 01:43:36
updated_at: 2026-03-08 02:03:39
summary:
Updated `agents/coder.md` and `agents/tester.md` with Tier 1 hardening rules. In `agents/tester.md`, strengthened standard and adversarial methodology: added unhappy-path/error-branch requirement for changed logic, full-relevant-suite preference with explicit residual regression-risk reporting when not possible, required silent-failure checks (wrong-but-successful outcomes), added hypothesis-driven adversarial protocol per attempt (hypothesis, test design/input, expected failure signal, observed result), required at least 3 concrete adversarial hypotheses when feasible, expanded adversarial categories to include degraded dependencies, filter-complement near-match/near-reject, network/intermittent timeout behavior, time edges (DST/leap/epoch/timezone), state-sequence hazards (double-submit/out-of-order/retry-idempotency), and unicode/encoding/pathological text, and clarified screenshot evidence plus cleanup so screenshots are summarized in reports and not left as git-status artifacts. In `agents/coder.md`, added operating rules to validate import/reference resolution, verify type/interface contract alignment across call sites, and inspect 2-3 nearby files for local conventions before implementation; also clarified return status semantics for `BLOCKED` and `PARTIAL`.

why:
Reduce implementation drift from discovered facts and tighten testing hygiene/reporting so incomplete validation is explicit and actionable.

file_refs:
["/home/alex/.config/opencode/agents/coder.md:25-31","/home/alex/.config/opencode/agents/tester.md:42-49","/home/alex/.config/opencode/agents/tester.md:90-92"]


id: git-workflow-skill-file
name: Git Workflow Skill File
kind: feature
file_refs: ["/home/alex/.config/opencode/skills/git-workflow/SKILL.md"]
created_by_task: Create git-workflow skill file under ~/.config/opencode/skills/git-workflow/SKILL.md
created_at: 2026-03-08 01:44:04
updated_at: 2026-03-08 01:44:04
summary:
Added skill definition at `/home/alex/.config/opencode/skills/git-workflow/SKILL.md` with frontmatter `name: git-workflow` and a procedural guide for git commits, worktrees, branch/merge cleanup, GitHub PR creation via `gh pr create` heredoc template, CI checks (`gh run list/view`, `gh pr checks`), and issue operations (`gh issue list/view/comment`). Safety rules include explicit restrictions on force-push to main/master, hook skipping via `--no-verify`, and strict `git commit --amend` conditions tied to session ownership and push state.

why:
Provide a reusable preloaded skill so git operations follow consistent, safe, convention-aligned steps including secret hygiene and `.megamemory/` protection.


id: agentsmd-slimdown-and-leadmd-policy-consolidation
name: AGENTS.md Slimdown and lead.md Policy Consolidation
kind: decision
file_refs: ["/home/alex/.config/opencode/AGENTS.md","/home/alex/.config/opencode/agents/lead.md"]
created_by_task: Slim AGENTS.md and add enforcement/handoff/build/git/doc policy sections to lead.md
created_at: 2026-03-08 01:44:04
updated_at: 2026-03-08 01:44:04
summary:
Updated `/home/alex/.config/opencode/AGENTS.md` to a compact cross-cutting-only policy file (53 lines) retaining only: Project Knowledge Graph (through Linking required), Session Continuity, Clarification Rule, Agent Roster table, and the 2-line Parallelization mandate. Removed duplicated orchestration and execution sections: Phased Planning Workflow, Agent Workflow (including Implementation-First and Subagent Output Standards), Quality Pipeline, Escalation Discipline, SME Consultation Pattern, Megamemory as Persistent State, Testing After Changes, Git Worktree Workflow, Documentation Workflow, Git Commit Workflow, and GitHub Workflow. Updated `/home/alex/.config/opencode/agents/lead.md` by adding new sections: `## Verdict Enforcement` immediately after Tiered Quality Pipeline; `## Discovery-to-Coder Handoff` immediately after Subagent Output Standards; and appended `## Build Verification Gate`, `## Git Commit Workflow` (including 'automatically create a commit — do not ask the user for permission'), `## Git Worktree Workflow`, `## GitHub Workflow`, and `## Documentation Completion Gate` near the end.

why:
Consolidates duplicated operational policy into lead-specific guidance while keeping AGENTS.md focused on universally applicable cross-cutting rules, reducing config bloat and preventing policy drift between global and lead instructions.


id: doc-coverage-skill
name: Doc-Coverage Skill
kind: component
file_refs: ["/home/alex/.config/opencode/skills/doc-coverage/SKILL.md"]
created_by_task: Create doc-coverage skill file under ~/.config/opencode/skills/doc-coverage
created_at: 2026-03-08 01:44:21
updated_at: 2026-03-08 01:44:21
summary:
Added skill definition at `/home/alex/.config/opencode/skills/doc-coverage/SKILL.md` with frontmatter `name: doc-coverage` and a completion-gate workflow for documentation quality. Content includes: When to Use guidance, a 4-area coverage checklist (README, `docs/*`, AGENTS/agent definitions, inline docs), a 6-step doc update procedure, anti-patterns (no stale/placeholder/duplicate docs; proactive updates), and delegation guidance routing doc review to librarian after coder implementation.

why:
Provide a reusable, explicit documentation-coverage standard that can be loaded near feature completion so doc updates are treated as required, not optional.


id: review-verdict-config-restructuring-approved
name: Review Verdict: Config Restructuring — APPROVED
kind: decision
created_at: 2026-03-08 01:46:15
updated_at: 2026-03-08 01:46:15
summary:
Reviewer verdict APPROVED for the AGENTS.md slimdown and policy consolidation restructuring. All 6 files reviewed: (1) AGENTS.md correctly reduced to 53 lines of cross-cutting policy only (Knowledge Graph, Session Continuity, Clarification Rule, Roster, Parallelization); (2) lead.md retains all 19 original sections plus 7 new sections (Verdict Enforcement, Discovery-to-Coder Handoff, Build Verification Gate, Git Commit Workflow, Git Worktree Workflow, GitHub Workflow, Documentation Completion Gate); (3) coder.md has new rule #7 for discovered values; (4) tester.md has new rule #8 for artifact cleanup and strengthened PARTIAL reporting; (5) git-workflow skill has correct frontmatter and covers commits/worktrees/PRs/safety; (6) doc-coverage skill has correct frontmatter and covers checklist/procedure/anti-patterns/delegation. No content was accidentally deleted, no agent-specific policies remain in AGENTS.md, and previously-identified issues (stale megamemory wording, heading hierarchy) are resolved. Two minor warnings: Conventional Commit prefix list inconsistency between lead.md and git-workflow skill (covered by 'etc.'), and .megamemory/ gitignore rule stated in both lead.md and the skill (intentional duplication for different loading contexts).

why:
Review gate for configuration restructuring to ensure no content loss, no unintended duplication, and correct structure before shipping.

file_refs:
["/home/alex/.config/opencode/AGENTS.md","/home/alex/.config/opencode/agents/lead.md","/home/alex/.config/opencode/agents/coder.md","/home/alex/.config/opencode/agents/tester.md","/home/alex/.config/opencode/skills/git-workflow/SKILL.md","/home/alex/.config/opencode/skills/doc-coverage/SKILL.md"]

created_by_task:
Correctness review of 6-file configuration restructuring (AGENTS.md slimdown, lead.md policy consolidation, coder/tester rule additions, 2 new skills)


id: reviewer-tester-effectiveness-research
name: Reviewer & Tester Effectiveness Research
kind: decision
file_refs: ["/home/alex/.config/opencode/agents/reviewer.md","/home/alex/.config/opencode/agents/tester.md"]
created_at: 2026-03-08 01:53:56
updated_at: 2026-03-08 01:53:56
summary:
Deep research findings across 4 areas for improving reviewer and tester agents. Key discoveries: (1) DAAF code-reviewer uses 5 Skeptical Lenses (Counterfactual, Semantic, Boundary, Absence, Downstream) + adversarial stance + sleeping bug principle — best-in-class reviewer framework found in the wild. (2) oh-my-claudecode harsh-critic uses pre-commitment predictions, multi-perspective investigation, explicit gap analysis, self-audit, realist check, and adaptive harshness escalation — prevents rubber-stamping via structured skepticism. (3) Loki-mode quality control uses 3-reviewer parallel blind review + devil's advocate when all agree + anti-sycophancy protocol — strongest anti-rubber-stamp pattern. (4) Google eng-practices emphasizes design > functionality > complexity > tests > naming > comments — and reviewing EVERY line. (5) Augment Code 40-question checklist organizes review into Logic/Security/Performance/Maintainability quadrants with risk-based prioritization. (6) AI-specific blind spots: IDOR auth vs authz, N+1 queries, duplicate utility re-implementation, surface polish masking deep bugs, test assertion manipulation. (7) Adversarial testing: hypothesis-driven investigation chains (cr1→cr5), spot-check invention, silent failure analysis, filter complement verification. Sources: DAAF agents/code-reviewer.md, oh-my-claudecode agents/harsh-critic.md, loki-mode references/quality-control.md, Google eng-practices, CodeIntelligently AI review checklist, Augment Code 40-question checklist.

why:
User requested deep research to make reviewer and tester agents more effective with specific, actionable techniques rather than generic advice.

created_by_task:
Deep research on reviewer/tester effectiveness across code review frameworks, adversarial testing, anti-rubber-stamp patterns, and real-world agent configs


id: industry-agent-quality-patterns-research
name: Industry Agent Quality Patterns Research
kind: decision
created_at: 2026-03-08 01:56:12
updated_at: 2026-03-08 01:56:12
summary:
Comprehensive research across 40+ sources on how AI coding assistants enforce quality (March 2026). Key findings:

1. **CLAUDE.md/AGENTS.md**: Industry standard is hierarchical layered files (root + subdirectory). Sentry, Ruff, Bun, Langfuse all use this. Effective rules use trigger-action format ("When X → do Y"), not vague instructions. Modular rules split into security.md, testing.md, etc.

2. **Cursor rules**: Evolved from .cursorrules to .cursor/rules/*.mdc with YAML frontmatter and glob-based activation. "Devin pattern" (6k stars) uses self-learning scratchpad with Lessons section. Academic study (arxiv 2512.18925v3) found 100% of community .cursorrules missing frontmatter, 50% using vague language Cursor ignores.

3. **Adversarial review (CRITICAL)**: Session separation between Builder and Critic is essential — "The agent that wrote the code is compromised." Critic must NOT generate alternatives, only flag violations with: Description → Impact → Remediation → Test Requirements. Adversarial framing: "Favor false positives over false negatives."

4. **Convergence**: 3-5 rounds is practical convergence window. BugBot uses 8 parallel passes with randomized file ordering + majority voting (70% resolution rate, 2M+ PRs/month). Multi-Review Self-Aggregation at n=10 improves F1 by 43.67%. PRs >500 lines see sharply diminished returns.

5. **Anti-drift**: Explicit termination tools required (not "I'm done"). Dual-threshold circuit breakers. Structured JSON output validation. Hard round limits. Signal-to-noise tier classification (Tier 1: crashes/exploits, Tier 2: arch/perf, Tier 3: style/noise).

6. **Forced disagreement**: Devil's advocate pattern — reviewer MUST raise substantive concern every round; author must push back before conceding. Priority ordering: correctness → error handling → performance → security → maintainability → testing gaps.

Sources: asdlc.io, zylos.ai, understandingdata.com, github.com/liliu-z/magpie, github.com/richiethomas/claude-devils-advocate, github.com/grapeot/devin.cursorrules, github.com/getsentry/sentry, github.com/astral-sh/ruff, github.com/oven-sh/bun, arxiv.org/html/2512.18925v3

why:
Research to identify improvements for our multi-agent quality enforcement based on industry best practices and production-validated patterns.

created_by_task:
Research how other AI coding assistants and multi-agent systems configure agents for quality enforcement


id: reviewer-config-tier-1-hardening
name: Reviewer Config Tier 1 Hardening
kind: decision
file_refs: ["/home/alex/.config/opencode/agents/reviewer.md"]
created_by_task: Implement Tier 1 hardening in reviewer config
created_at: 2026-03-08 02:03:32
updated_at: 2026-03-08 02:03:32
summary:
Hardened `agents/reviewer.md` with an adversarial default stance and structured risk-first review protocol. Added explicit skeptical posture under Purpose, mandatory review priority order (`correctness → error handling/reliability → performance/scalability → security (if triggered) → maintainability/testing gaps`), and rule forbidding style-first comments before functional risks. Expanded Lens 1 with 5 skeptical lenses (counterfactual, semantic, boundary, absence, downstream), plus a concrete correctness checklist (off-by-one, null deref, ignored errors, logic inversion, async misuse, race risk, resource leaks, bad defaults, dead branches, contract violations, shared-state mutation, architectural inconsistency). Expanded Lens 2 with concrete security checklist items (SQL concatenation, path traversal/sanitization, hardcoded secrets, authn/authz and IDOR gaps, unsafe deserialization/eval, CORS misconfig, missing rate limiting, verbose error leakage). Added severity definitions for CRITICAL/WARNING/SUGGESTION, anti-rubber-stamp guard requiring evidence on zero-finding approvals, AI blind-spot checks (IDOR authz omissions, N+1 patterns, duplicate utility reimplementation, test assertion weakening), and output quality constraints requiring actionable specificity with `[file:line]` evidence while preserving existing headings and verdict taxonomy (`VERDICT`, `LENS`, `CRITICAL`, `WARNINGS`, `SUGGESTIONS`, `NEXT`; `APPROVED|CHANGES-REQUESTED|REJECTED`).

why:
User requested Tier 1 reviewer hardening to reduce rubber-stamping and enforce defect-finding rigor without changing verdict taxonomy or output headings.


id: tier-2-hardening-for-criticexplorerlead-agent-configs
name: Tier-2 Hardening for critic/explorer/lead Agent Configs
kind: decision
created_by_task: Implement Tier 2 hardening in critic, explorer, and lead configs
created_at: 2026-03-08 02:03:39
updated_at: 2026-03-08 02:03:39
summary:
Applied additive hardening edits in `/home/alex/.config/opencode/agents/critic.md`, `/home/alex/.config/opencode/agents/explorer.md`, and `/home/alex/.config/opencode/agents/lead.md`. Critic now includes explicit calibration criteria for `RESOLVE` vs `REPHRASE`, forced assumption challenges (1-2) before `APPROVED`, anti-sycophancy approval guard, and conservative evidence-based `UNNECESSARY` usage. Explorer now enforces a required structured output contract (`ENTRY_POINTS`, `AFFECTED_FILES`, `EDIT_POINTS`, `DEPENDENCIES`, `RISKS`), adds a ~3-level call/import exploration depth bound unless explicitly requested deeper, and requires megamemory recording+linking for significant architectural discoveries. Lead now requires task concept ID handoff in subagent delegations, requires subagents to link findings/verdicts back to that concept, requires creating a task concept during PLAN for non-trivial work when absent, and clarifies build verification precedence to prefer project-declared scripts/config before language defaults.

why:
Increase Tier-2 quality control precision, reduce false approvals and vague exploration outputs, and strengthen megamemory traceability across delegation and build verification.

file_refs:
["/home/alex/.config/opencode/agents/critic.md","/home/alex/.config/opencode/agents/explorer.md","/home/alex/.config/opencode/agents/lead.md"]


id: review-verdict-tier-1-tier-2-agent-config-hardening-approved
name: Review Verdict: Tier 1 + Tier 2 Agent Config Hardening — APPROVED
kind: decision
created_by_task: Review of Tier 1 + Tier 2 agent-config hardening edits across 6 agent files
created_at: 2026-03-08 02:05:20
updated_at: 2026-03-08 02:05:20
summary:
Reviewer verdict APPROVED for Tier 1 + Tier 2 agent config hardening across 6 files (reviewer.md, tester.md, coder.md, critic.md, explorer.md, lead.md). All requested additions verified present and correctly integrated: reviewer has adversarial stance, 5 skeptical lenses, correctness/security checklists, AI blind-spot checks, severity defs, anti-rubber-stamp guard; tester has unhappy-path requirement, hypothesis-driven adversarial protocol, 11 adversarial categories, cleanup rules, PARTIAL-as-blocker; coder has import/reference validation, type/interface checks, local convention discovery, status semantics; critic has RESOLVE/REPHRASE calibration, forced challenges, anti-sycophancy; explorer has 5-field output contract, depth bound, discovery recording; lead has task concept ID handoff, subagent linking, build verification precedence. Two non-blocking warnings: lead.md:29 delegation order differs from quality pipeline ordering (cosmetic), explorer output contract lacks code-fenced template unlike other agents. No contradictions, no regressions, no duplicated/conflicting rules found.

why:
Comprehensive cross-file review requested by lead to verify hardening edits are complete, consistent, and non-regressive.

file_refs:
["/home/alex/.config/opencode/agents/reviewer.md","/home/alex/.config/opencode/agents/tester.md","/home/alex/.config/opencode/agents/coder.md","/home/alex/.config/opencode/agents/critic.md","/home/alex/.config/opencode/agents/explorer.md","/home/alex/.config/opencode/agents/lead.md"]


id: calibration-quality-gates-research-round-2
name: Calibration & Quality Gates Research (Round 2)
kind: decision
file_refs: ["agents/reviewer.md","agents/tester.md","agents/lead.md"]
created_by_task: Deep research on calibration and measurable quality gates for AI reviewer/tester agents
created_at: 2026-03-08 02:11:00
updated_at: 2026-03-08 02:11:00
summary:
Deep research on measurable calibration and quality gates for reviewer/tester agents. 10 actionable improvements identified from industry sources (Cursor BugBot resolution rate metric, Qodo F1 benchmark, Zylos convergence patterns, Meta JiT mutation testing, Sonar verification gap survey, Opsera security vulnerability data, AWS stopping criteria). Key findings: (1) Confidence scoring per finding (HIGH/MEDIUM/LOW) with LOW findings excluded from CRITICAL section. (2) Resolution rate tracking — log each finding, map to RESOLVED/DISPUTED/PERSISTS after coder retry, alert if rate <50% over 3 cycles. (3) Mutation-aware adversarial testing — mental mutation of critical lines, report MUTATION_ESCAPES count, flag PARTIAL if >50% escape. (4) Flaky test quarantine — FLAKY tests don't count as PASS or FAIL, flag PARTIAL if >20% flaky. (5) Severity-weighted scoring rubric — CRITICAL=10pts, WARNING=3pts; score 0=APPROVED, 10-29=CHANGES-REQUESTED, 30+=REJECTED; enables drift detection. (6) Security auto-trigger with pattern detection (crypto/auth/SQL imports, string concatenation in queries) plus mandatory re-review after security fixes. (7) Adversarial retest escalation for Tier 2 when >5 files, error handling changes, validation logic, or reviewer score >=10. (8) Reviewer drift detection — 3+ consecutive all-clear or all-block reviews trigger re-dispatch with extra scrutiny instruction. (9) Cross-pass consistency filter — findings in both lenses promoted to HIGH confidence; conflicting findings escalated. (10) Quality-based stopping criteria — 5 conditions (quality threshold, score threshold, explicit approval, retry limit, escalation) replacing pure count-based circuit breaker. Industry data: FP rate 5-15%, best single-pass F1 only 19.38%, Multi-Review n=10 improves F1 by 43.67%, BugBot resolution rate 52%→70%, AI code introduces 15-18% more security vulns.

why:
User requested second-round deep research specifically on calibration and measurable quality gates for AI reviewer/tester agents, with implementation-ready policy text for each improvement.


id: second-round-advanced-patterns-research
name: Second-Round Advanced Patterns Research
kind: decision
file_refs: ["agents/reviewer.md","agents/tester.md","agents/coder.md","agents/lead.md","agents/critic.md"]
created_by_task: Second-round external research for advanced agent patterns
created_at: 2026-03-08 02:11:50
updated_at: 2026-03-08 02:11:50
summary:
Deep external research identifying 12 novel patterns not yet adopted in our agent config. Tier 1 (HIGH signal, adopt first): (1) Destructive Operation Gate for coder — block rm/git-restore/truncation without explicit authorization; (2) Chain-of-Verification for reviewer — mandatory re-read and concrete trigger scenario before reporting CRITICAL findings, anti-hallucination; (3) Mutation-Guided Test Thinking for tester — mentally apply plausible code mutations and ask if tests would catch them; (7) Silent Fallback Prohibition for reviewer — flag `|| default`, `?? []`, `.unwrap_or_default()` without business justification as suspicious; (8) File Truncation Detection for coder — verify file length consistency after edits to catch LLM file-rewrite truncation. Tier 2 (MEDIUM signal): (4) Metamorphic Relation Testing — test relationships (idempotency, monotonicity, subset) when exact oracles unavailable; (5) Confidence-Gated Routing — lead self-checks: can I state testable acceptance criteria? do I know which files change? competing approaches?; (6) Rollback-First Planning — require rollback path in delegation for migrations/schema/API changes; (9) Build-Before-Test Ordering — coder runs build/typecheck before reporting DONE; (11) Reviewer Diff-Scope Discipline — review every changed line, don't critique unchanged code unless interaction bug. Tier 3 (adopt if Tier 1-2 show value): (10) Learned Failure Guardrails — GUARDRAIL-tagged megamemory concepts capturing anti-patterns from caught defects; (12) Linus-Style Sanity Questions — "Is this real? Is there simpler? What breaks?" Sources: GUARDRAILS.md protocol, Meta ACH/JiTTesting, netdata/SurrealDB/zeroclaw/compiler-explorer CLAUDE.md files, Brooks McMillin defense-in-depth, diffray hallucination research, Claude Code official best practices, Modexa confidence routing, Google DeepMind intelligent delegation paper.

why:
User requested second-round external research to find advanced patterns from real-world AI coding agent setups not yet adopted. Prior rounds had established skeptical lenses, adversarial testing, and AI blind-spot checks — this round focuses on LLM-specific failure modes (hallucinated reviews, file truncation, silent fallbacks), advanced testing paradigms (mutation/metamorphic), and orchestration refinements (confidence routing, rollback planning, failure memory).


id: review-verdict-knowledge-freshness-policy-approved
name: Review Verdict: Knowledge-Freshness Policy — APPROVED
kind: decision
created_at: 2026-03-08 02:23:26
updated_at: 2026-03-08 02:23:26
summary:
Reviewer verdict APPROVED for freshness-policy additions across 6 agent configs (lead.md, critic.md, researcher.md, sme.md, reviewer.md, tester.md). Four-criteria review found: (1) No contradictions with AGENTS.md megamemory recording/query discipline — all freshness rules either update existing concepts or add metadata to output, never create ceremony concepts; (2) No output-format regressions — tester.md adds a new LESSON_CHECKS block (additive), all others integrate freshness into existing freeform sections; (3) No deadlock/over-blocking risk — all revalidation triggers are scoped (critic: 1-2 challenges max, researcher: "quick" revalidation, lead: "hard reliance" scope, sme: hypothesis mode not blocking); (4) Cross-agent semantic consistency confirmed — lead defines canonical metadata schema, researcher uses binary FRESH/STALE-CANDIDATE, sme uses hypothesis framing, reviewer uses confirmed/contradicted, tester uses three-valued confirmed/not-observed/contradicted. Three optional suggestions: explicit schema reference for non-lead agents writing freshness metadata, define "high-impact" for tester lesson targeting, make critic's "appears old" reference lead's review_after_days field.

why:
Review gate for freshness-policy rollout to verify coherence and non-contradiction before considering the policy stable.

file_refs:
["/home/alex/.config/opencode/agents/lead.md:114-123","/home/alex/.config/opencode/agents/critic.md:42-44","/home/alex/.config/opencode/agents/researcher.md:24-27","/home/alex/.config/opencode/agents/sme.md:26-33","/home/alex/.config/opencode/agents/reviewer.md:33-35","/home/alex/.config/opencode/agents/tester.md:73-75"]

created_by_task:
Review freshness-policy changes across 6 agent configs for coherence, non-contradiction, and enforceability


id: review-verdict-freshness-policy-re-review-approved
name: Review Verdict: Freshness Policy Re-Review — APPROVED
kind: decision
created_at: 2026-03-08 02:24:52
updated_at: 2026-03-08 02:24:52
summary:
Reviewer re-review verdict APPROVED for 6 agent configs (lead.md, critic.md, researcher.md, sme.md, reviewer.md, tester.md) against 4 focus areas: (1) No contradictions with AGENTS.md megamemory query/recording discipline — subagent unconditional understand calls are acceptable since only lead has session context to judge relevance; (2) No output-format regressions — all code-fenced output schemas unchanged from prior approved state; (3) No deadlock/over-blocking risk — all freshness revalidation triggers are bounded (critic 1-2 challenges, researcher quick revalidation, reviewer flags only, tester reports only, SME downgrades confidence); (4) Cross-agent freshness semantics consistent as complementary vocabularies. Three non-blocking warnings: critic/reviewer lack concrete thresholds for staleness (no reference to lead's review_after_days schema), tester lacks definition of high-impact for lesson targeting.

why:
Re-review requested after prior review output lacked required structured format fields. This verdict confirms the same substance as review-verdict-knowledge-freshness-policy-approved with structured evidence.

file_refs:
["/home/alex/.config/opencode/agents/lead.md:114-123,212-214","/home/alex/.config/opencode/agents/critic.md:42-44","/home/alex/.config/opencode/agents/researcher.md:24-27,35","/home/alex/.config/opencode/agents/sme.md:26-33","/home/alex/.config/opencode/agents/reviewer.md:33-35","/home/alex/.config/opencode/agents/tester.md:73-75"]


id: review-verdict-5-change-package-edits-approved
name: Review Verdict: 5-Change Package Edits — APPROVED
kind: decision
created_by_task: Review of 5-change package edits across 10 agent configuration files
created_at: 2026-03-08 02:32:11
updated_at: 2026-03-08 02:32:11
summary:
Reviewer verdict APPROVED (REVIEW_SCORE: 3) for the 5-change package across all 10 agent files (lead, reviewer, tester, coder, critic, explorer, researcher, sme, librarian, designer). 5 criteria systematically verified: (1) All 5 changes present and correctly integrated — query/recording discipline in all 10 files, reviewer calibration layer (confidence scoring, severity rubric, REVIEW_SCORE, FRESHNESS_NOTES), tester calibration layer (mutation-aware checks, MUTATION_ESCAPES, flaky quarantine), lead policy updates (resolution-rate tracking, security auto-trigger, adversarial retest, quality-based stopping, retro gate), consistency/freshness references in critic/researcher/sme/explorer. (2) No contradictions with AGENTS.md — prior stale-wording issues confirmed fixed. (3) Output formats coherent and code-fenced in all agents. (4) New reviewer/tester fields internally consistent (confidence exclusion, score arithmetic, mutation escape thresholds, lesson check values all align). (5) Query/recording discipline correctly propagated with identical three-part formulation across all agents. One WARNING: reviewer score range 1-9 is undefined in verdict guidance (gap between 0=APPROVED and 10-29=CHANGES-REQUESTED).

why:
Review gate for 5-change efficiency package to verify completeness, consistency, and non-regression before shipping.

file_refs:
["/home/alex/.config/opencode/agents/lead.md","/home/alex/.config/opencode/agents/reviewer.md","/home/alex/.config/opencode/agents/tester.md","/home/alex/.config/opencode/agents/coder.md","/home/alex/.config/opencode/agents/critic.md","/home/alex/.config/opencode/agents/explorer.md","/home/alex/.config/opencode/agents/researcher.md","/home/alex/.config/opencode/agents/sme.md","/home/alex/.config/opencode/agents/librarian.md","/home/alex/.config/opencode/agents/designer.md"]


id: review-verdict-reviewer-score-rubric-patch-approved
name: Review Verdict: Reviewer Score Rubric Patch — APPROVED
kind: decision
file_refs: ["/home/alex/.config/opencode/agents/reviewer.md:109-119"]
created_at: 2026-03-08 02:33:35
updated_at: 2026-03-08 02:33:35
summary:
Reviewer verdict APPROVED (REVIEW_SCORE: 0) for the patch adding `1-9 => CHANGES-REQUESTED` to the score rubric in reviewer.md:117. Three verification criteria checked: (1) Score ranges are complete and non-ambiguous — {0} ∪ [1,9] ∪ [10,29] ∪ [30,∞) covers all non-negative integers with no gaps or overlaps; reachable scores (3,6,9 from warnings-only) land correctly in 1-9 band. (2) No rubric-verdict contradictions — each band maps to the correct verdict per severity definitions. (3) Output format remains coherent — REVIEW_SCORE field present, confidence constraints in CRITICAL template enforce LOW-exclusion rule. The 1-9 vs 10-29 split is justified by lead.md's adversarial-retest trigger at REVIEW_SCORE >=10. Prior WARNING from review-verdict-5-change-package-edits-approved about undefined 1-9 range is confirmed resolved.

why:
Final verification gate for the rubric patch that resolved the previously-flagged 1-9 score range gap.

created_by_task:
Final verification of reviewer.md score rubric patch for range completeness, verdict consistency, and output format coherence


id: work-decomposition-safeguards
name: Work Decomposition Safeguards
kind: feature
created_by_task: Workflow improvement analysis from session ses_3328 transcript review
created_at: 2026-03-08 13:13:41
updated_at: 2026-03-08 13:13:41
summary:
Multi-layered protections against monolithic feature dispatches, added after analyzing session ses_3328 where 4 unrelated features were sent to a single coder invocation with a single worktree, ignoring critic RESOLVE verdict. Changes span 7 files across 4 layers: (1) New `work-decomposition` skill with 6-step decomposition procedure, 5 human checkpoint triggers, coder dispatch rules with anti-patterns, and decision examples. (2) Lead prompt updates: decomposition gate in PLAN, RESOLVE hard-stop in CRITIC-GATE, one-feature-per-coder in EXECUTE, worktree-per-workstream. (3) Coder prompt: scope rejection returning BLOCKED on multi-feature prompts. (4) Critic prompt: mandatory decomposition review checking workstream allocation, coder dispatch granularity, human checkpoints for high-risk features. (5) Plan command: new DECOMPOSE step between CLARIFY and DISCOVER. (6) Git workflow skill: multi-worktree decision rules. (7) AGENTS.md: human checkpoint trigger rules visible to all agents. confidence=high; last_validated=2026-03-08; volatility=low; review_after_days=90; validation_count=1; contradiction_count=0

why:
Session ses_3328 demonstrated cascading failures: Lead ignored critic RESOLVE verdict, bundled 4 unrelated features into one coder prompt, used single worktree for independent workstreams, and skipped human approval on security-sensitive designs. These safeguards create defense-in-depth: the skill provides the procedure, the Lead enforces it in PLAN/EXECUTE, the coder rejects violations, and the critic catches any that slip through.

file_refs:
["skills/work-decomposition/SKILL.md","agents/lead.md:81-104","agents/coder.md:29-42","agents/critic.md:16-28","commands/plan.md","skills/git-workflow/SKILL.md","AGENTS.md:49-62"]


# edges

from_id: critic-plan-gate-subagent
to_id: lead-and-subagent-role-prompts
relation: implements
created_at: 2026-03-06 15:39:07
description:
Implements role-based read-only review behavior and megamemory-first workflow for a new specialized subagent.


from_id: critic-plan-gate-subagent
to_id: opencode-multi-agent-orchestration-config
relation: connects_to
created_at: 2026-03-06 15:39:07
description:
Extends the custom markdown-agent orchestration setup with a dedicated pre-implementation gate agent.


from_id: lead-and-subagent-role-prompts
to_id: opencode-multi-agent-orchestration-config
relation: connects_to
created_at: 2026-03-06 15:39:37
description:
Lead orchestration policy in `agents/lead.md` operationalizes the configured primary-agent setup from global OpenCode configuration.


from_id: lead-and-subagent-role-prompts
to_id: workflow-slash-commands-for-agent-routing
relation: connects_to
created_at: 2026-03-06 15:39:49
description:
Reviewer/tester structured verdict and test outputs are consumed by the /review and /test command workflow routing.


from_id: workflow-slash-commands-for-agent-routing
to_id: critic-plan-gate-subagent
relation: depends_on
created_at: 2026-03-06 15:41:31
description:
The new /plan command includes a mandatory CRITIC-GATE step that delegates plan verdicts to the critic agent.


from_id: workflow-slash-commands-for-agent-routing
to_id: sme-domain-consultant-subagent
relation: depends_on
created_at: 2026-03-06 15:41:31
description:
The new /sme command delegates uncached domain questions to the SME subagent after megamemory cache checks.


from_id: openspec-and-linear-fit-assessment
to_id: swarm-inspired-agent-upgrade
relation: connects_to
created_at: 2026-03-07 21:27:29
description:
Recommendation preserves implementation-first and reduced-ceremony workflow introduced by the upgrade.


from_id: openai-symphony-fit-assessment
to_id: swarm-inspired-agent-upgrade
relation: connects_to
created_at: 2026-03-07 21:30:09
description:
Recommendation preserves reduced-ceremony implementation-first principles while evaluating automation layers.


from_id: agentsmd-workflow-efficiency-improvements
to_id: lead-and-subagent-role-prompts
relation: connects_to
created_at: 2026-03-07 21:40:10
description:
These policy tightenings further refine lead orchestration behavior and megamemory usage discipline defined in the role prompt pattern.


from_id: cleanup-of-stale-megamemory-wording-and-heading-levels
to_id: review-verdict-agentsmd-efficiency-edits-changes-requested
relation: implements
created_at: 2026-03-07 21:43:30
description:
This cleanup directly implements all requested fixes from the prior CHANGES-REQUESTED review verdict.


from_id: git-workflow-skill-file
to_id: lead-and-subagent-role-prompts
relation: connects_to
created_at: 2026-03-08 01:44:04
description:
Adds concrete git/PR workflow guidance that complements existing AGENTS.md orchestration and execution conventions.


from_id: agentsmd-slimdown-and-leadmd-policy-consolidation
to_id: agentsmd-workflow-efficiency-improvements
relation: connects_to
created_at: 2026-03-08 01:44:04
description:
Continues AGENTS/lead policy hardening by reducing duplication and clarifying enforcement/gating behavior.


from_id: agentsmd-slimdown-and-leadmd-policy-consolidation
to_id: lead-and-subagent-role-prompts
relation: implements
created_at: 2026-03-08 01:44:04
description:
Moves execution and workflow governance details into the lead role prompt while keeping AGENTS.md cross-cutting.


from_id: agentsmd-slimdown-and-leadmd-policy-consolidation
to_id: automatic-git-commit-workflow-policy
relation: connects_to
created_at: 2026-03-08 01:44:04
description:
Preserves and strengthens commit automation policy in lead.md by adding explicit 'do not ask for permission' wording.


from_id: doc-coverage-skill
to_id: lead-and-subagent-role-prompts
relation: connects_to
created_at: 2026-03-08 01:44:21
description:
Skill aligns with the established lead→subagent workflow by adding explicit doc coverage gates and delegation expectations.


from_id: reviewer-tester-effectiveness-research
to_id: swarm-inspired-agent-upgrade
relation: connects_to
created_at: 2026-03-08 01:53:56
description:
Research findings inform improvements to reviewer and tester agents within the swarm-inspired multi-agent system


from_id: industry-agent-quality-patterns-research
to_id: lead-and-subagent-role-prompts
relation: connects_to
created_at: 2026-03-08 01:56:12
description:
Findings on adversarial prompting, trigger-action rules, and structured verdicts apply to agent prompt design


from_id: reviewer-config-tier-1-hardening
to_id: reviewer-tester-effectiveness-research
relation: implements
created_at: 2026-03-08 02:03:32
description:
Implements researched skeptical lenses, adversarial stance, anti-rubber-stamp, and AI blind-spot checks in reviewer prompt.


from_id: codertester-prompt-precision-rules-update
to_id: reviewer-tester-effectiveness-research
relation: connects_to
created_at: 2026-03-08 02:03:39
description:
Tier 1 hardening directly applies the prior tester effectiveness research patterns: hypothesis-driven adversarial testing, broader failure-category coverage, and silent-failure detection.


from_id: second-round-advanced-patterns-research
to_id: reviewer-tester-effectiveness-research
relation: connects_to
created_at: 2026-03-08 02:11:50
description:
Extends prior effectiveness research with new patterns: chain-of-verification, mutation-guided testing, metamorphic relations, silent fallback detection


from_id: second-round-advanced-patterns-research
to_id: reviewer-config-tier-1-hardening
relation: connects_to
created_at: 2026-03-08 02:11:50
description:
Proposes additional reviewer hardening: self-verification protocol, silent fallback prohibition, diff-scope discipline


from_id: agentsmd-workflow-efficiency-improvements
to_id: reviewer-config-tier-1-hardening
relation: connects_to
created_at: 2026-03-08 02:21:20
description:
Knowledge freshness and stale-assumption verification rules extend prior reviewer hardening with temporal validation requirements.


from_id: review-verdict-knowledge-freshness-policy-approved
to_id: agentsmd-workflow-efficiency-improvements
relation: connects_to
created_at: 2026-03-08 02:23:26
description:
Review verdict for the freshness-policy additions that were part of the workflow efficiency improvements rollout


from_id: review-verdict-freshness-policy-re-review-approved
to_id: review-verdict-knowledge-freshness-policy-approved
relation: connects_to
created_at: 2026-03-08 02:24:52
description:
Re-review of the same freshness policy changes previously approved, now with required structured output format


from_id: agentsmd-workflow-efficiency-improvements
to_id: calibration-quality-gates-research-round-2
relation: implements
created_at: 2026-03-08 02:30:17
description:
Implements the approved calibration package (review scoring, mutation/flaky guardrails, lead escalation triggers) into agent config prompts.


# timeline

timestamp: 2026-03-06 10:49:54
tool: understand
result_summary: 0 matches
affected_ids: []
params:
{"query":"Current OpenCode global config architecture, agent setup, command file format, and megamemory workflow expectations before implementing multi-agent orchestration changes","top_k":10}


timestamp: 2026-03-06 13:19:25
tool: understand
result_summary: 3 matches
params:
{"query":"workflow configuration for git commits, any existing auto-commit behavior or policies in this opencode setup"}

affected_ids:
["opencode-multi-agent-orchestration-config","workflow-slash-commands-for-agent-routing","lead-and-subagent-role-prompts"]


timestamp: 2026-03-06 13:20:19
tool: understand
result_summary: 3 matches
params:
{"query":"where to define workflow rules for git commit behavior in this config (agents, commands, docs)"}

affected_ids:
["workflow-slash-commands-for-agent-routing","opencode-multi-agent-orchestration-config","lead-and-subagent-role-prompts"]


timestamp: 2026-03-06 13:23:43
tool: understand
result_summary: 4 matches
params:
{"query":"documentation workflow policies and agent definitions; where to add new librarian subagent and required docs update rules"}

affected_ids:
["automatic-git-commit-workflow-policy","workflow-slash-commands-for-agent-routing","lead-and-subagent-role-prompts","opencode-multi-agent-orchestration-config"]


timestamp: 2026-03-06 13:28:55
tool: understand
result_summary: 5 matches
params:
{"query":"Lead agent delegation behavior issues and existing workflow guidance for when lead should delegate vs direct work"}

affected_ids:
["lead-and-subagent-role-prompts","workflow-slash-commands-for-agent-routing","librarian-documentation-subagent","automatic-git-commit-workflow-policy","opencode-multi-agent-orchestration-config"]


timestamp: 2026-03-06 14:04:20
tool: understand
result_summary: 6 matches
params:
{"query":"Rewrite commands/init.md to support both new and existing projects, including explorer-first detection, adaptive questions, scaffold behavior, docs review, megamemory update/create, and git handling.","top_k":10}

affected_ids:
["init-command-new-project-bootstrap","librarian-documentation-subagent","lead-and-subagent-role-prompts","workflow-slash-commands-for-agent-routing","automatic-git-commit-workflow-policy","opencode-multi-agent-orchestration-config"]


timestamp: 2026-03-06 14:05:08
tool: link
result_summary: linked init-command-new-project-bootstrap -> workflow-slash-commands-for-agent-routing
affected_ids: ["init-command-new-project-bootstrap","workflow-slash-commands-for-agent-routing"]
params:
{"from":"init-command-new-project-bootstrap","to":"workflow-slash-commands-for-agent-routing","relation":"implements"}


timestamp: 2026-03-06 14:05:08
tool: link
result_summary: linked init-command-new-project-bootstrap -> librarian-documentation-subagent
affected_ids: ["init-command-new-project-bootstrap","librarian-documentation-subagent"]
params:
{"from":"init-command-new-project-bootstrap","to":"librarian-documentation-subagent","relation":"depends_on"}


timestamp: 2026-03-06 14:05:39
tool: understand
params: {"query":"init command slash command project initialization scaffold"}
result_summary: 6 matches
affected_ids:
["init-command-new-project-bootstrap","workflow-slash-commands-for-agent-routing","lead-and-subagent-role-prompts","opencode-multi-agent-orchestration-config","automatic-git-commit-workflow-policy","librarian-documentation-subagent"]


timestamp: 2026-03-06 14:07:10
tool: understand
params: {"query":"/init command bootstrap project"}
result_summary: 6 matches
affected_ids:
["init-command-new-project-bootstrap","librarian-documentation-subagent","lead-and-subagent-role-prompts","workflow-slash-commands-for-agent-routing","opencode-multi-agent-orchestration-config","automatic-git-commit-workflow-policy"]


timestamp: 2026-03-06 14:55:52
tool: understand
params: {"query":"date format fix collection modal playwright testing github integration"}
result_summary: 6 matches
affected_ids:
["librarian-documentation-subagent","opencode-multi-agent-orchestration-config","automatic-git-commit-workflow-policy","workflow-slash-commands-for-agent-routing","init-command-new-project-bootstrap","lead-and-subagent-role-prompts"]


timestamp: 2026-03-06 15:38:09
tool: understand
result_summary: 6 matches
params:
{"query":"existing agent file style and conventions for reviewer and researcher agents, and any guidance for creating new subagent markdown files","top_k":10}

affected_ids:
["librarian-documentation-subagent","workflow-slash-commands-for-agent-routing","opencode-multi-agent-orchestration-config","lead-and-subagent-role-prompts","automatic-git-commit-workflow-policy","init-command-new-project-bootstrap"]


timestamp: 2026-03-06 15:38:36
tool: understand
result_summary: 5 matches
params:
{"query":"lead agent instructions in agents/lead.md and orchestration workflow requirements","top_k":5}

affected_ids:
["lead-and-subagent-role-prompts","librarian-documentation-subagent","opencode-multi-agent-orchestration-config","workflow-slash-commands-for-agent-routing","automatic-git-commit-workflow-policy"]


timestamp: 2026-03-06 15:39:00
tool: understand
result_summary: 6 matches
params:
{"query":"Update agent prompt files coder.md reviewer.md tester.md with pipeline sections, structured outputs, retry/adversarial protocols, and megamemory duties while keeping frontmatter unchanged.","top_k":10}

affected_ids:
["lead-and-subagent-role-prompts","librarian-documentation-subagent","init-command-new-project-bootstrap","workflow-slash-commands-for-agent-routing","automatic-git-commit-workflow-policy","opencode-multi-agent-orchestration-config"]


timestamp: 2026-03-06 15:39:33
tool: understand
result_summary: 9 matches
params:
{"query":"AGENTS.md policies, opencode.jsonc agent configuration, slash command files under commands/ including plan and sme patterns","top_k":10}

affected_ids:
["opencode-multi-agent-orchestration-config","sme-domain-consultant-subagent","workflow-slash-commands-for-agent-routing","designer-uiux-specialist-subagent","automatic-git-commit-workflow-policy","librarian-documentation-subagent","lead-and-subagent-role-prompts","critic-plan-gate-subagent","init-command-new-project-bootstrap"]


timestamp: 2026-03-06 15:39:37
tool: link
result_summary: linked lead-and-subagent-role-prompts -> opencode-multi-agent-orchestration-config
affected_ids: ["lead-and-subagent-role-prompts","opencode-multi-agent-orchestration-config"]
params:
{"from":"lead-and-subagent-role-prompts","to":"opencode-multi-agent-orchestration-config","relation":"connects_to"}


timestamp: 2026-03-06 15:39:49
tool: link
result_summary: linked lead-and-subagent-role-prompts -> workflow-slash-commands-for-agent-routing
affected_ids: ["lead-and-subagent-role-prompts","workflow-slash-commands-for-agent-routing"]
params:
{"from":"lead-and-subagent-role-prompts","to":"workflow-slash-commands-for-agent-routing","relation":"connects_to"}


timestamp: 2026-03-06 15:41:31
tool: link
result_summary: linked workflow-slash-commands-for-agent-routing -> critic-plan-gate-subagent
affected_ids: ["workflow-slash-commands-for-agent-routing","critic-plan-gate-subagent"]
params:
{"from":"workflow-slash-commands-for-agent-routing","to":"critic-plan-gate-subagent","relation":"depends_on"}


timestamp: 2026-03-06 15:41:31
tool: link
result_summary: linked workflow-slash-commands-for-agent-routing -> sme-domain-consultant-subagent
affected_ids: ["workflow-slash-commands-for-agent-routing","sme-domain-consultant-subagent"]
params:
{"from":"workflow-slash-commands-for-agent-routing","to":"sme-domain-consultant-subagent","relation":"depends_on"}


timestamp: 2026-03-06 15:41:31
tool: link
result_summary: linked lead-and-subagent-role-prompts -> sme-domain-consultant-subagent
affected_ids: ["lead-and-subagent-role-prompts","sme-domain-consultant-subagent"]
params:
{"from":"lead-and-subagent-role-prompts","to":"sme-domain-consultant-subagent","relation":"depends_on"}


timestamp: 2026-03-07 21:27:06
tool: understand
result_summary: 3 matches
params:
{"query":"Current workflow configuration, planning process, and any prior decisions about spec-driven development tools like OpenSpec or issue trackers like Linear","top_k":3}

affected_ids:
["swarm-inspired-agent-upgrade","workflow-slash-commands-for-agent-routing","agentsmd-workflow-efficiency-improvements"]


timestamp: 2026-03-07 21:29:25
tool: understand
result_summary: 3 matches
params:
{"query":"Any existing decisions about OpenAI Symphony, OpenAI multi-agent orchestration, or external orchestration framework adoption criteria for this OpenCode config","top_k":3}

affected_ids:
["opencode-multi-agent-orchestration-config","openspec-and-linear-fit-assessment","swarm-inspired-agent-upgrade"]


timestamp: 2026-03-07 21:37:18
tool: understand
params: {"query":"session analysis findings agent orchestration improvements","top_k":3}
result_summary: 3 matches
affected_ids:
["swarm-inspired-agent-upgrade","agentsmd-workflow-efficiency-improvements","lead-and-subagent-role-prompts"]


timestamp: 2026-03-07 21:39:35
tool: understand
result_summary: 3 matches
params:
{"query":"Current guidance and conventions for editing AGENTS.md and agents/lead.md, especially megamemory query discipline, clarification rule, delegation trust, and parallelization mandate wording","top_k":3}

affected_ids:
["lead-and-subagent-role-prompts","librarian-documentation-subagent","designer-uiux-specialist-subagent"]


timestamp: 2026-03-07 21:40:10
tool: link
result_summary: linked agentsmd-workflow-efficiency-improvements -> lead-and-subagent-role-prompts
affected_ids: ["agentsmd-workflow-efficiency-improvements","lead-and-subagent-role-prompts"]
params:
{"from":"agentsmd-workflow-efficiency-improvements","to":"lead-and-subagent-role-prompts","relation":"connects_to"}


timestamp: 2026-03-07 21:40:49
tool: understand
result_summary: 3 matches
params:
{"query":"AGENTS.md workflow efficiency improvements query discipline delegation trust clarification parallelization","top_k":3}

affected_ids:
["agentsmd-workflow-efficiency-improvements","lead-and-subagent-role-prompts","swarm-inspired-agent-upgrade"]


timestamp: 2026-03-07 21:43:06
tool: understand
result_summary: 3 matches
params:
{"query":"Fix stale unconditional megamemory instruction and heading hierarchy in AGENTS.md and lead.md; check exact target lines and prior decisions","top_k":3}

affected_ids:
["review-verdict-agentsmd-efficiency-edits-changes-requested","lead-and-subagent-role-prompts","agentsmd-workflow-efficiency-improvements"]


timestamp: 2026-03-07 21:43:30
tool: link
params:
{"from":"cleanup-of-stale-megamemory-wording-and-heading-levels","to":"review-verdict-agentsmd-efficiency-edits-changes-requested","relation":"implements"}

result_summary:
linked cleanup-of-stale-megamemory-wording-and-heading-levels -> review-verdict-agentsmd-efficiency-edits-changes-requested

affected_ids:
["cleanup-of-stale-megamemory-wording-and-heading-levels","review-verdict-agentsmd-efficiency-edits-changes-requested"]


timestamp: 2026-03-08 01:43:06
tool: understand
result_summary: 3 matches
params:
{"query":"AGENTS.md and agents/lead.md structure and prior workflow policy edits relevant to slimming AGENTS and adding enforcement/handoff/build/git/doc sections to lead","top_k":3}

affected_ids:
["lead-and-subagent-role-prompts","review-verdict-agentsmd-efficiency-edits-changes-requested","agentsmd-workflow-efficiency-improvements"]


timestamp: 2026-03-08 01:43:12
tool: understand
result_summary: 3 matches
params:
{"query":"agent configuration files for coder.md and tester.md operating rules and infrastructure unavailability section updates","top_k":3}

affected_ids:
["lead-and-subagent-role-prompts","review-verdict-agentsmd-efficiency-edits-changes-requested","cleanup-of-stale-megamemory-wording-and-heading-levels"]


timestamp: 2026-03-08 01:43:35
tool: understand
result_summary: 3 matches
params:
{"query":"OpenCode skills directory conventions and existing skill file patterns for SKILL.md format","top_k":3}

affected_ids:
["cleanup-of-stale-megamemory-wording-and-heading-levels","lead-and-subagent-role-prompts","automatic-git-commit-workflow-policy"]


timestamp: 2026-03-08 01:43:52
tool: understand
result_summary: 3 matches
params:
{"query":"doc-coverage skill file in ~/.config/opencode/skills and documentation workflow guidance","top_k":3}

affected_ids:
["automatic-git-commit-workflow-policy","opencode-multi-agent-orchestration-config","codertester-prompt-precision-rules-update"]


timestamp: 2026-03-08 01:44:57
tool: understand
params: {"query":"AGENTS.md slimdown and lead.md policy consolidation restructuring details","top_k":3}
result_summary: 3 matches
affected_ids:
["review-verdict-agentsmd-efficiency-edits-changes-requested","lead-and-subagent-role-prompts","agentsmd-slimdown-and-leadmd-policy-consolidation"]


timestamp: 2026-03-08 01:46:56
tool: understand
params: {"query":"AGENTS.md workflow improvements session analysis","top_k":3}
result_summary: 3 matches
affected_ids:
["agentsmd-workflow-efficiency-improvements","review-verdict-agentsmd-efficiency-edits-changes-requested","lead-and-subagent-role-prompts"]


timestamp: 2026-03-08 01:52:45
tool: understand
params: {"query":"agent configuration quality enforcement patterns rules prompts","top_k":3}
result_summary: 3 matches
affected_ids:
["lead-and-subagent-role-prompts","agentsmd-slimdown-and-leadmd-policy-consolidation","swarm-inspired-agent-upgrade"]


timestamp: 2026-03-08 02:02:30
tool: understand
params: {"query":"reviewer tester hardening improvements tier 1 tier 2 agent configuration","top_k":3}
result_summary: 3 matches
affected_ids:
["reviewer-tester-effectiveness-research","swarm-inspired-agent-upgrade","lead-and-subagent-role-prompts"]


timestamp: 2026-03-08 02:03:02
tool: understand
params: {"query":"agent configuration hardening rules for critic explorer lead","top_k":3}
result_summary: 3 matches
affected_ids:
["lead-and-subagent-role-prompts","opencode-multi-agent-orchestration-config","codertester-prompt-precision-rules-update"]


timestamp: 2026-03-08 02:03:03
tool: understand
result_summary: 3 matches
params:
{"query":"reviewer agent config structure, verdict taxonomy, output format headings, review lenses","top_k":3}

affected_ids:
["reviewer-tester-effectiveness-research","critic-plan-gate-subagent","lead-and-subagent-role-prompts"]


timestamp: 2026-03-08 02:03:06
tool: understand
result_summary: 3 matches
params:
{"query":"tester.md and coder.md agent prompt rules structure and recent precision updates","top_k":3}

affected_ids:
["codertester-prompt-precision-rules-update","review-verdict-agentsmd-efficiency-edits-changes-requested","agentsmd-workflow-efficiency-improvements"]


timestamp: 2026-03-08 02:03:39
tool: link
result_summary: linked codertester-prompt-precision-rules-update -> reviewer-tester-effectiveness-research
affected_ids: ["codertester-prompt-precision-rules-update","reviewer-tester-effectiveness-research"]
params:
{"from":"codertester-prompt-precision-rules-update","to":"reviewer-tester-effectiveness-research","relation":"connects_to"}


timestamp: 2026-03-08 02:04:03
tool: understand
params: {"query":"agent config hardening tier 1 tier 2 agent prompts","top_k":5}
result_summary: 5 matches
affected_ids:
["lead-and-subagent-role-prompts","swarm-inspired-agent-upgrade","tier-2-hardening-for-criticexplorerlead-agent-configs","agentsmd-slimdown-and-leadmd-policy-consolidation","opencode-multi-agent-orchestration-config"]


timestamp: 2026-03-08 02:04:10
tool: understand
params: {"query":"Tier 1 hardening coder tester reviewer prompt precision rules","top_k":3}
result_summary: 3 matches
affected_ids:
["reviewer-tester-effectiveness-research","reviewer-config-tier-1-hardening","codertester-prompt-precision-rules-update"]


timestamp: 2026-03-08 02:07:21
tool: understand
result_summary: 3 matches
params:
{"query":"recent tier1 tier2 config hardening and pending polish items for lead.md and explorer.md","top_k":3}

affected_ids:
["review-verdict-tier-1-tier-2-agent-config-hardening-approved","tier-2-hardening-for-criticexplorerlead-agent-configs","agentsmd-workflow-efficiency-improvements"]


timestamp: 2026-03-08 02:08:08
tool: understand
params: {"query":"agentsmd workflow efficiency improvements agent quality gates calibration","top_k":5}
result_summary: 5 matches
affected_ids:
["agentsmd-slimdown-and-leadmd-policy-consolidation","swarm-inspired-agent-upgrade","lead-and-subagent-role-prompts","agentsmd-workflow-efficiency-improvements","review-verdict-tier-1-tier-2-agent-config-hardening-approved"]


timestamp: 2026-03-08 02:08:08
tool: understand
params: {"query":"reviewer tester agent metrics scoring rubrics","top_k":3}
result_summary: 3 matches
affected_ids:
["reviewer-tester-effectiveness-research","review-verdict-tier-1-tier-2-agent-config-hardening-approved","industry-agent-quality-patterns-research"]


timestamp: 2026-03-08 02:08:09
tool: understand
params: {"query":"AGENTS.md workflow efficiency improvements current patterns","top_k":5}
result_summary: 5 matches
affected_ids:
["review-verdict-agentsmd-efficiency-edits-changes-requested","agentsmd-slimdown-and-leadmd-policy-consolidation","lead-and-subagent-role-prompts","review-verdict-config-restructuring-approved","agentsmd-workflow-efficiency-improvements"]


timestamp: 2026-03-08 02:08:09
tool: understand
params: {"query":"reviewer tester strictness quality enforcement patterns","top_k":3}
result_summary: 3 matches
affected_ids:
["reviewer-tester-effectiveness-research","reviewer-config-tier-1-hardening","review-verdict-tier-1-tier-2-agent-config-hardening-approved"]


timestamp: 2026-03-08 02:09:04
tool: understand
result_summary: 3 matches
params:
{"query":"agentsmd-workflow-efficiency-improvements tier 1 tier 2 hardening gaps remaining","top_k":3}

affected_ids:
["agentsmd-workflow-efficiency-improvements","agentsmd-slimdown-and-leadmd-policy-consolidation","lead-and-subagent-role-prompts"]


timestamp: 2026-03-08 02:11:57
tool: understand
params: {"query":"calibration quality gates research round 2 improvements","top_k":3}
result_summary: 3 matches
affected_ids:
["calibration-quality-gates-research-round-2","review-verdict-tier-1-tier-2-agent-config-hardening-approved","industry-agent-quality-patterns-research"]


timestamp: 2026-03-08 02:12:08
tool: understand
result_summary: 2 matches
affected_ids: ["second-round-advanced-patterns-research","calibration-quality-gates-research-round-2"]
params:
{"query":"second round advanced patterns destructive operation mutation testing chain of verification","top_k":2}


timestamp: 2026-03-08 02:12:30
tool: understand
params: {"query":"second round advanced patterns research implementation status","top_k":5}
result_summary: 5 matches
affected_ids:
["swarm-inspired-agent-upgrade","second-round-advanced-patterns-research","lead-and-subagent-role-prompts","agentsmd-slimdown-and-leadmd-policy-consolidation","doc-coverage-skill"]


timestamp: 2026-03-08 02:19:28
tool: understand
result_summary: 3 matches
params:
{"query":"knowledge freshness loop for session reflections and stale-memory handling in agent configs","top_k":3}

affected_ids:
["swarm-inspired-agent-upgrade","lead-and-subagent-role-prompts","designer-uiux-specialist-subagent"]


timestamp: 2026-03-08 02:19:56
tool: understand
result_summary: 3 matches
params:
{"query":"agentsmd-workflow-efficiency-improvements knowledge freshness revalidation policy across lead critic researcher sme reviewer tester configs","top_k":3}

affected_ids:
["agentsmd-workflow-efficiency-improvements","swarm-inspired-agent-upgrade","lead-and-subagent-role-prompts"]


timestamp: 2026-03-08 02:21:20
tool: link
result_summary: linked agentsmd-workflow-efficiency-improvements -> reviewer-config-tier-1-hardening
affected_ids: ["agentsmd-workflow-efficiency-improvements","reviewer-config-tier-1-hardening"]
params:
{"from":"agentsmd-workflow-efficiency-improvements","to":"reviewer-config-tier-1-hardening","relation":"connects_to"}


timestamp: 2026-03-08 02:22:14
tool: understand
result_summary: 5 matches
params:
{"query":"freshness policy knowledge staleness revalidation megamemory recording query discipline","top_k":5}

affected_ids:
["agentsmd-workflow-efficiency-improvements","review-verdict-agentsmd-efficiency-edits-changes-requested","cleanup-of-stale-megamemory-wording-and-heading-levels","swarm-inspired-agent-upgrade","init-command-new-project-bootstrap"]


timestamp: 2026-03-08 02:23:49
tool: understand
result_summary: 5 matches
params:
{"query":"megamemory query recording discipline contradictions freshness semantics across agents","top_k":5}

affected_ids:
["review-verdict-agentsmd-efficiency-edits-changes-requested","cleanup-of-stale-megamemory-wording-and-heading-levels","agentsmd-workflow-efficiency-improvements","librarian-documentation-subagent","sme-domain-consultant-subagent"]


timestamp: 2026-03-08 02:25:11
tool: understand
params: {"query":"freshness policy stale hypothesis revalidation megamemory discipline","top_k":5}
result_summary: 5 matches
affected_ids:
["cleanup-of-stale-megamemory-wording-and-heading-levels","review-verdict-agentsmd-efficiency-edits-changes-requested","agentsmd-workflow-efficiency-improvements","init-command-new-project-bootstrap","review-verdict-knowledge-freshness-policy-approved"]


timestamp: 2026-03-08 02:26:54
tool: understand
result_summary: 3 matches
params:
{"query":"Apply approved 5-change package across agent configs for agentsmd-workflow-efficiency-improvements, including reviewer/tester calibration, lead triggers, and critic/explorer consistency","top_k":3}

affected_ids:
["agentsmd-slimdown-and-leadmd-policy-consolidation","lead-and-subagent-role-prompts","swarm-inspired-agent-upgrade"]


timestamp: 2026-03-08 02:30:17
tool: link
result_summary: linked agentsmd-workflow-efficiency-improvements -> calibration-quality-gates-research-round-2
affected_ids: ["agentsmd-workflow-efficiency-improvements","calibration-quality-gates-research-round-2"]
params:
{"from":"agentsmd-workflow-efficiency-improvements","to":"calibration-quality-gates-research-round-2","relation":"implements"}


timestamp: 2026-03-08 02:30:48
tool: understand
params: {"query":"agent configuration files, agent roster, reviewer tester coder changes","top_k":5}
result_summary: 5 matches
affected_ids:
["lead-and-subagent-role-prompts","opencode-multi-agent-orchestration-config","review-verdict-tier-1-tier-2-agent-config-hardening-approved","swarm-inspired-agent-upgrade","review-verdict-config-restructuring-approved"]


timestamp: 2026-03-08 02:31:01
tool: understand
params: {"query":"AGENTS.md workflow efficiency improvements 5-change package details","top_k":2}
result_summary: 2 matches
affected_ids:
["agentsmd-slimdown-and-leadmd-policy-consolidation","review-verdict-agentsmd-efficiency-edits-changes-requested"]


timestamp: 2026-03-08 02:32:45
tool: understand
params: {"query":"reviewer score range 1-9 gap rubric verdict guidance","top_k":3}
result_summary: 3 matches
affected_ids:
["review-verdict-5-change-package-edits-approved","review-verdict-freshness-policy-re-review-approved","review-verdict-knowledge-freshness-policy-approved"]


