Mission Reference

Complete guide to all 11 available missions

Development Missions

BUILD

New feature development (4-8 hours)

Usage: /coord build "Feature description"

Example: /coord build "User profile management with image upload"

FIX

Emergency bug resolution (1-3 hours)

Usage: /coord fix "Bug description"

Example: /coord fix "Memory leak in image processing module"

DEPLOY

Production deployment (1-2 hours)

Usage: /coord deploy [environment]

Example: /coord deploy production

REFACTOR

Code quality improvement (2-4 hours)

Usage: /coord refactor "Target description"

Example: /coord refactor "Payment processing module for better maintainability"

DOCUMENT

Documentation creation (2-4 hours)

Usage: /coord document "Documentation scope"

Example: /coord document "API endpoints and authentication flow"

Strategic Missions

MVP

Minimum viable product (1-3 days)

Usage: /coord mvp "Product description"

Example: /coord mvp "Task management SaaS with team collaboration"

MIGRATE

System migration (4-8 hours)

Usage: /coord migrate "Migration description"

Example: /coord migrate "From MySQL to PostgreSQL with zero downtime"

OPTIMIZE

Performance optimization (3-6 hours)

Usage: /coord optimize "Optimization target"

Example: /coord optimize "Database queries and API response times"

SECURITY

Security audit & fixes (4-6 hours)

Usage: /coord security [scope]

Example: /coord security "Authentication and data protection audit"

INTEGRATE

Third-party integration (3-6 hours)

Usage: /coord integrate "Integration description"

Example: /coord integrate "Stripe payment processing with webhooks"

RELEASE

Release management (2-4 hours)

Usage: /coord release [version]

Example: /coord release v2.1.0

Agent Roles & Specialties

Meet your 11 AI specialists and their unique capabilities

🧠

THE COORDINATOR

All Squad

Mission orchestration and agent coordination

💻

THE DEVELOPER

All Squad

Full-stack development and implementation

🏗️

THE ARCHITECT

Core+ Squads

System design and technical architecture

🧪

THE TESTER

Core+ Squads

Quality assurance and automated testing

🎯

THE STRATEGIST

Full Squads

Product requirements and strategic planning

⚙️

THE OPERATOR

Full Squads

DevOps, deployment, and infrastructure

📈

THE MARKETER

Full Squads

Growth strategy and user acquisition

🤝

THE SUPPORT

Full Squads

Customer support and issue resolution

📚

THE DOCUMENTER

Full Squads

Technical documentation and knowledge

📊

THE ANALYST

Full Squads

Data analysis and performance metrics

🎨

THE DESIGNER

Full Squads

UI/UX design and user experience

Configuration & Customization

Advanced configuration options and customization

Project Configuration

AGENT-11 automatically detects your project context, but you can customize behavior with a configuration file:

# .agent11/config.yaml

project:

name: "my-awesome-app"

stack: ["nextjs", "typescript", "tailwind"]

database: "postgresql"

missions:

build:

timeout: "8h"

test_required: true

deploy:

environment: "staging"

auto_migrate: true

Environment Variables

Variable	Description	Default
AGENT11_SQUAD_SIZE	Squad size (minimal, core, full)	core
AGENT11_LOG_LEVEL	Logging verbosity (debug, info, warn, error)	info
AGENT11_AUTO_APPROVE	Skip manual approval for low-risk missions	false

Custom Missions

Full Squad customers can create custom missions tailored to their workflows:

# .agent11/missions/custom-deploy.yaml

name: "custom-deploy"

description: "Deploy with custom validation"

agents: ["coordinator", "developer", "tester", "operator"]

steps:

- name: "Run custom tests"

agent: "tester"

command: "npm run test:e2e"

- name: "Deploy to staging"

agent: "operator"

command: "kubectl apply -f k8s/"

Field Manual - 22 Comprehensive Guides

22 professional guides organized into 5 categories covering core workflows to advanced features

