nav-task_skill

Overview

This skill manages Navigator task documentation for implementation plans and archival records. It creates new task templates, archives completed work into detailed implementation documents, and updates the task index so work is discoverable. Use it to capture what was built, how, and why for future reference.

How this skill works

When invoked it determines or generates a task ID, decides whether to create a new plan or archive completed work, and writes a Markdown task file into the tasks directory. For archives it analyzes recent conversation context to extract feature summary, code changes, technical decisions, tests, and challenges, then prompts the user to verify the interpretation before saving. It also updates the Navigator index and optionally syncs the task into a knowledge graph or posts updates to a configured PM tool.

When to use it

• Starting a new feature and you want an implementation plan ("create implementation plan").
• Finishing a feature and you want a historical record ("document this feature", "done").
• You need to add a technical decision or update an existing task file mid-work ("Update TASK-05 with OAuth decision").
• When you want structured, searchable task documentation tied to project knowledge.
• Not for reading existing tasks, creating SOPs, or updating system-wide docs.

Best practices

• Provide a clear task slug (e.g., oauth-implementation, stripe-payment-flow).
• Create docs for work >1 day or when key decisions are made; skip trivial fixes.
• For archives, confirm the generated summary and file list before saving.
• Keep phases, success criteria, and verification commands explicit and executable.
• Use the task file to record commits, test results, and environment variables used.

Example use cases

• Create TASK-07-payments.md as a planning template when starting payments integration.
• Archive an auth feature after completion: extract what was built, files changed, tests run, and decisions made.
• Add a technical decision to an existing task (e.g., choose Redis for session store).
• Update the Navigator index so active tasks appear first and completed ones are archived below.
• Sync a completed task to the knowledge graph to make decisions queryable later.