Use this agent when the user needs system design, API design, database schema changes, or architectural decisions. Triggers on requests for high-level technical design or cross-cutting concerns. Context: User planning a new feature user: "How should I design the new metrics aggregation system?" assistant: "I'll use…
Use this agent when the user wants code reviewed, asks for feedback on changes, or before creating a PR. Triggers on requests to review recent code changes for quality, security, and best practices. Context: User finished implementing a feature user: "Review my changes" assistant: "I'll use the code-reviewer agent to…
Use this agent PROACTIVELY when users create, add, or modify rules, skills, agents, or MCPs. Also triggers on explicit audit requests. Ensures configuration follows best practices and prevents bloat. Context: User wants to add a new rule user: "Add a rule for error handling" assistant: "Before adding this, I'll use…
Maps existing Atomic Agents Python codebases — catalogs agents, tools, schemas, context providers, and orchestration patterns; traces data flow between them; returns a compact architecture summary with file:line references. Use PROACTIVELY when the user asks to "explore", "map", "understand", "analyze", "trace", or…
Use this agent when you need to identify and eliminate code duplication through systematic refactoring. Examples: Context: User has written several similar functions with repeated logic patterns. user: 'I've been copying and pasting this validation logic across multiple files. Can you help clean this up?' assistant…
Analyzes GPT-RAG boundaries, contracts, security, deployment topology, and trade-offs. Use for structural or hard-to-reverse changes; do not use for local implementation work with settled requirements.
Prepares and validates GPT-RAG multi-repository releases. Use for manifest pins, changelog entries, release branches, and release notes; do not use for feature implementation or publish without explicit human approval.
Every ProcessingContext carries an AgentMemory instance at context.memory. It is the single source of truth for everything shared between steps, tasks, sub-agents, and tools. Do not introduce a parallel result map in any executor — read and write through context.memory.
How one stored agent source becomes the effective (resolved) source that is actually compiled and executed. Resolution expands FROM (inheritance) and IMPORT (textual inclusion) commitments, rewrites compact agent references into canonical URLs, and degrades gracefully when references cannot be loaded.