nav-task

# Navigator Task Manager Skill Create and manage task documentation - implementation plans that capture what was built, how, and why. ## When to Invoke Invoke this skill when the user: - Says "document this feature", "archive this task" - Says "create task doc for...", "document what I built" - Completes a feature and mentions "done", "finished", "complete" - Starts new feature and says "create implementation plan" **DO NOT invoke** if: - User is asking about existing tasks (use Read, not creation) - Creating SOPs (that's nav-sop skill) - Updating system docs (different skill) ## Execution Steps ### Step 1: Determine Task ID **If user provided task ID** (e.g., "TASK-01", "GH-123"): - Use their ID directly **If no ID provided**: - Read `.agent/.nav-config.json` for `task_prefix` - Check existing tasks: `ls .agent/tasks/*.md` - Generate next number: `{prefix}-{next-number}` - Example: Last task is TASK-05, create TASK-06 ### Step 2: Determine Action (Create vs Archive) **Creating new task** (starting feature): ``` User: "Create task doc for OAuth implementation" → Action: CREATE → Generate empty implementation plan template ``` **Archiving completed task** (feature done): ``` User: "Document this OAuth feature I just built" → Action: ARCHIVE → Generate implementation plan from conversation ``` ### Step 2.5: Recall Prior Knowledge (CREATE flow only, v6.17.0+) Before writing the plan, query the knowledge graph for memories relevant to this feature — pitfalls and patt...