/archer-supreme

Overview

The /archer-supreme command is the Prismatic Platform's ultimate authority operation -- a COSMIC CLEARANCE command designed for impossible missions that require unlimited resource allocation, cross-domain agent coordination, and strategic-tactical synthesis at the highest level. Named after the platform's Supreme Commander (GENERAL ARCHER), this command activates the full power of the Prismatic Platform's autonomous intelligence ecosystem, deploying all available agents with unlimited authority and whatever timeline is necessary to achieve success. It represents the highest level of operational capability in the platform's 210+ command arsenal.

The philosophical foundation of ARCHER SUPREME is the belief that no mission is truly impossible given sufficient intelligence, coordination, and resourcefulness. Where standard commands operate within defined scopes and authority boundaries, /archer-supreme transcends these limitations. It has authority to coordinate any combination of the platform's 400+ agents, access any data source, invoke any tool, and allocate any resource. This unlimited authority is paired with a structured five-phase execution methodology that ensures even the most complex operations maintain strategic coherence while adapting tactically to emerging challenges.

The command operates at SUPREME authority level and is executed by the archer-supreme agent itself -- the platform's most powerful autonomous intelligence. The agent brings strategic execution capabilities, expert domain knowledge across all platform domains, coordinated multi-agent workflow orchestration, and quality-assured deliverables. Critically, the command includes mandatory context management protocols that ensure complete mission documentation, session context persistence, and knowledge transfer. No ARCHER SUPREME mission is considered complete until its context has been fully saved for future reference and restoration.

Usage

/archer-supreme [MISSION] [RESOURCES]

Execute an Impossible Mission with Unlimited Resources

/archer-supreme "Achieve 100/100 quality score across all 99 umbrella applications"

Strategic Architecture Overhaul

/archer-supreme "Redesign the storage layer for 10x throughput" unlimited

Platform-Wide Security Hardening

/archer-supreme "Eliminate all security vulnerabilities and achieve OWASP Top 10 compliance"

Complex Multi-Domain Integration

/archer-supreme "Integrate KuzuDB graph database with all existing storage adapters"

Emergency Production Recovery

/archer-supreme "Diagnose and resolve production deployment failure on prismatic-prod.fly.dev"

Options and Parameters

Mission Classification

Authority and Access

Technical Implementation

The ARCHER SUPREME command executes through a structured five-phase methodology that provides strategic coherence while maintaining tactical flexibility. Each phase has defined objectives, time allocations, and mandatory outputs. The implementation emphasizes context management as a first-class concern -- mission context is loaded at startup, saved after each phase, and comprehensively archived at mission completion.

defmodule PrismaticCrisis.ArcherSupreme do
  @moduledoc """
  ARCHER SUPREME command handler - ultimate authority operation
  for impossible missions with unlimited resource allocation.
  Implements 5-phase execution with mandatory context management.
  """

  alias PrismaticCrisis.{MissionAssessment, StrategicSynthesis, Execution, Validation}
  alias PrismaticClaude.SessionContext

  @context_dir ".claude/session-context/"
  @archive_dir ".claude/reports/ARCHER-SUPREME-MISSION-ARCHIVE/"

  @spec execute(String.t(), String.t()) :: {:ok, map()} | {:error, term()}
  def execute(mission, resources \\ "unlimited") do
    with {:ok, context} <- phase_0_context_loading(mission),
         {:ok, assessment} <- phase_1_assessment(mission, context),
         {:ok, strategy} <- phase_2_strategic_synthesis(assessment),
         {:ok, result} <- phase_3_execution(strategy, resources),
         {:ok, validation} <- phase_4_validation(result),
         :ok <- phase_5_context_preservation(mission, validation) do
      {:ok, %{
        mission: mission,
        status: :completed,
        phases: 5,
        validation: validation,
        context_saved: true
      }}
    end
  end

  defp phase_0_context_loading(mission) do
    latest_context = SessionContext.load_latest(@context_dir)
    previous_missions = load_mission_archive(@archive_dir)

    {:ok, %{
      session_context: latest_context,
      previous_missions: previous_missions,
      mission: mission,
      platform_state: assess_current_state()
    }}
  end

  defp phase_1_assessment(mission, context) do
    assessment = MissionAssessment.analyze(%{
      mission: mission,
      impossibility_factors: classify_impossibility(mission),
      resource_requirements: estimate_resources(mission),
      innovation_requirements: identify_innovations(mission),
      agent_requirements: determine_agent_formation(mission)
    })

    save_phase_context(1, assessment)
    {:ok, assessment}
  end

  defp phase_5_context_preservation(mission, validation) do
    context_file = build_context_filename(mission)

    SessionContext.save(%{
      mission: mission,
      validation: validation,
      deliverables: validation.deliverables,
      decisions: validation.decisions,
      files_modified: validation.files_modified,
      restoration_instructions: generate_restoration_instructions()
    }, Path.join(@context_dir, context_file))

    :ok
  end
end

