One-click install
npx skills add https://github.com/Navdeepgambhir9023/nav --skill use-nav-navdeepgambhir9023
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: use-nav
Source: https://github.com/Navdeepgambhir9023/nav/tree/main/skills/use-nav
Command: npx skills add https://github.com/Navdeepgambhir9023/nav --skill use-nav-navdeepgambhir9023

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agentic coding sessions often start cold, skip requirements clarification, and mark work done without independent verification. This Skill enforces a mandatory entry workflow for the Nav framework: it checks that a project Knowledge Base exists, then routes every non-trivial task through brainstorm, goal, plan, loop, and verify stages so work is provably done against a declared contract. ## Core Features & Use Cases - Mandatory KB Gate: Blocks all work until a kb/ Knowledge Base (product, architecture, principles, glossary, rules, decisions) exists, offering /kb-init or /kb-re-structure paths to create one. - Ordered Workflow Enforcement: Directs the agent through /brainstorm/goal/plan/loop/verify, with a skills inventory table explaining when to invoke each command, including /goal --research, /portfolio, /debt, and /meta-review. - Rule Namespaces and Guardrails: Distinguishes framework rules (NAV-R-00x), engine rules (.loop/memory/rules.md), and project rules (kb/rules.md), plus red-flag anti-patterns that signal skipped steps. - Use Case: A founder opens a new session to add a feature; the Skill halts until the KB exists, then walks the agent through clarifying the problem, defining a done-contract, decomposing a task DAG, executing in isolated worktree waves, and gating on independent verification. ## Quick Start Start a new task and ask the agent to use Nav to brainstorm, define a goal, plan, execute, and verify the work against the project knowledge base.

Frequently Asked Questions about use-nav

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

FAQPage Schema
How do I start a new task with the Nav framework?

Begin every session with the use-nav workflow: confirm a kb/ Knowledge Base exists, then run /brainstorm, /goal, /plan, /loop, and /verify in that order. Skipping steps or working without a KB is treated as the highest-cost mistake.

What is the correct order of Nav skills for a build task?

The mandatory sequence is /brainstorm to clarify the problem, /goal to define done as a contract, /plan to decompose into a task DAG, /loop to execute in waves, and /verify to prove done against six reviewer dimensions.

What happens if my project has no knowledge base?

The Skill stops all work and asks you to either run /kb-init to scaffold kb/product.md, architecture, principles, and glossary files, or dump existing docs and use /kb-re-structure to organize them. You may explicitly skip the KB, but the reason is documented.

Does Nav work with frameworks like React or Next.js?

Yes. Nav provides an architecture taste layer: kb/architecture-packs/<framework>.md feeds planning input to /plan, and skills/taste/<framework>/SKILL.md supplies runtime guardrails checked by a PreToolUse hook.

Can I run Nav headlessly without an interactive session?

Yes. The CLI supports nav run <goal-id> for headless /loop execution via claude -p, nav verify <goal-id> for headless verification, and nav doctor to check install health.

When should I use /goal --research instead of plain /goal?

Use /goal --research when validating a new-capability idea against the market (competitors, need, TAM, ICP, GTM) or researching prior art for a non-trivial technical problem before planning. Without the flag, /goal behaves as standard contract definition.