⚑PHASE 1 & 2 MODERNIZATION:Context Preservation β€’ Extended Thinking β€’ Professional Documentation

18 Proven Missions, One /coord Command

From emergency fixes to complete MVPs, execute complex development missions with project-local agents that understand your codebase.

Updated Β· covers v6.2.0

The 18 missions

πŸ—οΈ

BUILD

DevelopmentMedium to High

New feature development with full stack implementation

Duration
4-8 hours

Key Features

  • Full-stack feature implementation
  • Database schema design
  • API endpoint creation
  • +3 more features
🚨

FIX

DevelopmentLow to High

Emergency bug resolution and system recovery

Duration
1-3 hours

Key Features

  • Root cause analysis
  • Critical bug fixes
  • System stability restoration
  • +3 more features
πŸš€

MVP

StrategicHigh

Complete minimum viable product development

Duration
1-3 days

Key Features

  • Full product architecture
  • Core feature implementation
  • User interface design
  • +3 more features
🌐

DEPLOY

DevelopmentMedium

Production deployment and infrastructure setup

Duration
1-2 hours

Key Features

  • Production environment setup
  • CI/CD pipeline configuration
  • Domain and SSL setup
  • +3 more features
⚑

OPTIMIZE

StrategicMedium to High

Performance optimization and system tuning

Duration
2-6 hours

Key Features

  • Performance profiling
  • Database query optimization
  • Caching strategy implementation
  • +3 more features
πŸ”’

SECURITY

StrategicHigh

Security audit and vulnerability remediation

Duration
4-6 hours

Key Features

  • Security vulnerability scanning
  • Penetration testing
  • Authentication hardening
  • +3 more features
♻️

REFACTOR

DevelopmentMedium

Code quality improvement and technical debt reduction

Duration
2-4 hours

Key Features

  • Code structure improvement
  • Design pattern implementation
  • Dependency updates
  • +3 more features
πŸ“š

DOCUMENT

DevelopmentMedium

Comprehensive technical documentation creation

Duration
2-4 hours

Key Features

  • API documentation
  • Architecture guides
  • Setup instructions
  • +3 more features
πŸ”„

MIGRATE

StrategicHigh

System migration and technology stack upgrades

Duration
4-8 hours

Key Features

  • Data migration
  • Zero-downtime deployment
  • Rollback procedures
  • +3 more features
πŸ”Œ

INTEGRATE

DevelopmentMedium to High

Third-party service and API integration

Duration
3-6 hours

Key Features

  • API integration
  • Webhook handling
  • Error handling
  • +3 more features
πŸ“¦

RELEASE

StrategicMedium

Production release management and versioning

Duration
2-4 hours

Key Features

  • Version management
  • Release notes
  • Changelog generation
  • +3 more features
πŸ› οΈ

DEV-SETUP

Development

Development environment initialization for new projects

Duration
30-45 minutes

Key Features

  • Repository setup
  • Architecture documentation
  • Development tooling
  • +3 more features
🎯

DEV-ALIGNMENT

Strategic

Analyze and document existing codebase for team alignment

Duration
45-60 minutes

Key Features

  • Codebase analysis
  • Architecture review
  • Technical debt assessment
  • +3 more features
πŸ”—

CONNECT-MCP

Development

MCP server discovery, assessment and connection

Duration
45-90 minutes

Key Features

  • MCP requirement discovery
  • Server assessment
  • Credential and environment setup
  • +3 more features
πŸ”

RECON

StrategicHigh

UI/UX reconnaissance and interface assessment

Duration
2-4 hours

Key Features

  • Interaction and user-flow assessment
  • Responsive testing across viewports
  • Visual polish review
  • +3 more features
🌱

GENESIS

Strategic

Complete feature development from concept to production

Duration
1-3 days

Key Features

  • Requirements definition
  • Technical design
  • Full-team implementation
  • +3 more features
πŸ“

ARCHITECTURE

StrategicMedium

Create or update system architecture documentation

Duration
2-3 hours

Key Features

  • System design capture
  • Technology decisions and rationale
  • Data flow documentation
  • +3 more features
πŸ“‹

PRODUCT-DESCRIPTION

StrategicMedium

Comprehensive product description with risk management

Duration
2-3 hours

Key Features

  • Product definition
  • Target user and positioning
  • Feature inventory
  • +3 more features
πŸ›‘οΈNEW IN v6.2Loop Discipline

Agents cannot edit the gate files that judge them

The trust problem with autonomous agents is simple: an agent that can edit the test can pass the test. Gate files are unwritable at the tool layer. Anything outside them is instruction, not enforcement. Loops are watched first and merged by you.

πŸ”’

Read-only quality gates

Unwritable at the tool layer

The gate files, .quality-gates.json and gates/, are off limits at the tool layer. A test elsewhere that acts as acceptance criteria is not covered by any shipped rule.

  • Four Edit() rules in permissions.deny cover .quality-gates.json and **/*.quality-gates.json anywhere in the tree, plus gates/ and .gates/ at the repo root. Those two are root-anchored, so a nested packages/api/gates/ needs its own rule
  • A Bash guard hook blocks 12 common write forms against gate paths. It narrows the Bash route rather than closing it: the enforceable guarantee is the Edit() deny rules
  • Outside those paths, an agent is instructed not to touch the criteria. Nothing refuses it
βœ…

Default-fail verification

Evidence, not assertion

Every success criterion starts failing. It flips to pass only on captured command output. Claiming done is not enough: the agent has to show the run.

  • Criteria fail by default until proven
  • Pass requires real, captured output
  • No roleplayed completion
βš™οΈ

Ratchet mission-optimize

Keep-or-revert, you merge

Optimisation runs as a measured loop in an isolated git worktree. It keeps a change only if it beats a baseline and hard-reverts the rest. It never auto-merges, so you stay the judge.

  • Beat the baseline or get reverted
  • Every attempt logged, the loop caps itself
  • You decide at merge time
πŸ”

code-review-loop skill

Critic and fixer, separated

A read-only critic raises evidence-backed findings. A separate read-write fixer addresses only those findings. The pair re-audits until the work is clean or the loop caps out.

  • Critic and fixer default to different models. A critic sharing the generator's weights returns agreement rather than verification
  • Critic cannot edit the code it judges
  • Fixer addresses only raised findings
  • Re-audit until clean or capped
🚦

Phase-gated meta-loop

Advances on evidence only

/coord continue advances only on evidence and converges on two clean rounds. It spends a per-phase error budget, then escalates instead of grinding.

  • Converges on two clean rounds
  • Per-phase error budget, then escalates
  • Restarts from the last passed gate
πŸ—ΊοΈ

Map-first orientation

Locate before you read

On a large repo the expensive step is finding what to change, not changing it. Every one of the 11 specialists and 18 missions now carries the same stated rule: map the codebase first, then read narrowly.

  • Glob and Grep to locate, before opening a file
  • Read only the lines you need, not the whole file
  • Tokens spent on irrelevant files are the largest avoidable cost in a session

Phase 1 & 2 Modernization Features

Enterprise-grade capabilities for zero context loss and professional delivery

πŸ”„

Context Preservation System

Zero context loss

Zero context loss across multi-agent workflows. v6 consolidated tracking from 5 files to 3 for leaner, faster handoffs.

  • agent-context.md as the single accumulator for mission state
  • Phase Handoff blocks (Findings / Decisions / Warnings / Open Items / Evidence)
  • evidence-repository.md for artifacts
🧠

Extended Thinking

Deeper reasoning on demand

Three thinking modes for optimal decision-making: standard, think hard, and think harder for critical components.

  • Standard mode for routine tasks
  • Think hard for complex features
  • Think harder for security-critical code
πŸ“š

Field Manual

31 Guides

Professional-grade architecture documentation with comprehensive system design guides and best practices.

  • Architecture SOP templates
  • Security-first development principles
  • Production-ready templates
🎯

Memory Management

Persistent Knowledge

Agents learn and remember project patterns, technical decisions, and optimization insights across sessions.

  • Technical patterns storage
  • Decision history tracking
  • Lessons learned repository
πŸ”’

Security-First Architecture

Zero Compromises

Critical software development principles enforced at every level. Never compromise security for convenience.

  • Root cause analysis mandatory
  • Security feature validation
  • Strategic solution checklist
βš™οΈ

Tool Permission Framework

Agent-Specific Access

Granular tool permissions for each specialist agent, ensuring security and proper access control.

  • Role-based tool access
  • MCP integration support
  • Fallback strategies documented
🧭

Karpathy Constitution

Behavioural posture, not rules

Seven principles every specialist applies by default. Replaces ~150 lines of "always do X" prompt rules with a single posture that actually changes how agents work.

  • PAUSE-AND-PLAN before any non-trivial change
  • State assumptions out loud, prefer minimal diffs
  • Verify by running. Refuse to roleplay completion
πŸͺ

Quality-Gate Hooks

Enforced, not requested

v6 ships .claude/settings.json with native Claude Code hooks. Quality checks that used to be prompt suggestions are now real enforcement.

  • PostToolUse: tsc / ruff / rubocop on every Edit/Write
  • PreToolUse: confirmation for destructive Bash (rm -rf, force push, hard reset)
  • Auto-skip when toolchain is absent. Promote advisory to blocking with one flag
πŸ“š

3-Tier Skills Model

Aligned with Agent Skills standard

Skills are the unit of domain knowledge in v6. Aligned with Anthropic's open Agent Skills standard so they're portable across the ecosystem.

  • Tier 1: behavioural (loaded via CLAUDE.md)
  • Tier 2: project-domain (your own skills/ folder)
  • Tier 3: marketplace (7 SaaS skills shipped: auth, payments, multitenancy, billing, email, onboarding, analytics)

14 Slash Commands for Workflow Automation

Pre-configured workflows for common development scenarios

🎯
/coord

Mission Orchestration

Orchestrate multi-agent missions with systematic workflows. Execute build, fix, mvp, and more.

πŸ”
/recon

UI/UX Reconnaissance

Execute comprehensive UI/UX assessment using RECON Protocol for design audits.

🎨
/design-review

Design Review

Complete comprehensive design review of pending changes with systematic assessment.

πŸ”¬
/pmd

Post Mortem Dump

Analyze failures and suggest improvements with root cause analysis protocol.

πŸ“Š
/report

Progress Reports

Generate progress reports for stakeholders with metrics and accomplishments.

🀝
/meeting

Meeting Facilitation

Conversational meetings with AGENT-11 specialists for strategic discussions.

11 Specialist Agents with Proven Capabilities

Each agent has specific tool permissions and coordination protocols

🧠

THE COORDINATOR

All Squads

Mission orchestration and agent coordination. Manages task delegation and workflow execution.

πŸ’»

THE DEVELOPER

All Squads

Full-stack development and implementation. Ships clean, working code fast with tests.

πŸ—οΈ

THE ARCHITECT

Core+

System design and technical architecture. Plans scalable solutions and technology stack.

πŸ§ͺ

THE TESTER

Core+

Quality assurance and automated testing. Validates functionality and edge cases.

βš™οΈ

THE OPERATOR

Full Squad

DevOps, deployment, and infrastructure. Manages production environments and CI/CD.

🎯

THE STRATEGIST

Full Squad

Product requirements and strategic planning. Defines vision and execution roadmap.

🎨

THE DESIGNER

Full Squad

UI/UX design and user experience. Creates intuitive interfaces and design systems.

πŸ“š

THE DOCUMENTER

Full Squad

Technical documentation and knowledge base. Creates comprehensive guides and references.

πŸ“Š

THE ANALYST

Full Squad

Data analysis and performance metrics. Provides insights and optimization recommendations.

πŸ“ˆ

THE MARKETER

Full Squad

Growth strategy and user acquisition. Plans launches and marketing campaigns.

🀝

THE SUPPORT

Full Squad

Customer support and issue resolution. Handles user inquiries and feedback loops.

MCP Integration - Native Tool Search

AGENT-11 uses Claude Code's native tool-search primitive. Specialists discover MCP servers at runtime instead of loading a fixed list into every session, cutting context overhead and supporting long-running autonomous operation.

Native Tool Deferring (new in v6)

v6 retired the hand-rolled MCP profile system in favour of Claude Code's native primitive: ENABLE_TOOL_SEARCH=auto. Specialists discover MCP tools on demand instead of loading every tool into every session.

How it works
Threshold-based loading. Tools discovered via tool_search_tool_regex only when a task needs them.
Why it's better
No hand-maintained profile JSON. No /mcp-switch command. The framework gets out of the way.
What ships
.claude/settings.json ships with the flag enabled. No extra setup. Works on every fresh install.
On-demand
Tool Loading
Zero
Profile Maintenance

Tools load only when a task needs them, so the context budget goes back to the user's actual problem.

Advanced Capabilities

Enterprise-grade features for maximum efficiency and performance

🎯

Memory Management

Persistent Knowledge

Persistent file-based memory system that learns and remembers across sessions.

  • Cross-session learning

    Knowledge persists between restarts

  • Structured XML storage

    Clear, human-readable memory files

  • Long-running autonomous operation

    Memory keeps work going across sessions

🧠

Extended Thinking

Deeper Reasoning

Strategic reasoning modes for complex tasks requiring deep analysis.

  • 3 thinking modes

    Standard, think hard, and think harder

  • Strategic allocation

    Use deeper thinking where it matters most

  • Cost-optimized

    Match thinking depth to task complexity

⚑

Context Optimization

On-Demand Loading

Intelligent context management for optimal performance.

  • Native Tool Search

    Tools load via defer_loading only when needed

  • Strategic context clearing

    Preserve critical information

  • Memory integration

    Long-term knowledge persistence

  • Multi-session workflows

    Seamless pause and resume

Ready to Execute Your First Mission?

Deploy project-local agents that understand your codebase and execute missions with precision.