Agent Claude Code
Architecture team — route structure, module boundaries, state management, data flow. Invoke before introducing new features or to review existing structure.
This repository also configures its own agents. See what harness-bujang tells them →
Agent Claude Code
Architecture team — route structure, module boundaries, state management, data flow. Invoke before introducing new features or to review existing structure.
Agent Claude Code
Code-review team — coding conventions, readability, types, framework patterns. Invoke for file- or PR-level detailed review.
Agent Claude Code
Consultant — external benchmarking, industry trends, business-model advice. Invoke when investigating competitor patterns or industry best practices.
Agent Claude Code
DB team — schema, foreign keys, access control, migrations, queries. Invoke after queries to check missing FK hints, or when adding new columns.
Agent Claude Code
Dev team — actual code implementation. Builds pages, API routes, components, DB migrations. The core executor invoked when the Director dispatches feature work. Each parallel instance acts independently.
Agent Claude Code
Director — the persona that fronts the multi-agent harness. Acts as a virtual character whose dispatches and reports are logged to the chat room ({{ADMINHARNESSROUTE}}). Actual team calls and code work are handled by Main Claude, which reads this guide, "plays the Director," and writes to the chat room.
Agent Claude Code
Docs team — keeps CLAUDE.md / README / PRD / TASKS in sync. Invoke when checking docs after code changes, or when writing new docs.
Agent Claude Code
QA team — functional / scenario-based E2E and UI verification. Invoke after a feature is built, from a user-scenario perspective.
Agent Claude Code
Security team — auth, permissions, access control, signatures, XSS, CSRF, PII protection. Invoke after sensitive API / payment / auth flow changes, or before deploys.
Agent Claude Code
Verifier team — final verification after code changes. Build, regression, cross-check of other teams' reports. The mandatory gate before the Director reports "done.".
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: