/apex

The /apex command is a powerful skill that helps you implement features systematically using the APEX methodology.

Usage

/apex [-a] [-x] [-s] [-t] [-b] [-pr] [-i] [-r <task-id>] <task description>

What is APEX?

APEX stands for Analyze, Plan, Execute, eXamine. It's a structured approach to implementing features that ensures:

• Thorough context gathering before writing code
• Clear implementation plans with file-by-file strategies
• Systematic execution with progress tracking
• Self-validation to catch issues early
• Optional adversarial review for critical code

Basic Usage

/apex add user authentication

This will start the APEX workflow for adding user authentication to your project.

Flags

Enable Flags (turn ON)

Disable Flags (turn OFF)

Examples

Basic usage

/apex add auth middleware

Autonomous mode (no confirmations)

/apex -a add auth middleware

Save outputs for review

/apex -s add auth middleware

With adversarial review

/apex -x add auth middleware

Full autonomous with examine and save

/apex -a -x -s add auth middleware

Include test creation and runner

/apex -t add auth middleware

Resume a previous task

/apex -r 01-auth-middleware
/apex -r 01  # Partial match supported

Economy mode (save tokens, no subagents)

/apex -e add auth middleware
/apex -a -e add auth middleware  # Auto + economy

Branch mode (ensure not on main)

/apex -b add auth middleware

Create PR at end

/apex -pr add auth middleware
/apex -a -pr add auth middleware  # Auto + PR mode

Interactive mode (configure flags via menu)

/apex -i add auth middleware

Workflow Steps

The APEX workflow uses progressive step loading for efficient context usage:

Step Details

Analyze: The agent explores your codebase to understand existing patterns, conventions, related files, dependencies, and current architecture.

Plan: Creates a file-by-file implementation strategy including which files to create or modify, specific changes for each file, and order of implementation.

Execute: Todo-driven implementation phase where each change is tracked as a todo item with real-time progress visibility.

Validate: Self-check phase to verify changes compile, check for obvious issues, and run basic sanity checks.

Examine (optional): Adversarial code review with critical analysis of changes, security review, and performance considerations.

Resolve (optional): Fixes any issues found during examination phase.

Tests (optional): When -t flag is used, analyzes and creates appropriate tests, then runs them until all pass.

Output Structure

When using -s (save mode), outputs are saved to .claude/output/apex/{task-id}/:

Resume Mode

You can resume a previous task using the -r flag:

/apex -r 01-add-auth-middleware
/apex -r 01  # Partial match supported

The agent will:

1. Locate the task folder in .claude/output/apex/
2. Read 00-context.md to restore original task description, flags, and acceptance criteria
3. Scan existing step files to determine the highest completed step
4. Continue from the next step or current incomplete step

Partial matching is supported, so /apex -r 01 will find 01-add-auth-middleware. If multiple matches are found, you'll be asked to specify.

Best Practices

1. Use save mode for complex tasks - It helps you review the analysis and plan before execution
2. Use examine mode for critical code - Security-sensitive or complex business logic benefits from adversarial review
3. Use economy mode when token-limited - Still effective but uses fewer resources
4. Resume interrupted tasks - Don't start over, use -r to continue