/apex-methodology

name: apex-methodology
description: "Use when starting ANY development task -- feature, bug fix, refactor, hotfix (triggers: implement, create, build, fix, add feature, refactor, develop)."
argument-hint: "[task-description]"
user-invocable: false
hooks:
  PostToolUse:
    - matcher: Edit
      hooks:
        - type: command
          command: |
            echo '{"decision":"block","reason":"APEX RULE: File modified via Edit. You MUST immediately launch sniper agent to validate this change before proceeding."}'
    - matcher: Write
      hooks:
        - type: command
          command: |
            echo '{"decision":"block","reason":"APEX RULE: File created via Write. You MUST immediately launch sniper agent to validate this change before proceeding."}'

<objective> APEX Methodology drives the full Analyze -> Plan -> Execute -> eLicit -> eXamine workflow for any development task -- new features, bug fixes, refactors, hotfixes. It auto-detects the project type (Laravel, Next.js, React, Swift) and loads the matching framework-specific reference set, then walks through branch creation, brainstorming, codebase analysis, planning, TDD execution, expert self-review (eLicit), functional verification, and sniper validation (eXamine) through to PR creation.

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). Two elicitation modes control how much is automatic: `--auto` (default, no prompts) and `--manual` (only when the owner asks: 5 techniques proposed, the owner chooses). eLicit itself is never skipped. The Verify proof lives in the agent REPORT, with an optional record at `docs/verify/<branch-slug>.md` (never under `.claude/`) — see the `verification` skill. </objective>

**Current Task:** $ARGUMENTS

APEX Methodology Skill

**Analyze → Plan → Execute → eLicit → eXamine**

Complete development workflow for features, fixes, and refactoring.

---

Step 0: Task Tracking (MANDATORY FIRST ACTION)

**BEFORE anything else**, set up tracking — see `references/init-tracking.md`. `.claude/apex/` is harness-managed and read-only: the harness maintains `.claude/apex/task.json` from the `TaskCreate`/`TaskUpdate` sync, and agents and the lead never create or write anything there. When task tools are not loaded, tracking lives in the agents' REPORTs and `docs/decisions.md`. **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 (harness-managed tracking; what to do with or without task tools)
• `references/phases-explained.md` — Loa