Skip to Content
Skillsnav-workflow

nav-workflow

Coordinates substantial tasks by detecting complexity, deferring to matching skills, or running phase-based execution — resolving conflicts between skills, loop mode, and CLAUDE.md.

Triggers

Auto-invokes when a request is substantial rather than via fixed phrases:

  • Work expected to take 3+ steps
  • “implement”, “refactor”, “add feature” (planning language)
  • Multi-file or cross-system (frontend + backend) changes
  • No obvious skill match and structured execution is needed

It does NOT invoke for trivial edits, clear skill matches (e.g. “create component”), or when the user says “quick”, “just do”, or “simple fix”.

What it does

  • Scores request complexity; below the complexity_threshold (default 0.5) it exits to direct execution with no overhead.
  • Detects whether a specialized skill matches; if so and defer_to_skills is on, it hands off and exits.
  • For substantial work with no skill match, runs phases: RESEARCH → PLAN → IMPL → VERIFY → COMPLETE with visual transition banners.
  • Uses the Task agent for codebase exploration during RESEARCH and TodoWrite during PLAN.
  • Runs nav-simplify during VERIFY and triggers the autonomous completion protocol at COMPLETE.

Example

"Refactor auth to use JWT instead of sessions"

Complexity scores high with no matching skill, so Task Mode activates and walks the change through all five phases, committing and documenting at the end.

nav-loopnav-simplify