Skip to Content
Skillsnav-task

nav-task

Creates and archives Navigator task documentation — implementation plans that capture what was built, how, and why.

Triggers

Natural-language phrases that auto-invoke the skill:

  • “document this feature”
  • “archive this task”
  • “create task doc for…”
  • “document what I built”
  • “create implementation plan”
  • “update TASK-XX with…”

What it does

  • Resolves a task ID from your input, or generates one per task_id_source in .agent/.nav-config.json (v7.8.0): local (default) takes the next {prefix}-{number} from existing tasks; github creates the GitHub issue first and names the doc GH-<n>-{slug}.md, so two contributors branching at once can never collide (Pilot already addresses tasks as GH-<n>)
  • CREATE mode: writes an empty implementation-plan template (context, acceptance criteria, phases, technical decisions, verify/done) to .agent/tasks/TASK-XX-{slug}.md
  • ARCHIVE mode: reconstructs a completed-task record from the conversation (what was built, files changed, decisions, challenges, testing)
  • Runs a ToM verification checkpoint before committing an archive, since archive content is inferred from the session
  • Updates the Navigator index in .agent/DEVELOPMENT-README.md (active tasks first, completed below)
  • Syncs the task into the knowledge graph if present, extracting concepts and capturing Technical Decisions as decision memories
  • Comments on the linked Linear/GitHub ticket when a PM tool is configured

Example

"Document the auth feature I just finished"

Analyzes the session, generates TASK-06-auth.md with the full implementation record, updates the index, and (if configured) extracts decisions into the knowledge graph.

nav-triznav-sop