nav-init

Say "Initialize Navigator" or "Set up Navigator" in your Claude Code session. The skill creates the .agent/ directory structure, copies templates, detects your project name and tech stack, and writes a .nav-config.json configuration file.

It reads manifest files in order: package.json, pyproject.toml, go.mod, Cargo.toml, composer.json, then Gemfile. Frameworks like Next.js, FastAPI, Gin, or Laravel are identified from declared dependencies, falling back to the directory name if nothing is found.

The skill checks for an existing .agent/ directory before doing anything. If found, it stops without overwriting and tells you the project is already initialized, so it is safe to run multiple times.

No. Since v6.13.0, lifecycle hooks ship with the plugin manifest instead of being merged into settings.json. The included settings merger is retained only for non-hook keys and preserves existing user hooks with atomic writes.

It creates .agent/ with subdirectories for tasks, system docs, sops (integrations, debugging, development, deployment), and grafana dashboards, plus a .nav-config.json, a DEVELOPMENT-README.md, and .gitignore entries for temporary Navigator files.