apex-methodology

<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: files under 100 lines (split at 90), 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). </objective> **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.** ...