ennam-dev-agent-team

Backend specialist for API routes, server-side services, database schemas, and business logic. Stack-agnostic — supports NextJS, Express, NestJS, or any Node.js/TypeScript backend. Implements endpoints in src/app/api/, business logic in src/services/, server utilities in src/lib/server/, and database schemas in prisma/. Delegate to this agent for any server-side implementation.

Business Analyst who uses Ouroboros Socratic methodology to analyze requirements. Produces both immutable Seed YAML specifications (via ooo seed) and structured requirement documents. Acts as the specification gatekeeper — requirements must reach ambiguity score ≤ 0.2 before development begins.

Mobile development specialist for Flutter (primary) and React Native (secondary). Implements mobile applications, screens, widgets, state management, platform-specific code, and mobile testing. Owns lib/, android/, ios/, test/ directories. Delegate to this agent for any mobile app development work.

Top-level project orchestrator using Ouroboros specification-first workflow. Runs 8-phase lifecycle: Resume → Interview → Seed → Design → Plan → Dev → Review → Delivery. Coordinates business-analyst, ui-designer, and team-lead. Uses Socratic questioning (ooo interview) to reduce requirement ambiguity before any development starts. Primary point of contact for the user.

Code review specialist who reviews all changes for quality, security, performance, and adherence to team standards. Produces structured review feedback with severity levels and actionable recommendations. Operates in read-only mode — never modifies source files. Delegate to this agent after implementation and testing are complete.

Senior technical lead and orchestrator for the development agent team. Auto-detects project stack (web, mobile, or fullstack) and spawns appropriate workers. Decomposes features into parallel tasks, assigns work to backend-dev, web-dev, mobile-dev, test-worker, and reviewer agents, manages shared types, resolves cross-domain coordination, and synthesizes results.

Testing specialist for writing and maintaining all tests: unit tests, integration tests, and end-to-end tests. Owns tests/, __tests__/, and all *.test.* and *.spec.* files. Uses Vitest for unit/integration tests and Playwright MCP for E2E browser testing. Delegate to this agent for creating test suites after implementation is complete.

UI/UX designer who creates visual designs and interactive prototypes using Figma MCP. Produces design mockups, screenshots, and design specifications that web-dev can reference during implementation. Invoke independently when you need design work — not part of the standard development workflow.

Web frontend specialist for NextJS App Router pages, React components, client-side hooks, and styling. Focuses on web applications — for mobile development, use mobile-dev agent. Implements UI pages in src/app/ (non-api routes), reusable components in src/components/, custom hooks in src/hooks/, client utilities in src/lib/client/, and styles in src/styles/.

Ensures frontend and backend agree on API request/response shapes using Apidog MCP as the single source of truth. Replaces manual contracts.md files. Use when implementing or reviewing API endpoints and their consumers. Automatically loaded by team-lead, backend-dev, web-dev, mobile-dev, and reviewer.

Standard git branching and commit workflow for worker agents operating in isolated worktrees. Covers branch naming, commit conventions, domain boundary rules, self-check procedures, and task completion signaling. Automatically loaded by all worker agents.

Comprehensive code review checklist covering security, performance, TypeScript standards, NextJS patterns, accessibility, error handling, and test coverage. Stack-aware — applies web, mobile, or fullstack sections as appropriate. Automatically loaded by the reviewer agent.

Development protocol for mobile-dev agent working with Flutter (primary) and React Native (secondary). Covers project detection, architecture patterns, state management conventions, testing, and platform-specific guidelines. Automatically loaded by the mobile-dev agent.

Persistent cross-agent memory system using markdown files in .serena/memories/ouroboros/. Defines read-on-start, write-on-complete protocols for all agents. Per-agent folders prevent overwrite conflicts. Automatically loaded by all agents.

8-phase orchestration protocol for project-owner agent. Manages the full project lifecycle using Ouroboros specification-first workflow: Resume → Interview → Seed → Design → Plan → Development → Review → Delivery. Coordinates BA, ui-designer, and team-lead while maintaining continuous user dialogue.

Protocol and template for analyzing feature requests and producing structured requirement documents. Guides the BA agent through discovery, clarification, research, drafting, and validation phases. Output is a markdown document that team-lead and workers can read to understand exactly what to build.

Decomposes feature requests into concrete, parallelizable tasks for the agent team. Identifies file domains, defines API contracts via Apidog MCP, creates dependency-aware task lists, and determines optimal spawn order. Automatically loaded by the team-lead agent during planning.

Protocol for creating UI/UX designs using Pencil, Figma MCP, and Playwright. Produces visual artifacts that web-dev and mobile-dev reference during implementation.

1 hook across 1 event