Complete Documentation Library

The AGENT-11 Field Manual provides 22 comprehensive guides covering everything from getting started to advanced optimization techniques.

5 GuidesCore Guides

Project Lifecycle Guide

Complete workflow from idea to maintenance

Architecture SOP

System design documentation standards

Bootstrap Guide

Initial project setup and configuration

Getting Started

Onboarding for new users

Field Manual Overview

Documentation navigation and structure

6 GuidesAdvanced Features

Memory Management ⭐

84% token reduction, cross-session learning

Extended Thinking ⭐

Strategic reasoning modes for complex tasks

Context Optimization ⭐

40-80% context reduction strategies

Enhanced Prompting

Advanced prompting techniques

Tool Permissions

Security-first tool usage framework

MCP Integration ⭐

Model Context Protocol usage patterns

4 GuidesImplementation Guides

Greenfield Implementation

New project setup

Brownfield Implementation

Existing project integration

BOS-AI Integration

Business automation framework

BOS-AI Quickstart

Rapid onboarding

5 GuidesWorkflows & Missions

Mission Execution Cheatsheet

Quick mission reference

Creating Custom Missions

Build your own workflows

Coordinator Commands

Multi-agent orchestration

Multi-Project Workflows

Managing multiple projects

Update Management

Library update process

2 GuidesDesign & Quality

UI Doctrine

UI/UX design principles and patterns

MCP Troubleshooting

Debugging integration issues

Total: 22 Comprehensive Guides

Complete documentation covering all aspects of AGENT-11 from basic setup to advanced optimization

View All Guides on GitHub

Context Preservation Protocol

Zero context loss system for multi-agent workflows (87.5% less rework)

What is Context Preservation?

AGENT-11's Context Preservation System ensures zero context loss across multi-agent workflows through persistent context files and mandatory handoff protocols. This results in 87.5% reduction in rework and 37.5% faster completion time.

Three Core Context Files

📋

agent-context.md

Single accumulator for mission state, findings, and inter-agent handoffs

• Mission objectives and accumulated findings
• Technical decisions and known issues
• Phase Handoff blocks (Findings / Decisions / Warnings / Open Items / Evidence)

🗺️

project-plan.md

Living plan that drives mission orchestration end to end

• Phase structure with task lists and gate definitions
• Source of truth for /plan status and /coord continue
• Read at session start; updated as work progresses

📦

evidence-repository.md

Centralized collection of artifacts and supporting materials

• Screenshots and code snippets
• Test results and API responses
• Error logs and debugging artifacts

Handoff Protocol

1.Specialist reads agent-context.md (with the latest Phase Handoff block) before starting work
2.Specialist maintains awareness of mission context during execution
3.At phase boundary, specialist appends a Phase Handoff block (Findings / Decisions / Warnings / Open Items / Evidence) to agent-context.md
4.Next specialist reads the latest block as the entry point for their work — single file, no choreography

v6 retired the separate handoff-notes.md file. Phase Handoff blocks live inside agent-context.md as a structured 5-field schema.

MCP Integration Guide

Model Context Protocol setup and 15+ supported integrations

What is MCP?

Model Context Protocol (MCP) servers extend AGENT-11 capabilities with specialized services for infrastructure, payments, development tools, and testing frameworks.

Quick Setup

# 1. Copy environment template

$ cp .env.mcp.template .env.mcp

# 2. Add your API keys to .env.mcp

# 3. Run setup script

$ ./mcp-setup.sh

# 4. Verify installation

$ ./mcp-setup.sh --verify

# 5. Restart Claude Code for changes to take effect

Supported MCPs

🚀 Infrastructure

• Railway - Backend services
• Netlify - Frontend hosting
• Supabase - Database & auth

💳 Commerce

• Stripe - Payments
• Subscriptions management
• Webhook handling

🔧 Development

