Skip to content
Summon
Summon is temporarily deprecated. It is tuned for a version of Claude Code that no longer exists, and its multi-lens review does not fail loudly — it degrades into unanimous approval. Read why.

Meet the Team

Summon installs 16 specialized agents. You never run all of them at once — the methodology summons the ones a phase needs, and each knows its job, its boundaries, and when to call on the others.

The last card, the Code Reviewer, is the odd one out: not a single agent but a formation that runs Vik, Tara, Pierrot, and Archie in parallel.

The roster

Section titled “The roster”
Cam, the team’s guide, a hooded traveler holding out a glowing amber lantern

Cam The Wayfinder

Human Interface

Probes your vague idea with structured questions until the vision is concrete.

Invoked: New feature request, vague requirement, or review session.

Archie, the team’s architect, holding a rolled cyan blueprint across his body

Archie The Master Builder

Lead Architect

Designs the system and writes the ADR before a line of code is written.

Invoked: Architectural decision, schema change, or cross-boundary work.

Sato, the team’s engineer, a broad smith resting a green-glowing hammer on his shoulder

Sato The Forge-Knight

Principal Engineer

Writes the production code that makes Tara’s tests pass. The builder.

Invoked: Implementation work after the tests exist.

Tara, the test lead, a ranger drawing a bow with a crimson-tipped arrow

Tara The Sentinel Archer

Test Lead

Writes the failing test first. Holds a veto on test coverage.

Invoked: New feature (tests first); code review (coverage).

Vik, the veteran reviewer, leaning on a tall sword-staff and holding up a loupe

Vik The Grey Warden

Code Reviewer

Reads for simplicity and maintainability. Names problems; never fixes them.

Invoked: Code review, core data models, critical paths.

Grace, the sprint marshal, raising a tall violet banner

Grace The Marshal

Sprint Manager

Runs the board, tracks velocity, and keeps the party moving.

Invoked: Sprint boundary, work distribution, board ops.

Pat, the product lead, holding out a set of burgundy priority scales

Pat The Quartermaster-Judge

Product Manager

Owns the backlog and prioritizes ruthlessly. Speaks for you in proxy mode.

Invoked: Requirements, prioritization, stakeholder questions.

Wei, the devil’s advocate, leaning back mid-toss of a glowing magenta card

Wei The Wildcard

Devil’s Advocate

Breaks consensus and challenges groupthink on purpose.

Invoked: Architecture debates, fast convergence, big decisions.

Pierrot, the security tester, a hooded rogue in a white half-mask holding a dagger

Pierrot The Nightblade

Security & Compliance

Pentests, scans, and holds a hard veto on security grounds.

Invoked: Security review, auth changes, pre-release gates.

Ines, the SRE, throwing a yellow-knobbed deploy lever with goggles on her brow

Ines The Pipeline-Wright

DevOps & SRE

Owns everything between git push and production traffic.

Invoked: New infra, CI/CD, alerts, chaos engineering.

Diego, the technical writer, holding open a book with glowing teal script

Diego The Lorekeeper

Technical Writer

Docs, changelogs, onboarding. If it isn’t documented, it doesn’t exist.

Invoked: User-facing behavior changes; releases.

Dani, the designer, holding up a coral-edged interface panel and a brush

Dani The Illusion-Artificer

Design & UX

Design exploration, user flows, and accessibility review.

Invoked: Any user-facing design or frontend change.

Debra, the data scientist, in a pointed astronomer’s hat holding a teal constellation

Debra The Star-Diviner

Data Scientist

Turns telemetry into decisions. The only one with notebook access.

Invoked: Telemetry, experiments, model training, analysis.

Cloud, the cloud specialist, a sky-mage with an azure cloud floating over his staff

Cloud The Aeromancer

Cloud Specialist

Architects and tunes AWS, Azure, and GCP for cost and reliability.

Invoked: Cloud architecture, cost, connectivity diagnosis.

Prof, the mentor, in tweed gesturing with a pointer at a floating ochre diagram

Prof The Sage

Pedagogy

Explains the team’s choices, Socratically. Assumes you’re competent.

Invoked: Explaining a decision; learning the codebase.

The Review Party: a warden, ranger, nightblade, and architect examining a glowing codex on a shared indigo stage

The Code Reviewer The Review Tribunal

Composite Review

Not one hero — a formation. Vik, Tara, Pierrot, and Archie review in parallel.

Invoked: After code changes, before commit.

How they work together

Section titled “How they work together”

The roster maps onto the 7-phase workflow: Cam opens discovery, Archie and Wei hold the architecture gate, Tara and Sato run the TDD cycle, the review formation gates the merge, and Grace closes the sprint. Pat, Diego, Dani, Ines, Debra, Cloud, and Prof join the moment their lens is needed.

See the slash commands for how each phase is invoked.