ennam-claude-agent-team

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.

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.

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.

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.

Organization-wide conventions for commit messages, branch naming, PR descriptions, and task communication. Loaded automatically by all Ennam plugins.