Skip to Content
ConfigurationPM & Team Chat

Project Management & Team Chat (project_management, team_chat)

Navigator can drive your workflow straight from a ticket and announce when work ships — or stay fully manual. Three keys in .agent/.nav-config.json control this. All default to a no-integration mode, so Navigator works out of the box with plain Markdown docs.

Config keys

{
  "project_management": "none",
  "task_prefix": "TASK",
  "team_chat": "none"
}
  • project_management — "linear" | "github" | "jira" | "gitlab" | "none". Where tickets live. "none" means tasks are tracked only as .agent/tasks/ Markdown docs (the default).
  • task_prefix — the ID prefix for generated task docs (default "TASK"). With prefix TASK, nav-task creates TASK-07-payments.md; set it to match your tracker (e.g. GH, PROJ) when you want IDs to line up with your PM tool.
  • team_chat — "slack" | "discord" | "none". Where completion notifications post. "none" (default) means no chat messages are sent.

PM-integrated workflow

When project_management is set to a real tool, the task lifecycle gains two endpoints — read the ticket in, close the ticket out:

read ticket  →  generate .agent/tasks/TASK-XX doc  →  implement
             →  close / comment on ticket  →  notify team chat (if configured)
  1. Read ticket via the configured PM tool (Linear MCP, gh, Jira API, glab).
  2. Generate plan — nav-task writes the implementation plan to .agent/tasks/, keyed by task_prefix.
  3. Implement following the plan.
  4. Close ticket — on completion the autonomous finish protocol comments on or closes the ticket in the PM tool.
  5. Notify — if team_chat is set, post a completion message to the channel.

With everything at "none", steps 1, 4 and 5 are skipped: you get a pure local-docs flow with no external calls.

Example

{
  "project_management": "github",
  "task_prefix": "GH",
  "team_chat": "slack"
}

This reads issues via the gh CLI, names task docs GH-XX-*.md, comments back on the issue when done, and posts a completion note to Slack.

Metrics

Navigator’s workflow is instrumented with OpenTelemetry. To see token and session-efficiency numbers for your own PM-integrated runs, run /nav:stats rather than relying on quoted figures.

Auto-UpdateOverview