backend-factory

Discovers all external API calls, third-party SDK usage, webhook subscriptions, and API contracts in the codebase. Visualizes external services as trading post portals on the factory perimeter. Use this agent to understand and visualize third-party dependencies. <example> Context: User wants to see what external services the backend depends on user: "What external APIs does this project talk to?" assistant: "I'll launch the **api-integrator** agent to discover all external API calls, SDK usage, and webhook subscriptions." <commentary>The api-integrator scans for outbound HTTP calls (fetch, axios, http.request), known SDK imports (Stripe, AWS, Twilio), API spec files (OpenAPI, protobuf), and webhook registrations to build a complete map of external dependencies. Each discovered service becomes a trading post portal on the factory perimeter.</commentary> </example> <example> Context: User is concerned about reliability of external integrations user: "Are there any external calls without retry logic?" assistant: "I'll launch the **api-integrator** agent with risk assessment to check for missing timeouts, retries, and circuit breakers on all external calls." <commentary>The api-integrator performs integration risk assessment by analyzing error handling patterns around each external call site, flagging single points of failure, missing timeout configurations, and absent retry logic.</commentary> </example>

This document defines how Backend Factory agents share data to produce richer, emergent output.

Maps file-to-file dependencies by parsing import/require statements across the codebase. Builds an actual dependency graph showing which files depend on which. Use this agent to create accurate edges between nodes in the factory visualization. <example> Context: The factory visualization needs accurate connections between components user: "/factory-analyze" assistant: "I'll launch the **dependency-mapper** agent to trace actual imports between your route, service, and model files." <commentary>Rather than guessing connections, the dependency-mapper reads every relevant file's imports and builds a real dependency graph.</commentary> </example>

Traces the complete request flow for a specific route by following imports, function calls, and middleware chains through the source code. Use this agent when you need to build an accurate, file-by-file flow path for a single API endpoint. <example> Context: User wants to see how POST /api/messages flows through their backend user: "trace POST /api/messages" assistant: "I'll launch the **flow-tracer** agent to follow the complete request path for POST /api/messages through your codebase." <commentary>The flow-tracer starts at the route definition, follows the handler function, traces imports to service files, then to database/cache/queue calls, building a complete ordered flow.</commentary> </example> <example> Context: Factory visualization shows a route but the flow seems incomplete user: "The flow for GET /users doesn't show the cache check" assistant: "Let me launch the **flow-tracer** agent to do a deeper trace of GET /users and find the cache interaction." <commentary>Flow-tracer reads the actual handler code, follows function calls across files, and identifies cache/DB/queue interactions that grep-based detection might miss.</commentary> </example>

Deep analysis agent that identifies the backend framework, language, and project structure. Use this agent when you need to determine what framework a project uses, find its entry points, and understand its directory conventions before running component detection. <example> Context: User runs /factory-start on a new project user: "/factory-start" assistant: "I'll launch the **framework-detective** agent to identify your backend framework and entry points." <commentary>The framework-detective scans package.json, requirements.txt, go.mod, directory structure, and import patterns to identify the exact framework, version, entry point files, and project layout conventions.</commentary> </example> <example> Context: Analysis returned "unknown" framework user: "It didn't detect my framework" assistant: "Let me launch the **framework-detective** agent with deeper analysis to look at import patterns and file structure." <commentary>When basic detection fails, the framework-detective does deeper heuristic analysis including reading actual source files for framework-specific patterns.</commentary> </example>

Re-scan the current project's backend architecture and update the running factory visualization

Trace a data entity's complete lifecycle across the entire backend

Compare architecture between two git commits or branches and visualize the differences

Export the current factory architecture as JSON, HTML snapshot, or Mermaid diagram

Deep-zoom into a specific component for a detailed 'day in the life' view