nav-sop_skill

Overview

This skill creates Standard Operating Procedures (SOPs) from solved problems, new integrations, or established patterns so teams can reuse solutions and avoid repeating mistakes. It captures context, step-by-step solutions, code examples, tests, troubleshooting, and links into the Navigator index for discoverability. Use it when you want to save a repeatable process or make a fix reproducible for others.

How this skill works

The skill asks or infers a category (integrations, debugging, development, deployment) and a sanitized name for the SOP, checks for existing SOPs to avoid duplication, and generates a complete markdown document with context, symptoms, root cause, solution steps, examples, tests, and prevention notes. It writes the file into .agent/sops/{category}/{name}.md, updates the Navigator index, and optionally links the SOP to a related task.

When to use it

• After solving a novel or recurring issue: "save this for next time"
• When finishing a third-party integration: "document the setup"
• When defining a team workflow or pattern: "create SOP"
• When you want a reproducible, copy-paste-ready procedure for others
• When you want testing and troubleshooting steps bundled with the fix

Best practices

• Choose a specific, descriptive name (lowercase, hyphens) like stripe-payment-setup
• Pick the correct category so discoverability and structure stay consistent
• Check for similar SOPs first; update rather than duplicate when appropriate
• Include complete code examples and verification commands so others can test
• Add prevention tips and red flags to stop the issue from recurring

Example use cases

• Documenting Stripe webhook setup after successful integration
• Capturing the root cause and fix for CORS proxy errors for future debugging
• Recording the team-approved pattern for testing authenticated routes
• Creating deploy and rollback steps for a production release process