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