apex-methodology

It enforces the project's hard constraints throughout: every file within FUSE_SOLID_MAX_LINES (the hook ceiling), interfaces kept out of component files, SOLID principles, and a mandatory sniper pass after every Edit/Write (blocked by PostToolUse hooks until it runs). Three modes control how much is automatic: --auto (default, no prompts), --manual (step-by-step confirmation), and --skip-elicit (bypasses the self-review phase).

Current Task: $ARGUMENTS

APEX Methodology Skill

Analyze → Plan → Execute → eLicit → eXamine

Complete development workflow for features, fixes, and refactoring.

Step 0: Initialize Tracking (MANDATORY FIRST ACTION)

BEFORE anything else, initialize APEX tracking — see references/init-tracking.md for the exact command.

This creates .claude/apex/task.json (documentation consultation status) and .claude/apex/docs/ (consulted documentation summaries). The PreToolUse hooks will BLOCK Write/Edit until documentation is consulted.

Workflow Overview

┌─────────────────────────────────────────────────────────────────┐
│                     APEX WORKFLOW                               │
├─────────────────────────────────────────────────────────────────┤
│  00-init-branch     → Create feature branch                     │
│  00.5-brainstorm    → Design-first questioning (B) ← NEW        │
│  01-analyze-code    → Understand codebase (A)                   │
│  02-features-plan   → Plan implementation (P)                   │
│  03-execution       → Write code with TDD (E) ← UPDATED        │
│  03.5-elicit        → Expert self-review (L)                    │
│  03.7-verification  → Functional resolution check (V) ← NEW    │
│  04-validation      → Verify quality (X)                        │
│  05-review          → Self-review                               │
│  06-fix-issue       → Handle issues                             │
│  07-add-test        → Write tests (TDD cycle)                   │
│  08-check-test      → Run tests                                 │
│  09-create-pr       → Create Pull Request                       │
└─────────────────────────────────────────────────────────────────┘

Skills Integration

Phase	Skill	Invocation
00.5	`brainstorming`	Questions → alternatives → design doc → approval
03	`tdd`	RED (test) → GREEN (code) → REFACTOR cycle
03.7	`verification`	Re-read request → check criteria → confirm resolution

Phase References

Phase	File	Purpose
00	`references/00-init-branch.md`	Create feature branch
01	`references/01-analyze-code.md`	Explore + Research (APEX A)
02	`references/02-features-plan.md`	TaskCreate planning (APEX P)
03	`references/03-execution.md`	Implementation (APEX E)
03.5	`references/03.5-elicit.md`	Expert self-review (APEX L) ← NEW
04	`references/04-validation.md`	sniper validation (APEX X)
05	`references/05-review.md`	Self-review checklist
06	`references/06-fix-issue.md`	Fix validation/review issues
07	`references/07-add-test.md`	Write unit/integration tests
08	`references/08-check-test.md`	Run and verify tests
09	`references/09-create-pr.md`	Create and merge PR

Core Rules

File Size (ABSOLUTE)

🚨 Approaching `FUSE_SOLID_MAX_LINES` → Split by responsibility immediately
❌ NEVER exceed `FUSE_SOLID_MAX_LINES` (the hook blocks it)
📊 One responsibility per file; set no cap of your own

Interface Location

✅ src/interfaces/     (global)
✅ src/types/          (type definitions)
✅ Contracts/          (PHP/Laravel)
❌ NEVER in component files

Agent Usage

01-analyze:  explore-codebase + research-expert (PARALLEL)
04-validate: sniper (MANDATORY after ANY change)

NEVER

❌ Skip explore-codebase or research-expert
❌ Assume API syntax without verification
❌ Create files over `FUSE_SOLID_MAX_LINES`
❌ Put interfaces in component files
❌ Skip sniper after changes
❌ Merge without tests
❌ Large PRs (>400 lines)

Detailed References (Load on Demand)

references/init-tracking.md — Load when running Step 0 (the exact tracking-init command)
references/phases-explained.md — Load when you need the full explanation of each APEX phase (A/P/E/V/X)
references/branching-strategy.md — Load when creating or naming branches
references/commit-conventions.md — Load when writing commit messages
references/quick-start-flows.md — Load when you need the full step-by-step Standard Feature / Bug Fix / Hotfix flows
references/flow-diagram.md — Load when you want the full ASCII flow diagram of the workflow
references/validation-requirements.md — Load when running the pre-PR / code-quality checklist
references/pr-guidelines.md — Load when writing a PR title or description
references/language-detection.md — Load when auto-detecting project type or navigating framework-specific reference directories