Skip to content
Development
Skill

/nav-features

Show and toggle Navigator features. Auto-invoke when user says "show features", "enable/disable feature", "my navigator settings", or "configure navigator".

From plugin
navigator
23233 skills6 agents3 hooks
Install
$ npx -y skills add alekspetrov/navigator --skill nav-features --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/nav-features

Context preview

The summary Claude sees to decide when to auto-load this skill.

Show and toggle Navigator features. Auto-invoke when user says "show features", "enable/disable feature", "my navigator settings", or "configure navigator".

SKILL.md

nav-features.SKILL.md
name: nav-features
description: Show and toggle Navigator features. Auto-invoke when user says "show features", "enable/disable feature", "my navigator settings", or "configure navigator".
allowed-tools: Read, Write, Bash
version: 1.0.0

Navigator Features Skill

Display and toggle Navigator features with an interactive table. Helps users understand what's enabled and customize their setup.

When to Invoke

Invoke this skill when the user:

  • Says "show my features", "navigator features", "what features are enabled"
  • Says "enable [feature]", "disable [feature]", "turn on/off [feature]"
  • Says "configure navigator", "my navigator settings"
  • Asks "what can navigator do?", "what features are available?"

**DO NOT invoke** if:

  • User is asking about project features (not Navigator)
  • User is in middle of implementation
  • Just starting session (use nav-start instead)

Execution Steps

Step 1: Read Current Configuration

PLUGIN_DIR="${CLAUDE_PLUGIN_ROOT:-$HOME/.claude/plugins/cache/navigator-marketplace/navigator}"
[ -d "$PLUGIN_DIR" ] || PLUGIN_DIR="$HOME/.claude/plugins/marketplaces/navigator-marketplace"
python3 "$PLUGIN_DIR/skills/nav-features/functions/feature_manager.py" show

This displays the feature table (one row per configurable Navigator feature, current version's number in the header):

v<version> Features:

┌─────────────────────────┬────────┬───────────────────────────────────────────────┐
│ Feature                 │ Status │ Description                                   │
├─────────────────────────┼────────┼───────────────────────────────────────────────┤
│ task_mode               │ [x]    │ Auto-detects task complexity, defers to sk... │
│ tom_features            │ [x]    │ Verification checkpoints, user profile, di... │
│ loop_mode               │ [ ]    │ Autonomous loop execution (enable when nee... │
│ simplification          │ [x]    │ Post-implementation code cleanup with Opus    │
│ auto_update             │ [x]    │ Auto-updates on session start                 │
│ knowledge_graph         │ [x]    │ Unified project knowledge + experiential m... │
│ multi_agent             │ [x]    │ Parallel agent orchestration (nav-multi sk... │
│ multi_claude_scripts    │ [*]    │ External shell scripts for multi-Claude wo... │
│ compact_hook            │ [x]    │ Injects rich summary into compacted sessions  │
│ workflow_enforcer_hook  │ [x]    │ Enforces WORKFLOW CHECK block before task ... │
│ read_guard_hook         │ [x]    │ Warns on excessive Reads (push to agents)     │
│ workflow_state_hook     │ [x]    │ Tracks current task/phase across the session  │
│ task_graph_sync_hook    │ [x]    │ Auto-syncs task files into the knowledge g... │
│ profile_sync_hook       │ [x]    │ Auto-captures preferences/corrections into... │
│ dispatcher              │ [x]    │ Single hook dispatcher runtime (nav_dispat... │
│ tier1                   │ [ ]    │ Zero-token answers for whitelisted prompts    │
│ stop_completion         │ [ ]    │ Completion gate on Stop (decision:block)      │
│ jit_memory              │ [ ]    │ Injects relevant memories after tool use      │
│ subagent_context        │ [ ]    │ Injects project context into subagents (2k)   │
│ failure_diagnosis       │ [ ]    │ Surfaces graph pitfalls on tool failures      │
│ config_guard            │ [x]    │ Warns when .nav-config.json edits break JSON  │
│ setup_hook              │ [x]    │ One-line runtime status on the Setup event    │
└─────────────────────────┴────────┴───────────────────────────────────────────────┘

All v<version> features configured.

Step 2: Handle Toggle Request (If Applicable)

If user requested to enable/disable a feature:

PLUGIN_DIR="${CLAUDE_PLUGIN_ROOT:-$HOME/.claude/plugins/cache/navigator-marketplace/navigator}"
[ -d "$PLUGIN_DIR" ] || PLUGIN_DIR="$HOME/.claude/plugins/marketplaces/navigator-marketplace"
# Enable a feature
python3 "$PLUGIN_DIR/skills/nav-features/functions/feature_manager.py" enable task_mode

# Disable a feature
python3 "$PLUGIN_DIR/skills/nav-features/functions/feature_manager.py" disable loop_mode

**Supported features**:

Core (config-toggled):

  • `task_mode` - Unified workflow orchestration
  • `tom_features` - Theory of Mind (verification checkpoints, profile, diagnostics)
  • `loop_mode` - Autonomous loop execution
  • `simplification` - Code cleanup before commit
  • `auto_update` - Auto-update on session start
  • `knowledge_graph` - Unified project knowledge + memories (v6.0.0)
  • `multi_agent` - Parallel agent orchestration via `nav-multi` (v6.0.0)

Hooks (config-toggled, edit with caution):

  • `compact_hook` - Pre-compact summary injection
  • `workflow_enforcer_hook` - Mandatory WORKFLOW CHECK block (disabling weakens guardrails)
  • `read_guard_hook` - Anti upfront-loading guard
  • `workflow_state_hook` - Tracks task/phase across the session
  • `task_graph_sync_hook` - Auto-syncs tasks into knowledge graph
  • `profile_sync_hook` - Auto-captures profile corrections

v7 hooks runtime (config-toggled; new blocking/injecting features ship OFF):

  • `dispatcher` - Single hook dispatcher runtime (`nav_dispatch`); ON by default —

disabling turns off ALL hook ops at once

  • `tier1` - Zero-token answers for whitelisted prompts (per-rule flags live under

`tier1.rules.*` in `.agent/.nav-config.json`; edit those directly)

  • `stop_completion` - Completion gate on Stop via decision:block

(`stop_completion.continue_enabled` stays false; `max_continues` caps at 2)

  • `jit_memory` - Just-in-time memory injection after tool use
  • `subagent_context` - Project context injection into subagents

(`subagent_context.budget_chars`, default 2000)

  • `failure_diagnosis` - Graph-pitfall injection on PostToolUseFailure (ships OFF)
  • `config_guard` - systemMessage warning on invalid `.nav-config.json` edits

(safety surface, ON by default)

  • `setup_hook` - One-line runtime status on the Setup event (safety surface,

ON by default)

Install-based:

  • `mu
Read more
Ships withnavigator

Finish What You Start Sessions that last. AI that learns. Features that ship.

Get the whole plugin

Other skills on navigator.