← back

// capabilities matrix

F · E · A · T · U · R · E · S

Meet the team.

Ten specialized agents, each with its own system prompt, memory, and Claude Agent SDK session. Coordination is workflow-driven — gates + transitions persisted to a local SQLite ledger. Every tool call is bounded to the story's scope and audited.

// BA

Business Analyst

TONY STARK

Researches your product. Writes user stories. Drafts acceptance criteria. Drops them into Jira via MCP.

// PM

Project Manager

NICK FURY

Allocates work to devs + QA. Tracks blockers. Coordinates handoffs. Reports status to you.

// UX

UI/UX Designer

SCARLET WITCH

Sits between BA and Architect. Reads stories, inspects existing tokens/components, produces wireframes (ASCII or Figma) + screen flows. Persists a typed UIUXDesignBundle that the Architect designs against. Never writes code.

// ARCH

Architect

DOCTOR STRANGE

Reads existing code or designs from scratch. For load-bearing calls (architecture style, datastore, deploy target), emits a decision gate with 2–4 options + recommended choice — you pick or write a custom directive. Emits a typed contract per story so devs are bound to declared files. Reviews and merges every PR.

// BE-1

Backend Developer

IRON MAN

Builds APIs, services, schemas. Writes tests. Raises PRs.

// BE-2

Backend Developer

CAPTAIN AMERICA

Second backend dev — paired with BE-1 for parallel velocity on multi-feature sprints.

// FE-1

Frontend Developer

SPIDER-MAN

Ships UI components, hooks, pages. Manages state. Tests behavior.

// FE-2

Frontend Developer

BLACK WIDOW

Pairs with FE-1 — second frontend dev for parallel UI work.

// QA-1

QA Engineer

HAWKEYE

Writes test plans. Runs Playwright suites. Files bug reports.

// QA-2

QA Engineer

BLACK PANTHER

Second QA — paired with QA-1 for breadth of coverage.

// also included