nav-sop

Generate Markdown Standard Operating Procedures with metadata from solved issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After solving novel issues, teams often forget patterns that could prevent repeat issues. This Skill creates Standard Operating Procedures (SOPs) to capture reusable solutions, decisions, and workflows.

Core Features & Use Cases

  • Reusable SOPs for integrations, debugging, development, and deployment.
  • Document symptoms, root cause, solution steps, and prevention so knowledge travels with the team.
  • Quickly generate a shareable SOP when you say something like "document this solution" or "save this for next time."

Quick Start

Say: "Create SOP for debugging test-failures" to generate a complete SOP file under .agent/sops/debugging/.

Frequently Asked Questions about nav-sop

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

FAQPage Schema
How do I capture and document solutions from issues we've solved?

Create Standard Operating Procedures (SOPs) that document symptoms, root causes, solution steps, and prevention measures from solved problems. This Skill automates SOP generation with metadata, Markdown formatting, and deduplication checks, so your team can quickly save and reuse patterns across debugging, development, and deployment workflows.

What should an SOP include to prevent repeat issues?

SOPs generated by this Skill include problem statements, prerequisites, step-by-step procedures, verification steps, troubleshooting guidance, related documentation links, and notes. This structure captures the full context around a solved issue so team members can follow the same approach without rediscovery.

How do I organize SOPs so the team can find them later?

SOPs are automatically categorized and stored in a structured directory (.agent/sops/) with metadata including title, category, and dates. This organization prevents duplication by checking existing SOPs and makes knowledge discoverable when similar problems arise.

Can I create an SOP immediately after solving a problem?

Yes. Say "Create SOP for [problem type]" and the Skill generates a complete SOP file instantly. It works for integrations, debugging, development, and deployment scenarios, capturing your solution while context is fresh.

What happens if an SOP for this problem already exists?

The Skill checks for duplicate SOPs before creation. If a matching SOP is found, it prevents redundant documentation and helps your team maintain a single source of truth for each workflow or solution pattern.

Why document workflows as SOPs instead of just remembering them?

SOPs make knowledge portable across team members and prevent recurring issues when people leave or change roles. By capturing decisions, root causes, and steps in one place, SOPs turn solved problems into reusable institutional knowledge.