nav-workflow

# Navigator Task Mode Skill Unified workflow orchestration that coordinates between skills, loop mode, and direct execution based on task complexity and type. ## Why This Exists Navigator had three disconnected workflow systems: 1. **Skills** (frontend-component, etc.) - have mini-workflows (Step 1 → Step 7) 2. **Loop Mode** - separate phase system (INIT → COMPLETE) 3. **CLAUDE.md** - documents workflow nobody enforces **Result**: Conflicts when multiple systems try to run. **Solution**: Task Mode acts as a coordinator - detecting when skills should handle workflow vs when to provide standalone phase guidance. ## How It Works ``` User Request ↓ TASK MODE (this skill) ├─ Simple task? → Direct execution (no overhead) ├─ Skill matches? → Let skill run (it has workflow) └─ Substantial, no skill? → Task Mode phases ``` ## When to Invoke **Auto-invoke when**: - User starts substantial work (3+ steps expected) - No obvious skill match (not "create component", "add endpoint", etc.) - Request involves planning, refactoring, or multi-file changes - Loop mode is disabled but structured execution needed **DO NOT invoke if**: - Trivial task (typo fix, single line change) - Skill will clearly handle it (component creation, endpoint, migration, etc.) - User says "quick", "just do", "simple fix" - Already in Task Mode or Loop Mode ## Configuration Task Mode settings in `.agent/.nav-config.json`: ```json { "task_mode": { "enabled": true, "auto_detect": t...