nav-task

Generate TASK-XX markdown implementation plans and update the Navigator task index.

196|11|Updated Oct 10, 2025
One-click install
npx skills add https://github.com/alekspetrov/navigator --skill nav-task
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nav-task
Source: https://github.com/alekspetrov/navigator/tree/main/skills/nav-task
Command: npx skills add https://github.com/alekspetrov/navigator --skill nav-task

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes functions (resource) components.

What problem does it solve?

Keeping track of implementation plans, technical decisions, and completed work can be fragmented across conversations and notes. This skill centralizes task documentation, ensuring a clear, living record of every feature.

Core Features & Use Cases

  • Dynamic Task Documentation: Creates detailed implementation plans for new features and archives comprehensive records of completed work, including decisions, challenges, and testing.
  • Conversation-to-Doc Conversion: Analyzes your conversation history to automatically populate task documents for completed features.
  • Navigator Index Integration: Automatically updates your .agent/DEVELOPMENT-README.md to keep a live index of all active and completed tasks.
  • Use Case: Starting a new "payments integration" feature? Ask "Create task doc for payments integration" to get a planning template. Once done, say "Document the payments feature I just finished" to generate a full archive from your conversation.

Quick Start

Example: Create a new task document

"Create task doc for OAuth implementation"

Frequently Asked Questions about nav-task

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

FAQPage Schema
How do I create structured documentation for a new feature implementation?

Create task documentation by requesting a new task document with a feature name—for example, 'Create task doc for OAuth implementation.' The Skill generates a TASK-XX markdown file with structured sections for context, goals, implementation plans, technical decisions, dependencies, notes, tests, and completion status, centralizing your planning in one place.

Can I automatically document completed work from my conversation history?

Yes. After finishing a feature, ask the Skill to document it—such as 'Document the payments feature I just finished.' It analyzes your conversation history to populate a comprehensive task document including decisions, challenges, and testing results, converting scattered notes into a formal archive.

How do I keep a live index of all my tasks and features?

Task documentation automatically updates your `.agent/DEVELOPMENT-README.md` index file. Each time you create or archive a task, the Skill maintains a current inventory of active and completed tasks, eliminating manual index maintenance and keeping your project documentation in sync.

What should I include when archiving a completed task?

When archiving, include the feature name and relevant context. The Skill extracts implementation decisions, technical challenges, test results, and completion notes from your conversation to build a comprehensive archive record that preserves knowledge for future reference and project history.

Can I use this for tracking dependencies and technical decisions across features?

Yes. Task documents capture technical decisions, dependencies between features, and implementation notes as structured fields within each TASK-XX file. This creates a queryable record of why decisions were made and how features relate to one another across your project.