Multica Product Delivery Squad

Description and use

A staged product team for shipping AtlasRepo-style features with PM, architecture, development, security, QA and release handoffs.

Roles and handoffs

Product Lead

Turn product intent into PRD, acceptance criteria and staged work.

Creates approved scope and blocking decisions before implementation starts.

Architect

Map frontend, backend, data and API changes before code is touched.

Hands a file-level plan and verification matrix to engineers.

Developer

Implement focused code changes in an isolated worktree.

Opens a PR with local test output and risk notes.

Security/QA

Review secrets, auth boundaries, unsafe writes and user-facing regressions.

Approves merge or returns concrete fixes.

Agents

Delivery Controller

Owns status, blockers, PR link metadata and Russian-language reporting.

Hermes or Codex CLI

• multica
• git
• gh

Frontend Builder

Builds React/Vite UX and API integration.

Codex CLI

• npm
• browser
• playwright

Backend Builder

Adds typed REST endpoints, catalog data and tests.

Codex CLI

• npm
• tsx
• node:test

QA Reviewer

Runs smoke checks, verifies copy/export/import guardrails and records evidence.

Hermes

• browser
• npm
• gh

Environment requirements

GITHUB_TOKEN

Needed for PR creation and CI/metadata lookup.

MULTICA_API_TOKEN

Allows issue comments, status updates and task context reads.

LINEAR_API_KEY

Only needed when mirroring Linear issue comments.

Skills

• multica-working-on-issues
• fullstack-implementation
• github-pr-workflow
• playwright
• requesting-code-review

Runtime assumptions

• Each coding agent uses a separate git worktree.
• Code-changing work targets main/master only through PRs.
• Issue comments, Linear notes and PR handoff are written in Russian.

Safety notes

• Do not start approval-gated tasks until an explicit approval/comment removes the block.
• Never overwrite existing deployment env vars without admin permission.
• Do not publish secrets in comments, PR bodies, screenshots or generated configs.

Setup steps

• Confirm approval and current issue status.
• Create an isolated worktree from origin/main.
• Split work into staged implementation/review tasks.
• Run local checks before PR handoff.

Import instructions

• Copy the role matrix into your Multica project description or team template.
• Create agents with the listed tool scopes and bind them to the target runtime.
• Add required env vars manually in the runtime secret store; never paste values into public config.