The five execution phases provide a structured approach to impossible missions. Phase 0 (Context Loading, 5-10 minutes) loads the latest session context, reviews previous ARCHER SUPREME missions, and assesses the current platform state. Phase 1 (Mission Assessment, 0-30 minutes) performs situation analysis with unlimited agent coordination, classifies impossibility factors, estimates resource requirements, and identifies innovation needs. Phase 2 (Strategic Synthesis, 30-120 minutes) conducts strategic intelligence analysis, tactical execution planning, innovation strategy development, and multi-agent formation deployment. Phase 3 (Execution, variable duration) deploys all-agent coordination, implements real-time adaptation, monitors success metrics, and applies innovations as required. Phase 4 (Validation, 30-60 minutes) verifies success criteria, documents innovations, updates the mission pattern library, and confirms Archer-level confidence in the outcome. Phase 5 (Context Preservation, 15-30 minutes, MANDATORY) saves complete session context, creates mission archives, documents all deliverables, and writes restoration instructions.

The mandatory context preservation in Phase 5 is non-negotiable. A mission is not considered complete until its context has been saved to .claude/session-context/ with full details of objectives, actions taken, agents deployed, deliverables produced, decisions made, and instructions for future restoration.

Workflow Integration

The /archer-supreme command is reserved for scenarios where standard platform commands are insufficient to achieve the objective. This includes architectural overhauls spanning multiple applications, quality campaigns targeting the entire codebase, complex integrations requiring coordination across all platform domains, production emergencies requiring unlimited authority, and innovation initiatives that demand breakthrough approaches.

Before invoking ARCHER SUPREME, operators should verify that the mission genuinely requires unlimited authority. Many objectives that initially seem impossible can be achieved through standard commands like /orchestrate or /code. ARCHER SUPREME should be the last resort, not the first choice -- its power comes with the overhead of mandatory context management, multi-phase execution, and comprehensive documentation.

The command integrates tightly with the platform's session context system. Previous ARCHER SUPREME mission archives provide valuable institutional knowledge for future missions. The pattern library built from past missions enables the archer-supreme agent to apply proven strategies to new challenges, improving mission success rates over time.

Integration Points

Doctrine Compliance

All ARCHER SUPREME operations are governed by the NO MERCY, NO DOUBTS doctrine with elevated enforcement at SUPREME authority:

• NO MERCY: Missions are completed fully or not at all. There is no concept of partial success in ARCHER SUPREME operations. All five phases must execute to completion. Context preservation is mandatory and non-negotiable. Quality gates apply to every deliverable produced during the mission. Impossible is not an acceptable outcome -- the mission parameters include innovation authority specifically to enable breakthrough approaches when conventional methods are insufficient.
• NO DOUBTS: Phase 0 context loading ensures full understanding of the current state before action. Phase 1 assessment classifies impossibility factors with evidence-based analysis. Phase 4 validation verifies success criteria against concrete evidence. All decisions made during the mission are documented with rationale. The mission archive ensures that future operators can reconstruct the full decision chain and understand why each choice was made.

ARCHER SUPREME missions also enforce the NABLA Infinity Provenance Mandatory axiom at maximum strength: every claim, decision, and outcome produced during the mission must be traceable to specific evidence, analysis, or validated results. Unsubstantiated claims are never acceptable, regardless of the urgency of the mission.

Best Practices

1. Exhaust standard commands first: Before invoking ARCHER SUPREME, verify that the objective cannot be achieved through standard commands like /orchestrate, /code, or /fix. ARCHER SUPREME is designed for genuinely impossible missions, not routine tasks.

2. Define clear success criteria: Provide specific, measurable success criteria in the mission description. Vague missions like "improve the platform" lack the precision needed for effective Phase 4 validation. Concrete missions like "achieve 100/100 quality score" enable definitive success verification.

3. Review previous mission archives: Before starting a new ARCHER SUPREME mission, check .claude/reports/ARCHER-SUPREME-MISSION-ARCHIVE/ for related previous missions. Institutional knowledge from past operations often accelerates current missions significantly.

4. Allow sufficient time: ARCHER SUPREME missions are not designed for speed. They are designed for completeness. The "WHATEVER NECESSARY" timeline authorization exists because quality and thoroughness take precedence over speed in impossible missions.

5. Verify context preservation: At mission completion, verify that the context file was written successfully and contains all necessary information for future restoration. The context file is the mission's permanent record and must be comprehensive.

6. Document innovations: When a mission produces novel approaches or breakthrough solutions, ensure these are captured in the mission archive and propagated to the platform's pattern library for reuse in future missions.

Related Commands

• /emergency - Emergency response and crisis management activation
• /archer-supreme-dx - ARCHER SUPREME Developer Experience optimization
• /dark-ops - NABLA structural crisis detection and dark operations analysis
• /orchestrate - Multi-agent orchestration for complex operations
• /agents - List and manage agent ecosystem with status monitoring
• /analyze - System architecture analysis with dependency mapping
• /aiad-auto-evolution - Self-evolving command specification with meta-evolution

Connect & Contribute

Created by Tomáš Korcak (korczis) | Open Source under GHL

• GitHub | GitLab | LinkedIn | Contact
• Developer Portal | Architecture | Meet the Creator