Athena

Use before any creative work, new features, architecture changes, or behavior modifications — explores intent, constraints, and design before implementation begins

Execute an implementation plan using the coordinator pattern — per task, dispatch implementer → spec-reviewer → code-quality-reviewer; per wave, synthesize and verify. Parallel where independent, sequential where dependent. Use when you have a plan ready to execute.

Use during brainstorming when visual content would help — mockups, wireframes, layout comparisons, architecture diagrams. Zero-dependency, no server required.

Systematic debugging with hypothesis tracking, evidence collection, and checkpoint management. Use when encountering any bug, test failure, or unexpected behavior — diagnoses before fixing.

Use when implementation is complete and you need to merge, create a PR, keep, or discard a branch — handles integration and cleanup after development work

Use when creating new Athena skills, editing existing skills, or building skills for any Claude Code plugin — guides skill authoring with TDD validation

Use when starting any conversation — ensures Athena workflow skills are considered before taking ANY action, including before clarifying questions. Loaded at session start via SessionStart hook.

Use when the user wants to temporarily disable Athena workflow routing and gates — pauses all auto-triggers and skill checks until /athena-resume is invoked

Design and plan implementation — explores requirements, proposes approaches, creates structured plans with dependency graphs and parallel execution waves. Use before building anything non-trivial.

Handle incoming code review feedback with technical rigor — verify suggestions before implementing, push back on incorrect feedback, never agree performatively. Use when receiving PR comments, review notes, or correction requests.

Use when the user wants to re-enable Athena workflow routing and gates after a /athena-pause — restores all auto-triggers and skill checks

Two-pass code review — first checks spec compliance (did we build what was asked?), then code quality (is it built well?). Use after implementing features or before merging.

Pre-ship verification and merge preparation — runs full test suite, checks for uncommitted changes, validates branch state, creates PR or merges. Use when work is complete and ready to ship.

Route tasks to the right Athena workflow — detects whether you need planning, building, debugging, reviewing, testing, or shipping and invokes the correct Athena skill automatically

Enforced test-driven development with red-green-refactor gates — test must fail before implementing, pass before refactoring, pass after refactoring. Use when implementing features or fixing bugs.

Standalone verification gate — runs before claiming work is complete, fixed, or passing. Evidence before assertions, always. Use mid-conversation when about to say "done" or "fixed", not just at ship time.

Use when starting feature work that needs isolation, before executing plans in parallel, or when working on multiple branches simultaneously — creates and manages git worktrees