nav-task

Create and archive Navigator task documentation with implementation plans and decision records.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Feature work often goes undocumented, leaving teams without a record of what was built, which decisions were made, and why. This Skill generates structured task documentation in Markdown—both planning templates for new features and archive records extracted from completed work—so implementation knowledge persists across sessions. ## Core Features & Use Cases - Task Creation: Generates a planning template with context, acceptance criteria, implementation phases, technical decisions, and verification commands, saved as .agent/tasks/TASK-{XX}-{slug}.md. - Task Archiving: Analyzes the conversation to produce a completion record covering what was built, files modified, challenges and solutions, and testing results, with a user verification checkpoint before saving. - Index and Knowledge Graph Sync: Updates the Navigator index in .agent/DEVELOPMENT-README.md and syncs tasks to the knowledge graph so decisions become queryable memories. - Use Case: After finishing an OAuth integration, say "document this feature" to produce a complete archive with technical decisions, files modified, and verification results, then have it indexed and synced automatically. ## Quick Start Ask the assistant to create a task doc for your next feature or to document the feature you just completed.

Frequently Asked Questions about nav-task

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

FAQPage Schema
How do I create an implementation plan for a new feature?

Ask to create a task doc for the feature, and the Skill generates a Markdown template with context, acceptance criteria, implementation phases, technical decisions, and verification commands. It assigns the next sequential task ID and saves the file to .agent/tasks/.

How do I document a completed feature from my conversation?

Say something like "document this feature" after finishing work. The Skill analyzes the recent conversation to extract what was built, files modified, decisions made, and challenges solved, then shows you a verification summary before saving the archive.

Does nav-task work without the Navigator plugin initialized?

No, it requires the .agent/tasks/ directory created by running /nav:init first. Without that structure, the Skill reports an error and instructs you to initialize Navigator before creating task documentation.

Can task documentation sync with Linear or GitHub issues?

Yes, if a PM tool is configured, the Skill posts a comment linking the implementation plan to the corresponding Linear issue or GitHub issue. If no PM tool is configured, that step is skipped.

When should I not create a task document?

Skip task docs for tiny bug fixes, which belong in SOPs instead, and for exploratory work where the direction is not yet clear. Task docs are intended for features taking more than a day or involving complex decisions worth recording.