nav-sop

Creates Standard Operating Procedure markdown documents for reusable solutions and workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Solved a tricky bug or set up a complex integration? Without documentation, that knowledge disappears and your team repeats the same mistakes. This Skill captures solutions as structured Standard Operating Procedures so they become reusable team knowledge. ## Core Features & Use Cases - Categorized SOP Creation: Organizes procedures into integrations, debugging, development, and deployment categories under .agent/sops/. - Structured Templates: Generates complete SOPs with problem symptoms, root cause, step-by-step solutions, code examples, testing instructions, and troubleshooting sections. - Duplicate Detection & Indexing: Checks for existing similar SOPs, updates the Navigator index in .agent/DEVELOPMENT-README.md, and cross-links related task documents. - Use Case: After fixing a CORS proxy error, say "save this for next time" to produce .agent/sops/debugging/cors-proxy-errors.md with the full diagnosis and fix. ## Quick Start Ask the assistant to document the solution you just implemented as an SOP, for example by saying "create an SOP for the Stripe webhook setup we just finished".

Frequently Asked Questions about nav-sop

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

FAQPage Schema
How do I create a Standard Operating Procedure for a solved bug?

Invoke the skill after solving the issue by saying "document this solution" or "save this for next time". It generates a markdown SOP with symptoms, root cause, fix steps, and prevention guidance, saved under `.agent/sops/debugging/`.

What SOP categories does this documentation workflow support?

Four categories are supported: integrations for third-party service setups, debugging for common issues and solutions, development for workflows and patterns, and deployment for CI/CD and release procedures.

What happens if a similar SOP already exists?

The skill checks the target category for existing SOPs before writing. If a similar file is found, it prompts you to read the existing SOP, update it with new information, or create a separate new document.

When should I not create an SOP?

Skip SOP creation for one-off bugs with no reusable pattern, obvious solutions, or task-specific documentation. Task documentation belongs in the nav-task skill, and architecture updates belong in system docs.

Does the SOP skill require Navigator to be initialized?

Yes, it writes to the `.agent/sops/` directory structure and updates `.agent/DEVELOPMENT-README.md`. If the structure is missing, you must run the Navigator init command first.