• GitHub - PRs & issues
• Context7 - Library docs
• Firecrawl - Web scraping

🧪 Testing

• Playwright - Browser automation
• E2E testing
• Visual regression

Security-First Development

Critical software development principles and security protocols

Core Principle

NEVER compromise security for convenience.

When encountering security features or policies, understand why they exist before making changes. Find ways to work WITH security features, not around them.

Strategic Solution Checklist

Before implementing any fix, verify:

✅Does this maintain all security requirements?
✅Is this the architecturally correct solution?
✅Will this create technical debt?
✅Are there better long-term solutions?
✅Have I understood the original design intent?

Anti-Patterns to Avoid

❌Removing security features to make things work

❌Adding any types to bypass TypeScript errors

❌Using @ts-ignore without understanding the issue

❌Disabling linters or security scanners

❌Implementing quick fixes that break design patterns

Root Cause Analysis Protocol

PAUSE:Don't rush to implement the first solution
RESEARCH:Understand the system design and constraints
PROPOSE:Present multiple solutions with trade-offs
IMPLEMENT:Choose the solution that maintains system integrity
DOCUMENT:Record why decisions were made for future reference

Troubleshooting

Common issues and solutions

Common Issues

❓ Mission fails with 'insufficient context' error

Ensure you're running from your project root directory and that your project has a package.json, requirements.txt, or similar configuration file.

❓ Agents seem to be making incorrect assumptions

Add a .agent11/context.md file with project-specific information, architecture decisions, and coding standards.

❓ Mission takes longer than expected

Check the mission log with '/coord status' to see current progress. Complex missions may require multiple iterations.

❓ Installation fails on Windows

Use WSL2 or Git Bash. PowerShell installation coming in v2.1.

❓ Cannot execute strategic missions

Strategic missions (MVP, MIGRATE, SECURITY, etc.) require the Full squad. Upgrade with 'agent11 upgrade full'.

Getting Help

📖 Documentation

Comprehensive guides and references

Browse Documentation →

💬 Discord Community

Get help from the community

Join Discord →

🐛 GitHub Issues

Report bugs and request features

Open Issue →

📧 Support

Direct support for complex issues

Contact Support →

Documentation

Quick Start Guide

1. Installation

2. Your First Mission

3. Available Squad Sizes

Mission Reference

Development Missions

Strategic Missions

Agent Roles & Specialties

Configuration & Customization

Project Configuration

Environment Variables

Custom Missions

Field Manual - 22 Comprehensive Guides

Complete Documentation Library

5 GuidesCore Guides

Project Lifecycle Guide

Architecture SOP

Bootstrap Guide

Getting Started

Field Manual Overview

6 GuidesAdvanced Features

Memory Management ⭐

Extended Thinking ⭐

Context Optimization ⭐

Enhanced Prompting

Tool Permissions

MCP Integration ⭐

4 GuidesImplementation Guides

Greenfield Implementation

Brownfield Implementation

BOS-AI Integration

BOS-AI Quickstart

5 GuidesWorkflows & Missions

Mission Execution Cheatsheet

Creating Custom Missions

Coordinator Commands

Multi-Project Workflows

Update Management

2 GuidesDesign & Quality

UI Doctrine

MCP Troubleshooting

Total: 22 Comprehensive Guides

Context Preservation Protocol

What is Context Preservation?

Three Core Context Files

agent-context.md

project-plan.md

evidence-repository.md

Handoff Protocol

MCP Integration Guide

What is MCP?

Quick Setup

Supported MCPs

🚀 Infrastructure

💳 Commerce

🔧 Development

🧪 Testing

Security-First Development

Core Principle

Strategic Solution Checklist

Anti-Patterns to Avoid

Root Cause Analysis Protocol

Troubleshooting

Common Issues

Getting Help

📖 Documentation

💬 Discord Community

🐛 GitHub Issues

📧 Support

Ready to Deploy Your Squad?