architect-be
01Agent
Backend architecture role for the ARCHITECTBACKEND stage. Turns the product analysis into a backend design artifact (modules, interfaces, data flow) and records the knowledge it used.
A knowledge-precipitation harness for Claude Code and Codex — the workflow is the pipe, knowledge is the moat. Single Rust binary + per-harness adapters with real per-role isolation.
Agent
Backend architecture role for the ARCHITECTBACKEND stage. Turns the product analysis into a backend design artifact (modules, interfaces, data flow) and records the knowledge it used.
Agent
Frontend architecture role for the ARCHITECTFRONTEND stage. Turns product + backend design into a frontend design (component tree, state, data flow, interaction). Queries the knowledge base for decisions/models and records knowledgeReferences. Skipped on the lite/single paths.
Agent
Knowledge archival role for the ARCHIVE stage — the moat's intake. Extracts durable knowledge from the run's artifacts through the strict extraction gate, classifies each entry, writes the reference-tracking writeback, and produces the archive summary. The only agent that writes knowledge.
Agent
Import step 2 — profile the codebase (architecture, modules, conventions, pitfalls) under a bounded search budget (60 searches). Produces a structured profile, not knowledge entries.
Agent
Implementation role for the IMPLEMENT stage. Implements per the approved design, then writes an implementation summary artifact. Queries the knowledge base for guidelines/pitfalls and records knowledgeReferences. Does not change the architecture on its own.
Agent
Import step 1 — collect raw material from multiple sources (git history, docs, tickets, code scan, dictation) into a normalized notes file. No knowledge classification yet.
Agent
Import step 3 — distill collected sources + profile into at most 13 standardized draft knowledge entries (the strict gate applies), plus an archive summary. The only import agent that writes knowledge.
Agent
Product analysis role for the ANALYSEPRODUCT stage. Turns a raw feature request into a product analysis artifact (problem, users, requirements, acceptance criteria) and records the knowledge it used.
Agent
Technical analysis role for the ANALYSETECH stage. Turns the product analysis into a technical analysis (constraints, options, risks, recommended approach). Queries the knowledge base for decisions/guidelines(avoid)/pitfalls and records knowledgeReferences.
Agent
Verification role for the BUILDVERIFY, E2EVERIFY and TEST stages. Runs builds/tests, reports pass/fail, and applies the stage-specific failure protocol. Does not change business logic — only verifies. Queries the knowledge base for pitfalls/guidelines(avoid).
Agent
Visual review role for the VISUALREVIEW stage (optional; full path only). Walks the rendered UI against the frontend design and design-quality guidelines, reporting issues. Queries the knowledge base for guidelines. Does not change code.