nav-workflow

Orchestrates task execution by detecting complexity and deferring to matching skills or running phase-based workflows.

232|12|Updated Oct 10, 2025
One-click install
npx skills add https://github.com/qf-studio/navigator --skill nav-workflow-qf-studio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nav-workflow
Source: https://github.com/qf-studio/navigator/tree/main/skills/nav-workflow
Command: npx skills add https://github.com/qf-studio/navigator --skill nav-workflow-qf-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? When multiple workflow systems (skills, loop mode, documented conventions) coexist, they conflict over who controls execution, causing duplicated overhead or unstructured work on substantial tasks. ## Core Features & Use Cases - Complexity Detection: Scores incoming requests (0-1) using weighted signals like multi-file scope, planning language, and cross-system changes to decide between direct execution and structured phases. - Skill Deferral: Matches requests against available skills (e.g., "create component" → frontend-component) and hands off execution when a skill already owns the workflow. - Phase-Based Execution: Runs substantial unmatched tasks through RESEARCH, PLAN, IMPL, VERIFY, and COMPLETE phases with visual progress indicators. - Use Case: A request like "Refactor auth to use JWT" scores above the complexity threshold, matches no skill, so Task Mode activates and guides the work through all five phases with progress banners. ## Quick Start Ask the assistant to refactor the authentication system to use JWT and let Task Mode detect the complexity and orchestrate the phases.

Frequently Asked Questions about nav-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does Task Mode decide when to activate?

Task Mode runs a complexity detector that scores the request from 0 to 1 using weighted signals like multi-file scope, planning language, and cross-system changes. If the score exceeds the configured threshold (default 0.5) and no skill matches, Task Mode activates.

How do I configure the complexity threshold for task detection?

Set the task_mode section in .agent/.nav-config.json with options like enabled, auto_detect, defer_to_skills, complexity_threshold, and show_phase_indicator. Lowering complexity_threshold makes Task Mode activate on smaller tasks.

What is the difference between Task Mode and Loop Mode?

Task Mode provides lightweight phase guidance (RESEARCH through COMPLETE) without strict iteration gates, while Loop Mode enforces stagnation detection and an EXIT_SIGNAL for autonomous run-until-done work. Loop Mode can wrap Task Mode phases when both are active.

When does Task Mode defer to another skill instead of running?

When the skill detector matches the request to an available skill with sufficient confidence, such as "create component" matching frontend-component, Task Mode exits and lets that skill run its own workflow. Set defer_to_skills to false to override this.

When should I not use Task Mode for a request?

Skip Task Mode for trivial tasks like typo fixes or single-line changes, requests a dedicated skill clearly handles, or when the user asks for something quick. These cases route to direct execution or the matching skill instead.