nav-soplisted

# Navigator SOP Creator Skill Create Standard Operating Procedures (SOPs) - reusable documentation for processes, integrations, debugging solutions, and workflows. ## When to Invoke Invoke this skill when the user: - Says "document this solution", "save this for next time" - Says "create SOP", "make this reusable" - Solves a novel issue and mentions "don't want to hit this again" - Sets up integration and says "document the setup" - Establishes pattern and mentions "team should follow this" **DO NOT invoke** if: - Creating task documentation (use nav-task skill) - Updating architecture docs (different purpose) - Simple bug fix with no reusable pattern ## Execution Steps ### Step 1: Determine SOP Category Ask user which category (or infer from context): **Categories**: 1. **integrations** - Third-party service setups 2. **debugging** - Common issues & solutions 3. **development** - Dev workflows, patterns 4. **deployment** - Deploy procedures, CI/CD **Examples**: - "How to set up Stripe webhooks" → `integrations/` - "Fixing CORS errors" → `debugging/` - "Testing authenticated routes" → `development/` - "Deploy to production" → `deployment/` ### Step 2: Determine SOP Name **If user provided name**: - Use their name (sanitize: lowercase, hyphens) - Example: "Stripe Payment Setup" → "stripe-payment-setup" **If no name provided**: - Generate from context: `{service}-{action}` - Example: "github-oauth-integration" - Example: "cors-proxy-errors" ### Step 3: Check if SOP